Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

SMI-S with CV-EVA 7.0.1 not working

Andrew Scott_3
Regular Advisor

SMI-S with CV-EVA 7.0.1 not working

We've been trying to get CIM to monitor our EVAs as well as DataProtector ZDB working with little success.

I've finally tracked down what looks to be the major impediment: SMI-S as installed with Command View EVA does not work on our system.

As you can see below, all the hpeva providers are in Error status.

I have just removed CV 7 and installed CV 7.0.1 along with the included SMI-S component. CVEVA works perfectly, but nothing can talk to CV via the CIM providers. This prevents CIM from seeing the storage as well as ZDB from being able to execute operations on the EVAs.

What do I need to look at next to find out why these providers are in Error status?

From cimprovider:

C:\Program Files\Hewlett-Packard\pegasus_home\bin>cimprovider -ls

MODULE STATUS

ComputerSystemModule2 OK

OperatingSystemModule OK

ComputerSystemModule OK

ProcessModule OK

ProcessorProviderModule OK

IPProviderModule OK

SLPProviderModule OK

HPCertificateInstanceProviderModule Error

hpeva_affectedjobelement_providerModule Error

hpeva_alertindication_providerModule Error

hpeva_allocatedfromstoragepool_providerModule Error

hpeva_associatedmanifestcollection_providerModule Error

hpeva_authorizedsubject_providerModule Error

hpeva_authorizedtarget_providerModule Error

hpeva_basedon_providerModule Error

hpeva_blockmemberofcollection_providerModule Error

hpeva_blockstatisticscapabilities_providerModule Error

hpeva_blockstatisticsservice_providerModule Error

hpeva_chassisinrack_providerModule Error

hpeva_componentcs_providerModule Error

hpeva_component_providerModule Error

hpeva_computersystempackageforcard_providerModule Error

hpeva_computersystempackage_providerModule Error

hpeva_concretecomponent_providerModule Error

hpeva_concreteidentity_providerModule Error

hpeva_consistencyset_providerModule Error

hpeva_controllerconfigurationservice_providerModule Error

hpeva_controllerinstalledsoftwareelement_providerModule Error

hpeva_controllersoftwareelement_providerModule Error

hpeva_devicesapimplementationforfcport_providerModule Error

hpeva_devicefcportstatisticaldata_providerModule Error

hpeva_diskdrive_providerModule Error

hpeva_diskdriveblockmanifest_providerModule Error

hpeva_diskextent_providerModule Error

hpeva_diskfcport_providerModule Error

hpeva_diskmedia_providerModule Error

hpeva_diskmodule_providerModule Error

hpeva_diskportscsiprotocolcontroller_providerModule Error

hpeva_disksoftwareelement_providerModule Error

hpeva_elementcapabilities_providerModule Error

hpeva_elementsettingdata_providerModule Error

hpeva_elementstatisticaldata_providerModule Error

hpeva_extentconcreteidentity_providerModule Error

hpeva_fcdriveportblockmanifest_providerModule Error

hpeva_fchostportblockmanifest_providerModule Error

hpeva_hostfcportstatisticaldata_providerModule Error

hpeva_folderinfolder_providerModule Error

hpeva_folder_providerModule Error

hpeva_hardwareidconcretedependency_providerModule Error

hpeva_hostedcollection_providerModule Error

hpeva_hostedservice_providerModule Error

hpeva_hostedstoragepool_providerModule Error

hpeva_hostedwebaccesspoint_providerModule Error

hpeva_hostfcport_providerModule Error

hpeva_hsvproductphysicalcomponent_providerModule Error

hpeva_hsvstorageproduct_providerModule Error

hpeva_initiatorelementsettingdata_providerModule Error

hpeva_installeddiskfirmware_providerModule Error

hpeva_instcreation_providerModule Error

hpeva_instdeletion_providerModule Error

hpeva_instmodification_providerModule Error

hpeva_job_providerModule Error

hpeva_lockingservice_providerModule Error

hpeva_lockingservice_methodproviderModule_lockfeature Error

hpeva_lockingservice_methodproviderModule_unlockfeature Error

hpeva_lunmaskingelementcapabilities_providerModule Error

hpeva_lunmaskprivilegeservice_providerModule Error

hpeva_manifestcollection_providerModule Error

hpeva_mediaaccessstatdataforspindle_providerModule Error

hpeva_mediaaccessstatdata_providerModule Error

