:can not start session with server ripley:bad database version

[jmdc]

Has anyone everseen this error?. I'm using legato 5.7 under win2k. I ger this error when I'm on the client trying to restore a backup. I can't get the server to back up the client. I get this error from the server. WISS error,bad database version.

-Justin

 

[Guest_imported]

Run "nsrck -F client_name" - where client_name is the name of your client - from the command line on the server. The WISS error usually means some type of corruption in the index datbase for your client_name. If you do not specify your client_name the command will run thru all your client's index db's and may take longer.

Good Luck,

 

[ukraine12]

To avoid index problems you can do the following:
when stopping legato make sure that nothing is running.
backups or clonings need to be stopped and all the drives need to be unmounted.
when this is done you can stop legato in a clean way.
When startin up again check the daemon.log wether or not index problems occur. legato will check all clientindexes and the ones with errors need to be manually repared(nsrck -F). This way you can prevent errors before actually starting your backups.

 

[Guest_imported]

has anyone seen this error on an AIX environmen:

backup failed with the following errors:

savepnpc: RPC error, Remote system error
savepnpc: Cannot open savepnpc session with hostname

I can ping , telnet, rpc, etc...between both systems.

 

[ag100]

One point.. The nsrck command in NetWorker 5 rarely catches index errors. nsrck -F will compress and fix, but I wouldn't trust the nsrck on startup too much. As an alternative, I used a script that would do a small nsrinfo on each client.. We found quite a few more bad indexes that way..

Also, NetWorker 6 uses a different client indexing scheme, that appears to be a lot more reliable.

Good luck!!