Networker

Re: [Networker] Save Set Consolidation Question

2007-07-16 13:46:49
Subject: Re: [Networker] Save Set Consolidation Question
From: Curtis Preston <cpreston AT GLASSHOUSE DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 16 Jul 2007 13:40:17 -0400
I agree with everything that Bob has said.  I strongly agree with the
disk part of his comment.  Not only does it help minimize device
requirements, the more you use disk in an operation like this, the
better it will work.

I would add that saveset consolidation can help a lot _IF_ the reason
your backups are slow is either a slow network connection or low CPU
power on the client AND you have a beefy CPU on your NetWorker server or
storage node.  If the reason your backup is slow is that it has millions
of files, then I'm not sure if saveset consolidation will help you.  You
need to look into image backup.

If you've already tried a storage node on the client and that didn't
help, then I doubt saveset consolidation will help you.

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies 

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Wood, R A (Bob)
Sent: Monday, July 16, 2007 8:58 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Save Set Consolidation Question

Heather,
        I have used consolidation backups in the past. They work quite
well but there are a couple of gotchas.

You will need an initial full before any of the consolidation runs will
work. The consolidation works by doing a level 1 backup and then
creating consolidated full from the last full and the level1. Now, if
you've been counting, that's three (3) devices required for that single
backup.

It can also be a bit of a CPU load on the box doing the consolidation.

You can mitigate these issues by using a server with sufficient
horsepower and by using a disk staging area to back up to (i.e. do the
level 1 backup to disk and that way you only use two drives for the
consolidation.

On the plus side, only the changed data gets sent over the wire.

If the large servers are near the backup server consider using one or
more of them as storage nodes and sharing the library. Similarly, for
the remote data, if the consolidation backups prove unworkable, consider
making the remore server a storage node and attach a small library (you
will need local intervention to change tapes but that tends to keep the
local people in touch with the backup so could be seen as a good thing)

Regards
Bob


 

>-----Original Message-----
>From: EMC NetWorker discussion 
>[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Campbell, Heather
>Sent: 16 July 2007 08:40
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: [Networker] Save Set Consolidation Question
>
>All,
>
>            We have some servers that are in remote sites and 
>also some large file servers that take way to long to backups 
>on their weekly Fulls. I have looked at "Save Set 
>Consolidation" and was wondering if anybody uses that 
>functionality or for me not to even use it. Just looking for 
>some input on this Legato feature or if others use some other 
>way of doing theses kinds of backups.
>
> 
>
>Thank you!!
>
> 
>
>Heather
>
>
>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

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