hpeva_mediapresent_providerModule Error

hpeva_orderedmemberofcollection_providerModule Error

hpeva_owningjobelement_providerModule Error

hpeva_packagedcomponent_providerModule Error

hpeva_packageinchassis_providerModule Error

hpeva_perfmemberofcollection_providerModule Error

hpeva_diskdrivestatisticaldata_providerModule Error

hpeva_physicalelementlocation_providerModule Error

hpeva_privilegeconcretedependency_providerModule Error

hpeva_privilegehosteddependency_providerModule Error

hpeva_privilege_providerModule Error

hpeva_productparentchild_providerModule Error

hpeva_productphysicalcomponent_providerModule Error

hpeva_protocolcontrollerfordiskdrive_providerModule Error

hpeva_protocolcontrollerfordiskport_providerModule Error

hpeva_protocolcontrollerforhostport_providerModule Error

hpeva_protocolcontrollerforvolume_providerModule Error

hpeva_protocolcontrollermaskingcapabilities_providerModule Error

hpeva_rack_providerModule Error

hpeva_realizesextent_providerModule Error

hpeva_realizes_providerModule Error

hpeva_sapavailableforelement_providerModule Error

hpeva_scsihostedaccesspoint_providerModule Error

hpeva_scsiprotocolendpoint_providerModule Error

hpeva_statisticscollection_providerModule Error

hpeva_storagecapabilities_providerModule Error

hpeva_storageclientsettingdata_providerModule Error

hpeva_storageconfigurationcapabilities_providerModule Error

hpeva_storageconfigurationservice_providerModule Error

hpeva_storagecontrollerchassis_providerModule Error

hpeva_storagediskenclosure_providerModule Error

hpeva_storagehardwareidmanagementservice_providerModule Error

hpeva_storagehardwareid_providerModule Error

hpeva_storagepool_providerModule Error

hpeva_storageprocessorcard_providerModule Error

hpeva_storageprocessorsystem_providerModule Error

hpeva_storageproduct_providerModule Error

hpeva_storageremotereplicationservice_providerModule Error

hpeva_storagesetting_providerModule Error

hpeva_storagesynchronizedforclone_providerModule Error

hpeva_storagesynchronizedfordrgroups_providerModule Error

hpeva_storagesynchronized_providerModule Error

hpeva_storagesystemblockmanifest_providerModule Error

hpeva_storagecontrollersystemblockmanifest_providerModule Error

hpeva_storagesystemcontrollerstatisticaldata_providerModule Error

hpeva_storagesystemstatisticaldata_providerModule Error

hpeva_storagesystem_providerModule Error

hpeva_storagevolumeblockmanifest_providerModule Error

hpeva_storagevolume_providerModule Error

hpeva_storagevolumestatistics_providerModule Error

hpeva_subsystemcontrollerenclosurelocation_providerModule Error

hpeva_subsystemdiskenclosurelocation_providerModule Error

hpeva_subsystemracklocation_providerModule Error

hpeva_systemdevice_providerModule Error

hpeva_viewconcretedependency_providerModule Error

hpeva_viewprotocolcontroller_providerModule Error

hpeva_volumeinfolder_providerModule Error

hpeva_volumestatisticaldata_providerModule Error

hpeva_webaccesspoint_providerModule Error

hpeva_redundancyset_providerModule Error

hpeva_memberofprocessorcollection_providerModule Error

hpeva_iscsiconfigurationservice_providerModule Error

hpeva_storagereplicationcapabilities_providerModule Error

hpeva_masoftwareidentity_providerModule Error

hpeva_maelementsoftwareidentity_providerModule Error

hpeva_registeredprofile_providerModule Error

hpeva_registeredsubprofile_providerModule Error

hpeva_subprofilerequiresprofile_providerModule Error



C:\Program Files\Hewlett-Packard\pegasus_home\bin>



Thanks!
Andrew
11 REPLIES
Rob Buxton
Honored Contributor

Re: SMI-S with CV-EVA 7.0.1 not working

HPSIM uses the server hosting CV EVA to detect the EVA itself. It doesn't detect it directly. You can add wbem specific credentials for the server costing CV EVA into HPSIM. Those credentials will be whatever you entered into the SMI-S part of the install.

You can also check the connection from the HPSIM Server using the wbemdisco command. Again you'll need to provide the wbem credentials. Not sure what they are in CV 7 but in CV6 the default was administrator/administrator.

