UNSOLVED
Restarting an NDMP Grp
Hi,
I had some failures on our NAS box this morning, (backing up via NDMP), but when I restarted the job, expecting the failed directories only to back up, ALL the savesets are now queued for back up.
I restarted the grp via cmd line (savegrp -R ). NW ver is 7.4 build 187
Is this normal behaviour ?
Is it possible to only specify the failed directories ?
Tks,
Liam
I had some failures on our NAS box this morning, (backing up via NDMP), but when I restarted the job, expecting the failed directories only to back up, ALL the savesets are now queued for back up.
I restarted the grp via cmd line (savegrp -R ). NW ver is 7.4 build 187
Is this normal behaviour ?
Is it possible to only specify the failed directories ?
Tks,
Liam
- If you restart a group, it will not backup only the
save sets which got completed during the previous
backup job. If ny saveset was incomplete at the time
of group failure, Networker will backup the entire
save set again.
This is not entirely correct as it depends on restart window interval. DavidHampson
2 Intern
•
1080 Posts
632
1
Posted June 9th, 2009 07:00
Go to configuration; groups, select group, right click properties, advanced. Check the field Restart window which by default is 12 hours - it means if you restart more than this time later then it will treat the run as a completely new run of the group. You may want to set this to a different value - if you always want a restart to be a restart set it to 24:00Check the field Restart window which by default is 12 hours - it means if you restart more than this time later then it will treat the run as a completely new run of the group. You may want to set this to a different value - if you always want a restart to be a restart set it to 24:00 I really wish there was some way to suppress this behaviour. It's simply not backwards compatible with the pre-7.3 notion of restarting a group.
In the environment here in most cases it's the worst possible default action. When someone helpfully restarts a failed group only to have several terabytes of pointless backup activity take place for the sake of a couple of failed savesets.
I'd rather it just fail and say why rather than do something I didn't ask for.
If only you could set the restart interval to 0 and disable it, or even to set it arbitrarily high would be fine, better than the manual hacking around required to perform a restart in the manner which used to 'just work'.
Jason.
Anandkrishna
36 Posts
632
0
Posted July 23rd, 2010 07:00
I completely agree with David. And this holds true for all the backup groups not just NDMP.
amediratta
2 Intern
•
2014 Posts
632
0
Posted June 9th, 2009 03:00