Primary-Hosting-Farm and Backup-Hosting-Farm
In case of a service failure, the switch from the Primary-Hosting-Farm to the Backup-Hosting-Farm takes place automatically. Since December 2019 the Backup-Hosting-Farm has always up-to-date EGroupware date and is already WRITABLE. The EGroupware files are coming by default from the "NFS-Fileserver" of the Primary-Hosting-Farm. In case of a failure of the "primary NFS-Fileserver", we switch over to the NFS-Fileserver of the Backup-Hosting-Farm.
The following procedure is applied:
1: You are already redirected to our Backup-Hosting-Farm and your data is fully writable.
2: In case of longer time failure of Primary-Hosting-Farm, we will scale our Backup-Hosting-Farm up, for better performance.
If the "primary NFS-Fileserver" is effected from the failure, you may can't access the files which have been uploaded in the last 15 minutes before the failure.
3: Stay informed about Primary-Hosting-Farm status. We will update the right site of this page!
4: In case Primary-Hosting-Farm is back, clear your browser history and re-open it.
Testing of the Backup Hosting Farm:
To test your EGroupware data, stored in the backup farm, you can access it with this URL anytime: "instance name - top-level domain.egroupware.cc".
For example for our support centre instead of "my.egroupware.org": "my-org.egroupware.cc" or "mycompany-net.egroupware.cc" for all ".net" domains. In case of a service failure, the switch from the primary hosting farm to the backup hosting farm takes place automatically.