EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on 
04/01/2008 04:45:17 PM:

> Everyone will have a different answer. 
> 
> In our case, our largest SQL server backups are development servers, and
> can be as large as 2+ TB. 
> 
> Our solution is to make each one of these servers a dedicated storage
> node, over Fiber attached tape drives.  When the backup starts running,
> it has it's own dedicated tape drive, separate from the other backups
> running. Backups still take a while, but much improved over GigE.
> Backups went from 36-48 hours down to 15-18 hours. That's a long time,
> but something we can live with.  We run FULL on the weekend, with
> differential backups during the week. 

How can you do differential on SQL databases? I thought a MSSQL: backup 
was *always* forced to FULL, even if you set it to incremental. I tried 
setting one of my jobs that does a SQL DB backup to incremental, and it 
said it was forcing it to FULL. This is using the NW SQL Module 5.x on NW 
7.4.1.

Or did you mean filesystem backup, as opposed to the actual SQL DBs?

> 
> David M. Browning Jr.
> IT Project Coordinator Enterprise Backups and Help Desk
> 
> 
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of sunman1
> Sent: Tuesday, April 01, 2008 9:09 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Backups of Large clients 1+ TBs
> 
> What is a standard configuration with NetWorker to backup a system with
> a large amount of data?  We have systems with 600-1000MB file systems,
> and MSSQL systems with 2-4TBs of data. With our 100BaseT network
> connections these clients can take days to backup.  What is a better
> way, GigE, StorageNodes, VTLs, Data Deduplication...?
> 
> +----------------------------------------------------------------------
> |This was sent by timothy.sage AT dowjones DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------
> 
> 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

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