The BFC installation process includes an option to create a replica database. You can use the replica later, to recover the database for some reason. Consider the following general requirements when using the replica database features.
If you choose to create a replica database during the installation process, the following rules apply:
Note: Do not use the /home/bfcadmin folder for your replica database. If you uninstall the BFC, this folder is removed.
If you must recover from a replica database, the following rule applies:
Important!
If the replica is stored on a FAT filesystem (for example, a USB stick or drive), there is no owner/group supported by the filesystem. Here, the replica should be mounted on the BFC node using the CentOS "vfat" filesystem type with a mount option to set the uid/gid to bfcadmin/bfc for all files in the filesystem. For example:
mount -t vfat -o rw,noexec,nosuid,shortname=winnt,uid=64870,gid=64869 /dev/sdb1 /replica
If the replica directory is made into a tar file and moved, you should extract the tar file as root (or with the "-p" or "--preserve-permissions" flag). By doing this, the extracted files will preserve their original owner/group identities, even on a system where the BFC accounts are not defined. In this example, the owner/group (as reported by 'ls') will be numeric. Since the bfcadmin/bfc accounts are always given the same numeric values on all machines this extracted tar should yield a recoverable replica.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|