Andrew Scott_3
Regular Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

HPSIM uses the CIMOM interface to extract EVA information.

CIMOM's hpeva providers don't work, thus HPSIM can't poll any information, and ZDB can't tell the EVAs to do anything.

I've done the wbemdisco thing. I can get into the CIMOM server and poll it for information using that tool, and Dataprotector's SMI-S agent can also hit the CIMOM components. CIMOM simply doesn't know anything about the EVA because these providers aren't working.

I to know how to troubleshoot cimprovider and how it loads these components.


Andrew Scott_3
Regular Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

My last sentence in that post should read:

"I need to know...", sorry.
Carlos Mexia
Occasional Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

I'm having the exact same problem

could be resolved?


Please help me

Thanks!
Andrew Scott_3
Regular Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

I never got a resolution. The only answer I could get from HP, even from Support, was "This should work, we don't know why it doesn't." And the conversation would always end there.

I've given up. Zero Downtime Backup using the EVA and the Dataprotector SMI-S agents is a myth as far as I'm concerned. I may try again after the next major revision of all the pieces.
Carlos Mexia
Occasional Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

Good news, find a solution, now ZDB work

My English is bad, attempts to explain

I'm having the exact same problem:

-Data Protector 6.0
-Command View 7.00.01
-When I execute "cimprovider -ls" I have the same errors, eg:

.....................
.....................
IPProviderModule OK
SLPProviderModule OK
HPCertificateInstanceProviderModule Error
hpeva_affectedjobelement_providerModule Error
hpeva_alertindication_providerModule Error
.....................
.....................


-In the debug i saw:

"A Pegasus-based exception occurred when trying to connect.
The string returned was 'Malformed HTTP response message.'.
Cannot create a ComputerSystem from an uninitialized instance!"


The solution, is very simple:

In the Cell Server DP 60 to give the command:

omnidbsmis -ompasswd -add 162.51.1.128 -port 5988 -user administrator -passwd hpinvent -namespace root/eva

The important part is: "-namespace root/eva"

Because in the Apppliance (Command View Server) in the path:

C:\Program Files\Hewlett-Packard\pegasus_home\repository

are the following directories

root#cimv2
root#eva
root#PG_Internal
root#PG_InterOp

These are associated with the namespace

And within root#eva\classes are the "commandos" necessary for the ZDB through the SMI-S communicate with the EVA


Not important (in my opinion) errors that are obtained by giving the command "cimprovider -ls"

The important thing is to give the proper "namespace" in command:

omnidbsmis -ompasswd -add 172.17.1.128 -port 5988 -user administrator -passwd hpinvent -namespace root/eva


Now I'm going to test the Instant Recovery

I tell you the result tomorrow

Carlos
Carlos Mexia
Occasional Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

Andrew

