This only works if you have the tool that will change the UUID.  Around here we 
have to do everything manually.  I have no idea how I would change the UUID 
during the cloning process.  Even if I did it is one more thing to remember to 
do.

We don't use Red Hat, do I guess I don't have to worry.

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
John Summerfield
Sent: Thursday, August 14, 2008 8:47 PM
To: [email protected]
Subject: Re: Root filesystem


David Boyes wrote:

>
> 3) It complicates cloning and replication of system images in that if
> you use a template VG structure, it is difficult to be able to import a
> VG for repair in another system if all the VG names are the same (ie,
> you can't easily fix it if all your VGs are called "system_vg",
> including the one in your recovery system).
>

fyi
Red Hat is moving from labelling filesystems to using UUIDs.

I imagine it would be prudent for those cloning systems to include part
that generates new UUIDs.

You should also consider adding a script to your cloning process to
change the default "standard" volume and group names to names that are
unique. This would alleviate the problem of importing a VG for repair.





--

Cheers
John

-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

__________________________________________________________________________________________________

CONFIDENTIALITY NOTICE: This email from the State of California is for the sole 
use of the intended recipient and may contain confidential and privileged 
information.  Any unauthorized review or use, including disclosure or 
distribution, is prohibited.  If you are not the intended recipient, please 
contact the sender and destroy all copies of this email.  

Reply via email to