Microsoft's Lovely NTBackup application...
-
Just like MS to produce a high-quality product. I recently migrated all 5 of my Win32 home systems DLP Tape backups via NTBackup and shared drives to BackupPC[^] (which is pretty sweet, BTW). However, my primary Dev system started developing hard-drive trouble during the migration. This was not really noticed until a few days later (SMART monitoring was disabled). As a result, BackupPC has incomplete backups and the last full backup is one of the NTBackup backups (~22GB)...
**WHICH NTBACKUP WILL NOT ****ING READ!!!**It complains that the file contains invalid data. Transfer logs show no errors, filesystems show no errors... So I am now going through the file a-file-at-a-time using some open source code trying to recover stuff. Add to that the fact that the tool seems to bail on certain entries that I have to skip over and/or add code to get around just makes things even more fun... (Yes, I had NTBackup verify the data after each backup, and the copy on the shared drive and the tape are identical.) Gotta love a product that cannot round-trip its own data files... OK - rant done... (Just a bad week last week, is all...) Peace!-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
Just like MS to produce a high-quality product. I recently migrated all 5 of my Win32 home systems DLP Tape backups via NTBackup and shared drives to BackupPC[^] (which is pretty sweet, BTW). However, my primary Dev system started developing hard-drive trouble during the migration. This was not really noticed until a few days later (SMART monitoring was disabled). As a result, BackupPC has incomplete backups and the last full backup is one of the NTBackup backups (~22GB)...
**WHICH NTBACKUP WILL NOT ****ING READ!!!**It complains that the file contains invalid data. Transfer logs show no errors, filesystems show no errors... So I am now going through the file a-file-at-a-time using some open source code trying to recover stuff. Add to that the fact that the tool seems to bail on certain entries that I have to skip over and/or add code to get around just makes things even more fun... (Yes, I had NTBackup verify the data after each backup, and the copy on the shared drive and the tape are identical.) Gotta love a product that cannot round-trip its own data files... OK - rant done... (Just a bad week last week, is all...) Peace!-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesFor what it is worth, although bundled with the operating system, this is a just an old version/feature reduced of Veritas Backup Executive so its not that Microsoft wrote this code.
John
-
For what it is worth, although bundled with the operating system, this is a just an old version/feature reduced of Veritas Backup Executive so its not that Microsoft wrote this code.
John
It comes packaged with the OS and it's got their name in the version information. From my point of view, it's their responsibility to make it work. It doesn't matter a rat's ass where they got the code. That said, I would never use Windows Backup. It's overly complicated. Recovering single files is difficult and extremely slow. It stores too much meta-data about the backup separately from the backup data, often rendering the backup data itself useless. Its worst attribute (as mentioned in the original post), is that it will create backups that it claims have been 'verified' and are 'error-free', yet are unrecoverable.
Software Zen:
delete this;