Networker

Re: [Networker] savegrp -O

2008-06-12 04:29:15
Subject: Re: [Networker] savegrp -O
From: Davina Treiber <Davina.Treiber AT PEEVRO.CO DOT UK>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 12 Jun 2008 09:25:13 +0100
MIchael Leone wrote:

My NetWorker server is down, at the moment, while a tape library is being repaired. But I have jobs that save to disk (disk space on my SAN), and from there clone onto tape. This is all done in the job configurations, and it all Just Happens. There is no need for me to manually clone data from saved disk to tape; NetWorker does it all.

In simple environments, the automatic cloning as part of a group may be sufficient. However when an environment becomes more complex, a scripted solution to handle cloning is usually more reliable, more controllable, and more flexible. Below are some examples where a scripted solution is superior to automatic cloning.

If you have multiple savegroups which all require cloning, you may not want to run the cloning as soon as the backups have completed, since you may not want to tie up tape drives that are still required for other backups.

If automatic cloning fails for any reason, you may not easily know which save sets did not get cloned. Also a failure of cloning does not cause the group to fail so you may not be aware of the failure.

You may choose a solution where save sets are cloned to different pools depending on level, automatic cloning could not do this.

If you have a lot of tape drives available, you may want to run multiple cloning sessions to optimise drive usage. This leads to some scripting challenges but can be done.

There are probably other good examples.

You say that NetWorker "does it all", well I wouldn't quite agree, but what it does do that some rivals don't is to provide you with the hooks and tools to fill in the gaps in the way that you want.

I suppose that hundreds of NetWorker users have written cloning scripts (I have probably written a dozen or so variants myself over the years), and some might say this is something that the product should do better natively. However, cloning requirements vary widely for different users and it would be hard to meet all those needs with a single product.

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>