backup server instance.
backup server web admin console.
After data are backed up from AhsayOBM / AhsayACB to AhsayCBS backup server, replication will be triggered almost instantly.
When a corresponding AhsayCBS backup server is down, the replication server can be quickly converted into a backup server to keep serving the backup users.
If data is replicated to another AhsayCBS, retention period and restore point interval can be configured for keeping multiple replication versions.
If you don't want to use another AhsayCBS as the replication receiver, cloud storage can be used as the replication destination for saving hardware and hosting investments.
System administrator can choose individual backup sets created on AhsayOBM / AhsayACB to replicate.
IP restriction can be set to prevent unwanted IPs from accessing the replication server.
Traffic limit can be set for specific period of time to reserve bandwidth for other purpose.
Cyclic redundancy checking (CRC) can be set to run automatically for verifying the integrity of the replicated data.
One AhsayCBS replication server can be used for receiving data replicated from multiple backup servers.
Both SSL and proxy server are supported for enhancing the security and compatibility of the replication server.
Real time replication and receiver status can be tracked in the System Panel of AhsayCBS.
Detailed replication logs are available for troubleshooting purpose.
When AhsayCBS is configured as a redirection server, it can redirect backup users to multiple backup servers.
User management can be simplified as all backup users on different backup servers just need to use a single URL as the backup server URL.
When creating users, user names will be checked on all backup servers in the farm to prevent duplication.
Real time redirection status can be tracked in the System Panel of AhsayCBS.
Detailed redirection logs are available for troubleshooting purpose.