A quick supplement...  I found this old press article on thie module:

http://findarticles.com/p/articles/mi_m0EIN/is_1994_Dec_19/ai_15993944/

One for the Archives... Pun intended.

Well have used it but not very freqent. Used it to archive user homedirectories when they left the firm.

Even thoug it's doable, I belive that the hard part is to name the archive in a searchable manner.

Maskerading the saveset to the project name was one that worked, in another case we used a external db to keep track or corrolate the

project with the archivedata.

You very seldom remember the servername that hosted your home directory 6 years ago.

Best regards

Håkan Engman

I have been using the NetWorker archive module - and is still using it.

I'd really appreciate some enhancements for this module as I can see we get more and more requests for such functionality.

Main problems today:

* scheduling

* error control

* monitoring

* reporting

Other:

* searchability (nsrinfo could do better)

* browseable recoveries

* tagging of archieves to maintain archives in an easy manner when clients are removed or renamed.

(an archive index, which is not related to the archiveing client itself - when client is removed/renamed)

* simple HSM functionality (some competitors have this, and the customers remind us about it)

Yep. Ah the days when Archiving was simple, and not mixed up with HSM!

Purely for the backup and delete capability with a comment.

What is an Archive? It is just that, IMNSHO. A Backup that optionally deletes the original data afterwards and has an easy way to find it. Add that to NetWorker savesets, and you can retire NetWorker archiving.

HSM? Bah! Won't work until someone creates a file system that goes to pooh because you have billions of objects which are just stubs, or you have  a single name space that can with files having moved to another device, but still look like they were where they were.

Hello Siobhan!

Long time no talk.  Thanks for all the feedback today.  We've been having a few back/forths on the archiving module again this week so your comments are timely.  There's so little chatter about NetWorker Archive in general that we tend to just let it stay as is.  HSM? Don't get us started .

BTW - are you making it to EMC World this year?

Well you don't call! I don't get any flowers... nothing! :-)

Biggest frustration on the Archive module? For archive requests we should be able to set hours when it can be automatically responded to. This should be seperated on recovers and archives. You might want to do that on the pool.

I'm trying to get there, but HP is not exactly keen on us going to EMC world. :-(

Hi Eric,

Please do not leave it as is, usage is probably a result of the functionality...

Why not combine probe backup technology with the archive module.

Application dump/export data to a directory, NetWorker archive it of the disk "automagically".

Maybe this is a lack of knowledge, but would it be possible to interface NetWorker with the Centera ?

(Directly. Change the behaviour of the NSRMMD, connect it to the Centera. SSID for the archive in

the mediadb would point to a hash in a centera.)

Cheers,

Hakan

That's a damn good idea! I actually needed the integration with Centera recently.