#SCV plugin with VM Consistency

1 messages · Page 1 of 1 (latest)

plush topaz
#

Hello,

may somebody from the vendor (NetApp) confirm that SnapCenter VMware plugin (SCV) takes copy-only backups when VM-Consistency parametr is checked? So the VSS writer inside the VM will not breake backup chain if there is another backups running.

As per my fast tests with SCS+SCV 6.0.1 and SQL database, it looks they are really copy-only.

Btw. Is this somewhere inside the SCV configurable? How plugin will behave?

Thx,
Lukas

burnt phoenix
#

as I understand it, if consistency is checked it will perform VSS inside the VM, but if VSS cannot be performed (due to another backup running, for example) the VM will just be marked as "not consistent" (i.e. crash consistent) and the backup will continue.

But I'm not a NetApp employee so you don't need to take my word for it

rose quartz
#

For vm consistency to function, I am pretty sure the guest os must have vm tools installed so VMware may properly communicate with the guest

plush topaz
#

Yeah, that’s pretty clear, question is if SCV has any option in regards of VSS_BACKUP_TYPE parametr, eg tell vss writer which type to use. So far from my testing it is using vss_bt_copy so “copy-only” type.

errant bolt
#

Where are your SQL databases located? On guest-connected LUNs via iSCSI software-initiator? Then you only need the SC server.
If they are on VMDKs or RDMs you additionally need the SCV plugin.

But if you are only triggering backups via the SCV GUI these are not application-consistent. SCV is not aware that an SQL server is running on the VM you're backing up. So it's unable to break any backup chain, create log backups, etc.
Only if you're configuring the backup on the SC server the backup will be application-consistent and it will interact with MS SQL.

burnt phoenix
#

MSSQL is VSS-aware and so it will correctly create a consistent "copy" type backup as long as VMware tools are installed. But the backup type will always be just a copy (because that's what a Snapshot is, basically)... If you want to truncate logs, create incremental/differential chains, etc, you either need SCV or some very creative scripting (pre/post scripts)

plush topaz
#

Correct, I do not want to have possibility to backup logs, do common full backups etc via SCV…. We normally do this via SC to be able restore point-in-time / clone DBs etc.

BUT. In one particular case SQL single instance server which is running on vmdk disk is being backup via Veeam not SC, and I still need to create VM consistent snapshot via SCV with consistent DB inside. That’s why I do not want to break Veeam chain.

Well, @burnt phoenix is basically confirming my assumption and testing. MSSQL db also shows VM consistent backup as copy_only.

burnt phoenix
#

The VSS snapshot should not break the backup chain? or does it?

rose quartz
#

If I’m not mistaken, unless databases are on a block device (guest iscsi for example) then scv isn’t technically supported. Pretty sure I read that in the guides/notes.