06-12-2009 08:50 AM
Solved! Go to Solution.
06-12-2009 09:02 AM
06-12-2009 09:02 AM
06-12-2009 10:03 AM
06-12-2009 12:46 PM
Judy is correct but there are more things that you need to keep in mind.
NetBackup is mis-named. It should be called NetRestore as the backups are only as good the ability to safely and efficintly restore data :)
1. Databases should either be shutdown for imaging or else purchase, install, configure and TEST restore the NetBackup database agents
2. Timing is critical for a server that does batch jobs or data migration. In other words make sure that the data that is supposed to be able to restore is actually there when the backup image is created.
3. Remember to use the restoration time (time to recover data) as the determining factor for creating the backup image. Too many backup admins focus on making the backup window that they miss the whole point of the image is the restore. What is the best rstore procedure?
4, Retention level MUST be set by the person that is the data owner. Determination of using 1 month or 7 years retention is their responsibility of the person that "owns" the data. Our job is to ensure we meet their retention needs when we setup the backup policy
5. Partial backups are too many times wrongly acknowledged as successfull. Here is a clue. Partials are NOT acceptable until verified as such. You must determine why the backup was only partially successful. Determine the files that were not included in the backup image and discuss it with the data owner to determine what to do with failing files.
6. Failed backups need to be identified and fixed as soon as possible.
7. TEST, TEST, TEST the restores and prove that you can recover the data as required by the data owner.
06-12-2009 12:59 PM
11-22-2009 09:46 PM
11-23-2009 03:22 AM
11-23-2009 07:19 AM