Veritas-bu

[Veritas-bu] changing pool name

2005-12-15 13:38:03
Subject: [Veritas-bu] changing pool name
From: Mark.Donaldson AT cexp DOT com (Mark.Donaldson AT cexp DOT com)
Date: Thu, 15 Dec 2005 11:38:03 -0700
Interesting to know - it's an active lookup, then, for display purposes.  I
knew that might be possible but I thought unlikely.  Thanks for testing
this.

-M

-----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 Simon I.
Tetelbaum
Sent: Thursday, December 15, 2005 11:16 AM
To: WEAVER, Simon
Cc: 'Mark.Donaldson AT cexp DOT com'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] changing pool name


I did run the "vmquery -w -a" and the new pool name showed up correctly. 
I think that the media database does store the tape by pool number but 
the vmquery command may refer to the the poolDB file to find the 
associated pool name. Anyway, I'm fairly convinced that this isn't going 
to cause a problem.

-Simon

>Looks like I wont be taking this on board yet :)
>I know in 3.4 it was a serious "NO" "NO" to change it!
>
>Simon Weaver 
>Technical Support 
>Windows Domain Administrator 
>
>EADS Astrium 
>Tel: 02392-708598 
>
>Email: Simon.Weaver AT Astrium.eads DOT net 
>
>
>
>-----Original Message-----
>From: Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT com] 
>Sent: 14 December 2005 17:38
>To: WEAVER, Simon; simont AT mitre DOT org
>Cc: veritas-bu AT mailman.eng.auburn DOT edu
>Subject: RE: [Veritas-bu] changing pool name
>
>
>I think the volDB stores pool by both name and number.  You might get in
>trouble by changing the poolDB file.
>
>Do a "vmquery -w -a" to see both fields (fields 12 & 13).
>
>-M
>
>-----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 WEAVER, 
>Simon
>Sent: Wednesday, December 14, 2005 10:11 AM
>To: 'Simon I. Tetelbaum'
>Cc: veritas-bu AT mailman.eng.auburn DOT edu
>Subject: RE: [Veritas-bu] changing pool name
>
>
>
>You should be ok then! Yes I checked, but I did wonder if a name change was
>not allowed, even by editing poolDB file!
>
>But if it works, its something I will take on board now :-)
>
>Simon Weaver 
>Technical Support 
>Windows Domain Administrator 
>
>EADS Astrium 
>Tel: 02392-708598 
>
>Email: Simon.Weaver AT Astrium.eads DOT net 
>
>
>
>-----Original Message-----
>From: Simon I. Tetelbaum [mailto:simont AT mitre DOT org] 
>Sent: 14 December 2005 17:12
>To: WEAVER, Simon
>Cc: veritas-bu AT mailman.eng.auburn DOT edu
>Subject: Re: [Veritas-bu] changing pool name
>
>
>As far as I can tell, no. The image database knows the pool by number, 
>not by name. If you print out the poolDB file, the first column is a 
>number that netbackup associates with that pool. All images seem to 
>reference that number rather than the pool name, so changing the pool 
>name has no effect. Changing the number would probably be a disaster.
>
>-Simon
>
>  
>
>>I may be wrong, but if you change the pool name, wont the images that
>>are linked to this pool expire?
>>
>>Simon Weaver
>>Technical Support
>>Windows Domain Administrator 
>>
>>EADS Astrium
>>Tel: 02392-708598
>>
>>Email: Simon.Weaver AT Astrium.eads DOT net
>>
>>
>>
>>-----Original Message-----
>>From: Simon I. Tetelbaum [mailto:simont AT mitre DOT org]
>>Sent: 14 December 2005 16:51
>>To: veritas-bu AT mailman.eng.auburn DOT edu
>>Subject: [Veritas-bu] changing pool name
>>
>>
>>Hi,
>>  I wanted to change the name of one of my media pools, but couldn't 
>>find a command to do this. Will I muck up netbackup somehow if I change 
>>the pool name by editing the /usr/openv/volmgr/database/poolDB file? 
>>I've tested this somewhat and had no problems, but I'm wondering if the 
>>pool name (rather than number) is buried in some other netbackup 
>>database files that will cause end up causing problems down the line.
>>
>>-Simon
>>_______________________________________________
>>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>>This email is for the intended addressee only.
>>If you have received it in error then you must not use, retain,
>>disseminate or otherwise deal with it. Please notify the sender by 
>>return email. The views of the author may not necessarily constitute 
>>the views of EADS Astrium Limited. Nothing in this email shall bind 
>>EADS Astrium Limited in any contract or obligation.
>>
>>EADS Astrium Limited, Registered in England and Wales No. 2449259
>>Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 
>>2AS, England
>> 
>>
>>    
>>
>
>This email is for the intended addressee only.
>If you have received it in error then you must not use, retain, disseminate
>or otherwise deal with it. Please notify the sender by return email. The
>views of the author may not necessarily constitute the views of EADS
Astrium
>Limited. Nothing in this email shall bind EADS Astrium Limited in any
>contract or obligation.
>
>EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered
>Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>This email is for the intended addressee only.
>If you have received it in error then you must not use, retain, disseminate
or otherwise deal with it.
>Please notify the sender by return email.
>The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
>Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
>
>EADS Astrium Limited, Registered in England and Wales No. 2449259
>Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England
>  
>

_______________________________________________
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>