Please tell us about your configuration, it's difficult to help you with so few information...
Networker version? OS? How many drives? how many pools? Storage node? Check mounts/unmounts in your logs
Hello,
this error "Unable to extract resource info for client" usually comes from incorrect alias. Check client resource for both nodes and cluster logical name.
Networker volume manager maintains some usefull counters which can help you:
mminfo -q pool=MYPOOL -r volume,mounts,recycled,olabel
This command will give you the number of times the read-label function was performed, the number of times the volume was relabeled and the first time the volume...
If you want to do a directed recover: yes it is possible, but you have to set the "remote access" in client resource.
If you want to recover X and rename it Z: yes it is possible, but you will need to use the "force" option.
What do you mean "with 10bd"?
Do you mean "start/stop Networker service" (why??) or "start/stop Networker backup"
First case patrikjelinko had replied, but if you want to start/stop all backups, you can use Networker Groups from Networker server.
2 ways to do that:
- If you use the internal Networker scheduler, you can analyse the result of the nsradmin request, but it's more difficult:
show status;completion;last start
print name:MYGROUP; type:NSR group
quit
- The best way for me is that the scheduler itself submit the savegrp...
Please tell us which Networker version do you use?
Check name resolution ping\nslookup (DNS error?)
Check aliases for this client (Edit client \ Preferences)
Is it possible to reduce I/O when a Networker save is running? Using savegroup priority is not a solution.
Networker client 7.2:AIX5.3/oracle
The problem occurs when a save is running late, and Oracle need I/O performance;
We accept to slow down a Networker save, to keep good performance for...
We use Networker to backup Active Directory, and we were able to recover sucessfully. Read carfully Adm'Guide, and test it before; it works.
To my knowledge it's not possible to export SYSTEM STATE as data, it must be recovered by a Networker client.
True, you can disable Networker cleaning :
Edit Autochanger \ Preferences \ Auto Clean= NO
But the usual choice is to let Networker manage the cleanings (and disable the internal library autoclean option), because Networker "knows" when the clean is necessary, and because Networker will tell...
- Remove username and password from client resource
- if the restore result is still error, use an admin acount on the client system
- check that this acount is listed in "Set Up Server/Administrator" from Networker administator
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.