We have a NT Client and its SaveSet is very very long >255 characters
The Networker Server won't backup this directory.
Is there a solution for this? Or maybe a workaround?
Hi all,
we want to move our networker server from our solaris system to a hpux system, then we want to migrate the storage nodes (alsso from solaris) to our hpux systems.The hostnames will change for the networker server and also for the storage nodes. So what would be the best way to do this...
You can even use scanner to recover files while NetWorker server is NOT running.
Try this:
##########
scanner -S ssid /dirA/dirB |uasm -rv
This will only extract the given Saveset...and therefor it should not take so long time.
Good luck!
Elif
Hi,
the best would be to update to a newer version of NetWorker.
What is your Networker server? HP-UX or W2k...
Sometimes there are network problems, NetWorker keeps some tcp connections open and in the case of an error it forgets to close them.
So also check for open tcp connections.
Good...
You can use other tools for saveing networker index. I do this occasional.
Do someting like this :
####################
DBDIR=/nsr/index/nw_server
SVDIR=/tmp_exp/networker
/opt/networker/bin/nsrck -Fq
pwd=`pwd`
status=`echo $?`
if test $status -eq 0
then
tar pcvf...
I think it's a Exchange problem. Some folks which use other Backup products have sometimes similar appearances.
At Microsoft Site I found a thread for this, which may explain the problem and solution.
It includes an HOTFIX for Exchange.
But until now we haven't the hotfix...it takes some time...
You can do this via the GUI too. First you have to look for versions. In the GUI, you can find a menu called "View".
There is the "change browse time" button and the versions.
Now you get a list of different backup versions and its backup time. Use this time to change your...
Did you enter in the backup command field :"save -c <share_name or virt.server> ????
What did you do with the "old" index files after you upgraded from nt to win2k. Possible you have to rename the old client-indexes and create new one for the win2k-servers.
I have a backup problem with our Exchange backup. Our networker server is NetWorker 6.1.1.Build.238 an our nt client is 6.0.1.Build.174. We use exchange modul 2.0.
Since some time I get this strange notification in the savegroup completion:
* server00:MSEXCH:DS HrBackupPrepare: unknown error 0...
Have a look!
I had a problem similar to this and I tried this
1. stop all running groups and eject the tapes from the drives
nsrjb -vvvEH
2. stop networker damons
/sbin/init.d/networker stop
3. nsrck -F
4. start networker damons
/sbin/init.d/networker start
5. wait 2-5 minutes
6. nsrck...
Maybe the wrong volume was loaded:
You can check this with the following steps:
1 - Load the tape without reading the label:
nsrjb -ln -S xx -f /dev/rmt/3mnb
2 - Read the actual volume id by using:
scanner -v
This shows the volume id = abcd
You do not have to wait for scanner...
You can check the number of licenses you usw with nsrlic or nsrlic -v .
There you see which clients are connected and which OS they have.
And at the end you have to buy some client connection license.
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.