Hi,
I have recently inherited a backup environment (commvault) at my new Job, and i have a question about backing up transaction logs.
I am responsible for guaranteeing a complete disaster recovery of a couple of our critical SQL servers, which I have been accomplishing with commvault, with a daily full backup of the database, and a backup of transaction logs every 30 min. The problem is my transaction logs need to be copied to our DR location, over the WAN, every 30 min, and when the daily maintenance job runs every evening at 7pm, it re indexed the database, creating a huge transaction log that is almost the size of the database, which takes 5-10 hours, or longer to copy over to our DR location, this is unacceptable.
Is there anyway to keep the reindex from creating such a huge transaction log, which to commvault appears to be all changed data?
I am new to SQL, but i assume there has to be solution to this, as i would think anyone with a short SLA on SQL would run into this.