Wizard​

In a new instance of senhasegura, after the EULA acceptance, the application will present the first step of the Orbit Wizard.

First step​

caution

The application will restart the server when changing the Hostname (This configuration is optional because it was already defined in the previous step).

When changing the NTP server, the application will restart the NTP service, and users will be logged off.

When changing the DNS server, make sure that the senhasegura will have access to the DNS server, or this step of the Wizard will fail, or the DNS settings will not be preserved.

Important

The administrator must define the application URL correctly because senhasegura will use this information to generate several links in senhasegura!

Second step​

In the second step, you can configure senhasegura Backup.

If you want the backup to be exported to a remote disk partition, you can configure it through CIFS, NFS, or direct sending using RSYNC.

In the second step, you can define: Enable application backup, Enable sessions file backup, and Mount a remote partition.

info

If the client has a backup agent, we indicate that this agent is installed on the server that contains the remote folder that will receive the backup copy.

danger

If the system loses access to the remote backup directory, a notification via email and SIEM will be sent.

Third step​

You can create a new cluster or add the instance to an existing cluster in this third and last step.

caution

If you have chosen to configure the cluster, the application will restart the database service.

The settings of this third step of the Wizard can be summarized as follows:

1. If you want to activate the cluster, select yes in enable high availability and/or Contingency environment;
2. By default, the senhasegura will only replicate the database layer between the instances. If you also want to replicate the video files, select yes in enabling replication of session files
3. In the section members, What will be the members of the High Availability or Contingency environment? indicate the IP of the cluster members.

caution

The order of these members should be the same among all members.

1. If cluster members are in different datacenters, select yes at the members are in other datacenters fields; Configure latency between clusters within field options Latency between nodes. Also, set the instance indicator in the Network segment field if you have more than one instance of senhasegura in the same data center.

2. Click Finish for Orbit to apply cluster settings.

3. Application will direct you to the replication status screen to check the results.

When you finish the third step, wait for the instance to normalize, and you will be ready to activate the application and use all functionalities!