How to avoid putting weekly full backup on hold for monthly backup.
For more information on this topic, please see the Administration Module 2-Basic Operation of NetVault Backup-Web-based Training
The solution to this would be to use different Backup Selection Sets for the Monthly and Weekly backup. Often times with NetVault, you will find that the NetVault Backup Admin has used the same Backup Selection Set for his Full Weekly and Full Monthly backup. This might be overlooked because they are backing up the same server and 99% of the time, the same directories. Doing this however is where the problem would comes about. When the occassion arises where the Weekly Full and Monthly fall on the same day, one job will have to be put on hold (often the Weekly) and or there will be an Index Conflict because both backups are using the same Selection Set. To avoid this from happening, do the following:
a) Create a Weekly Full backup with a naming convention of your choosing.
Example: " Server X Full Backup_Weekly "
b) Create another backup the same way but with a different name
Example: " Server X Full Backup_Monthly "
This will enable you to not only avoid the schedule issue, but also enable you to run both jobs at the same time against the same server, depening on the number of devices.
*Often times, users will load the same Full Selection set as the Weekly Full, much like they would when they create the Incremental Backup. In many cases, you can load the same selection set, however, you have the potential to run into the issue that is being described when running into the same time slot as the job utilizing the Monthly.
