08-10-2009 04:13 PM
08-10-2009 04:47 PM
If you use vault, NetBackup will try to do the same routine on the fixed schedule.
Good in ongoing maintenance perspective.
And vault will give you good book-keeping insight on the tapes onsite and offsite.
Bad (not desirable) to run un-necessary tasks if there's plenty of space left on disk - vault will not check if the disk array needs to be dup-emptied or not, it will just run when it's due to run.
And if some error condition occurs with vault, you will need to spend time to fix it while all that might have been un-necessary from the first place.
Unless customer's requirement says all overnight backups to be sent offsite the following morning, DSSU is more flexible in utilizing tape resource, I think.
One nice thing about DSSU is that the restores can be much faster - if configured properly, even after the backup images have been duplicated to tape, sometimes you would not need to mount the tape at all.
You can mix-n-match DSSU (duplication) and vault (offsiting) for the optimal efficiency, if you already have vault license in your hands.
48TB ... I'd try to utilize the disk as much as possible, while ensuring backup images are properly protected on tape too.
A
08-10-2009 11:55 PM
Recently we found one problem with master server installed at the box with T2 processor: EMM database is a single-thread app and this can lead to unwanted bottlenecks, so if you are planning to perform a lot of backups - it's better to use some X-series Sun boxes for it (because each single thread at T2 processor is quite slow comparing to Intels and AMDs).
08-11-2009 12:00 AM