2.2. Best Practices

A successful deployment depends on being mindful during deployment, operations and ongoing maintenance.

2.2.1. Best Practices: Deployment

  • Identify the best deployment method for your environment and use that in production and testing. See Section 10.1, “Comparing Staging and INI tpm Methods”.

  • Standardize the OS and database prerequisites. There are Puppet and Chef modules available for immediate use or as a template for modifications.

  • For security purposes you should ensure that you secure the following areas of your deployment:

  • Choose your topology from the deployment section and verify the configuration matches the basic settings. Additional settings may be included for custom features but the basics are needed to ensure proper operation. If your configuration is not listed or does not match our documented settings; we cannot guarantee correct operation.

  • If you are using ROW replication, any triggers that run additional INSERT/UPDATE/DELETE operations must be updated so they do not run on the slave servers. See http://kb.vmware.com/kb/2112599.

  • Make sure you know the structure of the Tungsten Replication home directory and how to initialize your environment for administration. See Section 8.1, “The Tungsten Replication Home Directory” and Section 8.2, “Establishing the Shell Environment”.

  • Prior to migrating applications to Tungsten Replication test failover and recovery procedures from Chapter 8, Operations Guide. Be sure to try recovering a failed master and reprovisioning failed slaves.

2.2.2. Best Practices: Operations

2.2.3. Best Practices: Maintenance

  • Your license allows for a testing cluster. Deploy a cluster that matches your production cluster and test all operations and maintenance operations there.

  • Disable any automatic operating system patching processes. The use of automatic patching will cause issues when all database servers automatically restart without coordination. See Section 8.13.3, “Performing Maintenance on an Entire Dataservice”.

  • Regularly check for maintenance releases and upgrade your environment. Every version includes stability and usability fixes to ease the administrative process.