Highlighted
LTO6
1 Nickel

Obtaining media database information

Hello all,

I have encountered strange behavior when trying to clone to LTO tapes. Command I used is "nsrclone -b Name_of _ Media_pool -y "1 year" -d Storage_Node -v -S savesets".

I used around 80+ savesets and the command stopped on "Obtaining media database information on server networker_hostname" for several hours.

Clones from other media pools are working perfectly fine. I have tried also creating new media pool for these savesets ... unfortunately with the same result.

When I tried to clone less savesets (I've tried 1 SS and 4 SS), command started immediately cloning.

This has been working for months and suddenly stopped last month.

If anyone has ideas why this is happening, I would appreciate help.

Tags (3)
0 Kudos
3 Replies
bingo.1
4 Tellurium

Re: Obtaining media database information

If this has already worked and you did not make any changes to NW, this could be a temporary problem (restart NW or even the NW server himself). If this does not help, consult support.

0 Kudos
LTO6
1 Nickel

Re: Obtaining media database information

Too bad restart is not always possible Seems if this continues, I will end up creating a ticket with EMC.

0 Kudos
bdos1
1 Nickel

Re: Obtaining media database information

I had an issue similar to this before.
The resolution was to add all the Storage Nodes being used during the clone into the “Storage Nodes” field of the NetWorker Server's client properties. It needs to be above the “nsrserverhost” and 1 per line.

Strange, I know, but it worked...

If it's still not working, then add the source and destination storage nodes to the clone command and check the debug log.

# nsrclone -D9 -b Media_pool -y "1 year" -J Storage_Node_A -d Storage_Node_B -v -S savesets

0 Kudos