Should be a connectivity issue with this client. Is this a fresh install?
If your client initiated backups work, check to ensure your hosts files are updated on server as well as client. Update aliases & Server Network Interface for the client resource.
Job is restarted because it fails and it fails because client doesn't send anything backup thus hitting inactivity. Do you get FS01 failing only for this saveset or any saveset from that machine would do the same?
If it happens on all savesets you had for machine it is probably machine related rather than saveset. Did you test rpcinfo and nsradmin communication in both directions.
And if this occour just for one of the save sets? This is happening with me, and the other save sets is backuped without problems. Then this save set is restarted for 5 times and then is marked as failed.
What saveset is that? If system one it could be corruption. If using VSS it could faulty writer. If file system, it could be spot of disk being corrupted. If clustered system, it could be ownership/permission. And so on...
Try running the save group from the command line with verbose logging enabled and see what the logs are reporting -
savegrp -vvv
(That is 3x v )
Reading through the log may give you more help, if this is a large backup save group then you may have to redirect the output to a file then read the file rather than letting the text scroll.
This is might be the issue of consistent network connectivity. As the backup job get aborted after some time or after taking some GB backup. There is some default setting of network connectivity on the server or client sometimes its very low. It should be minimum 4 to 6 hours . So as we start the backup the job get aborted after sometime and restart again because of inconsistency in the network. By increasing the connectivity time period to 4 to 6 hours may resolve the issue
amediratta
2 Intern
•
2K Posts
0
August 16th, 2007 12:00
If your client initiated backups work, check to ensure your hosts files are updated on server as well as client. Update aliases & Server Network Interface for the client resource.
ble1
4 Operator
•
14.4K Posts
0
August 16th, 2007 15:00
GWJr
2 Posts
0
August 17th, 2007 05:00
It is happening for all 3 savesets for the same machine.
ble1
4 Operator
•
14.4K Posts
0
August 17th, 2007 06:00
If it happens on all savesets you had for machine it is probably machine related rather than saveset. Did you test rpcinfo and nsradmin communication in both directions.
jmarcos2
2 Posts
0
April 30th, 2008 05:00
And if this occour just for one of the save sets? This is happening with me, and the other save sets is backuped without problems. Then this save set is restarted for 5 times and then is marked as failed.
Tks,
ble1
4 Operator
•
14.4K Posts
0
April 30th, 2008 13:00
IKP1
198 Posts
0
April 30th, 2008 23:00
Try running the save group from the command line with verbose logging enabled and see what the logs are reporting -
savegrp -vvv
(That is 3x v )
Reading through the log may give you more help, if this is a large backup save group then you may have to redirect the output to a file then read the file rather than letting the text scroll.
IKP
Biku1
42 Posts
0
May 27th, 2008 04:00
This is might be the issue of consistent network connectivity. As the backup job get aborted after some time or after taking some GB backup. There is some default setting of network connectivity on the server or client sometimes its very low. It should be minimum 4 to 6 hours . So as we start the backup the job get aborted after sometime and restart again because of inconsistency in the network. By increasing the connectivity time period to 4 to 6 hours may resolve the issue