Possibility of corruption from taking frequent snapshots?

VMware specific discussions

Possibility of corruption from taking frequent snapshots?

Veeam Logoby braddock » Wed Jun 08, 2016 7:35 pm

Hi,
Can taking a snapshot corrupt a VM at the vmdk level?

We have a linux VM that we want to replicate using Veeam to a new host every 30 mins, and I know there was an issue when Vsphere 6 first came out where taking a snapshot could corrupt the original VM. I think that's been fixed a long time ago thoguh.

Is there an increased chance of something going wrong the lower the replication interval of a job or does Veeam not touch the original VM's in any way?

Thanks.
braddock
Influencer
 
Posts: 13
Liked: 1 time
Joined: Tue May 10, 2016 3:06 pm

Re: Possibility of corruption from taking frequent snapshots

Veeam Logoby braddock » Thu Jun 09, 2016 2:53 pm

Hi again, let me rephrase this question - I've researched into this a bit more through the forum.

What is the safest way to backup a linux VM that runs with a transactional database (Progress) using with Veeam in 2016 ? The method that is least likely to 'break' the guest VM.



Gostev said in this post from 2009 : ( veeam-backup-replication-f2/transactionally-consistent-backups-t1557.html )

Gotev wrote:"The general consensus for hot backups of Linux VM is the following:
- If you are NOT running databases, mail servers or other transactional applications in VM - hot backups using "Enable VMware Tools Quiescence " is fine.
- If you are running transactional applications in VM - you should use pre-freeze and post-thaw scripts to stop/suspend and start/resume services before/after snapshot creation, as described here for instance."


Gostev also says on that thread that taking a backup without using the vmware tools quiescence will not affect the production VM (though this is in regards to Windows)

Gotev wrote:"3. Next is to run backup without VMware Tools quiescence. Backup will be crash consistent but often restorable, production VM will not be affected."



Now in our case we have tested the pre-freeze and post-thaw scripts and they do work but the impact on the system is that they freeze the Database for 5-15 seconds which is very noticeable to users during working hours. So we want to create crash-consistent backups instead (not using VMware tools quiescense OR the pre and post scripts) and depend on the built in application level database backups in the event of a restore.



So going back to my question above - can taking snapshot without using vmwaretools quiesce corrupt a PRODUCTION linux VM ?

Thanks
braddock
Influencer
 
Posts: 13
Liked: 1 time
Joined: Tue May 10, 2016 3:06 pm

Re: Possibility of corruption from taking frequent snapshots

Veeam Logoby braddock » Mon Jun 13, 2016 7:27 pm 1 person likes this post

No replies : ) I guess most people use windows on here with Veeam.


Anyway I worked this out myself and will put this here for anyone else who comes across this via a google search:

In certain situations, taking a snapshot with Vmware tools quiescence can and will crash the guest OS on occasion (if linux). We run RHEL 5 which has an incompatibility with vmware tools (vmtoolsd) - we can either upgrade Red Hat version or disable VMware tools on the guest OS. Unfortunately due to the application that we run upgrading the OS is not possible for us so if we want to use Veeam taking crash consistent backups is the only option.

We tested this for 2 weeks taking a backup through Veeam every 15 minutes and twice the guest OS crashed when a snapshot was initiated (out of hundreds).

links:

https://kb.vmware.com/selfservice/micro ... Id=2038606

https://access.redhat.com/solutions/484303
braddock
Influencer
 
Posts: 13
Liked: 1 time
Joined: Tue May 10, 2016 3:06 pm


Return to VMware vSphere



Who is online

Users browsing this forum: Majestic-12 [Bot] and 13 guests