Writing Sybase Dumps to a DXi Appliance

Overview

Some customers may protect Sybase resources by running a “dump database” command against the database and then write those dump files to a DXi appliance. This topic describes how to run the dump command to get a better deduplicaiton ratio and overall performance.

 

SR Information: This information came out of a POC with a company named Synnex (SR1345484).

 

Product / Software Version: Not available.

 

Problem Description: Customers run a “dump database” command gainst the database and then write those dump files to a DXi appliance, which negatively impacts the DXi system's deduplication ratio and performance.

 

 

To avoid this problem, consider the following two solutions:  

 

  1. You will see better deduplication ratios on the DXi system if the dump command is run without the compression parameter in the dump syntax.

For example, using “compress 0” (as shown below) will result in a lower deduplication ratio:

 

dump database PROD

to 'compress::0::/mnt/QBackup/sybase/PROD.dmp1'

stripe on 'compress::0::/mnt/QBackup/sybase/PROD.dmp2'

stripe on 'compress::0::/mnt/QBackup/sybase/PROD.dmp3'

stripe on 'compress::0::/mnt/QBackup/sybase/PROD.dmp4'

stripe on 'compress::0::/mnt/QBackup/sybase/PROD.dmp5'

go

 

  1. Run the Sybase dump command using a larger blocksize if possible. The DXi is tuned to perform better when processing data with larger blocksizes. 

 


  Additional Resources:

 



This page was generated by the BrainKeeper Enterprise Wiki, © 2018