Business Copy on EVA fails mounting FS

[Sergio Tostao]

Hello; I'm implementing Snapclones using Business Copy on a EVA storage. The propose is create a snapclone a VG of system A and present it on system B, mouning the respective filesystems. Its happens that the BC job creates the disk clones, present them correctly to system B, but it aborts reporting it can not create the Volume Group on system B, and so it can not go further and mount the filesystems. Can you please help me on this?
System A/B are hpux 11.11; BCopy server/agents are v 2.2.2; Command View is 3.3. System A is part of a MC/SG cluster and has several HBAs so using SecurePath; system B has only one HBA and so doesn't have SPath.
Send job log file.

[Vincent Fleming]

You don't mention importing the volume group, which is required to mount the FS.

For information on how to import a volume group, just search these forums for "import volume group" - there are lots of examples.

Good luck,

Vince

[Sergio Tostao]

Hello,
I'm talking about Business Copy software for EVA Snapclones/Snapshots, and not a manual script.
I don't have to create or import any VG manualy because this should be done automaticaly by the BCopy Agent on the system B. All that should be done is creating a "Business Copy Job" on Business Copy Server that does the VG clone and mounts it's filesystems on the specified target host.
The problem here is that it creates the VG clone, presents the clone disks to system B, but it aborts when trying to create the vg struture and mount the filesystems.

Can help?

I send the Business Copy Job in attached file.

Thanks. Regards,
Sergio

[Alzhy]

Sergio,

You probably are forgotting (as most BC sites do) to run the 2 scripts on the Servers where you're doing your BC operations on. These are:

/opt/CPQevm/bin/UpdateHost.ksh
/opt/CPQevm/GenerateMapfiles.ksh

These scripts MUST be ran at least once post install of BC agents OR everytime you make a change in the servers' LVM configuration -- ie. adding a new VG, new PV, extend/shrink an LVOL.. etc.

I think this is where the problem is.. The SMA (appliance) does not have a clue on what is the LVM landscape on the server where you are presenting the Snapclones.