The tip from PGPhantom was first rate. I now have a single policy for each type of backup I do (NT Servers, Exchange, SQL, etc.) Under each policy are just two schedules--one for full backups on Friday, one for incrementals Monday-Thursday. Window and frequency are set appropriately. Then...
Yeah--but NBU cannot do SIMPLE scheduling and SIMPLE tape separation and that is a massive drawback, given the price. My original comment stands--there appears to be little use for a frequency of more than 24 hours and something like 5 weeks, which would appear to be an answer, is not. And I...
That is a very interesting idea--I was not aware that the volume pool assigned to the policy could be changed from the command line. Your earlier tip about changing the frequency was another piece of the puzzle. It means that I can simply create a policy with just two jobs--full which runs...
It strikes me that the term "expired" is misunderstood by the original writer. In fact, NBU will only use a tape on which the images HAVE expired. In 4.5, once all images on the tape have expired, the tape goes back into the Scratch pool from which other volume pools are fed. So you...
I sort of follow your reasoning and I will puzzle it out completely at lunch, plus I have sent it on to our installation contractor, but there is something else going on here. I need a frequency of five weeks because I want to have five sets of tapes which means that I can separate my backups...
Environment: Multiple WIN2K servers as clients
Single backup server running NetBackup 4.5
(with all known patches applied)
Created a policy with five jobs contained in it.
Friday: Full backup written to a specified volume pool
Monday: Cumulative incremental...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.