4 Replies Latest reply: Jul 2, 2013 10:11 AM by pedro.rocha RSS

Another question about SMVI, app consistency and SMSQL/SMExch

Currently Being Moderated

Hello there,

I know that this argument is widely discussed in a lot of posts, but after hours of reading I'm not able to clarify a doubt.


I have a customer with a vmware VM (win 2008R2) located into an nfs datastore (both os disk and data disk) and doesn't have snap manager software but has a DR site synced via snapmirror relationship.

The question is: Using the backup feature of the VSC plugin with the options to trigger a vmware snapshot before taking the netapp snapshot will the sql database (located in D:) be usable after a restore (or, same question: in case of DR does the snapmirror copy contains usable database data?)


Reading the tr-3737 pdf at page 29 (chapter 9.2.3) seems that shouldn't be a problem and the only feature that you cannot use is point in time recovery cause missing rollforward capabilities but, if the scenario with only one backup per day is acceptable, then could I sleep with peace of mind about the DB consistency?


i attach a piece of tr-3737...

Sorry for my poor english, I hope you can understand.


9.2.3  Application Consistency in Combined Solution Environments

NetApp  offers  two  solutions  today  for  addressing  application-consistent  data  protection  in  a  VMware environment:

•  SMVI,  working  through the  VMware  guest  VSS  stack, provides  application-consistent  backup  and recovery  for  applications  that  have  VSS  writers  and  store  their  data  on  virtual  disks  (VMDKs). Recovery, in this scenario, is at the full VM level only.

•  SnapDrive® and application-specific SnapManager products such as SnapManager for Exchange (SME)  and  SnapManager  for  SQL  (SMSQL)  running  in  the  guest  OS,  provide  application-consistent backup and fine-grained recovery for applications whose data is stored using Microsoft iSCSI Software Initiator LUNs or RDMs. 



The  critical  difference  in  the  level  of  protection provided  by  each  of  these  solutions  is  in  the  granularity  of

recovery.  To  understand  the  significance  of  this,  you  need  to  understand  the  concept  of  roll-forward

recovery. Roll-forward recovery replays information stored in transaction log files to return a database to the

state it was in at an exact point in time. In order to perform a roll-forward recovery, archival logging must be

enabled, a full backup image of the database must be available, and there must be access to all logged files

created since the last successful backup.

Since  the  only  recovery  mode  available  today  for  applications  backed  up  using  SMVI  (using  the  VMware

built-in  VSS  support)  is  recovery  to  the  point  of  the  last  backup,  customers  must  use  the  relevant

SnapManager application if more fine-grained, roll-forward recovery is required. 

More Like This

  • Retrieving data ...