Subscribe

Snap creator failed after vol rename

[ Edited ]

Hello Community,

     I was able to create a job with vibe plugins and mysql. All work fine on the first use, but i was forced to do a vol rename on datastore where resides VM.

Since i do that the job failed, normal, but even if I change the name of the volume in the volume tab, the name remains the same flight.

I create another job, restart snap creator services, nothing change.

Original vol name is "IS_SRM", the new vol name is "IS_srm". Perhaps uppercase to lowercase trouble something....

Best,

FDE

Behind the debug log off the job :

########## Detecting Data ONTAP mode for auto ##########

[2013-06-20 17:58:00,830] INFO: STORAGE-03031: System version details of [pa-ofc-netapp-2].

[2013-06-20 17:58:00,830] DEBUG: <system-get-version/>

[2013-06-20 17:58:00,830] DEBUG: <system-get-ontapi-version/>

[2013-06-20 17:58:00,830] INFO: STORAGE-03032: System version details of [pa-ofc-netapp-2] finished successfully.

########## Agent validation ##########

[2013-06-20 17:58:01,101] INFO: Agent validation completed successfuly for agent sugar-uat.ullink.lan:9090

########## Plugin validation ##########

[2013-06-20 17:58:01,117] INFO: Plugin validation completed successfuly for plugin vibe

########## PRE APPLICATION QUIESCE COMMANDS ##########

[2013-06-20 17:58:01,126] INFO: Pre application quiesce commands are not defined

########## PRE APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY  ##########

########## Application Discovery ##########

[2013-06-20 17:58:22,785] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] vibe::setENV finished successfully

[2013-06-20 17:58:22,785] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking if VIBE pre-requisites already run (function: discover) ....

[2013-06-20 17:58:22,785] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Executing VIBE configuration.

[2013-06-20 17:58:22,785] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Initializing connectivity to vCenter(s) and storage controller(s)/vserver(s) ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Converting vCenter hostname(s) to IP address(es) ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Attempting to ping vCenter server xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Ping of vCenter server successful.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Logging into vCenter server xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] vCenter server login successful.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Updating vCenter name/object for VM sugar-uat ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Attempting to ping storage controller/vserver pa-ofc-netapp-2 ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Ping of storage controller/vserver pa-ofc-netapp-2 successful.

[2013-06-20 17:58:22,786] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Updating NTAP_USERS storage controller/vserver pa-ofc-netapp-2 with IP address xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Creating login to storage controller/vserver xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Setting transport port for storage controller/vserver xxx.xxx.xxx.xxx to 80.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] 7-Mode ONTAP detected for xxx.xxx.xxx.xxx.

[2013-06-20 17:58:22,786] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking if controller xxx.xxx.xxx.xxx is a vFiler or not (API rsh-get-stats call) ...

[2013-06-20 17:58:22,786] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting IP address information for controller xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found interface-config-info structures.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.

