Avamar backup for MSSQL

Trying to use two backup tools on the same SQL database is likely to end badly. If you want Avamar to truncate the transaction logs, you need to rely on Avamar to truncate the transaction logs. If the transaction logs are truncated before they are backed up by the Avamar client, subsequent incremental backups will fail because there are logs missing from the log chain. This will force you to take a new Full backup before you could resume creating incrementals.

Hi Shailesh,

  Thanks for the screenshot.  This screenshot says about the type of backup tobe done.  But my question is like this.

1) Run database backup of system A

2) While database backup is running can we run another transaction log backup alone using Veritas tool to system A itself.

Most of the time its best to only use one solution to backup a SQL database but there is a SQL feature called copy-only backup that Microsoft considers safe to use with multiple backup solutions backing up a SQL database.  Starting in version 7.4 Avamar supports copy-only SQL backups.  A copy-only backup will not interact with transaction logs at all.  That way you can have one solution that backups up and truncates logs and another that only does full copy-only backups.  You will still run into issues if both solution try to do a backup at the same time so you have to do extra planning to schedule the two solutions so the jobs do not try to run at the same times.

We are using this MSSQL as database for SAP. size about 4.7TB.  We are running database compression (since initially version it came like that) for improving performance.  When database backup thru Avamar tool runs for 8-10 hrs, we observe Transaction log getting full and error out/stops SAP from working.  It may be highly difficult to get more space added to increase transaction log (as we may not say how much since it is db compression).   Thats the reason for my initial question: When my database backup is running, is it not possible to run another backup that just runs the transaction log thru Avamar itself.  I am not intending to run manually.

Hi,

As a suggestion - May be you can try to change the backup methodology here. Schedule SAP database backups using SAP Backup/Recovery native tool to filesystem and backup those flat files using external tool.

Obviously- this will have other challenges, but your application will not be impacted due to database is down.