Performing basic administration tasks
These topics contain instructions on how to perform database server administration tasks when your system is running HDR.
- Changing the configuration parameters for an HDR replication pair
- Back up storage spaces and logical-log files
When you use HDR, you must back up logical-log files and storage spaces only on the primary database server. Be prepared, however, to perform storage-space and logical-log backups on the secondary database server in case the type of the database server is changed to standard. - Changing the logging mode of databases
- Add and drop chunks and storage spaces
- Renaming chunks
- Saving chunk status on the secondary database server
For high-availability cluster servers, if the status of a chunk (down or online) is changed on the secondary database server, and that secondary server is restarted before a checkpoint is completed, the updated chunk status is not saved. - Use and change mirroring of chunks
- Manage the physical log
- Manage the logical log
- Manage virtual processors
- Manage shared memory
- Configure SMX connections
Server Multiplexer Group (SMX) is a communications interface that supports encrypted multiplexed network connections between servers in high availability environments. SMX provides a reliable, secure, high-performance communication mechanism between database server instances. - Replicate an index to an HDR secondary database server
- Encrypting data traffic between HDR database servers
- Adjust LRU flushing and automatic tuning in HDR server pairs
- Cloning a primary server
You can use the ifxclone utility to perform one-step server instantiation, allowing a primary server in a high-availability cluster to be cloned with minimum setup or configuration. - Database updates on secondary servers
You can enable applications connected to secondary servers to update database data. If you enable write operations on a secondary server, DELETE, INSERT, MERGE, and UPDATE operations are propagated to the primary server. - Backup and restore with high-availability clusters
You cannot perform most backup and restore operations on secondary servers. - Change the database server mode
If you change the mode of a database server in a high-availability cluster, replication stops. - Changing the database server type
You can change the type of either the primary or the secondary database server. - Prevent blocking checkpoints on HDR servers
- Monitor HDR status
Parent topic: Cluster administration