A successful deployment depends on being mindful during deployment, operations and ongoing maintenance.
Identify the best deployment method for your environment and use that
in production and testing. See
Section 9.1, “Comparing Staging and
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:
Ensure that you create a unique installation and deployment user, such as tungsten, and set the correct file permissions on installed directories. See Section B.2.3, “Directory Locations and Configuration”.
When using ssh and/or SSL, ensure that the ssh key or certificates are suitably protected. See Section B.2.2.2, “SSH Configuration”.
Use a firewall, such as iptables to protect the network ports that you need to use. The best solution is to ensure that only known hosts can connect to the required ports for Continuent Tungsten. For more information on the network ports required for Continuent Tungsten operation, see Section B.2.2.1, “Network Ports”.
If possible, use authentication and SSL connectivity between hosts to protext your data and authorisation for the tools used in your deployment.
See Section 2.7, “Deploying SSL Secured Replication and Administration” for more information.
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 there are an even number of database servers in the cluster, configure the cluster with a witness host. An active witness is preferred but a passive one will ensure stability. See Section 2.1.4, “Witness Hosts” for an explanation of the differences and how to configure them.
Make sure you know the structure of the Continuent Tungsten home directory and how to initialize your environment for administration. See Section 5.1, “The Continuent Tungsten Home Directory” and Section 5.2, “Establishing the Shell Environment”.
Prior to migrating applications to Continuent Tungsten test failover and recovery procedures from Chapter 5, Operations Guide. Be sure to try recovering a failed master and reprovisioning failed slaves.
Setup proper monitoring for all servers as described in Section 5.16, “Monitoring Continuent Tungsten”.
Configure the Continuent Tungsten services to startup and shutdown along with the server. See Section 4.3, “Configuring Startup on Boot”.
Schedule the Section 8.6, “The cluster_backup Command” tool on each database server at least each night. The script will take a backup of at least one server. Skip this step if you have another backup method scheduled that takes consistent snapshots of your server.
Schedule regular tests for local and DR failover. This should at least include switching the master server to another host in the local cluster. If possible, the DR cluster should be tested once per quarter.
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 5.14.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.