mech_tech wrote:Latest Version of NovaBackup. I have created a backup set for a week rotation. Friday is a full backup the rest of the week days are incremental backups. I have setup a schedule to run these days 3 times now and the program keeps "loosing" them. where is this schedule stored?
What do you mean "losing them"? Do you mean the output NBD datasets you expect are not produced?
Assuming you're running in Advanced mode (set from the Home page), the LOGS tab will show you the output of each job that ran. You can specify "detail" in the Notification setup of Settings for the job, to see each folder/file backed up.
And the SCHEDULE tab shows the last run date and the next scheduled run date.
And the RESTORE tab shows each "disk backups" with an entry for each backup job that created an NBD output.
The target folder (specified in the "Backup to..." item at the bottom-left of the job definition) shows where the output NBD goes, and what the "media name" (i.e. file name) should be in that folder.
If you use the same job run each of the 6 days, then the only way you'll get unique output NBD datasets each day is if you specify "append" in the "write mode" of Settings for the job. This will cause a date/time suffix to be appended to the file name you specified in the "media name" of the "Backup to...". Each time this job runs, a brand new named output NBD dataset will be created, producing an ever-growing accumulation of such NBD datasets. You will have to "prune" them yourself, deleting them manually when you no longer want them. And you will also have to "prune" the XML media definitions for those output NBD datasets, by going to the RESTORE tab and selecting each "disk backup" and deleting it (corresponding to each NBD dataset you've deleted).
If instead you want every week's 6 incremental backups to rotate over themselves, replacing last week's incremental NBD with this weeks version, then you want to use "overwrite" in the "write mode" but that means you also need to have six separate jobs, scheduled weekly on each of those 6 days of the week. And each of the six unique jobs (for each day of the week) will also have to have a unique "media name" for its output NBD dataset. But this way you will simply have 6 incremental NBD datasets and they'll just keep overlaying the prior week's version with this week's version as time marches on. Thus you don't have to manually "prune" either the NBD datasets in the target folder, nor the XML media definitions. They will all just keep overlaying themselves and you'll only have 6 versions of both objects.
You could apply the same concepts to your Friday FULL backup. If you only wanted 7-days worth of total backup, then you could use "overwrite" for the Friday job. But if you wanted an ever-growing collection of individual weekly Friday NBD datasets, you should specify "append"... which again, would require manual "pruning" if you eventually wanted to delete the oldest objects.
So... exactly what has been "lost", that you expect to see but can't see? Friday FULL backup? Or the other mid-week incrementals? And exactly which piece of the output objects do you feel is missing?
Have you scheduled your repeating jobs as follows: