[Veritas-bu] class and schedule naming standards

You can rename a class using -- bpclassnew <existing_class_name> -renameto
<new_class_name>

Yours sincerely,

Patrick Whelan
ZIT P 7.43 Data Backup Operation

_______________________________________________________________

Contact:        Phone:  +49 69 136 44927
                E-Mail: Patrick.Whelan AT CommerzbankIB DOT com

Address:        Commerzbank AG
                Zentraler Servicebereich IT Produktion
                C/S Services Investment Banking - ZIT P 7.43
                Mainzer Landstr. 151 - DLZ, Bld. 1 - 06.52.0210
                60261 Frankfurt
_______________________________________________________________
Of all the things I've lost, I miss my mind the most.

"NEW LYRICS TO BEATLES SONGS"
YESTERDAY

Yesterday,
All those backups seemed a waste of pay.
Now my database has gone away.
Oh I believe in yesterday.

Suddenly,
There's not half the files there used to be,
And there's a milestone hanging over me
The system crashed so suddenly.
I pushed something wrong
What it was I could not say.
Now all my data's gone
and I long for yesterday-ay-ay-ay.

Yesterday,
The need for back-ups seemed so far away.
I knew my data was all here to stay,
Now I believe in yesterday.



-----Original Message-----
From: Jason Ahrens [mailto:Jason.Ahrens AT telus DOT com]
Sent: Monday, July 29, 2002 10:32 PM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] class and schedule naming standards


> From: Letnes, David G. [mailto:david.letnes AT unisys DOT com]
> Sent: Monday, July 29, 2002 3:48 PM
>
> them more understandable.  Are there any things I need to look out for if
> and when I change the class and schedule names?  I was thinking that there
> might be a problem with recoverign old files or something with the ca

The way netbackup works, it's not possible to "rename" a class. Renaming a
class is basically recreating it from scratch. For this reason, why you
rename a class, NetBackup is going to want to do full backups for all your
systems again. It's good to plan class name changes around when your full
backups would occur.

For restores, NetBackup does not care what class a system was backed up
with. During restore the only thing that's of any importance is the client
name.

You can delete clients and classes from the "active" NetBackup list.
NetBackup will not expire existing images done with those names. It will
keep them around until their natural expiry.

During whatever transition time you have until all the "old" images have
expired, your metadata backups will contain references to both names. In
practice, this really doesn't have any great functional impact.

Jason

--
Jason Ahrens, System Analyst
TELUS Enterprise Solutions
http://www.telus.com

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