Search results for query: *

Hi, You should definitely try to fix this. Earlier versions of Networker wouldn't save if the clocks were too far out of sync. The problem is that the system clocks are not close enough on the server and the clients. This has implications for differential and incr. backups, which rely on...

Hi, Hold your horses here... you shouldn't need to go for a full DR. Run nsrck -F on the server index multiple times until you can run nsrinfo on it reliably. Then do the same for the client indexes, with troubles. You need to think why you actually need to have a complete server file index...

Hi, BIG WARNING HERE!!!! this is definetly anti-social behavior towards networker and it may well crash it / cause index corruption. YMMV kill off the nsrmmd process that has the drive locked. On Solaris I do this using fuser -k /dev/rmt/Xcbn. Regards, Simon.

Hi, You don't state whether you have an Offsite facility. I'll assume not. The is the easiest way of doing it is to do the backups in an offsite location. You then get decent DR. If you have enough data this may work out cheaper in media. The cloning process is very inefficient so we tried to...

Hi, This should not be a problem, if you are using hostnames not IPs. If you are renaming the clients then you have a problem. You have to add a new client because you cannot rename one easily. This means a full backup as well the first time it is run. Don't worry about deleting the clients...