UNSOLVED
Storage node affinity for nsrachive
So I am trying to use networker as a viable archive solution, to reduce backup times. And financial challenges, means I have to look at what I've got to make it work.
The Idea was to create a single storage node, and let it handle the various archive requests, thereby cutting down on the number of devices I would need for archive. but I cant for the life of me get it to work.
I put in the archive SN in the storage node field, but still it wants the archive pool mounted on the SN used for backups.
Is what I am doing impossible in NW7.6.2 ?
if it is, then ARGH, and why dont nsrachive support -J as the save command does...
Yes i could make a device on each SN, but it will give me so many devices i need to keep track of. 1 central SN should do fine for archive purposes...
362
0
Posted September 12th, 2011 23:00
That would work, just testet it.
But it does mean having to change all clients save operations field - sigh
Maybe I just apply for the money for the archive software
Although I prefer integrated solutions, and while archive is not backup, its part of the same corner of the shop. Come on EMC, nsrachive needs a boost, u still pay for it...
Or give me an Archive node field ?
ble1
6 Operator
•
14354 Posts
•
56186 Points
362
1
Posted September 12th, 2011 08:00
To my best knowledge nsrarchive hasn't been touched for quite some times by dev team as most of the time this is handled by archiving software, but I can see your pain. NW storage node allocation comes from sn list for client so if 1st listing is backup storage node then archiving job will use that one too. Eventually, you could try to place archive storage node as first in the list and for backup jobs use -J option in backup command (never tested this though). I agree that adding -J option for nsrarchive would be the way to go.