Add a "force stop" time on policies or clients
Created: 13 Dec 2012 | 3 comments
I did a bit of digging, and it looks like people may have found a way to do this via scripting which I guess I have to dig into next, but we have a couple different clients that have to have their backup jobs finished by a specific time. 99% of the time this isn't an issue, and the job is done well before this timeframe, however there are times where the backup is going slow for one reason or another, the job runs late, and unfortunatly this stops users from being able to use the application.
Even a timeout for a job or a client would work.
Thanks.
Idea Filed Under:
Comments 3 Comments • Jump to latest comment
Hi LorenL,
Well this is a good point raise , since when i define that my backup window is from x hours to y hours and i don't want backup to run beyond that time .
But netbackup doesn't work in that way , this window is applicable only for Resources and not after backup reserve a resources , I would say Symantec should come up with some option in the Host entry where we say backup stop as soon as the backup window is close.
Cheer,
Rajesh Kumar
Hi All,
Agreeing the same.
It seems as if there is a misunderstanding about backup window.
In NBU, the backup window is called a START window, meaning that you define the window during which you allow the backup to start.
Close backup window earlier to ensure that backups do not run into business hours and investigate why backups are not starting at desired 'start time'.
If Frequency based scheduling, check for possible 'schedule creeping' - explained in David Chapa's article: https://www-secure.symantec.com/connect/articles/netbackup-frequency-based-scheduling
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Would you like to reply?
Login or Register to post your comment.