My support case ID is 02205329.
I can not understand why VM snapshot needs to be taken when storage integration is enabled with VM quiescence and application-aware processing disabled.
This is causing problems in my production SQL servers (service disconnection).
My production datastores sit in NetApp and I am backing up to Hitachi HDS, both using SAN.
I have configured DirectSAN and Storage Integration.
Somehow, a VM snapshot needs to be taken and commit before the storage snapshot is read.
I hope this VM snapshot can be eliminate away since i am reading the data from the storage snapshot.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jul 03, 2017 12:20 pm
- Full Name: Raven Tan
- Contact:
-
- Product Manager
- Posts: 20405
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: VM Snapshot taken even though Storage Integration is wor
VM snapshot is needed to be able to use CBT. Check this section of the User Guide for more detailed description of the process. Thanks!
-
- Veeam Software
- Posts: 219
- Liked: 111 times
- Joined: Jun 29, 2015 9:21 am
- Full Name: Michael Paul
- Contact:
Re: VM Snapshot taken even though Storage Integration is wor
Hi,
If you're having problems with prolonged snapshots (I'm assuming they're prolonged as SQL seems to handle snapshots fairly well). What vSphere version are you on? I used to have stun problems until ESXi 6 and now people don't notice when the backups kick in.
If you're having problems with prolonged snapshots (I'm assuming they're prolonged as SQL seems to handle snapshots fairly well). What vSphere version are you on? I used to have stun problems until ESXi 6 and now people don't notice when the backups kick in.
-------------
Michael Paul
Veeam Data Cloud: Microsoft 365 Solution Engineer
Michael Paul
Veeam Data Cloud: Microsoft 365 Solution Engineer
Who is online
Users browsing this forum: Amazon [Bot], BostjanUNIJA and 54 guests