Index backup from storage node

[mgdaviso]

Hi, been a while since I posted on here, but here you go:

I have just installed a new storage node on a remote site.

it is succesfully backing up 8 clients on a LTO2 device.

The index information comes across our private WAN to our main backup server.

My savegroups are set to automatically clone.

The backup server uses IBM 3590 drives (not the issue)

herein lies the problem:
When the remote clients have finished backing up and cloning, the backup group WAITS until both of my IBM 3590 drives are free to backup the indexes on the server.

is there any way I can make the indexes for these remote clients back up to the LTO2 device instead of the 3590, so my savegroups are not hanging around for ages waiting for free tapes?

TIA

Mike davison
mike.davison@avon.com

 

[NWNinja]

This is from Legato´s Knowledge base, but i have never done this myself:

---------------------------------------------
How to configure NetWorker to send client data to a storage node

First of all, make sure the Storage Node is at the NetWorker version as the server. Please see Compatibility Guides

1. Edit each client in the groups that you want to write to a storage node

a. In NetWorker Administrator, select manage clients
b. Edit the client
c. Click on the Preferences tab.
d. In the Storage node field enter the name of the storage node above nsrserverhost. The field should look like this:

storagenode_name
nsrserverhost

e. Click ok to apply the changes.
f. Do this for each client in these groups.

2. Edit all of the pools that have been created for these groups and change the setup to restrict the devices to be used.

a. Click on Mange Pools.
b. Edit one of the pools.
In the devices field put check marks beside the rd devices, leaving \\.\tape0\ & \\.\tape1 etc unchecked.
c. Click on ok to save the changes
d. Do this for each pool.


To direct index saves to the storage node,edit the client configuation for the NetWorker server, click on the preferences tab and added the storage node name to the storage node field so it looks like this:

nsrserverhost
storagenode_name

NOTE: Bootstrap backups will require backup to a local device
Note 2: Verify that servers file in storage node has the server's short and long name listed appropriately .
------------------------------------------------------

Hope it helps!

Cheers!
Maverick

 

[mgdaviso]

I'll try that out - thanks.

Mike davison
mike.davison@avon.com

 

[surfrat6]

Mike,
Did that work for you? I am looking to implement a similar solution.

Just curious, before I try it myself.

Thanks!

 

[mgdaviso]

Yes it worked, but our WAN wasn't beefy enough to take the index backup, so we had to back the change out. So, yes this does work, but make sure your WAN can take it!

Thanks maverick

Mike davison
mike.davison@avon.com