• TheAccidentalDBA (8/27/2014)


    SSC-Addicted nice points and links. I posted two responses separately.Yes, totally agree on your points that its needs to be tested with restore. Logically, the following might work.

    1. Only Veeam backup for the SQL Server, 'Application Aware Processing' is turned ON. Also, select 'Truncate logs on Successful backups'

    2. Veeam backup and Native full backups daily, 'Application Aware Processing' is turned ON. Also, select 'Do not Truncate logs'

    3. Veeam backup & Native full/differential/transaction back up , 'Application Aware Processing' is turned OFF, the db data/transaction log/backup drives not included.

    Snapshot can get a valid backup on the db data/transaction log/back up drives only after quescing. These drives are actively used by SQL Server Process which needs to be momentarily stopped for a quick snapshot. If these drives are not included in the snapshot, then it will not try to stop the SQL Server Process.

    Does this make sense?

    I think it does also. I'm trying to get the best of both worlds. I'm very annoyed at how beautifully the two methods would work together without this flaw.

    RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