Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

Mirny

1 Message

1546

November 10th, 2012 02:00

Replication manager does not unmout a replica after job copletion

Hello,

Replication manager does not unmount a snapview replica from a backup server after a backup job has completed.

The job log is as follows:

10.11.2012 10:40:33 pknbck01 Replica 10.11.2012 10:40:33 created from application set PKNFS01-VOLUME-D, job PKNFS01-VOLUME-D-SNAP by Administrator.

10.11.2012 10:40:33 pknbck01 Starting Replication of [application set:PKNFS01-VOLUME-D / job:PKNFS01-VOLUME-D-SNAP] at time 10.11.2012 10:40:33.

10.11.2012 10:40:33 pknbck01 This Replication uses array resident consistent split technology

10.11.2012 10:40:33 pknbck01 This operation can take a long time. Please be patient.

10.11.2012 10:41:25 PKNFS01 102395 INFORMATION: Combination of luns in MV/A and MV/S sessions in the same appset are not allowed.One of the Source Lun is in MV/S session.Ensure that all the other luns in the appset are in MV/S sessions.

10.11.2012 10:41:27 pknbck01 001564 INFORMATION: Need storage for 1 source device residing on clariion CKM00103000092.

10.11.2012 10:41:27 pknbck01 001566 INFORMATION: Storage Policy will consider 2 device(s) from the entire Replication Manager database.

10.11.2012 10:41:27 pknbck01 001568 INFORMATION: After removing 0 in use devices, 0 devices that are not visible on the mount host and 0 devices that are the wrong storage type, there are now 2 devices being considered for this replica.

10.11.2012 10:41:28 pknbck01 Original device clariion_CKM00103000092_0050 is paired with replication device clariion_CKM00103000092_pknbck01-0050-5125.

10.11.2012 10:41:28 PKNFS01 Replication validation --Begin.

10.11.2012 10:41:28 PKNFS01 100692 INFORMATION: Not running user scripts, skip checking user credentials

10.11.2012 10:41:28 PKNFS01 Replication validation --End.

10.11.2012 10:41:28 PKNFS01 Replication validation The volumes for this replication are all on basic disk.

10.11.2012 10:41:32 pknbck01 Verifying software packages and versions. This may take a few moments ...

10.11.2012 10:41:32 pknbck01 Finished verifying software packages and versions.

10.11.2012 10:41:32 PKNFS01 Starting storage preparation.

10.11.2012 10:41:42 PKNFS01 Checking to make sure we can create CLARiiON snapshots for this replica.

10.11.2012 10:41:59 PKNFS01 Starting to copy replication data.

10.11.2012 10:42:04 PKNFS01 Beginning freeze of D:\ for NTFilesystem agent.

10.11.2012 10:42:04 PKNFS01 Completing freeze of D:\ for NTFilesystem agent.

10.11.2012 10:42:04 PKNFS01 The users application is in an appropriate state to support replication.

10.11.2012 10:42:04 PKNFS01 Creating CLARiiON replica snapshots.

10.11.2012 10:42:06 PKNFS01 Beginning thaw of D:\ for NTFilesystem agent.

10.11.2012 10:42:06 PKNFS01 Completing thaw of D:\ for NTFilesystem agent.

10.11.2012 10:42:07 PKNFS01 The users application has been taken out of the state used for replication.

10.11.2012 10:42:17 PKNFS01 File C:\Windows\TEMP\3ad644fa-7320-438c-aa79-4964d5b01091 has been saved to the server for future mount or restore of this replica.

10.11.2012 10:42:17 pknbck01 Replication of [application set:PKNFS01-VOLUME-D / job:PKNFS01-VOLUME-D-SNAP] successfully completed at time 10.11.2012 10:42:17.

10.11.2012 10:42:19 pknbck01 Starting mount of the replica created at 10.11.2012 10:42:10 from application set PKNFS01-VOLUME-D, at time 10.11.2012 10:42:19 on host pknbck01.

10.11.2012 10:42:37 pknbck01 Mount validation --Begin.

10.11.2012 10:42:37 pknbck01 Mount validation --End.

10.11.2012 10:42:37 pknbck01 Verifying software packages and versions. This may take a few moments ...

10.11.2012 10:42:37 pknbck01 Finished verifying software packages and versions.

10.11.2012 10:42:42 pknbck01 000162 INFORMATION: Retrieving file RM_DB_Metadata as part of the replication.

10.11.2012 10:42:42 pknbck01 000162 INFORMATION: Retrieving file C:\Windows\TEMP\RM_VSS_BCD2012111094237430.xml as part of the replication.

10.11.2012 10:42:42 pknbck01 Acquired resources for mount, restore, or unmount operation.

10.11.2012 10:42:42 pknbck01 Beginning to prepare recovery of D:\ for NTFilesystem agent.

10.11.2012 10:43:11 pknbck01 Importing VSS shadow copy, this operation can take a long time. Please be patient.

10.11.2012 10:44:16 pknbck01 All storage device(s) enabled.

10.11.2012 10:44:23 pknbck01 Imported VSS shadow copy.

10.11.2012 10:44:34 pknbck01 Performing a read-only mount.

10.11.2012 10:44:34 pknbck01 Mounted file system C:\RM_Mounts\PKNFS01_D_Drive_Snapshot\Ddrive\.

10.11.2012 10:44:39 pknbck01 Shared resources are now available for another mount restore or unmount operation.

10.11.2012 10:44:39 pknbck01 Beginning validation of replica of D:\ for NTFilesystem agent.

10.11.2012 10:44:39 pknbck01 File C:\RM_Mounts\PKNFS01_D_Drive_Snapshot Job\RM_DB_Metadata saved as part of mount.

10.11.2012 10:44:39 pknbck01 File C:\RM_Mounts\PKNFS01_D_Drive_Snapshot Job\RM_VSS_BCD saved as part of mount.

10.11.2012 10:44:39 pknbck01 Beginning recover of D:\ for NTFilesystem agent.

10.11.2012 10:44:40 pknbck01 Replica 10.11.2012 10:42:10 mounted from application set PKNFS01-VOLUME-D to host pknbck01 by Administrator.

10.11.2012 10:44:40 pknbck01 Mount of the replica created at 10.11.2012 10:42:10 from application set PKNFS01-VOLUME-D, successfully completed at time 10.11.2012 10:44:40.

10.11.2012 10:44:45 PKNFS01 The users application can now resume normal operation.

10.11.2012 10:44:45 PKNFS01 Completing replication of D:\ for NTFilesystem agent.

10.11.2012 10:44:45 PKNFS01 Post Replica Activity complete.

10.11.2012 10:44:45 pknbck01 Starting to run program C:\RM_Scripts\Test_Job.cmd on replica created at 10.11.2012 10:42:10, on machine pknbck01 at time 10.11.2012 10:44:45.

10.11.2012 10:44:46 pknbck01 100690 INFORMATION: 'C:\RM_Scripts\Test_Job.cmd' exists and has read privilege

10.11.2012 10:44:46 pknbck01 100690 INFORMATION:

10.11.2012 10:44:46 pknbck01 100690 INFORMATION: C:\Windows\system32>"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" c:\RM_Scripts\TEST.ps1

10.11.2012 10:46:07 pknbck01 100690 INFORMATION:

10.11.2012 10:46:07 pknbck01 100690 INFORMATION: Name                          JobStatus      JobType StartTime EndTime

10.11.2012 10:46:07 pknbck01 100690 INFORMATION: ----                          ---------      ------- --------- -------

10.11.2012 10:46:07 pknbck01 100690 INFORMATION: Full Backup DB Bank-Full Ba... Succeeded      Backup     10.11.2... 10.11.2...

10.11.2012 10:46:07 pknbck01 100690 INFORMATION:

10.11.2012 10:46:07 pknbck01 100690 INFORMATION:

The backup job has ended but the replica stays mounted thus preventing recurring the job next day.

This had been working fine till I upgraded backup software Symantec Backup Exec 2010 to 2012 version. The change is in the way the backup job is called from Replication manager. An exe file used to be called with BE 2010, now a power shell script is called with BE 2012.

What can be the root cause of this behavior?

Thank anyone for an advice.

Mirek Novotny

FoolInTheRain

123 Posts

November 11th, 2012 10:00

Not sure if this will help, but I found this in the knowledge base (emc166669) that suggests there are issues with Powershell. I suggest making sure your new script at least have a null returned. in my mind, your script is running, but RM does not know it's done... (see info below for the solution from the above mentioned article)

The execution of PowerShell commands scripts are typically more sensitive to command script file location and signed security of the command line.

  1. Make sure to always explicitly define the full path name when calling the PowerShell command file.

    For example, in batch file C:\PowerScript.bat:

    powershell -command C:\PshellCommands.ps1 


    For example, in PowerShell Command file C:\PshellCommands.ps1
      
  2. Add a line at the beginning of the PowerShell script to relax the execution security of PowerShell by adding the following line as the first PowerShell command:

    powershell -command set-executionpolicy unrestricted

    For example:

    C:\PowerScript.bat

    powershell -command set-executionpolicy unrestricted
    powershell -command C:\PshellCommands.ps1

     
  3. To ensure correct termination of the PowerShell session, ensure to suffix " calling of the PowerShell command from the batch file.

    For example:

    C:\PowerScript.bat

    powershell -command set-executionpolicy unrestricted
    powershell -command C:\PshellCommands.ps1

Let me know if this helps!

Was this post helpful?

View All

No Events found!

Top