Re: LUN cloning and LVM. (163 Views)
Reply
Frequent Advisor
mpua
Posts: 52
Registered: ‎08-02-2010
Message 1 of 5 (214 Views)

LUN cloning and LVM.

Hi there,

 

In order to carry out some tasks related to Oracle databases, my boss wants the Storage team to replicate (manually, with FlashCopy) the data between two LUNS presented to two different servers.

Question is, How should we manage that in SO (HP-UX 11.23 & 11.31)? Should we vgimport the cloned LUN in the target server??

Regular Advisor
Ralf_Wegener
Posts: 131
Registered: ‎08-21-2010
Message 2 of 5 (201 Views)

Re: LUN cloning and LVM.

From an HP TRIM point of view (in my own personal view)....At the application level the metadata (oracle) and the content store (NTFS or some volume on a server that is backed up according to ones regime is irrelevant). Application (HP TRIM) should not impact on how IT or your technical support team manage the data from an infrastructure point of view...
Regular Advisor
Ralf_Wegener
Posts: 131
Registered: ‎08-21-2010
Message 3 of 5 (198 Views)

Re: LUN cloning and LVM.

Furthermore, im sure the4re many post on this site or through the HP support (openview) site to assist when attempting to replicate production data with settings to a non production environment to UAT purposes.
Frequent Advisor
mpua
Posts: 52
Registered: ‎08-02-2010
Message 4 of 5 (196 Views)

Re: LUN cloning and LVM.

Both are Production, it's gonna be a filesystem for dumping the database export in one of them and for performing the import on the other node, they wanna do it with a FlashCopy to avoid using the network for sending the (big) import file to the other machine.

I did perform a search before and found nothing that solved my query, which is about LVM and cloned LUNs. I think I have to  perform a vgchid and vgimport on the cloned LUN but still not completely sure.

Honored Contributor
Bill Hassell
Posts: 14,210
Registered: ‎05-29-2000
Message 5 of 5 (163 Views)

Re: LUN cloning and LVM.

When the LUN(s) are replicated, you can import the VG on the remote server. vgchid isn't needed and it will be overwritten the next time data is synced. But most important, the data updates must stop once the VG is activated and the lvols mounted. The remote VxFS filesystem code is unable to handle any changes that are made to the filesystem once the VG and LVs are mounted. And when the lvols are mounted, they will require fsck to fix the directory structures since the filesystem was not unmounted when the replication took place.

 

To update the LUN(s), the LVs must be unmounted, then the VG deactivated and then sync the LUN(s). When complete, the VG can be activated again and the LVs mounted.

 

If the lvols are raw (ASM), then it is up to the local Oracle tools to handle live updates.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.