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 ?