Backup Central

NW 7.6.2, running on Win 2003 SP2. I have a number of storage nodes with
AFTD devices. I want to run a manual clone job from NMC (i.e., go to MEDIA
tab; SAVE SETS; choose my client and date range; highlight the returned
savesets ; right click and say CLONE). This works to clone the savesets,
but they clone only onto one tape at a time. Is there a way to have a
manual clone job like this clone to more than one tape at a time? I know
there didn't used to be, but somehow I was under the impression that 7.6.x
could do it. But I'm not finding out how, so I may be wrong.

Anyone know definitely? If yes, any pointers to what I would need to
change?

(These are big savesets, and I'd like to cut down the clone time by using
multiple tapes simultaneously)

--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone < at > pha.phila.gov>


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Concerning big save sets: NW needs to keep track about the 'segment's location and sequence. It is not possible to spread a single save set's data over multiple media simultaneously. This is obvious as NetWorker could theoretically split such save set and start with 'segment_x' on tape_2. However, it would not know in advance whether all data up to 'segment_x-1' would be successfully written on tape_1.

I am pretty sure that NetWorker can not even spread multiple small save sets from the GUI to different media. But it might do so if the other parameters fit as well (small Target Session value for the tape drives etc).

Best practice i would use is to run multiple nsrclone commands/scripts for this purpose.
Using the command line you can of course also clone directly to multiple clone pools which the GUI does not offer you (unfortunately this is rarely an option).

If your backup command has saveset=all, then the short answer for the
cloning of same to my knowledge is "no."

If you are looking for a long term solution that involves splitting the
backup, I believe the closest you can come is determine backup size of
your data directories and setup separate backups/clones of the same host
splitting it up by directory level. DPA can help you plan this or if you
do not have DPA you can manually figure this out using mminfo commands.

Backup1/Clone1
Host007\ONE

Backup2/Clone2
Host007\TWO

Your choke point then becomes your network. Is your network setup so
that you can saturate two LTO3, LTO4, LTO5 or EDL device interfaces? If
yes, KUDOS and please share your network design with us. I hope this is
helpful.

Semper fidelis et paratus, /ALE


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of bingo
Sent: Tuesday, November 29, 2011 9:03 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Can a manual clone job use more than 1 tape volume?

Concerning big save sets: NW needs to keep track about the 'segment's
location and sequence. It is not possible to spread a single save set's
data over multiple media simultaneously. This is obvious as NetWorker
could theoretically split such save set and start with 'segment_x' on
tape_2. However, it would not know in advance whether all data up to
'segment_x-1' would be successfully written on tape_1.

I am pretty sure that NetWorker can not even spread multiple small save
sets from the GUI to different media. But it might do so if the other
parameters fit as well (small Target Session value for the tape drives
etc).

Best practice i would use is to run multiple nsrclone commands/scripts
for this purpose.
Using the command line you can of course also clone directly to multiple
clone pools which the GUI does not offer you (unfortunately this is
rarely an option).

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld < at > avus-cr.de via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

If your backup command has saveset=all, then the short answer for the
cloning of same to my knowledge is "no."

It isn't, There were 12 savesets in all, one of which was 1.5 TB. Since I
did have the time, I just selected them all and said clone. I suppose I
could have selected them in smaller quantities (i.e., 2 sets of 6), and
see if each selection and manual clone would use a different drive.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER