Hi Folks

I am facing an issue with backing up one SQL server. We have one application deployed for 2 different customers and I am backing up these 2 databases server in same protection group. 

Customer A's Database server is very busy because they upload heavy files into application which mackes databases busy continously. 
Customer B's Database server isn't much more activ e but is been in general use since they are uploading small and average files. 

Now when DPM backing up this protection group, Database B server is backing up normally. But Server A databases are taking longtime (15-18 Hours) to complete syncing and Backing up. 
This is excpected to take time since there are lot of changes in databases but not expecting such a long time where next scheduled backup jobs are overlapping with old ones. 

I just want to know How DPM track SQL changes on protected Server like through voume filter or bitmap? What precuation I should take to resolve this issue!

Here are few points related to these databases. 

1. Databases sizes are from 30 GB to 300 GB
2. These are Simple mode databases but files are spreaded through .ndf files. 
3. Application is loading heavy files interacting those databases. 
4. I have set Sync Frequency 4 hours and Express full backups 2 times in a day 10AM, 10PM
5. Support guys are taking manual backups randomly in .bak format. 

Also during DB backups, Sysem file is creating and growing upto 50-60 GB.




Please help on this. 

• Moved by Mike JacquetMicrosoft employee, Moderator Friday, April 17, 2015 10:40 PM

Thanks Mike. 

Adding another drive as shadow copy volume really made progress there, now these databases are backing up successfully. however the time consumed is decreased from 10-15 hours to 3-4-5 hours. 

Now I have enabled 1 express full backup per day and consistency check just before recovery point. These are simple mode databases (having multiple .ndf files). by enabling 2 times express full backups will make any progress there in time consumption??

Hi,

You mean you set the protection group to synchronize right before recovery point ?  If the DB's are simple recovery mode then that will not have any effect.  Making two express full recovery points / day may help - it depends on the sql db churn pattern.  If the same tables change through out day, then you are just transmitting different versions of the same tables twice a day, but if different tables change over a longer period of time, then you could see smaller / faster express full backup times.   Only time will tell.