This article explains how to deploy a SafeHaven Cluster. Once the cluster is deployed, a user can log in to SafeHaven Console to access their SafeHaven Environment and start the DR setup.
- Please ensure that the SafeHaven CMS server is already created and it is reachable from the PC/machine on which the user will use to launch the SafeHaven Console to create/login to the SafeHaven Cluster.
- TCP and UDP Ports 20080 and 20081 must be opened.
- CMS server has internet access.
- CMS server has been deployed in the DR Datacenter
- The CMS server is reachable from the PC/machine you are running the SafeHaven Console on.
- The CMS server has internet access.
Note: SafeHaven Cluster installation will fail without internet access.
Most Recent SafeHaven Release Updates
Please ensure that you are using the most recent SafeHaven release update to create a new cluster. Please refer to Most Recent SafeHaven Release Updates for information on what's most recent.
Download the SafeHaven Console Application
Download the GUI Package from the Download Links section of the most recent SafeHaven release notes. Please refer to Most Recent SafeHaven Release Updates for the most recent SafeHaven version. Once the file is downloaded, extract it, and run safehaven-console.exe.
Create a New SafeHaven Cluster
Launch the safehaven-console.exe.
Click on Create new cluster.
Enter the Organization Name and the License key provided to you by your Lumen Resource. Click Next.
Note: You can request a license key by sending an email to firstname.lastname@example.org and specifying the number of VMs in the request
Fill in the following fields:
a. Enter CMS Hostname.
b. CMS Access IP (used to connect to the SafeHaven Console GUI) and CMS Service IP (used for communication between CMS and SRN's). Typically the CMS Private IP address is entered in these fields although they can differ in some cases. You can get this information from the CMS Server deployed in the recovery datacenter which is AWS in this case.
c. Set the Administrator Password (Password required to login to the SafeHaven Console GUI to manage the DR environment and initiate recovery operations).
d. Enter the CMS root password. You can get this information from the CMS Server deployed in the recovery datacenter which is AWS in this case.
NOTE: Best practice is to use different passwords for Administrator and root user.
e. Click on Validate CMS Access to confirm connectivity to the CMS.
f. Copy the Debian Package for CMS/SRN link from the Download Links section of the most recent SafeHaven release notes : Most Recent SafeHaven Release Updates. Enter it in the SafeHaven distribution URL field.
NOTE:Please contact your Lumen Cloud Resource if you have any questions regarding the latest version of Debian
Package for CMS/SRN. Do not modify the Service Port (TCP), Heartbeat Port (UDP), Installation ID.
A warning message will appear.
"By clicking continue, a fresh cluster will be installed. Previous configuration will be replaced. Are you sure to continue ?" Click on Continue.
Wait for the SafeHaven software to complete the configuration of the CMS server. When this process is complete, a pop-up window appears to let you know that the configuration was successful.
Click OK and then Finish.
NOTE: The CMS will reboot as part of the installation procedure.
Login to the SafeHaven Console
- Login to the SafeHaven Console by using the Client Access IP address for the CMS.
- Enter Administrator in the User field and enter the Administrator Password you had set during the cluster installation procedure stated above.
- Click Log In.
- Install the SSL Certificate (This will require Administrator rights).
- The SafeHaven Cluster will appear and you can start configuring it.
Next Step is to Register Datacenters within a SafeHaven Console.md