"Cancel & Save" Backup Cancel Option
We would like to have an option in NetBackup to "keep" (Cancel & Save) whatever has backed up to the point in time where we need to Cancel jobs for maintenance or other reasons.
Currenlty when you cancel a job you loose all that has been backed up on that job. If I have a slow running job and it has run for 3 days and has backed up 4+ TB and I need to emergency patch a server, I would like for the "Cancel & Save" to take a current checkpoint at the end of the last file backed up, then go clear Archive bits (Full and Diff backups) on the files that did get backed up, then end the job (preferrably with a new exit code - I suppose a Status 1 will work...but could be confusing).
I know Checkpoints and Suspend give me similar capabilities, but it is not alway desirabe to resume a job...but more desirable to wait for the next window.
This would not be an approriate feature for all backup types or backup purposes (like maybe agent backups or system recovery backups). But for simple file level backups where the the restores requests are generally a few files or folders, it is desirable to at least get something if we can't get the whole backup...and it is already on the media and cataloged....just give me the option to keep it.
Comments
This is already there...in a sense
If your policy is using Checkpoint Restart, and marking its progress every 15 minutes (default), then by 'pausing' the job (instead of cancel), and then restarting it later, you will restart at the last checkpoint (which is a point in time within the last 15 minutes). The minimum time period you can set is 5 minutes.
This feature is supported with some types of backups, like file and folder style backups. It is not supported with some backup types, like databases, for data consistency reasons.
Principal Learning Consultant with Symantec Education Course Development
Not quite the same...
With Checkpoint, you must resume the job and complete the job in order to have any of the the data be restorable. I'm asking to be able to stop that job and have whatever has been backed up to that point be restorable without resuming and completing the job later.
Sometimes getting part of the data backed-up is better than having a job run for a long period of time and not getting anything.
Agree with proposal
In fact this is the standard behaviour with some competitors products
Would you like to reply?
Login or Register to post your comment.