[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found v4-primary-address structure.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for address string ...

[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address (v4-primary-address) xxx.xxx.xxx.xxx found.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Adding IP address xxx.xxx.xxx.xxx for storage controller/vserver xxx.xxx.xxx.xxx...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found v4-primary-address structure.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for address string ...

[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address (v4-primary-address) xxx.xxx.xxx.xxx found.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found v4-primary-address structure.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for address string ...

[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address (v4-primary-address) xxx.xxx.xxx.xxxfound.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Adding IP address xxx.xxx.xxx.xxx for storage controller/vserver xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Storage controller/vserver login successful.

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting vSphere and storage configuration data ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting datacenter information ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found 3 Datacenter(s).

[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting list of VirtualMachine objects planned for snapshots ...

[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Updating VirtualMachine objects planned for snapshots ...

[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for VirtualMachine object named sugar-uat ...

[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Saving VM named sugar-uat.

[2013-06-20 17:58:22,788] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collection of VirtualMachine objects successful.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Parsing list of VMs for list of datastore names ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] VM sugar-uat stored on datastore IS_srm ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for Datastore IS_srm ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Requested Datastore (IS_srm) is available.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting LUN information ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Already collected LUN serial numbers for storage controller/vserver xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for matching disk name naa.60a9800042436f554d244372504e7371 ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking host system sunrise.xxx.lan ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Name = naa.60a9800042436f554d244372504e7371, UUID = 42436f554d244372504e7371.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found LUN with UUID 42436f554d244372504e7371, host xxx.xxx.xxx.xxx, path /vol/IS_SRM/IS_1.

[2013-06-20 17:58:22,788] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting VM information on VMFS Datastore IS_srm.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking to ensure our list of storage controllers/vservers is correct for all Datastores ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Saving name:volume pair entry for VOLUMES named pa-ofc-netapp-2:IS_SRM.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Setting VOLUMES entry for pa-ofc-netapp-2 to IS_SRM.

[2013-06-20 17:58:22,788] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Setting VOLUMES configuration variable for Snap Creator to "pa-ofc-netapp-2:IS_SRM".

[2013-06-20 17:58:22,929] INFO: Updating configuration parameter VOLUMES from plugin vibe

[2013-06-20 17:58:22,929] DEBUG: Parameter VOLUMES set to pa-ofc-netapp-2:IS_SRM

########## Application Discovery finished successfully ##########

########## Application Quiesce ##########

[2013-06-20 17:58:23,286] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] mysql::setENV finished successfully

[2013-06-20 17:58:23,286] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing databases

[2013-06-20 17:58:23,286] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing database sugar_uat

[2013-06-20 17:58:23,286] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Connection to sugar_uat successfully established

[2013-06-20 17:58:23,286] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Executing sql command 'flush tables with read lock' for database sugar_uat

[2013-06-20 17:58:23,286] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Executing sql command 'flush logs' for database sugar_uat

[2013-06-20 17:58:23,287] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing database sugar_uat finished successfully

[2013-06-20 17:58:23,287] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing databases finished successfully

########## Application Quiesce finished successfully ##########

########## Application Quiesce ##########

[2013-06-20 17:58:35,906] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] vibe::setENV finished successfully

[2013-06-20 17:58:35,906] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking if VIBE pre-requisites already run (function: quiesce) ....

[2013-06-20 17:58:35,906] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Discovery already completed -- not re-running prerequisites.

[2013-06-20 17:58:35,906] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Creating vSphere snapshots (if applicable) ...

[2013-06-20 17:58:35,906] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Creating snapshot for VM sugar-uat ...

[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking power state of VM sugar-uat ...

[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking snapshot capability of VM sugar-uat ...

[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Removing leftover snapshots for VM sugar-uat ...

[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Creating snapshot of VM sugar-uat (attempt #1) ...

[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Creation of snapshot for VM sugar-uat successful.

[2013-06-20 17:58:35,907] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Snapshot creation process completed successfully.

########## Application Quiesce finished successfully ##########

########## POST APPLICATION QUIESCE COMMANDS ##########

[2013-06-20 17:58:35,910] INFO: Post application quiesce commands are not defined

########## POST APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY  ##########

########## PRE NTAP COMMANDS ##########

[2013-06-20 17:58:35,911] INFO: Pre ntap commands are not defined

########## PRE NTAP COMMANDS FINISHED SUCCESSFULLY ##########

########## Generating Info ASUP on pa-ofc-netapp-2 ##########

[2013-06-20 17:58:35,920] INFO: STORAGE-01001: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0.0 Backup for scf_sugar_uat ACTION: backup POLICY: hourly Plugin: vibe Supported Volumes: IS_SRM, Started], level [INFO], hostname [w2k8R2-netapp [sugar-uat.xxx.lan:9090]].

[2013-06-20 17:58:35,920] DEBUG: <ems-autosupport-log>

<computer-name>w2k8R2-netapp [sugar-uat.xxx.lan:9090]</computer-name>

<event-id>0</event-id>

<event-source>SNAPCREATOR</event-source>

<app-version>Snap Creator Framework 4.0.0</app-version>

<category>Backup Started</category>

<event-description>INFO: Snap Creator Framework 4.0.0 Backup for scf_sugar_uat ACTION: backup POLICY: hourly Plugin: vibe Supported Volumes: IS_SRM, Started</event-description>

<log-level>6</log-level>

<auto-support>false</auto-support>

</ems-autosupport-log>

[2013-06-20 17:58:35,921] INFO: STORAGE-01002: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0.0 Backup for scf_sugar_uat ACTION: backup POLICY: hourly Plugin: vibe Supported Volumes: IS_SRM, Started], level [INFO], hostname [w2k8R2-netapp [sugar-uat.xxx.lan:9090]] finished successfully.

[2013-06-20 17:58:35,921] INFO: ASUP finished successfully on pa-ofc-netapp-2

########## Running Snapshot copy Rename on Primary devices ##########

[2013-06-20 17:58:35,929] INFO: Skipping Snapshot copy rename

########## File system plug-in not defined. Skipping file system quiesce ##########

########## SNAPSHOT CREATE COMMANDS ##########

########## Snapshot copy create commands finished successfully ##########

[2013-06-20 17:58:35,933] INFO: Skipping SIS clone backup.

[2013-06-20 17:58:35,934] INFO: Skipping consistency group Snapshot copy

########## Taking Snapshot copy on Primary pa-ofc-netapp-2:IS_SRM ##########

[2013-06-20 17:58:35,945] INFO: STORAGE-02007: Creating Snapshot copy [scf_sugar_uat-hourly_20130620175800] on volume [IS_SRM].

[2013-06-20 17:58:35,945] ERROR: com.netapp.snapcreator.storage.executor.ZapiExecutorException: netapp.manage.NaAPIFailedException: The specified volume IS_SRM does not exist. (errno=13040)

at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:62)

at com.netapp.snapcreator.storage.api.ontap.Ontap7ModeApi.snapshotCreate(Ontap7ModeApi.java:137)

at com.netapp.snapcreator.storage.StorageCoreImpl.snapshotCreate(StorageCoreImpl.java:800)

at com.netapp.snapcreator.workflow.task.SnapShot.execute(SnapShot.java:83)

at com.netapp.snapcreator.workflow.impl.SCTaskCallable.call(SCTaskCallable.java:48)

at com.netapp.snapcreator.workflow.impl.SCTaskCallable.call(SCTaskCallable.java:20)

at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Caused by: netapp.manage.NaAPIFailedException: The specified volume IS_SRM does not exist. (errno=13040)

at netapp.manage.NaServer.invokeElem(NaServer.java:671)

at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:53)

... 10 more

[2013-06-20 17:58:35,945] ERROR: STORAGE-02009: Creating Snapshot copy [scf_sugar_uat-hourly_20130620175800] on volume [IS_SRM] failed with error [netapp.manage.NaAPIFailedException: The specified volume IS_SRM does not exist. (errno=13040)].

########## File system plug-in not defined. Skipping file system unquiesce ##########

########## Application Unquiesce ##########

[2013-06-20 17:58:40,835] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] vibe::setENV finished successfully

[2013-06-20 17:58:40,836] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking if VIBE pre-requisites already run (function: unquiesce) ....

[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Discovery already completed -- not re-running prerequisites.

[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Removing snapshots (if applicable)

[2013-06-20 17:58:40,837] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking power state of VM sugar-uat ...

[2013-06-20 17:58:40,837] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking snapshot capability of VM sugar-uat ...

[2013-06-20 17:58:40,837] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Removing snapshot for VM sugar-uat ...

[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Removing VM snapshot named sc_vApp_snapshot for VM sugar-uat (1 found).

[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Snapshot removed for VM sugar-uat.

[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Snapshot removal process completed successfully.

########## Application Unquiesce finished successfully ##########

########## Application Unquiesce ##########

[2013-06-20 17:58:41,155] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] mysql::setENV finished successfully

[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing databases

[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing database sugar_uat

[2013-06-20 17:58:41,155] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Connection to sugar_uat established successfully

[2013-06-20 17:58:41,155] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Executing sql command 'unlock tables' for database sugar_uat

[2013-06-20 17:58:41,155] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Disconnecting from database sugar_uat

[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing database sugar_uat finished successfully

[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing databases finished successfully

########## Application Unquiesce finished successfully ##########

########## Snap Creator Framework 4.0.0 failed ##########

[2013-06-20 17:58:41,156] INFO: Pre Exit commands are not defined. Skipping !

Re: Snap creator failed after vol rename

I think even though you changed the volume name, the datastore in vCenter still points to the old volume name.

I would guess that you need to fix the datastore in vCenter and then try again.

Kapil

Snap creator failed after vol rename

Hi Kapil,

     I already done this, but no change.

FDE

Re: Snap creator failed after vol rename

It is highly unlikey because Vibe is performing auto discovey, in the below logs we see that it found that VM sugar-uat is stored on datastore IS_srm

and afterwords it tries to match the lun UUID collected from vCenter with the list from the controller and it finds the matching UUID(42436f554d244372504e7371) entry for /vol/IS_SRM/IS_1.

So there are two possibilities:

1) Controller is returning stale UUID

2) vCenter is returning stale UUID

Can you match them manually and see ?

Kapil

VM sugar-uat stored on datastore IS_srm ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for Datastore IS_srm ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Requested Datastore (IS_srm) is available.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting LUN information ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Already collected LUN serial numbers for storage controller/vserver xxx.xxx.xxx.xxx ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for matching disk name naa.60a9800042436f554d244372504e7371 ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking host system sunrise.xxx.lan ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Name = naa.60a9800042436f554d244372504e7371, UUID = 42436f554d244372504e7371.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found LUN with UUID 42436f554d244372504e7371, host xxx.xxx.xxx.xxx, path /vol/IS_SRM/IS_1.

[2013-06-20 17:58:22,788] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting VM information on VMFS Datastore IS_srm.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking to ensure our list of storage controllers/vservers is correct for all Datastores ...

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Saving name:volume pair entry for VOLUMES named pa-ofc-netapp-2:IS_SRM.

[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Setting VOLUMES entry for pa-ofc-netapp-2 to IS_SRM.

[2013-06-20 17:58:22,788] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Setting VOLUMES configuration variable for Snap Creator to "pa-ofc-netapp-2:IS_SRM".

[2013-06-20 17:58:22,929] INFO: Updating configuration parameter VOLUMES from plugin vibe

[2013-06-20 17:58:22,929] DEBUG: Parameter VOLUMES set to pa-ofc-netapp-2:IS_SRM

Re: Snap creator failed after vol rename

One question:

Do you have SC agent to backup this VM installed in the same VM i.e. sugar-uat?

If yes, I would not reccomend that as you are trying to backup the VM from within itself.

Kapil

Snap creator failed after vol rename

Yes, i use the same scAgent for both vibe and mysql plugin.

So, is it require to have another scAgent to manage vibe backup ? where is it the best place to installe scAgent ? Vcenter its self ? another Windows VM ?

Thx

FDE

Re: Snap creator failed after vol rename

You can install it anywhere from where both controller and vCenter can be reached.

It could be any machine, vCenter, SC server or any other machine but not the VM itself.

If your VM crashes your agent is gone too and then you would need to use another SC agent.

I am assuming you are using 4.0, is that correct?

Kapil

Snap creator failed after vol rename

Yes i'm use 4.0, and i try to install on the scServer  but it seems that it's not possible to install both scServer And ScAgent on same server.

The installation Wizard propose only uninstall scServer, not install scAgent...

FDE

Re: Snap creator failed after vol rename

I opened issue 7 for the VIBE plugin for this same problem. Restarting the agent after the rename fixes it up for me.