06-22-2021 08:09 PM
06-22-2021 09:02 PM
Thats what Application Consistency we talk about. I have restored VM's for many customers with MSSQL consistency.
06-22-2021 09:05 PM
I was going to write the following, but @pats_729 has real world experience of this, so I defer to his greater knowledge.
"The database would be in a crash consistent mode only from the full VM recovery. It may work but no guarantees.
To properly recover the database, you will need to perform an SQL recovery. This process is reasonably well described in the NetBackup MS-SQL Admin Guide."
06-22-2021 10:00 PM
we are taking backups of VM where SQL database is housed. i was wondering, if we perform complete VM recover will SQL database recovers in that or we need to take seperate SQL backup(agent based backup through SQL policy type) to recover the DB?
i was thinking to just stop SQL DB backup to save FETB and blackened capacity, only if SQL DB recovery is feasible with complete VMware recovery
06-22-2021 10:29 PM
As @pats_729 has indicated, you can recover the SQL DB when the MSQL application state catpure for that VM is enabled.
What this is though is a point in time snapshot of the database. It is not possible to use this backup with transaction logs to roll forwards or backwards to recover to a particular point in time. If this is not required then using the VM backup with appliaction capture will be sufficient.
If you need the granularity of recovery that comes with transaction logs and rollback / roll forwards, then you should use the NetBackup agent in the VM. As for FETB - although you are running two backups it is the same data, so an adjustment can be made when reviewing the nbdeplyutil. Or it is possible to exclude the database VDMK files from the VM backup, which would avoid the backend capacity being used. This later will depend on how the VM is setup (separate VMDK files for the database areas).
06-22-2021 11:03 PM
First of all, you have to install netbackup client inside the VM.
As dimension earlier, when you restore the VM. you have 99% chance that the SQL will be operational.
But the supported method is to restore the VM and then restore the SQL from the Backup (This is NOT an extra backup, netbackup index and catalog the SQL at the same time.)
AS mentioned earlier with VM/SQL backup you can only truncate the logs. You can not do a point in time restore. If you need a point in time restore, you have to do regular SQL Full backup and log backups.
06-22-2021 11:30 PM
one question..may be silly :)
Can we take database backup under VMware policy and transection logs backup from SQL agent policy?
If Yes, in case of recover can we recover databse in point in time from both backups?
06-22-2021 11:47 PM
If you read carefully, me and davidmoline wrote that you can not do that. You can not "blend" VM-SQL backup with log backups to do a point in time restore.
VM-SQL backup is an SQL copy-only backup. If you need point in time restore you have to configure regular SQL full and log backups
06-23-2021 02:16 AM
"VM-SQL backup is an SQL copy-only backup. If you need point in time restore you have to configure regular SQL full and log backups"
This one reason is why we don't use this feature on any production system. I'm not sure if this is something that can be fixed in a future release, but if it could then it would work very well.