Hi Richard,
I will try to briefly describe what we are doing.
We have one NetBackup master server and three media
servers. The master and media server 1 manage the
database backups.
Master Server (Sun E5500) - Solaris 8/NetBackup 3.4
A5200 (100GB RAID5) - half of /usr/openv/netbackup/db/images
master server catalogs contained in master:/images
media1:/images NFS mounted as master:/images2
L700 (10-DLT 8000)
Media Server1 (Sun E5500) - Solaris 8/NetBackup 3.4
D1000 (87GB RAID5) - other half of /usr/openv/netbackup/db/images
media server 1 catalogs contained in media1:/images
L700 (10-DLT 7000)
Backup Process:
1) Make sure backups are finished.
2) Both master and media1 servers have two sets of two
tapes for a total of eight database backup tapes,
four in each L700.
3) Sequential backup runs use alternate tape sets in
the event of a database backup failure.
4) More disks can be added to the disk arrays, because
each backup job (master and media1) has two tapes, for
a total of four catalog tapes for a single backup run.
The alternate set brings the total catalog tape
count up to eight. Remember, two more tapes are required
for the built-in database backups.
5) These tapes have an infinite retention, so four designated
tapes must be deassigned before the catalog backups begin.
6) Deassign four tapes in specific sets for the current run.
7) Initiate concurrent master and media1 server backups, each
saves one half of /usr/openv/netbackup/db/images, which
are mounted as master:/images and media1:/images on the
respective servers.
8) If the total 100GB of used catalog space is evenly
distributed, it will take a little more than 2.5 hours
to back up the NetBackup catalog images.
9) Follow this with a conventional NetBackup database
backup, including only master:/images/master and
media1:/images/media1 (no other server catalogs). This
database backup will only take minutes.
Subject: BkupDB on master - 0 NetBackup Database Backup Status
Host: master
Date: 11/26/2001 14:59:28
NB database backup to media id BU1400 SUCCEEDED
Paths backed up:
----------------
master:/usr/openv/netbackup/db
master:/usr/openv/volmgr/database
master:/usr/openv/var
master:/images/master
master:/images/media1
media1:/usr/openv/netbackup/db
media1:/usr/openv/volmgr/database
media2:/usr/openv/netbackup/db
media2:/usr/openv/volmgr/database
media3:/usr/openv/netbackup/db
media3:/usr/openv/volmgr/database
Restore Process
1) Restore NetBackup configuration with "bprecover".
2) Use regular restores to recover master:/images
and media1:/images.
3) IMPORTANT! DO NOT RESTORE:
master:/images/master
master:/images/media1
These catalogs came back with "bprecover".
I hope this helps. As you can see, we have a lot of
flexibility now.
Leo
-----Original Message-----
From: Richard Bond [mailto:rbond AT mbt.washington DOT edu]
Sent: Monday, November 26, 2001 4:47 PM
To: Labonte, L R (Leo), SITS
Subject: RE: [Veritas-bu] NBU master server catalog size concerns
?? could you elaborate on this structure please ??
I do not understand the configuration/etc (visual type here)
thanks
rcb
On Mon, 26 Nov 2001, Labonte, L R (Leo), SITS wrote:
> Date: Mon, 26 Nov 2001 14:32:57 -0500
> From: "Labonte, L R (Leo), SITS" <llabonte AT att DOT com>
> To: Jeff Kennedy <jlkennedy AT amcc DOT com>, larry.kingery AT veritas DOT com
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] NBU master server catalog size concerns
>
> Folks,
>
> Our total images size is 98GB, but we are able to back up
> our NetBackup configuration in minutes. We perform regular
> backups of the images across two media servers and a tape
> drive per media server. We don't use compression, are able
> to do NetBackup configurations while catalogs are getting
> backups, and multiple tape drives give us similar backup
> performance to the built in mechanism. Best of all, we can
> keep adding disk drives to our catalog arrays, knowing
> that we are no longer confined to a single tape's capacity.
> We have quadrupled our catalog tape capacity.
>
> I sleep great at night, and when the load eventually
> gets balanced out, we will be able to back up the entire
> 98GB in 2.5 hours. :)
>
> Leo
>
> -----Original Message-----
> From: Jeff Kennedy [mailto:jlkennedy AT amcc DOT com]
> Sent: Monday, November 26, 2001 12:51 PM
> To: larry.kingery AT veritas DOT com
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] NBU master server catalog size concerns
>
>
> Larry,
>
> Does Veritas have any plans to make the catalogue more efficient? I
> have figured that the catalogue takes about 3% of the total data backed
> up, which can be huge in current environments and it will do nothing but
> get bigger. I realize that compression is an option but that can lead
> to issues in time to restore, which is why we backup in the first
> place.....
>
> Thanks.
>
> ~JK
>
> Larry Kingery wrote:
> >
> > The master size can become an issue. At around 20GB, it can take an
> > hour or so to backup (or restore), and during that time no backups can
> > be initiated. When it gets to the point where it will no longer fit
> > on a single tape, you have to add a second step to the database backup
> > process.
> >
> > The layout of the "database" is just a hierarchy of files. There are
> > of course a few which are critical in that they affect the whole
> > system, but the vast majority (both in size and number) have no
> > dependence on each other. They're just files, and if one gets dinged
> > you can restore it from backup, or scan the tape, etc.
> >
> > You've got a long time before you have anything to worry about.
> > Personally, I'd take some time to walk through the DR process (chap 5,
> > troubleshooting guide) and make sure your catalog backups are
> > configured correctly and restorable, and document the process in your
> > own words.
> >
> > chad.haywood AT storability DOT com writes:
> > > Hi,
> > >
> > > As someone familiar with Legato Networker 5.x index stability issues,
I
> > > was concerned to learn that a Netbackup 3.4 master server I recently
> > > assumed responsibility for has a master server catalog size of 1.6 Gig
> due
> > > to NFS mounted backups. In a Networker environment I would have made
> > > shrinking this a major priority to avoid likely headaches should a DR
> > > situation arise. From those of you with more Netbackup experience, is
> the
> > > master catalog size a major issue in a DR situation? Obviously it
will
> > > impact the time needed to recover the master's catalog, but how likely
> is
> > > it to cause difficult to resolve issues due to corruption or other
> > > problems?
> > >
> > > Thanks,
> > > Chad
> > >
> > > Chad Haywood
> > > Senior Solutions Engineer
> > > Storability, Incorporated
> > > www.storability.com
> > > _______________________________________________
> > > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
> > --
> > Larry Kingery
> > It's not if, it's when and how hard
> > _______________________________________________
> > Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
--
-
Richard Bond (rbond AT gs.washington DOT edu (206) 605-3561
System Administrator K-324, Health Sciences Center
Department of Genome Sciences Box 357730
University of Washington
|
