Reclaiming a repository in a different or new Oracle VM Manager


For the upgrade of Oracle VM Server 3.1.1 to version 3.4.3 we decided to create a new repository and mount this repository to the current Oracle VM environment. After cloning the virtual machines to the new repository we reclaim the repository and can start the virtual machines on the new Oracle VM environment.

The following procedure describes the steps taken to migrate the virtual machines to the new Oracle VM 3.4.3 environment.

Current situation:
mote_repo - situation

We have two Oracle VM Servers and Managers (version 3.1.1 and 3.4.3) and two repository LUNS. The new repository is currently owned by the 3.4.3 environment.

Find the correct path in Oracle VM Manager:
move_repo - 2 - repo info

Use the command “mounted.ocfs2 -d” to check the current cluster id of the repository:
move_repo - 1 - ovm104 (new)

The cluster id will match with the cluster id in Oracle VM Manager:
move_repo - 4 - get cluster id

Release ownership of the repository:
move_repo - 3 - release ownership

Use the command “fsck.ocfs2 <PATH>” to reset the cluster id:
move_repo - 6- new cluster id

The repository now has the cluster id of the 3.1.1 environment:
move_repo - 7 - new cluster id

move_repo - 8 - new cluster id

Re-scan the shared file system and take ownership:
move_repo - 9 - refresh file system

move_repo - 10 - take ownership

Refresh the repository:
move_repo - 11 - refresh repo

You can use the clone functionality of the VM Manager to copy the virtual machines to the new repository.

Repeat the procedure and reclaim the repository on the new Oracle VM environment.

About Author

Ronnie is an Oracle consultant at AMIS. He is specialized in Oracle database (Data Guard, RAC, ASM, RMAN, SQL, PL/SQL) and has experience with EM Cloud Control, Oracle VM Server, Oracle Failsafe, Oracle Fusion Middleware, Oracle/Red Hat Linux, ODA (bare metal/virtualized).

Leave a Reply