Networker

Re: [Networker] Speeding up a clone job

2011-06-14 11:43:07
Subject: Re: [Networker] Speeding up a clone job
From: Lancy Quadros <Lancy.Quadros AT ROTARY DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 14 Jun 2011 10:42:11 -0500
Do all the databases that you are backing up have one data file and one log 
file? If they do, then it may help to split the database files into multiple 
files. This way, you will be able to parallelize the backups and speed up the 
overall process.

You will need help from the DBA's to split the files - it could be time 
consuming depending on the size of the database.

Lance 

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Michael Leone
Sent: Wednesday, February 02, 2011 3:10 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Speeding up a clone job

NW 7.5.2, Windows 2003 (server and client)

I know I will phrase this wrong, or use a technical term wrong, so I'll just 
describe what I want, and then someone can tell me what it's properly called, 
and (hopefully) how to do it.

I run a backup job that backs up MS SQL databases on one client. This client is 
an AFTD storage node. So the job backs up to disk (fiber connected SAN 
storage), and then clones onto a fiber connected library (library connected to 
my NW server, not the storage node). Problem is, I have about 1.7TB of DBs to 
back up, and my DBAs tell me they can't get rid of any of them, and that - in 
fact - they might have more DBs soon, what with the upcoming projects.

The problem I have is time, of course. It takes a long while to save to disk, 
and even longer to clone to tape. And I have to run this job every night, I'm 
told - no backing up only on the weekends, when I have a longer backup time 
window.

So what I am wondering - what can I do to speed up this job? I don't think I 
will be able to put a tape library/jukebox on this client, so I am stuck using 
my existing library (an Overland 8 drive, LTO-4 fiber connected library).

Are there any settings I can tweak to speed this up? Savegrp parallelism won't 
help, since there's only 1 client running in this job. Server parallelism is 
set at 32 (which is probably a bit high, anyway).

Client saveset definition is just "MSSQL:", since I don't know the names of the 
specific DBs to list them, and the DBAs have a tendency to just add new ones 
that I don't know about.

Suggestions? Where else to look? Some way to have it clone onto more than
1 tape at a time (is that "multiplexing")? To write out the cloned savesets to 
multiple tapes at the same time, I mean, not to duplicate the same savesets to 
more than 1 tape.

Thanks for any help.

--
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 DOT gov>

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

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>