Unsolved
This post is more than 5 years old
27 Posts
0
4436
How to restart full backup jobs instead of level
We have some weekly full jobs that fail or do not run completely - how can we restart the jobs?
Also - it looks like the windows and linux jobs are mixed.
Is there a how to guide to walk you though creating jobs?
I would also like to break out the MS Exchange job from this schedule or big job.
Need some help.
Thanks
John
ble1
14.3K Posts
0
July 16th, 2012 17:00
When you do group restart (from GUI or from CLI) it will start backup with same level as it was running last time if within restart interval defined in group properties. If not, it will use current schedule. So, if you wish to restart full backup (which is same as starting full backup) much later when, let's say, incremental schedule takes palce, do from CLI savegrp -lfull -c . This example command will run only for with level full.
John Leonard
27 Posts
0
July 17th, 2012 09:00
Thanks for the info.
So if I want to run a full - I would type in from the command line savegrp -lfull -c windows corp
That will break the schedule to not run the level?
Please advise.,
thanks,.
ble1
14.3K Posts
1
July 17th, 2012 11:00
Not sure I understand last par of the question (well, I'm sure I do not understand it). If you run it from CLI, the level applied is controlled by -l switch (small L). you can use full, incr, or any differential level you want - depending what you wish to do. It does not matter if you have schedule set in client saying something else - schedule/level from group overrides client schedule. And savegrp command from CLI with level set will override whatever is set for level or schedule for that group in GUI.
John Leonard
27 Posts
1
July 17th, 2012 12:00
I was able to start the full backup job by typing in the following:
savegrp -l full -G "Windows Corp"
That kicked off the full backup.
I am keeping my fingers crossed.
Thanks.
-John
John Leonard
27 Posts
0
July 20th, 2012 10:00
Hrvoje,
Is there a command to kill a job?
It has been running for 72 hrs.
I need to get ready for my regular schedule.
Thanks.
-John
ble1
14.3K Posts
0
July 20th, 2012 12:00
In NW8 you can kill individual jobs. In NW7 you can abort it with jobkill command, but I never used that for jobs - only for groups. You can stop your group (kill it) and that will do the job. Depending what NW version you run, you can also use hard limit setting to build window frontier within which group can run.
mridul_singh
57 Posts
0
July 23rd, 2012 19:00
You can kill a job by killing the savegrp process assocaited with it.
Otherwise you can use jobkill to kill individual save jobs.
To restart the backup at the same level, either use the NMC console or from the coomand line with option -R. for eg. if "Windows Corp" backup failed and you wish to restart it at the same level use
savegrp -vv -R "Windows Corp"
ble1
14.3K Posts
0
July 24th, 2012 04:00
Bare in mind that, as in example above, -R won't restart since you are doing it after restart interval since it is running for few days already thus original schedule most likely won't match the day when it is started.