Extend Businiss Copy volume group.

[Leif Halvarsson_2]

Hi,

We are using Business Copy for cloning volume group from a production server to a disaster recovery (DR) server and a development server (DEV). Now we need to extend some of the volume groups.

Extending the volume groups on the production server is strait forward but, extending the clones seems to be a bit tricky.

Below is what I have found out, is there any better way ?

- Extend the volume groups on the production server.

- Edit the Raid Manager configuration files (horcm).

- Export the volume groups from the DR and DEV server.

- Create a map file on the production server using "vgexport -s".

- Run the BC clone scripts.

- Import the volumegroups on the DR and DEV. server using the previous created map file.

/leif

[Adam Winebaugh]

Leif,
I came to the same conclusion not long ago. It is a bit tricky but you have the jest of it yes. The only addition I would ahve would be to, make sure that in the BC scripts you don't use a mount -r. My scripts had this and it caused some very odd errors. Modify the scripts to run a simple mount command, then the next time they run, it will be ok, then modify the script again with a mount -r (IF NEEDED).

[Leif Halvarsson_2]

Hi,

Yes, the filesystems on the DR server is mounted as read-only (mount -r).

But, the first cloning after the RM configuration has been modifyed has to be done without any mounting/unmounting as the volume groups is exported in the previous step.

After all BC pairs has been syncronized I assume it should not be any problem using mount -r.

[Leif Halvarsson_2]

Hi,

Yes, the filesystems on the DR server is read only (mount -r).

But, the first cloning after the RM configuration has been modifyed has to be done without any mount/unmount as the volume groups is exported in the previous step.

After the BC pairs has been syncronized I assume it should not be any problem using mount options.