Hi,
I have installed a backup sever on Windows 2008 server. It all works fine, but when the server loses the connection to the tape drives (reboot of VTL connected through FC or something like that), the device manager removes the tape drives and don't pick them up when the tape drives are...
Hi,
I have installed a backup sever on Windows 2008 server. It all works fine, but when the server loses the connection to the tape drives (reboot of VTL connect through FC or something like that), the device manager removes the tape drives and don't pick them up when the tape drives are online...
Are you using nsr_render_log to read the log files or are you just using a text editor? Since NetWorker 7.4 you should render the log files to get them in a readable format. That's the case for all .raw log-files.
Hi,
You can get the same information from a script as you can from the GUI. If you want to know what status a group has through a script you should use nsradmin and look for the field Status under the NSR GROUP resource.
Hi,
Yes, I think testing BIGASM is a good idea. Then you will see what performance you can get from the backup device. There should really not be any trouble with aftd and remote backups. That is a very common setup, so there should be lots of people knowing if that was a limitation.
But...
If you can't start the backup from the client, you would hopefully get a better error message. But in either case, you must ensure that all aliases are set up correctly and can be reversed looked up too. You can always try hosts-files if you are using DNS, just to rule out the name lookup.
No idea. What platform are we talking about? Is the disk local, or NAS? What about the one that is working? Have you tried BIGASM to see the throughput? If not, you can have a look at the performance tuning guide. That might give you an idea.
Hi,
are you using the same script when you try to run the scheduled backup as the ad-hoc? Is the connect string the same?
Start with trying to run the same script with the root account and see that it works. If that is the case, and the scheduled still fails, have a look at your NSRNMO script.
Try NetWorker user on your client and see if you can start with a backup from there.
Also check that all your aliases for the clients are listed in the alias field.
Hi,
Can you run a manual backup from one of the clients? You can also try to run the savegrp command instead of starting it from the GUI and add -v for verbose and see if you get any clerar messags.
You can always have a look at your cisco boxes and see if there is any "tcp session timeout" you can increase. I know this is usually a problem when running backups through a PIX.
Verify that you have both the short anf long name of the backup server in the servers file.
You should not use remote user and password for regular clients, they will run under the account that started the client daemon nsrexecd. There are exemption to this of course if you are running NetWare...
Hi,
I have never seen that NW uses exclusive locks for the files during backups?! What does networker say about the backup failure? Is the save process still running so you can kill that instead of rebooting?
Hi,
you've got two choices. You can set up the cleaning on the library itself or you can let NetWorker handle it if you have CDI enabled for the tape drives. Auto clean is set up on the jukebox resource in NetWorker, but verify the CDI setting before if you will let networker handle it.
Looks like you are right 605. To bad the pass phrase is showed and stored in clear text. So you can just restore the res directory from the bootstrap and all of a sudden you have the pass phrase used for all AES backups.
So obviously, you have to be more careful with bootstrap backups than...
I don't have any personal experience of this, hopefully someone else can pop in and enlighten us!
The companies having these appliances I know about are decru, neoscale and crossroads. There are most certainly more of those, but should at least be a start.
Hi,
AES encryption was added in networker 7.3 and all encryption is done on the client side. If you only want to encrypt your clones you'll have to use a hardware encryption appliance.
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.