Advantages of having VM backup and seperate application backup instead of app aware backup

 Hello @Ajal 

App-aware backup will join the VSA backup job and the application based backup into one with the goal of creating simplicity. The issues you can hit with App-aware backups is that troubleshooting them can be a bit of a rabbit hole filled with red herrings due to the workflow that is involved and the dependency on each checkpoint it has to reach. 

When it works, it works really well but when it has errors and fails it quickly leads to a support ticket. 

On the other hand when you have the jobs separate, the configuration and troubleshooting of issues is more isolated and easier to find the core problem without involving support. 

Either way, both methods are supported and it comes down to how hands on you are wanting to be and your skill/knowledge with the product. Both protect your data and that is the goal. 

Kind regards

Albert Williams

@Ajal @Albert Williams also consider how restores differ… app aware requires both the VM and App jobs to be available in order for recovery to work. Can usually take a little longer to restore too due to the various dependencies the workflow follows. 
 

• Both the VSA job and the associated application job must be available when you restore data for an application. The point-in-time software snapshot that is created by the application backup operation is part of the data that is stored for the VSA backup job. Ensure that both the VSA job and the application job are retained in the same storage policy copy that is used for restore operations.
   

More info is here: https://documentation.commvault.com/2023e/essential/restore_operations_from_application_aware_backups.html

If you compare that to a traditional backup method, you can simply restore back into the app directly instead of needing to worry about any VM level recovery or mount process needing to take place.

Hope this helps

Regards,

Chris​