Database replication enables you to specify a location where the BFC database is replicated. This replication occurs in real time automatically to help ensure that the replicated database is always current. To activate this feature you specify the location to store the replicated database.
If you need to restore a BFC (due to a hardware failure, disaster, or anything else), you simply run the installation program on the new BFC machine and specify the directory location of the replicated database (this is the first question in the installation program). The new BFC is then installed with the replicated database.
If you need to change the location of the database replica, you can run the stop_replication script, described at the end of this topic.
Note: The new BFC machine should have the same hostname and IP addresses (backbone and external network) as the original BFC control node. Also, the new machine should have the exact same settings of version download directory as the original BFC control node.
To configure database replication
The Administration page opens.
Path location for the replicated database (preferably on a network-mounted volume or external storage device). A database replica is not required for BFC operation, but highly recommended. The replica path should be writable by the bfcadmin account. You can run the chown or chmod commands to provide the required access to the replica path. For example:
chown bfcadmin <replica path> chmod 700 <replica path>
Note: Do not use the /home/bfcadmin folder for your replica database. If you uninstall the BFC, this folder is removed.
You can also edit the location of the database replication.
To change the location of the database replication
"su - bfcadmin"
<BFC Installation Directory>bin/stop/stop_replication
By default, the installation directory is opt/bfc.
The new replica directory should populate in several minutes.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|