Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unsuccessful backups

Status
Not open for further replies.

COTLG

Technical User
Apr 15, 2003
107
US
Hi,

I get these failed backup messages and unsynchronized client clock detected after backup of some NT clients. How do I resolve them?



savegrp: xxx:index index was never started

--- Unsuccessful Save Sets ---

* client3:E:\ aborted



--- Unsuccessful Save Sets ---

* client1:index 5 retries attempted
* client1:index Connection refused

* client2:index 5 retries attempted
* client2:index Connection refused

AND

--- Successful Save Sets ---

* clien4:C:\ Warning: unsynchronized client clock detected
client4: C:\ level=full, 325 MB 01:04:41 4324 files


 
"unsynchronized client clock detected" is just a warnig message, your server and client have a small date/time difference (I think more than 3 minutes).

The aborted message is sometime due to backup stopped bu the administrator. In your case it must (maybe) be caused by a timeout.
 
Hi,

I shut down legato, renamed the client index files, started Legato and ran nsrck -L7 for all the clients. I got this sort of message after the next backup ran. Please how do I resolve this?

--- Unsuccessful Save Sets ---

* client1:index 1 retry attempted
* client1:index usage: save [<options>] [path ...]
* client1:index
* client1:index options: [-BEiLnqvx] [-s server] [-c client-name] [-N name] [-e expiration]
* client1:index [-f dirfile] [-b pool] [-F file] [-I input file] [-g group]
* client1:index [-l level] [-t date] [-m masquerade] [-W width]

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top