1 retry attempted
39077:save: error, no matching devices for save of client `networker.***.ru'; check storage nodes, devices or pools
5777:save: Cannot open save session with networker.***.ru
12578:nsrlpr: Either a printer isn't defined for printing the Bootstrap for this savegroup,
or the '-P PRINTER' part of the notification resource is absent.
Please correct as appropriate.
printing bootstrap information failed (reproduced below).
Июль 23 16:14 2008 networker.***.ru's bootstrap information Page 1
date time level ssid file record volume
22.07.2008 18:19:18 full 3414551654 0 0 Mysys-1-007
22.07.2008 18:19:18 full 3414551654 0 0 Mysys-1-007.RO
22.07.2008 18:32:47 full 3364220815 0 0 Mysys-1-007
22.07.2008 18:32:47 full 3364220815 0 0 Mysys-1-007.RO
networker.***.ru:index 1 retry attempted
networker.***.ru:index 39077:save: error, no matching devices for save of client `networker.***.ru'; check storage nodes, devices or pools
networker.***.ru:index
networker.***.ru:index 5777:save: Cannot open save session with networker.***.ru
Could you please perform following tests: 1. delete client x from resources of BackupPool pool (leave only group test) - then perform backup
if it won't work perform following test:
2. delete client x and group from resources of BackupPool pool. On the client x (instance attached to group test) definition put: save -b BackupPool in the "backup command" resource - then perform backup
Usually this happens when you configure pool which you use on remote storage node with device restriction for it and you can't mount same pool on server to write bootstrap. Check if that is your case.
Yes it is possible. In example you can create pool, let's say INDEX and at the save set selection enter: index: bootstrap Then assign this pool to NW server devices.
your networker server has to be in an active group as a client. the group can have skipped schedlue but it has to be in the active group so if you do not have a group containing your networker server just add it to some
benzino1
2 Intern
•
244 Posts
3621
0
Posted July 25th, 2008 02:00
1. delete client x from resources of BackupPool pool (leave only group test) - then perform backup
if it won't work perform following test:
2. delete client x and group from resources of BackupPool pool. On the client x (instance attached to group test) definition put: save -b BackupPool in the "backup command" resource - then perform backup