Unsolved
This post is more than 5 years old
1 Rookie
•
4 Posts
0
1234
February 23rd, 2017 15:00
SQL Backups CIFS - Best Practice
New DD User. Have a mixture of DLM and new with CIFS. DLM is working well. Wanted to switch some backups to CIFS. In particular was interested in what is the best practices for backing up SQL Server.
We don't have DD Boost.
Currently the SQL DBA's are creating a SQL backup dump and placing it on the CIFS of the DD. Which in turn gets replicated to our offsite DD. Some of them dumps wipe out the old one daily and create a new dump. Where there are others that maintain a daily copy for a few days.
Am finding the CIFS sync is not getting down in a timely manner.
Is there any recommendations on the best way to do this? Like compress the SQL dump or not. Create dailys for a week, etc.
Need to improve this process.
Dennis
ble1
4 Operator
•
14.3K Posts
0
March 6th, 2017 09:00
Compression might kill your dedupe performance so I would avoid compression.
James_Ford
30 Posts
0
March 16th, 2017 03:00
So I would agree with the above - compression is not ideal as it will cause the de-duplication on the DDR to be less effective. In addition as DD replication is de-dupe aware you might actually end up replicating more physical data between DDRs than you are now.
One thing to watch out for with MS SQL is if you are performing striped backups (i.e. multiple read streams during backup on the SQL Server system) you need to make sure that MAXTRANSFERSIZE and BLOCKSIZE are set larger than default on the MS SQL system. Failure to do this means that data can be reordered between streams during each backup which causes fragmentation of data on the DDR. This then means that the data can be very slow to read/replicate.
The following KB article contains more information and Microsoft should be able to help you understand how to set these parameters: https://support.emc.com/kb/336525
Thanks, James