Veritas-bu

[Veritas-bu] NB 4.5 and ClearCase VOB backups

2003-09-03 17:36:12
Subject: [Veritas-bu] NB 4.5 and ClearCase VOB backups
From: jkennedy AT qualcomm DOT com (Kennedy, Jeffrey)
Date: Wed, 3 Sep 2003 14:36:12 -0700
Maybe I'm missing something but couldn't you just use FlashBackup?  I
know it's an additional cost but it sure would make life a lot simpler.

~JK

> -----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 Joost Mulders
> Sent: Wednesday, September 03, 2003 1:05 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] NB 4.5 and ClearCase VOB backups
> 
> 
> Hi John,
> 
> I am afraid it's even worse in the NetBackup world ;-)
> 
> First of all: No, the filesystem that is being backed up is not
> available in the bp[start|end]_notify scripts.
> 
> Secondly, if yo define a policy with multiple filesystems and enable
> multiplexing (parallelism in lgto speak) then, for each datastream the
> bp[start|end]_notify scripts will be executed multiple times, once for
> each filesystem (actually; once for each datastream).
> 
> To backup multiple filesystems on one client in parallel WITH session
> pre- and post commands is really difficult. I attached two template
> scripts which do that, but it still is a pain. The scripts do have
some
> comments though that explain how bpstart and -end work (and why it is
a
> pain ;-)
> 
> What I normally do for complex session stop- and start procedures is
to
> forget about bpstart- and -end and initiate the backup on the client
(fe
> by cron), including pre- and post processing.
> 
> For this, you'll need these steps;
> 
> - Create a policy with the clients in them
> - Create a schedule of the type "User Backup" in that policy with the
>   window always open. This allows the client(s) to initate a backup.
> 
> Your script should do
>  - lock, snapshot, unlock all filesystems
>  - run bpbackup with the "-w 0" option. This will cause the command
>    for backup completion instead of initiating and returning to the
>    command prompt
>  - do the post processing
> 
> With this, you'll lose Netbackup's scheduling features but it's a lot
> simpler then bp[start|end]_notify.
> 
> Cheers,
> 
> Joost
> 
> 
> 
> >Hi all,
> >
> >I've been researching what it will take to backup our ClearCase VOB
> >servers, all of which are Solaris boxes.  The issue I have is that
> >I've got multiple filesystems on each server, each with one or more
> >VOBs.   We're running NB 4.5FP4 (maybe FP5) on Solaris 9, on a V880.
> >Still in test mode before we deploy it.
> >
> >Currently we're using Legato Networker for the backup and it's
working
> >just fine.  I've got a script which takes the place of the 'save'
> >command (think bpbkar, maybe?) to do the pre and post processing
> >needed to make proper snapshots of the VOBs before doing backups.
> >
> >>From the looks of it, I need to use the bpstart_notify and
> >bpend_notify scripts to do my pre and post processing, which
shouldn't
> >be a problem.  The only issue I have is that I need to know which
> >filesystem is going to be backed up on each invocation, and I don't
> >see anything about this in the various NetBackup guides which tells
me
> >how this works.
> >
> >Do I need to create a policy for each and every filesystem with VOBs,
> >on each and every client, and then setup a copy of the
> >bp[start,end]_notify scripts specifically setup for each defined
> >policy?  Is that the only way I can tell which filesystem I'm backing
> >up?
> >
> >For example, I have a server, swvob1, with a bunch of VxFS (or UFS)
> >filesystems called:  /sw_VOBS1, /sw_VOBS2, ... , /sw_VOBSN.  My plan
> >is to:
> >
> >   - lock the vob(s) on a filesystem
> >   - create a VxFS snapshot of the filesystem
> >   - unlock the vob(s)
> >   - mount the snapshot
> >   - backup the snapshot
> >   - unmount the snapshot
> >   - destroy the snapshot volume
> >
> >But I don't know how to get the filesystem name from the scripts.  If
> >I had that, I'd simply tell the server to backup
> >
> >  /sw_VOBS1_backup
> >  /sw_VOBS2_backup
> >  .
> >  .
> >  .
> >  /sw_VOBSN_backup
> >
> >and the script would know where to get the snapshot from.
> >
> >Thanks,
> >John
> >   John Stoffel - Senior Unix Systems Administrator - Lucent
> Technologies
> >      stoffel AT lucent DOT com - http://www.lucent.com - 978-952-7548
> >
> >_______________________________________________
> >Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> >http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> --
> Long may you run.