This is a multipart message in MIME format.
--=_alternative 006FFC51862570D9_=
Content-Type: text/plain; charset="US-ASCII"
In NB 5.0, i have noticed that one DSSU(a) can't delete the contents of
another DSSU(b) if it needs more space.
example:
/export/dsu is a single partition
/export/dsu/daily all information has been duplicated to tape
/export/dsu/monthend needs more space, but can't/won't ask
/export/dsu/daily to delete some information.
Currently, your better splitting off a slice for each DSSU. Which leads to
wasted space.
Maybe that has changed under 6.0.
Karl
veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 12/16/2005 01:20:42 PM:
> Veritas says to create a different filesystem for Full and Incrementals,
> due to the backup sizes generally involved and how many files have to
> get deleted for each when cleaning a DSSU. Future versions of NetBackup
> sound like they'll do a much better job of handling staging disks.
>
> Some light reading for you:
> http://seer.support.veritas.com/docs/270101.htm
> http://seer.support.veritas.com/docs/270079.htm
> http://seer.support.veritas.com/docs/268777.htm
> http://seer.support.veritas.com/docs/265305.htm
> http://seer.support.veritas.com/docs/278169.htm
> http://seer.support.veritas.com/docs/273532.htm
>
> Depending on what you're using for back-end storage, EMC also has a pair
> of whitepapers/briefs you can get on running backups to disk. They
> should be available from their webpage somewhere.
> "Effective Write Bandwidth with CLARiiON ATA Disk Drives and RAID 3:
> Backup-to=Disk and Streaming Media"
> "EMC Backup Storage Solutions: Backup-to-Disk Guide with VERITAS
> NetBackup"
>
> Have fun. =)
> - John Nardello
> "Your backups are only as good as your restores."
>
>
>
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ed Wilts
> Sent: Friday, December 16, 2005 10:51 AM
> To: Johnson, Eric K
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Disk volume layout question
>
>
> On Fri, Dec 16, 2005 at 12:52:05PM -0500, Johnson, Eric K wrote:
> > We are in the early stages of migrating from Legato NetWorker to
> Veritas
> > NetBackup 5.1. As part of our migration, we are adding enough disk
> space
> > to hold one week worth of backups before they are staged to tape.
> >
> > When configuring our disk (approximately 9.6TB before RAID in a Sun
> > StorEdge 3511 SATA array. NetBackup server is a Sun E450 running
> Solaris
> > 10) are there any recommendations for how it should be separated out
> > into volumes?
> >
> > Is it better to have one large volume? Many small volumes? What are
> the
> > advantages and disadvantages to the given volume sizes from a
> NetBackup
> > perspective?
>
> With 5.1, a job will fail if the DSSU fills up. There are no mechanisms
> to throw a bunch of volumes at it and let NetBackup chose. With 6.0,
> this problem is supposed to go away.
>
> For now, I'd think that you would want to create a single large array.
>
> All of this assumes that all backups are created equally. If there is
> some stuff that you need to guarantee stays on disk for a week, you may
> need to set up individual DSSUs for that stuff (we're doing this for
> some Oracle databases).
>
> .../Ed
>
> --
> Ed Wilts, Mounds View, MN, USA
> mailto:ewilts AT ewilts DOT org
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
--=_alternative 006FFC51862570D9_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">In NB 5.0, i have noticed that
one DSSU(a) can't delete the contents of another DSSU(b) if it needs more
space.</font>
<br>
<br><font size=2 face="sans-serif">example:</font>
<br><font size=2 face="sans-serif">/export/dsu is a single partition</font>
<br><font size=2 face="sans-serif">/export/dsu/daily all information has
been duplicated to tape</font>
<br><font size=2 face="sans-serif">/export/dsu/monthend needs more space,
but can't/won't ask /export/dsu/daily to delete some information.</font>
<br>
<br><font size=2 face="sans-serif">Currently, your better splitting off
a slice for each DSSU. Which leads to wasted space.</font>
<br>
<br><font size=2 face="sans-serif">Maybe that has changed under 6.0.</font>
<br>
<br><font size=2 face="sans-serif">Karl</font>
<br>
<br><font size=2><tt>veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on
12/16/2005
01:20:42 PM:<br>
<br>
> Veritas says to create a different filesystem for Full and
Incrementals,<br>
> due to the backup sizes generally involved and how many files have
to<br>
> get deleted for each when cleaning a DSSU. Future versions of NetBackup<br>
> sound like they'll do a much better job of handling staging disks.
<br>
> <br>
> Some light reading for you:<br>
> http://seer.support.veritas.com/docs/270101.htm<br>
> http://seer.support.veritas.com/docs/270079.htm<br>
> http://seer.support.veritas.com/docs/268777.htm<br>
> http://seer.support.veritas.com/docs/265305.htm<br>
> http://seer.support.veritas.com/docs/278169.htm<br>
> http://seer.support.veritas.com/docs/273532.htm<br>
> <br>
> Depending on what you're using for back-end storage, EMC also has
a pair<br>
> of whitepapers/briefs you can get on running backups to disk. They<br>
> should be available from their webpage somewhere. <br>
> "Effective Write Bandwidth with CLARiiON ATA Disk Drives and
RAID 3:<br>
> Backup-to=Disk and Streaming Media" <br>
> "EMC Backup Storage Solutions: Backup-to-Disk Guide with VERITAS<br>
> NetBackup"<br>
> <br>
> Have fun. =) <br>
> - John Nardello<br>
> "Your backups are only as good as your restores."<br>
> <br>
> <br>
> <br>
> -----Original Message-----<br>
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu<br>
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ed
Wilts<br>
> Sent: Friday, December 16, 2005 10:51 AM<br>
> To: Johnson, Eric K<br>
> Cc: veritas-bu AT mailman.eng.auburn DOT edu<br>
> Subject: Re: [Veritas-bu] Disk volume layout question<br>
> <br>
> <br>
> On Fri, Dec 16, 2005 at 12:52:05PM -0500, Johnson, Eric K wrote:<br>
> > We are in the early stages of migrating from Legato NetWorker
to<br>
> Veritas<br>
> > NetBackup 5.1. As part of our migration, we are adding enough
disk<br>
> space<br>
> > to hold one week worth of backups before they are staged to tape.<br>
> > <br>
> > When configuring our disk (approximately 9.6TB before RAID in
a Sun<br>
> > StorEdge 3511 SATA array. NetBackup server is a Sun E450 running<br>
> Solaris<br>
> > 10) are there any recommendations for how it should be separated
out<br>
> > into volumes?<br>
> > <br>
> > Is it better to have one large volume? Many small volumes? What
are<br>
> the<br>
> > advantages and disadvantages to the given volume sizes from a<br>
> NetBackup<br>
> > perspective?<br>
> <br>
> With 5.1, a job will fail if the DSSU fills up. There are no
mechanisms<br>
> to throw a bunch of volumes at it and let NetBackup chose. With
6.0,<br>
> this problem is supposed to go away.<br>
> <br>
> For now, I'd think that you would want to create a single large array.<br>
> <br>
> All of this assumes that all backups are created equally. If
there is<br>
> some stuff that you need to guarantee stays on disk for a week, you
may<br>
> need to set up individual DSSUs for that stuff (we're doing this for<br>
> some Oracle databases).<br>
> <br>
> .../Ed<br>
> <br>
> -- <br>
> Ed Wilts, Mounds View, MN, USA<br>
> mailto:ewilts AT ewilts DOT org<br>
> _______________________________________________<br>
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<br>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
> <br>
> _______________________________________________<br>
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<br>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
> <br>
> <br>
> <br>
</tt></font>
--=_alternative 006FFC51862570D9_=--
|
