Networker

Re: [Networker] Advanced File Device Size

2003-09-17 01:59:55
Subject: Re: [Networker] Advanced File Device Size
From: Riaan Louwrens <riaanl AT SOURCECONSULTING.CO DOT ZA>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Wed, 17 Sep 2003 08:10:09 +0200
Hi,

Some more info: ALthough the cloning process in "single" ended - you can as
stated before on this line, have more than one cloning session. What is
however quite nice is the fact that you will clone a saveset at a time -
with no interleaving of other data - so stream A has no stream B C or D
inbetween.

Goes quite a way to make your restores jump around a bit faster.

Ive done some research and it seems that the best approach is to do a
immediate clone (or scheduled clone if you dont want to over task your disk
devices / Backup Server) and to then do a script to clear the disk when
savesets are "X" days old.

Staging does this for you - but it is a bit to inflexible for my linking and
you could end up either wasting disk space (aggresive policies) or running
out of space (your tape reaction is to slow).

One big dump space seems to be the way to go - remember to have more than
one device for your different pools (if you apply different retention
policies - it work out easier in practise this way).

The disk is formatted in whatever filesystem you access it from - there are
some hints and tips for the various OS's to make it go faster. Typical
scenario I am looking at is a Nexsan Ataboy2 SCSI split between 2 clients -
Solaris and Win2K of which one is a B/S and the other will be a SN.

The way I understand that uasm treats the backup to disk data - you could
end up with "more" than 500GB on a 500GB device. I havent however tested how
this will then compress / write to tape.

Have Fun !

Riaan



-----Original Message-----
From: Shawn Cox [mailto:shawn.cox AT PCCA DOT COM]
Sent: Tuesday, September 16, 2003 9:40 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Advanced File Device Size


I write to disk initially and then immediatly clone to LTO2 tape.  As soon
as the clone is done the tapes go offsite.  I have a script I wrote that
cleans off the Disk Devices once a saveset is 3 days old.

The disk device is much more forgiving for slow networks.  I have two file
servers that are across WAN links that peak at 50K.  You can imagine how bad
an LTO tape drive performs when being fed data at 50k/sec.

Going from the Disk to LTO2 tape lets me jam data onto the tape as fast as
possible especially since my Disk Devices are SAN attached.

-Shawn


----- Original Message -----
From: "Joel Fisher" <jfisher AT WFUBMC DOT EDU>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Tuesday, September 16, 2003 8:54 AM
Subject: Re: [Networker] Advanced File Device Size


Hey Shawn,

Do you use it more as a staging area, or do you keep the data online for
several days/weeks?

Thanks,

Joel

-----Original Message-----
From: Shawn Cox [mailto:shawn.cox AT PCCA DOT COM]
Sent: Tuesday, September 16, 2003 9:50 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Advanced File Device Size

I'm Windows based, so may not apply. I have 2 500GB devices and one
200GB
device.  Works nicely.
--Shawn

----- Original Message -----
From: "Joel Fisher" <jfisher AT WFUBMC DOT EDU>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Tuesday, September 16, 2003 8:43 AM
Subject: [Networker] Advanced File Device Size


Hey All,



Anyone using AFDs as their main targets for backups?  How large did you
create your devices.  It seems to me that the design of the AFD is
geared towards very large devices.  Anyone using a vxvm managed volume
cooked with vxfs as an AFD?  What size volumes did you go with?



TIA,



Joel


--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=