Comprehensive data protection for all workloads
- Posts: 125
- Liked: 2 times
- Joined: Mar 23, 2009 4:44 pm
- Full Name: Matt
I run Veeam on a Windows 2003 x86 system. I learned a valuable lesson the other day, that if I plan to take down half the SAN fabric for maintenance, it is best to stop all Veeam jobs beforehand, because even though my MPIO driver did recognize the fabric fail and switched over, there was enough of a pause that it caused consolidated backup snapshots on currently being backed up VM's to get stuck. I had to go back and manually remove them (even restart the management services on one ESX host to get it unstuck).
Dependant on your Veeam OS, SAN driver and probably version of vSphere, I'm sure your mileage may vary.
I'm not complaining, just wanted to share so that you think of that before you mess with your SAN
- Product Manager
- Posts: 25048
- Liked: 2137 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Matt, thanks for the tip! And if you happen to have hidden snapshots after this mess, Veeam Monitor can help to identify them
Users browsing this forum: EdgarRicharte, Google [Bot] and 65 guests