topic Re: Snap creator failed after vol rename in Data Protection https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36864#M1835 <HTML><HEAD></HEAD><BODY><P>One question:</P><P>Do you have SC agent to backup this VM installed in the same VM i.e. <SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">sugar-uat</SPAN>?</P><P></P><P>If yes, I would not reccomend that as you are trying to backup the VM from within itself.</P><P></P><P>Kapil</P></BODY></HTML> Fri, 21 Jun 2013 08:03:49 GMT Arora_Kapil 2013-06-21T08:03:49Z Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36844#M1831 <HTML><HEAD></HEAD><BODY><P>Hello Community,</P><P></P><P>&nbsp;&nbsp;&nbsp;&nbsp; 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.</P><P>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.</P><P>I create another job, restart snap creator services, nothing change.</P><P></P><P>Original vol name is "IS_SRM", the new vol name is "IS_srm". Perhaps uppercase to lowercase trouble something....</P><P></P><P>Best,</P><P></P><P>FDE</P><P></P><P></P><P>Behind the debug log off the job :</P><P></P><P class="p1">########## Detecting Data ONTAP mode for auto ##########</P><P class="p1">[2013-06-20 17:58:00,830] INFO: STORAGE-03031: System version details of [pa-ofc-netapp-2].</P><P class="p1">[2013-06-20 17:58:00,830] DEBUG: &lt;system-get-version/&gt;</P><P class="p2"></P><P class="p1">[2013-06-20 17:58:00,830] DEBUG: &lt;system-get-ontapi-version/&gt;</P><P class="p2"></P><P class="p1">[2013-06-20 17:58:00,830] INFO: STORAGE-03032: System version details of [pa-ofc-netapp-2] finished successfully.</P><P class="p1">########## Agent validation ##########</P><P class="p1">[2013-06-20 17:58:01,101] INFO: Agent validation completed successfuly for agent sugar-uat.ullink.lan:9090</P><P class="p1">########## Plugin validation ##########</P><P class="p1">[2013-06-20 17:58:01,117] INFO: Plugin validation completed successfuly for plugin vibe</P><P class="p1">########## PRE APPLICATION QUIESCE COMMANDS ##########</P><P class="p1">[2013-06-20 17:58:01,126] INFO: Pre application quiesce commands are not defined</P><P class="p1">########## PRE APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY&nbsp; ##########</P><P class="p1">########## Application Discovery ##########</P><P class="p1">[2013-06-20 17:58:22,785] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] vibe::setENV finished successfully</P><P class="p1">[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) ....</P><P class="p1">[2013-06-20 17:58:22,785] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Executing VIBE configuration.</P><P class="p1">[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) ...</P><P class="p1">[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) ...</P><P class="p1">[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 ...</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Ping of vCenter server successful.</P><P class="p1">[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 ...</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] vCenter server login successful.</P><P class="p1">[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 ...</P><P class="p1">[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 ...</P><P class="p1">[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.</P><P class="p1">[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 ...</P><P class="p1">[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 ...</P><P class="p1">[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.</P><P class="p1">[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.</P><P class="p1">[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) ...</P><P class="p1">[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 ...</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found interface-config-info structures.</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.</P><P class="p1">[2013-06-20 17:58:22,786] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found v4-primary-address structure.</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for address string ...</P><P class="p1">[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.</P><P class="p1">[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...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] IP address string not found.</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found v4-primary-address structure.</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for address string ...</P><P class="p1">[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.</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking interface-config-info object ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found v4-primary-address structure.</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for address string ...</P><P class="p1">[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.</P><P class="p1">[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 ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Storage controller/vserver login successful.</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting vSphere and storage configuration data ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting datacenter information ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Found 3 Datacenter(s).</P><P class="p1">[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 ...</P><P class="p1">[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Updating VirtualMachine objects planned for snapshots ...</P><P class="p1">[2013-06-20 17:58:22,787] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Looking for VirtualMachine object named sugar-uat ...</P><P class="p1">[2013-06-20 17:58:22,787] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Saving VM named sugar-uat.</P><P class="p1">[2013-06-20 17:58:22,788] INFO: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collection of VirtualMachine objects successful.</P><P class="p3">[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 ...</P><P class="p3">[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 ...</P><P class="p3">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for Datastore IS_srm ...</P><P class="p3">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Requested Datastore (IS_srm) is available.</P><P class="p3">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting LUN information ...</P><P class="p3">[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 ...</P><P class="p3">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for matching disk name naa.60a9800042436f554d244372504e7371 ...</P><P class="p3">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking host system sunrise.xxx.lan ...</P><P class="p3">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Name = naa.60a9800042436f554d244372504e7371, UUID = 42436f554d244372504e7371.</P><P class="p4">[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.</P><P class="p3">[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.</P><P class="p3">[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 ...</P><P class="p3">[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.</P><P class="p3">[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.</P><P class="p3">[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".</P><P class="p3">[2013-06-20 17:58:22,929] INFO: Updating configuration parameter VOLUMES from plugin vibe</P><P class="p3">[2013-06-20 17:58:22,929] DEBUG: Parameter VOLUMES set to pa-ofc-netapp-2:IS_SRM</P><P>########## Application Discovery finished successfully ##########</P><P>########## Application Quiesce ##########</P><P>[2013-06-20 17:58:23,286] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] mysql::setENV finished successfully</P><P>[2013-06-20 17:58:23,286] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing databases</P><P>[2013-06-20 17:58:23,286] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing database sugar_uat</P><P>[2013-06-20 17:58:23,286] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Connection to sugar_uat successfully established</P><P>[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</P><P>[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</P><P>[2013-06-20 17:58:23,287] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing database sugar_uat finished successfully</P><P>[2013-06-20 17:58:23,287] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Quiescing databases finished successfully</P><P>########## Application Quiesce finished successfully ##########</P><P>########## Application Quiesce ##########</P><P>[2013-06-20 17:58:35,906] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] vibe::setENV finished successfully</P><P>[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) ....</P><P>[2013-06-20 17:58:35,906] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Discovery already completed -- not re-running prerequisites.</P><P>[2013-06-20 17:58:35,906] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Creating vSphere snapshots (if applicable) ...</P><P>[2013-06-20 17:58:35,906] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Creating snapshot for VM sugar-uat ...</P><P>[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking power state of VM sugar-uat ...</P><P>[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking snapshot capability of VM sugar-uat ...</P><P>[2013-06-20 17:58:35,907] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Removing leftover snapshots for VM sugar-uat ...</P><P>[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) ...</P><P>[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.</P><P>[2013-06-20 17:58:35,907] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Snapshot creation process completed successfully.</P><P>########## Application Quiesce finished successfully ##########</P><P>########## POST APPLICATION QUIESCE COMMANDS ##########</P><P>[2013-06-20 17:58:35,910] INFO: Post application quiesce commands are not defined</P><P>########## POST APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY&nbsp; ##########</P><P>########## PRE NTAP COMMANDS ##########</P><P>[2013-06-20 17:58:35,911] INFO: Pre ntap commands are not defined</P><P>########## PRE NTAP COMMANDS FINISHED SUCCESSFULLY ##########</P><P>########## Generating Info ASUP on pa-ofc-netapp-2 ##########</P><P>[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]].</P><P>[2013-06-20 17:58:35,920] DEBUG: &lt;ems-autosupport-log&gt;</P><P>&lt;computer-name&gt;w2k8R2-netapp [sugar-uat.xxx.lan:9090]&lt;/computer-name&gt;</P><P>&lt;event-id&gt;0&lt;/event-id&gt;</P><P>&lt;event-source&gt;SNAPCREATOR&lt;/event-source&gt;</P><P>&lt;app-version&gt;Snap Creator Framework 4.0.0&lt;/app-version&gt;</P><P>&lt;category&gt;Backup Started&lt;/category&gt;</P><P>&lt;event-description&gt;INFO: Snap Creator Framework 4.0.0 Backup for scf_sugar_uat ACTION: backup POLICY: hourly Plugin: vibe Supported Volumes: IS_SRM, Started&lt;/event-description&gt;</P><P>&lt;log-level&gt;6&lt;/log-level&gt;</P><P>&lt;auto-support&gt;false&lt;/auto-support&gt;</P><P>&lt;/ems-autosupport-log&gt;</P><P></P><P></P><P>[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.</P><P>[2013-06-20 17:58:35,921] INFO: ASUP finished successfully on pa-ofc-netapp-2</P><P>########## Running Snapshot copy Rename on Primary devices ##########</P><P>[2013-06-20 17:58:35,929] INFO: Skipping Snapshot copy rename</P><P>########## File system plug-in not defined. Skipping file system quiesce ##########</P><P>########## SNAPSHOT CREATE COMMANDS ##########</P><P>########## Snapshot copy create commands finished successfully ##########</P><P>[2013-06-20 17:58:35,933] INFO: Skipping SIS clone backup.</P><P>[2013-06-20 17:58:35,934] INFO: Skipping consistency group Snapshot copy</P><P>########## Taking Snapshot copy on Primary pa-ofc-netapp-2:IS_SRM ##########</P><P>[2013-06-20 17:58:35,945] INFO: STORAGE-02007: Creating Snapshot copy [scf_sugar_uat-hourly_20130620175800] on volume [IS_SRM].</P><P>[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)</P><P>at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:62)</P><P>at com.netapp.snapcreator.storage.api.ontap.Ontap7ModeApi.snapshotCreate(Ontap7ModeApi.java:137)</P><P>at com.netapp.snapcreator.storage.StorageCoreImpl.snapshotCreate(StorageCoreImpl.java:800)</P><P>at com.netapp.snapcreator.workflow.task.SnapShot.execute(SnapShot.java:83)</P><P>at com.netapp.snapcreator.workflow.impl.SCTaskCallable.call(SCTaskCallable.java:48)</P><P>at com.netapp.snapcreator.workflow.impl.SCTaskCallable.call(SCTaskCallable.java:20)</P><P>at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)</P><P>at java.util.concurrent.FutureTask.run(Unknown Source)</P><P>at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)</P><P>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)</P><P>at java.lang.Thread.run(Unknown Source)</P><P>Caused by: netapp.manage.NaAPIFailedException: The specified volume IS_SRM does not exist. (errno=13040)</P><P>at netapp.manage.NaServer.invokeElem(NaServer.java:671)</P><P>at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:53)</P><P>... 10 more</P><P></P><P></P><P>[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)].</P><P>########## File system plug-in not defined. Skipping file system unquiesce ##########</P><P>########## Application Unquiesce ##########</P><P>[2013-06-20 17:58:40,835] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] vibe::setENV finished successfully</P><P>[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) ....</P><P>[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Discovery already completed -- not re-running prerequisites.</P><P>[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Removing snapshots (if applicable)</P><P>[2013-06-20 17:58:40,837] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking power state of VM sugar-uat ...</P><P>[2013-06-20 17:58:40,837] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Checking snapshot capability of VM sugar-uat ...</P><P>[2013-06-20 17:58:40,837] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Removing snapshot for VM sugar-uat ...</P><P>[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).</P><P>[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Snapshot removed for VM sugar-uat.</P><P>[2013-06-20 17:58:40,837] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Snapshot removal process completed successfully.</P><P>########## Application Unquiesce finished successfully ##########</P><P>########## Application Unquiesce ##########</P><P>[2013-06-20 17:58:41,155] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] mysql::setENV finished successfully</P><P>[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing databases</P><P>[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing database sugar_uat</P><P>[2013-06-20 17:58:41,155] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Connection to sugar_uat established successfully</P><P>[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</P><P>[2013-06-20 17:58:41,155] DEBUG: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Disconnecting from database sugar_uat</P><P>[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing database sugar_uat finished successfully</P><P>[2013-06-20 17:58:41,155] INFO: [sugar-uat.xxx.lan:9090 (4.0.0.1)] Unquiescing databases finished successfully</P><P>########## Application Unquiesce finished successfully ##########</P><P>########## Snap Creator Framework 4.0.0 failed ##########</P><P>[2013-06-20 17:58:41,156] INFO: Pre Exit commands are not defined. Skipping !</P></BODY></HTML> Thu, 05 Jun 2025 05:59:57 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36844#M1831 f_defrocourt 2025-06-05T05:59:57Z Re: Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36848#M1832 <HTML><HEAD></HEAD><BODY><P>I think even though you changed the volume name, the datastore in vCenter still points to the old volume name.</P><P>I would guess that you need to fix the datastore in vCenter and then try again.</P><P>Kapil</P></BODY></HTML> Fri, 21 Jun 2013 07:31:41 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36848#M1832 Arora_Kapil 2013-06-21T07:31:41Z Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36855#M1833 <HTML><HEAD></HEAD><BODY><P>Hi Kapil,</P><P></P><P>&nbsp;&nbsp;&nbsp;&nbsp; I already done this, but no change. </P><P></P><P>FDE</P></BODY></HTML> Fri, 21 Jun 2013 07:34:55 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36855#M1833 f_defrocourt 2013-06-21T07:34:55Z Re: Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36859#M1834 <HTML><HEAD></HEAD><BODY><P>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</P><P>and afterwords it tries to match the lun UUID collected from vCenter with the list from the controller and it finds the matching UUID(<SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">42436f554d244372504e7371</SPAN>) entry for <SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">/vol/IS_SRM/IS_1.</SPAN></P><P></P><P><SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">So there are two possibilities:</SPAN></P><P><SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">1) Controller is returning stale UUID </SPAN></P><P><SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">2) vCenter is returning stale UUID</SPAN></P><P></P><P><SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">Can you match them manually and see ?<BR /></SPAN></P><P><SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">Kapil<BR /></SPAN></P><P></P><P>VM sugar-uat stored on datastore IS_srm ...</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for Datastore IS_srm ...</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Requested Datastore (IS_srm) is available.</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Collecting LUN information ...</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[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 ...</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Searching for matching disk name naa.60a9800042436f554d244372504e7371 ...</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Checking host system sunrise.xxx.lan ...</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,788] DEBUG: [sugar-uat.ullink.lan:9090 (4.0.0.1)] Name = naa.60a9800042436f554d244372504e7371, UUID = 42436f554d244372504e7371.</P><P class="p4" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[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.</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[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.</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[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 ...</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[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.</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[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.</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[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".</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,929] INFO: Updating configuration parameter VOLUMES from plugin vibe</P><P class="p3" style="font-family: Arial, Helvetica, Verdana, sans-serif; color: #454545; background-color: #ffffff;">[2013-06-20 17:58:22,929] DEBUG: Parameter VOLUMES set to pa-ofc-netapp-2:IS_SRM</P></BODY></HTML> Fri, 21 Jun 2013 07:59:06 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36859#M1834 Arora_Kapil 2013-06-21T07:59:06Z Re: Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36864#M1835 <HTML><HEAD></HEAD><BODY><P>One question:</P><P>Do you have SC agent to backup this VM installed in the same VM i.e. <SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;">sugar-uat</SPAN>?</P><P></P><P>If yes, I would not reccomend that as you are trying to backup the VM from within itself.</P><P></P><P>Kapil</P></BODY></HTML> Fri, 21 Jun 2013 08:03:49 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36864#M1835 Arora_Kapil 2013-06-21T08:03:49Z Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36869#M1836 <HTML><HEAD></HEAD><BODY><P>Yes, i use the same scAgent for both vibe and mysql plugin.</P><P>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 ?</P><P></P><P>Thx </P><P></P><P>FDE</P></BODY></HTML> Fri, 21 Jun 2013 08:17:46 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36869#M1836 f_defrocourt 2013-06-21T08:17:46Z Re: Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36874#M1837 <HTML><HEAD></HEAD><BODY><P>You can install it anywhere from where both controller and vCenter can be reached.</P><P>It could be any machine, vCenter, SC server or any other machine but not the VM itself.</P><P>If your VM crashes your agent is gone too and then you would need to use another SC agent.</P><P>I am assuming you are using 4.0, is that correct?</P><P></P><P>Kapil</P></BODY></HTML> Fri, 21 Jun 2013 08:23:46 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36874#M1837 Arora_Kapil 2013-06-21T08:23:46Z Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36879#M1838 <HTML><HEAD></HEAD><BODY><P>Yes i'm use 4.0, and i try to install on the scServer&nbsp; but it seems that it's not possible to install both scServer And ScAgent on same server.</P><P>The installation Wizard propose only uninstall scServer, not install scAgent...</P><P></P><P>FDE</P></BODY></HTML> Fri, 21 Jun 2013 08:32:14 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36879#M1838 f_defrocourt 2013-06-21T08:32:14Z Re: Snap creator failed after vol rename https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36883#M1839 <HTML><HEAD></HEAD><BODY><P>I opened issue 7 for the VIBE plugin for this same problem. Restarting the agent after the rename fixes it up for me.</P></BODY></HTML> Tue, 23 Jul 2013 15:33:55 GMT https://community.netapp.com/t5/Data-Protection/Snap-creator-failed-after-vol-rename/m-p/36883#M1839 clilescapario 2013-07-23T15:33:55Z