Issue with NTBackup Used On a Network
Hello, I have what I would classify as a multi-layered issue so I'm not sure where to post it. If it's in the wrong place, I apologize in advance. I work for a small IT department that services a domain of approximately 100 PC's, of these 100 I need about 15 (manager and supervisor machines) to produce backups to a location on our backup server. While I am very aware of the benefits that "real" backup software such as Backup Exec would offer us, it simply is not within our budget to make such a purchase. For years, with varying degrees of success, we have been using NTBackup as a way to meet our need to create backups for these off-site computers but because it randomly stops working and with the users never checking to ensure if it worked or not, we really need to shore things up so the backup is working when it's scheduled to do so. Presently, the machines causing us the issues are off-site from our domain controller but are a part of our network and can be accessed directly via UNC paths to shares but do not show up in our Microsoft Windows Network hierarchy. NTBackup is locally configured to back up all of their My Documents files to a mapped drive that points to our Backup server (A Lacie box) using the user's local pc logon credentials. While this process is working to some degree at these locations, it is creating very, very small backup files - to the tune of < 30Kb - yet shows it ran successfully. Since on any given machine, my backup files should be around 50MB in size, there's obviously an issue with this. We were having a problem previously with NTBackup failing to run after restarts due to the Mapped Drive connection showing it was connected, but when trying to access it, it still prompted for credentials. I have since started using the following command in the form of a batch file at startup: net use x: "\\servername\share" /persistent:no /user:username password" And this appears to have resolved that component of the problem. We are using Windows XP on all of these PC's and it seems as though the program is running successfully yet not capturing all of the data we need for the backup. Any help or thoughts as to why this process seems to be dropping the ball would be greatly appreciated. Thanks, Gabe1 person needs an answerI do too
April 2nd, 2010 7:48pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics