This post is more than 5 years old

1 Rookie

 • 

29 Posts

23053

July 2nd, 2014 00:00

Delete PS snapshots automatically - How to?

Hi, I've got a three nodes Hyper-V 2012 cluster connected to an iSCSI SAN, a PS6210XV.

Currently I'm backing up the vms using Microsoft DPM 2012, using EQL hw provider.

The backups are running fine and fast, but every time the DPM runs a backup, the PS generates a SAN snapshot of the volume containing the vm. When the backup completes however, the snapshot is not deleted, but remains online until someone deletes it.

How can I have my snapshots automatically deleted after a backup job?

I don't want to use the Hyper-V software provider to do my backups.

Thank you :) .

1 Rookie

 • 

51 Posts

July 2nd, 2014 03:00

I'm using the latest DPM wit Hyper-V on a 2012 R2 Cluster (with VMM) and the snapshots are deleted right after the backup process.

You should check the ASM logs on the host and the event/audit logs on the array for any errors.

It shows like this in the eventlog of the array:

Severity  Date and Time        Member  ID               Message                                                                                                                                                                                                                                                                                      

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

Info     01.07.2014 18:02:23  ps1     8.2.5            Successfully deleted snapshot s1-hv-vm2-2014-07-01-18:00:30.41.1.                                                                                                                                                                                                                            

Info     01.07.2014 18:02:23  ps1     7.2.51           Snapshot s1-hv-vm2-2014-07-01-18:00:30.41.1 was set offline by the administrator.                                                                                                                                                                                                            

Info     01.07.2014 18:02:23  ps1     7.2.15 | 7.2.17  iSCSI session to target '192.168.55.11:3260, iqn.2001-05.com.equallogic:0-8a0906-b1e3f4402-84f0015c7a253b2d-s1-hv-vm2-2014-07-01-18:00:30.41.1' from initiator '192.168.55.110:56840, iqn.1991-05.com.microsoft:hv2.saxsys.de' was closed. | Logout request was received from the initiator.  

Info     01.07.2014 18:00:32  ps1     7.2.14           iSCSI login to target '192.168.55.11:3260, iqn.2001-05.com.equallogic:0-8a0906-b1e3f4402-84f0015c7a253b2d-s1-hv-vm2-2014-07-01-18:00:30.41.1' from initiator '192.168.55.110:56840, iqn.1991-05.com.microsoft:hv2.saxsys.de' successful, using Jumbo Frame length.                            

Info     01.07.2014 18:00:30  ps1     7.2.52           Snapshot s1-hv-vm2-2014-07-01-18:00:30.41.1 was set online by the administrator.                                                                                                                                                                                                              

Info     01.07.2014 18:00:30  ps1     8.2.4            Successfully created snapshot s1-hv-vm2-2014-07-01-18:00:30.41.1                                                                                                                                                                                                                              

1 Rookie

 • 

29 Posts

July 2nd, 2014 04:00

I found this on Hyper-V event log:

"Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}. Routine details could not free LUN [hr = 0x80042306, The shadow copy provider had an error. Check the System and Application event logs for more information.

]. "

Any clue?

1 Rookie

 • 

29 Posts

July 2nd, 2014 09:00

Hi, many thanks.

With an upgrade from 4.6 to 4.7 the problem has been fixed (I'm running a 7.x fw).

Thanks again.

Top