:( Bad news, Another problem

When I run:

First Backup. Works, is Ok
Second Backup.Not work, is not Ok
Third Backup. Works, is Ok
Fourth Backup.Not work, is not Ok

The Second backup erased of SnapClone (First backup) and fails

The Fourth backup erased of SnapClone (Third backup) and fails

When the second backup and fourth backup are executed, their messages are as follows:

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:27:36 AM
Starting agent on sever02.lab.com.

[Normal] From: SMISA@sever01.lab.com "SMISA" Time: 7/22/2008 10:27:36 AM
Starting agent on sever01.lab.com.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:27:36 AM
Starting purge of ZDB database.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:27:36 AM
The target volumes that will be purged:
50001fe150128820\\Virtual Disks\Laboratorio HE\DP-2008.07.22-2-04885F9A9\ACTIVE


[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:27:37 AM
Beginning the resolve of storage volumes.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:27:37 AM
Beginning the resolve of the storage volume with a UUID
of 6005-08b4-0006-e7b2-0000-b000-1675-0000.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:13 AM
The resolve of this storage volume has succeeded. The information
returned is:
Storage volume name : 50001FE150128820\\Virtual Disks\Laboratorio HE\DP-2008.07.22-2-04885F9A9\ACTIVE
Storage volume WWN : 6005-08b4-0006-e7b2-0000-b000-1675-0000
Storage volume UUID : 6005-08b4-0006-e7b2-0000-b000-1675-0000

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:13 AM
The resolve of storage volumes has completed.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:13 AM
Beginning the resolve of the StorageWorks EVA units that
control the storage volumes.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:13 AM
A StorageWorks EVA unit has been successfully located
for the storage volume:
Storage volume name : 50001FE150128820\\Virtual Disks\Laboratorio HE\DP-2008.07.22-2-04885F9A9\ACTIVE
StorageWorks EVA name : EVA_TRIARA_HE1

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:13 AM
The resolve of StorageWorks EVA units has completed.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:19 AM
StorageWorks EVA SMI-S agent is attempting to delete this storage volume:
Storage volume name : 50001FE150128820\\Virtual Disks\Laboratorio HE\DP-2008.07.22-2-04885F9A9\ACTIVE
StorageWorks EVA name : 5000-1fe1-5012-8820

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:24 AM
The storage volume has been successfully deleted.

[Normal] From: SMISA@sever01.lab.com "SMISA" Time: 7/22/2008 10:29:24 AM
Resolving backup objects on the application system.

[Normal] From: SMISA@sever01.lab.com "SMISA" Time: 7/22/2008 10:29:25 AM
Resolving of backup objects on the application system completed.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:26 AM
Beginning the resolve of storage volumes.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:26 AM
Beginning the resolve of the storage volume with a WWN of
6005-08b4-0006-e7b2-0000-b000-04d5-0000 and exists on a StorageWorks EVA with a WWN of
5000-1fe1-5012-8820.

[Minor] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:39 AM
[236:7103] The resolve of this storage volume has failed.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:39 AM
The resolve of storage volumes has completed.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:39 AM
Beginning the resolve of the StorageWorks EVA units that
control the storage volumes.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:39 AM
The resolve of StorageWorks EVA units has completed.

[Critical] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:29:39 AM
There are no valid objects left.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:30:15 AM
SMIS-Backup agent will start with clean up.

[Normal] From: SMISA@sever02.lab.com "SMISA" Time: 7/22/2008 10:30:15 AM
ABORTED SMIS-Backup agent on sever02.lab.com.

[Normal] From: SMISA@sever01.lab.com "SMISA" Time: 7/22/2008 10:30:14 AM
SMIS-Application agent will start with clean up.

[Normal] From: SMISA@sever01.lab.com "SMISA" Time: 7/22/2008 10:30:14 AM
ABORTED SMIS-Application agent on sever01.lab.com.

[Critical] From: BSM@dp01.lab.com "prueba-zdb" Time: 7/22/2008 10:30:15 AM
None of the Disk Agents completed successfully.
Session has failed.

[Normal] From: BSM@dp01.lab.com "prueba-zdb" Time: 7/22/2008 10:30:15 AM

Backup Statistics:

Session Queuing Time (hours) 0.04
----------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 1
Aborted Disk Agents .......... 0
----------------------------------------
Disk Agents Total ........... 1
========================================
Completed Media Agents ....... 0
Failed Media Agents .......... 0
Aborted Media Agents ......... 0
----------------------------------------
Media Agents Total .......... 0
========================================
Mbytes Total ................. 0 MB
Used Media Total ............. 0
Disk Agent Errors Total ...... 0


============================================================================
Session failed!
============================================================================


accepted ideas please

seek solution for this failure


Carlos
Andrew Scott_3
Regular Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

Is 6005-08b4-0006-e7b2-0000-b000-04d5-0000 the volume you're trying to back up?

What if you increase the number of copies of snapshots it keeps beyond 1?

I'm going to call licensing in a bit and get my Eval extended so I can start hammering from this end again, we'll see if two heads are better than one.

Thanks for the update!
Carlos Mexia
Occasional Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

Thanks Andrew

Yes, 6005-08b4-0006-e7b2-0000-b000-04d5-0000 is the volume I attempt to backup.

The First backup, and the third backup, give messages like:

============================================================================

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:23 PM

Starting agent on server02.lab.com.

[Normal] From: SMISA@server01.lab.com "SMISA" Time: 7/22/2008 12:32:23 PM

Starting agent on server01.lab.com.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:23 PM

Starting purge of ZDB database.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:23 PM

Purge of ZDB database completed.

[Normal] From: SMISA@server01.lab.com "SMISA" Time: 7/22/2008 12:32:23 PM

Resolving backup objects on the application system.

[Normal] From: SMISA@server01.lab.com "SMISA" Time: 7/22/2008 12:32:24 PM

Resolving of backup objects on the application system completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:25 PM

Beginning the resolve of storage volumes.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:25 PM

Beginning the resolve of the storage volume with a WWN of

6005-08b4-0006-e7b2-0000-b000-04d5-0000 and exists on a StorageWorks EVA with a WWN of

5000-1fe1-5012-8820.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:34 PM

The resolve of this storage volume has succeeded. The information

returned is:

Storage volume name : 50001FE150128820\\Virtual Disks\Laboratorio HE\Vdisk008\ACTIVE

Storage volume WWN : 6005-08b4-0006-e7b2-0000-b000-04d5-0000

Storage volume UUID : 6005-08b4-0006-e7b2-0000-b000-04d5-0000

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:34 PM

The resolve of storage volumes has completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:34 PM

Beginning the resolve of the StorageWorks EVA units that

control the storage volumes.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:34 PM

A StorageWorks EVA unit has been successfully located

for the storage volume:

Storage volume name : 50001FE150128820\\Virtual Disks\Laboratorio HE\Vdisk008\ACTIVE

StorageWorks EVA name : EVA_T_HE1

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:34 PM

The resolve of StorageWorks EVA units has completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:36 PM

Beginning the check for snapshot type and snapshot policy requirements.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:38 PM

The snapshot type and policy requirements have been fulfilled.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:38 PM

The check for snapshot type and snapshot policy requirements

has completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:38 PM

Beginning the check of disk group redirection for snapclone creation.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:38 PM

Locating the current disk groups for the storage volumes.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:46 PM

A disk group has been successfully located for the storage volume:

Storage volume name : 50001FE150128820\\Virtual Disks\Laboratorio HE\Vdisk008\ACTIVE

Disk group name : DG3_Bck

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:46 PM

The resolve of disk group locations has completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:46 PM

The check for disk group redirection for snapclone creation has completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:49 PM

Creation of replica started on host server02.lab.com.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:52 PM

A snapclone was successfully created:

Source storage volume : 50001FE150128820\\Virtual Disks\Laboratorio HE\Vdisk008\ACTIVE

Source disk group name : DG3_Bck

StorageWorks EVA name : 5000-1fe1-5012-8820

Target storage volume : 50001fe150128820\\Virtual Disks\Laboratorio HE\DP-2008.07.22-13-0488619C1\ACTIVE

Target disk group name : DG3_Bck

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:52 PM

Creation of replica on host server02.lab.com completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:52 PM

Preparing the backup system:

1) Mounting of filesystems

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:52 PM

Beginning the creation of presentations.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:52 PM

A presentation is being created for:

Storage volume name : 50001fe150128820\\Virtual Disks\Laboratorio HE\DP-2008.07.22-13-0488619C1\ACTIVE

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:55 PM

The presentation has been successfully created.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:32:55 PM

The creation of presentations has completed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:33:07 PM

Filesystem \\?\Volume{8aab7c9b-4a12-11dd-a75b-0016358217ee}

has been successfully mounted

to C:\Program Files\OmniBack\tmp\virtual01.lab.com\H\EVSTLSG04_2008-07-22-13.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:33:07 PM

Waiting 90 minutes for creation of clone.

[Normal] From: BSM@dp01.lab.com "prueba-zdb" Time: 7/22/2008 12:38:08 PM

Starting rescan of library "HP:ESL E-Series(2)" with drive "HP:Ultrium 3-SCSI_2(2)".

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:38:08 PM

Preparation of the backup system completed.

[Normal] From: UMA@server02.lab.com "HP:ESL E-Series(2)" Time: 7/22/2008 12:38:08 PM

STARTING Media Agent "HP:ESL E-Series(2)"

[Normal] From: UMA@server02.lab.com "HP:ESL E-Series(2)" Time: 7/22/2008 12:39:29 PM

COMPLETED Media Agent "HP:ESL E-Series(2)"

[Normal] From: BSM@dp01.lab.com "prueba-zdb" Time: 7/22/2008 12:39:29 PM

Finished rescan of library "HP:ESL E-Series(2)" with drive "HP:Ultrium 3-SCSI_2(2)".

[Normal] From: BMA@server02.lab.com "HP:Ultrium 3-SCSI_2(2)" Time: 7/22/2008 12:39:35 PM

STARTING Media Agent "HP:Ultrium 3-SCSI_2(2)"

[Normal] From: BMA@server02.lab.com "HP:Ultrium 3-SCSI_2(2)" Time: 7/22/2008 12:39:38 PM

By: UMA@server02.lab.com@scsi6:0:5:2

Loading medium from slot 18 to device scsi6:0:4:1C

[Normal] From: VBDA@server02.lab.com "H:\EVSTLSG04" Time: 7/22/2008 12:40:19 PM

STARTING Disk Agent for server02.lab.com:C:\Program Files\OmniBack\tmp\virtual01.lab.com\H\EVSTLSG04_2008-07-22-13 "H:\EVSTLSG04".

[Normal] From: VBDA@server02.lab.com "H:\EVSTLSG04" Time: 7/22/2008 12:41:52 PM

COMPLETED Disk Agent for server02.lab.com:C:\Program Files\OmniBack\tmp\virtual01.lab.com\H\EVSTLSG04_2008-07-22-13 "H:\EVSTLSG04".

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:41:52 PM

Resuming the backup system.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:41:52 PM

Filesystem \\?\Volume{8aab7c9b-4a12-11dd-a75b-0016358217ee}

has been successfully dismounted

from C:\Program Files\OmniBack\tmp\virtual01.lab.com\H\EVSTLSG04_2008-07-22-13.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:41:52 PM

Removing any presentations of:

Storage volume name : 50001fe150128820\\Virtual Disks\Laboratorio HE\DP-2008.07.22-13-0488619C1\ACTIVE

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:41:53 PM

The presentations have been successfully removed.

[Normal] From: BMA@server02.lab.com "HP:Ultrium 3-SCSI_2(2)" Time: 7/22/2008 12:43:34 PM

scsi6:0:4:1C

Medium header verification completed, 0 errors found

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:43:48 PM

The backup system was successfully resumed.

[Normal] From: SMISA@server02.lab.com "SMISA" Time: 7/22/2008 12:43:48 PM

COMPLETED SMIS-Backup agent on server02.lab.com.

[Normal] From: SMISA@server01.lab.com "SMISA" Time: 7/22/2008 12:43:48 PM

COMPLETED SMIS-Application agent on server01.lab.com.

[Normal] From: BMA@server02.lab.com "HP:Ultrium 3-SCSI_2(2)" Time: 7/22/2008 12:43:54 PM

By: UMA@server02.lab.com@scsi6:0:5:2

Unloading medium to slot 18 from device scsi6:0:4:1C

[Normal] From: BMA@server02.lab.com "HP:Ultrium 3-SCSI_2(2)" Time: 7/22/2008 12:44:07 PM

COMPLETED Media Agent "HP:Ultrium 3-SCSI_2(2)"

[Normal] From: BSM@dp01.lab.com "prueba-zdb" Time: 7/22/2008 12:44:07 PM

Backup Statistics:


Session Queuing Time (hours) 0.10

----------------------------------------

Completed Disk Agents ........ 1

Failed Disk Agents ........... 0

Aborted Disk Agents .......... 0

----------------------------------------

Disk Agents Total ........... 1

========================================

Completed Media Agents ....... 1

Failed Media Agents .......... 0

Aborted Media Agents ......... 0

----------------------------------------

Media Agents Total .......... 1

========================================

Mbytes Total ................. 1040 MB

Used Media Total ............. 1

Disk Agent Errors Total ...... 0



============================================================================

Session completed successfully!

============================================================================


Where

- server01.lab.com is the application server in cluster (volume source, production)

- virtual01.lab.com is the virtual server (volume source, production)

- server02.lab.com is the "backup" server (which present the snapclone)

- dp01.lab.com is the Cell Server DP60.

- EVA_T_HE1 is the EVA

I'm going to increase the number of copies of snapclone to 2.

Thank you

Carlos
Carlos Mexia
Occasional Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

With a value equal to 2 replica, the backs have the following behavior:

First Backup. Works, is Ok
Second Backup.Works, is Ok
Third Backup. Not work, is not Ok
Fourth Backup.Works, is Ok
Fifth Backup. Not work, is not Ok
Sixth Backup.Works, is Ok

- The First Backup create snapclone, and backup snapclone
- The Second Backup create snapclone, and backup snapclone
- The Third Backup erased of SnapClone and fails
- The Fourth Backup create snapclone, and backup snapclone
- The Fifth Backup erased of SnapClone and fails
- The Sixth Backup create snapclone, and backup snapclone

does not work

But we are closer to focus lights

Thanks!
Carlos
Andrew Scott_3
Regular Advisor

Re: SMI-S with CV-EVA 7.0.1 not working

So after running a delete operation on a snapclone, it can no longer see the original volume.

Weird.