Veritas-bu

[Veritas-bu] renaming classes

2002-01-18 09:11:37
Subject: [Veritas-bu] renaming classes
From: david AT xbpadm-commands DOT com (David A. Chapa)
Date: Fri, 18 Jan 2002 08:11:37 -0600
If you rename or even delete a class, that doesn't preclude you from being
able to perform restores...

As far as hacking, I would only do it if you have a Unix Master.  NT freaks
out if you try this, at least it did when I tried it.

stop bprd and bpdbm

bprdreq -terminate
bpdbm -terminate

this is just to be safe.

mv /usr/openv/netbackup/db/class/$CLASSNAME
/usr/openv/netbackup/db/class/$NEWCLASSNAME

initbprd

and view  you classes in  your GUI  the old class should be gone and the new
class in its place.

Remember if you have any 'class-specific' stuff peppered throughout any of
your scripts you'll have to make changes there as well.

TRY THIS WITH A TEST CLASS FIRST...After you change the name perform a
backup...then a restore.


***This is the recommendation section***
PRINT OUT THE ENTIRE CLASS CONFIG SO YOU HAVE IT JUST IN CASE SOME OF THE
CLASSES GET BLOWN AWAY...(Murphy's law you know)

bpcllist -allclasses -U > /tmp/class.config

Also do a NBU catalog backup before you attempt any production classes
***This is the recommendation section***

Good luck

David

<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
NetBackup Consultant
DataStaff, Inc.
http://www.consulting.datastaff.com
847 413 1144
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com

-----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 Geibel,
Jonathan
Sent: Thursday, January 17, 2002 7:35 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] renaming classes



hello all,

we are looking to rename all of our classes in order to fit a better
naming convention..

I know that once you just rename the classname netbackup will think that
it is a new class and will do 2 things bad:

a) it'll immediately kick off a new full backup
b) you can't restore older data using the new class name (which gets quite
confusing)

my question is this:  is there a way to change the class names in a way
that would not cause those two problems to occur?

I'm guessing I could go in and hack away at the db/images stuff and could
probably get netbackup to be convinced that nothing really changed, but I
figured I'd ask this group first to see if someone has a better idea..

Thanks!

Jon



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


<Prev in Thread] Current Thread [Next in Thread>