node in the figure represents a data node (ChunkServer). A CopySet is the basic unit of data replication in CurveBS. A CopySet contains multiple chunks. Copysets in CurveBS are created in advance. 1. Reduce metadata. If the replication group membership is saved for each chunk, the number of metadata will be large. 2. Example Reduce the number of replication groups. The size of chunk is such as 16MB by default. If replication groups are created based on chunk. The number of replication groups is large and the communication traffic between replication groups is heavy. Once a CopySet

service-ldap Installation 3 service-ldap-access-control Access control 3 service-ldap-replication Replication 3 service-ldap-usage Simple LDAP user and group management 3 service-ldap-with-tls SSL/TLS repositories Reporting bugs Kernel crash dump OpenLDAP Introduction Installation Access control Replication Simple LDAP user and group management SSL/TLS Backup and restore Kerberos Introduction Kerberos should the LDAP server become unresponsive. This is done through LDAP replication. Replication is achieved via the Sync replication engine, syncrepl. This allows changes to be synchronised using a Consumer

$SystemLogRateLimitInterval 0 And then restart the rsyslog daemon: sudo systemctl restart syslog.service 1.6. Replication The LDAP service becomes increasingly important as more networked systems begin to depend on it done through LDAP replication. Replication is achieved via the Syncrepl engine. This allows changes to be synchronized using a Consumer - Provider model. The specific kind of replication we will implement The two databases (suffix: dc=example,dc=com) should now be synchronizing. 1.6.3. Testing Once replication starts, you can monitor it by running ldapsearch -z1 -LLLQY EXTERNAL -H ldapi:/// -s base -b dc=example

create a full database backup; • if the database uses replication make sure that all nodes are in sync and have no issues. Do not upgrade if replication is broken. • select a single node that will perform changes Agent 2 plugins MySQL The correct master host is now returned if specified in the mysql.replication.get_slave_status[] item ”masterHost” parameter. Previously the ”masterHost” parameter was ignored Test if a connection is alive or not. mysql.replication.discoveryReturns the list of MySQL replications. mysql.replication.get_slave_status The replication status. mysql.version The MySQL version. oracle

create a full database backup; • if the database uses replication make sure that all nodes are in sync and have no issues. Do not upgrade if replication is broken. • select a single node that will perform Test if a connection is alive or not. mysql.replication.discoveryReturns the list of MySQL replications. mysql.replication.get_slave_status The replication status. mysql.version The MySQL version. net pgsql.replication.count The number of standby servers. pgsql.replication.process The flush lag, write lag and replay lag per each sender process. pgsql.replication.process.discovery The replication process

username, password - MySQL login credentials. This item is supported for the MySQL plugin. mysql.replication.discovery[connString,,] 297 Key List of MySQL replications. Used for low-level credentials. This item is supported for the MySQL plugin. mysql.replication.get_slave_status[connString,,,] Replication status. Result of the ”show slave status” SQL query in connString - URI or session name. username, password - MySQL login credentials. masterHost - Replication master host name. This item is supported for the MySQL plugin. mysql.version[connString,

password - MySQL login credentials. This item is supported for the MySQL plugin. mysql.replication.discovery[connString, , ] List of MySQL replications. Used for low-level item is supported for the MySQL plugin. mysql.replication.get_slave_status[connString, , , ] 273 Key Replication status. Result of the ”show slave status” SQL connString - URI or session name. username, password - MySQL login credentials. masterHost - Replication master host name. This item is supported for the MySQL plugin. mysql.version[connString

HTTP • Control-M server by HTTP • Veeam Backup Enterprise Manager by HTTP • Veeam Backup and Replication by HTTP 16 See setup instructions for HTTP templates. Updated templates The template Oracle create a full database backup; • if the database uses replication make sure that all nodes are in sync and have no issues. Do not upgrade if replication is broken. • select a single node that will perform HTTP • Control-M server by HTTP • Veeam Backup Enterprise Manager by HTTP • Veeam Backup and Replication by HTTP See setup instructions for HTTP templates. The template Oracle by Zabbix agent 2 has

Control-M enterprise manager by HTTP • Veeam Backup Enterprise Manager by HTTP • Veeam Backup and Replication by HTTP See setup instructions for HTTP templates. The template Oracle by Zabbix agent 2 has Control-M enterprise manager by HTTP • Veeam Backup Enterprise Manager by HTTP • Veeam Backup and Replication by HTTP See setup instructions for HTTP templates. The template Oracle by Zabbix agent 2 has changes Agent 2 plugins MySQL The correct master host is now returned if specified in the mysql.replication.get_slave_status[] item ”masterHost” parameter. Previously the ”masterHost” parameter was ignored

password - MySQL login credentials. This item is supported for the MySQL plugin. mysql.replication.discovery[connString, , ] List of MySQL replications. Used for low-level item is supported for the MySQL plugin. mysql.replication.get_slave_status[connString, , , ] 250 Key Replication status. Result of the ”show slave status” SQL connString - URI or session name. username, password - MySQL login credentials. masterHost - Replication master host name. This item is supported for the MySQL plugin. mysql.version[connString