Because a binary copy moves database files from one machine to another, the mechanism is subject to the following strict limitations:
Both machines must run the same operating system, including any service packs or patches.
Both machines must share the same processor architecture. For example, you can perform binary copy between two UltraSPARC T1 processors but not between an UltraSPARC T1 and an AMD Opteron processor.
Both machines must be either big endian or little endian.
Both machines must map memory the same way. For example, you can perform binary copy between server instances on two 64-bit systems, but not between one server instance on a 32-bit system and another on a 64-bit system.
Both machines must have the same version of Directory Server installed, including binary format (32 bits or 64 bits), service pack, and patch level.
Both servers must have the same directory tree divided into the same suffixes. The database files for all suffixes must be copied together. Individual suffixes cannot be copied.
Each suffix must have the same indexes configured on both servers, including VLV (virtual list view) indexes. The databases for the suffixes must have the same name.
Each server must have the same suffixes configured as replicas.
If fractional replication is configured, it must be configured identically on all servers.
Attribute encryption must not be used on either server.
The attribute value uniqueness plug-in must have the same configuration on both servers if enabled, and it must be re-configured on the new copy, as explained in the following procedures.
These procedures describe alternate ways of performing a binary copy: a binary copy that does not require stopping the server and a binary copy that uses the minimum amount of disk space.