This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C28C79.9C6C7440
Content-Type: text/plain
NB 4.5 makes this easier because you could then group your various disk
storage units into a "storage group" then assign the Storage Group to a
class and/or schedule.
Otherwise, for v3.4, your disk STU's could be made as always available, not
"on demand only". This'll let any backup to use them and roll to the next
if one fills up and becomes unavailable. This'll also make the backups you
intend for tape potentially hit the disk, too. If you have only one
library, however, you can make the library STU to be "on demand only" then
assign your classes and schedules that are intended for tape be assigned
directly to the library STU in the class setup. The other ones intended for
disk can write to "Any Available" storage unit and should pick up the disks
since they're not on-demand.
Note, for STU's that are all freely usable, not "on demand only", then NB
will pick them in alphabetical order.
All this is fixed in 4.5 which lets you pool your devices into Storage
groups and prioritize within the group. You can set a disk-priority group
that'll roll to tape if they're all full or set a group that normally goes
to tape but will write to disk if your library fails.
I do write backups to tape and disk but the disk stuff is duplicated to tape
on a schedule and the disk image is expired if successfully duplicated. It
increases the speed and availability of backups for critical stuff (archived
oracle redo) to backup to disk but I don't have enough capacity to not move
it regularily and frequently to tape.
HTH - Mark
-----Original Message-----
From: Christina Whitaker [mailto:whitaker AT gsu DOT edu]
Sent: Thursday, November 14, 2002 2:31 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] backing up to disk
I wanted to ask about using netbackup to back up to disk. I have gone
through the mailing list archives and really didn't see a definite
answer about this issue.
We are currently using Netbackup 3.4 on Solaris8 and have SAN disk
attached to our master/media server. We created a bunch of disk pool
filesystems (disk1, disk2, disk3, etc). We want to keep our fulls on
tape and our incrementals on disk. We tried a test yesterday and
filled up the first filesystem disk1 and found out that NBU would not
move on to the next disk filesystem.
Is there a way to configure NBU so that if it fills up a filesystem,
it will start writing to the next filesystem that has been designated
for writing? Has anyone successfully implemented a backup-to-disk
system using Netbackup?
Thanks for any help you can provide.
Chris
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C28C79.9C6C7440
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] backing up to disk</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>NB 4.5 makes this easier because you could then group =
your various disk storage units into a "storage group" then =
assign the Storage Group to a class and/or schedule.</FONT></P>
<P><FONT SIZE=3D2>Otherwise, for v3.4, your disk STU's could be made as =
always available, not "on demand only". This'll let any =
backup to use them and roll to the next if one fills up and becomes =
unavailable. This'll also make the backups you intend for tape =
potentially hit the disk, too. If you have only one library, =
however, you can make the library STU to be "on demand only" =
then assign your classes and schedules that are intended for tape be =
assigned directly to the library STU in the class setup. The =
other ones intended for disk can write to "Any Available" =
storage unit and should pick up the disks since they're not =
on-demand.</FONT></P>
<P><FONT SIZE=3D2>Note, for STU's that are all freely usable, not =
"on demand only", then NB will pick them in alphabetical =
order.</FONT>
</P>
<P><FONT SIZE=3D2>All this is fixed in 4.5 which lets you pool your =
devices into Storage groups and prioritize within the group. You =
can set a disk-priority group that'll roll to tape if they're all full =
or set a group that normally goes to tape but will write to disk if =
your library fails.</FONT></P>
<P><FONT SIZE=3D2>I do write backups to tape and disk but the disk =
stuff is duplicated to tape on a schedule and the disk image is expired =
if successfully duplicated. It increases the speed and =
availability of backups for critical stuff (archived oracle redo) to =
backup to disk but I don't have enough capacity to not move it =
regularily and frequently to tape.</FONT></P>
<P><FONT SIZE=3D2>HTH - Mark</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Christina Whitaker [<A =
HREF=3D"mailto:whitaker AT gsu DOT edu">mailto:whitaker AT gsu DOT
edu</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, November 14, 2002 2:31 PM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] backing up to disk</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>I wanted to ask about using netbackup to back up to =
disk. I have gone</FONT>
<BR><FONT SIZE=3D2>through the mailing list archives and really didn't =
see a definite</FONT>
<BR><FONT SIZE=3D2>answer about this issue.</FONT>
</P>
<P><FONT SIZE=3D2>We are currently using Netbackup 3.4 on Solaris8 and =
have SAN disk</FONT>
<BR><FONT SIZE=3D2>attached to our master/media server. We created a =
bunch of disk pool</FONT>
<BR><FONT SIZE=3D2>filesystems (disk1, disk2, disk3, etc). We =
want to keep our fulls on</FONT>
<BR><FONT SIZE=3D2>tape and our incrementals on disk. We tried a test =
yesterday and</FONT>
<BR><FONT SIZE=3D2>filled up the first filesystem disk1 and found out =
that NBU would not</FONT>
<BR><FONT SIZE=3D2>move on to the next disk filesystem. </FONT>
</P>
<P><FONT SIZE=3D2>Is there a way to configure NBU so that if it fills =
up a filesystem,</FONT>
<BR><FONT SIZE=3D2>it will start writing to the next filesystem that =
has been designated</FONT>
<BR><FONT SIZE=3D2>for writing? Has anyone successfully implemented a =
backup-to-disk</FONT>
<BR><FONT SIZE=3D2>system using Netbackup?</FONT>
</P>
<P><FONT SIZE=3D2>Thanks for any help you can provide.</FONT>
<BR><FONT SIZE=3D2>Chris</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C28C79.9C6C7440--
|
