tombozzo
asked on
Veritas: Overwrite / Append Periods Scenario - Question inside
good afternoon all,
I am trying to correctly configure the following scenario using Veritas BackupExec 8.6:
Nightly backups-to-disk, running at 12:30 AM on Tu, Wed, Thur, Fri, Sat of our Information Store and primary network file share. I've got the job configured just fine but the issue i am running into (i think) is with the overwrite/append periods.
Ideally, I would like it so backupexec is saving the last five days worth of nightly backups but overwrites as it reaches the following week so that there is only ONE bkf file at all times (due to storage restrictions on the server).
Currently, it backs up to the same bkf for a week but then moves to create a new backup file without overwriting the first. Not sure why, but my guess is that i am not getting something right with my understanding of the overwrite / append periods. Also, I do have it set for the job to append but overwrite if no appendable media is found.
Can anyone offer some advice on how I should set the period lengths for what I am trying to achieve?
thanks in advance,
Tom
I am trying to correctly configure the following scenario using Veritas BackupExec 8.6:
Nightly backups-to-disk, running at 12:30 AM on Tu, Wed, Thur, Fri, Sat of our Information Store and primary network file share. I've got the job configured just fine but the issue i am running into (i think) is with the overwrite/append periods.
Ideally, I would like it so backupexec is saving the last five days worth of nightly backups but overwrites as it reaches the following week so that there is only ONE bkf file at all times (due to storage restrictions on the server).
Currently, it backs up to the same bkf for a week but then moves to create a new backup file without overwriting the first. Not sure why, but my guess is that i am not getting something right with my understanding of the overwrite / append periods. Also, I do have it set for the job to append but overwrite if no appendable media is found.
Can anyone offer some advice on how I should set the period lengths for what I am trying to achieve?
thanks in advance,
Tom
simsjrg
You have to set the Overwrite Protection on the Media Set for the desired time (5 days) and set the Job to Overwrite Media. When the job kicks off if will the the media in that set cannot be overwritten (yet) and creates a new file. The job will try this every day until the media expires and can overwritten and on this day the job will overwrite the media.
Wow sorry for the typos:
Corrected:
You have to set the Overwrite Protection on the Media Set for the desired time (5 days) and set the Job to Overwrite Media. When the job kicks off it will see that the media in that set cannot be overwritten (yet) and creates a new file. The job will try this every day until the media expires and can overwritten… on this day the job will overwrite the media.
Corrected:
You have to set the Overwrite Protection on the Media Set for the desired time (5 days) and set the Job to Overwrite Media. When the job kicks off it will see that the media in that set cannot be overwritten (yet) and creates a new file. The job will try this every day until the media expires and can overwritten… on this day the job will overwrite the media.
ASKER
Thanks, simsjrg, but it sounds like what you are saying is that after one week of backups then the first time the job is run the next week it will completely overwrite the previous week's data - am I right?
If possible, i'd like to have it so that it is always keeping five days of backups going back but still retaining this info to one BKF file.
Is this possible?
If possible, i'd like to have it so that it is always keeping five days of backups going back but still retaining this info to one BKF file.
Is this possible?
You can set the Overwrite Protection in Hours/Days/Week/Year/Infin
Now backing these up into one file to my knowledge can not be done. Backup to Disk files are only 1 GB each and each time one fills up another is created.
Now backing these up into one file to my knowledge can not be done. Backup to Disk files are only 1 GB each and each time one fills up another is created.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The timer starts when the backup finishes so if you set 5 days overwrite protect the tape will not be available overwrite until 5 days plus the backup time. So as a rule of thumb you subtract one day from what your rotation is, i.e. a 14 day rotation has an overwrite protection of 13 days.
> rindi very valid point. I don't know why I assumed he was backing up to disk. I was just commenting because we run a 12pm backup of our Exchange IS every day and keep 3 days on the disk even though we run a full backup to tape every night. How I have the job setup is exactly how I have it explained and it works just fine for me.
> The timer starts when the backup finishes so if you set 5 days overwrite protect the tape will not be available overwrite until 5 days plus the backup time. So as a rule of thumb you subtract one day from what your rotation is, i.e. a 14 day rotation has an overwrite protection of 13 days.
Correct. I left that out. Thank you!
> The timer starts when the backup finishes so if you set 5 days overwrite protect the tape will not be available overwrite until 5 days plus the backup time. So as a rule of thumb you subtract one day from what your rotation is, i.e. a 14 day rotation has an overwrite protection of 13 days.
Correct. I left that out. Thank you!
He is backing up to disk, but because the software was built for tapes historically, it will act the same. Overwrite and append contradict each other. At least as long as the backup consists of one tape or one file.