3par Snapshots left behind

VMware specific discussions

3par Snapshots left behind

Veeam Logoby michaelryancook » Thu Jan 07, 2016 11:33 pm

Hello and TIA. I plan on opening a ticket to determine why some Veeam created snapshots are left behind but in the meantime I need to know if they are safe to delete. My understanding is that they are but I do have not used 3par enough to be confident. I have a number of VVOLs with copies left behind. They each have zero exports. If I understand it correctly they are a point in time and can be deleted. Can anyone please give me some advice on this?

As well, Veeam B&R is unaware of the snapshots and shows a snapshot count of zero on all these volumes.

Michael
michaelryancook
Expert
 
Posts: 113
Liked: 14 times
Joined: Tue Nov 26, 2013 6:13 pm
Full Name: Michael Cook

Re: 3par Snapshots left behind

Veeam Logoby Shestakov » Fri Jan 08, 2016 5:38 am

Hello Michael,
The behavior you`ve described is not expected, so contacting the Veeam support is what you need to do here. Once you do, please provide your support case number.
You can also review the topic where your post has been merged to for more info.
Thanks!
Shestakov
Veeam Software
 
Posts: 4842
Liked: 393 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: 3par Snapshots left behind

Veeam Logoby michaelryancook » Fri Jan 08, 2016 5:22 pm

Thanks Nikita. I have opened a ticket 01310630. I will try to update here with the results. Am I missing something though as I haven't noticed my posts being merged yet?

Thanks.
michaelryancook
Expert
 
Posts: 113
Liked: 14 times
Joined: Tue Nov 26, 2013 6:13 pm
Full Name: Michael Cook

Re: 3par Snapshots left behind

Veeam Logoby v.Eremin » Fri Jan 08, 2016 5:30 pm

It's been merged by mistake to the discussion talking about different issue. Now, we've returned everything back. Thanks.
v.Eremin
Veeam Software
 
Posts: 13255
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: 3par Snapshots left behind

Veeam Logoby michaelryancook » Tue Jan 12, 2016 9:38 pm

The response I received was "Since these snapshots don't show up in Veeam, you can delete them manually from the HP 3PAR console. This might be caused when Veeam tries to remove a storage snapshot when the SAN is too busy processing other requests. If the snapshot removal fails for this reason, Veeam doesn't display any error message."

We have removed the orphaned snapshots and will try to monitor going forward to determine if we can determine a root cause.
michaelryancook
Expert
 
Posts: 113
Liked: 14 times
Joined: Tue Nov 26, 2013 6:13 pm
Full Name: Michael Cook


Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 20 guests