Skip to main content

 

Druva Documentation

Post upgrade configurations

Overview

This topic explains the configuration activities that you must complete after upgrading to inSync Private Cloud 5.2.2.

Modifying the quota assigned to users

The versions earlier than 5.2 defined quota as the space within storage that was allocated to a user. With every backup or synchronization operation from a user's device, incremental data was added till the quota permitted.

Starting with version 5.2, quota is defined as the size of native data that is backed up or synchronized from user devices. Users exceeding this quota can simply delete backup folders or shared folders, thus ensuring that backups do not halt.

To align with the new definition, an inSync administrator should reduce quota assigned to each user.

Installing an SSL certificate for restores

Starting with inSync 5.2, restore requests are initiated from inSync Web. inSync Web interacts with inSync server over a secure HTTP connection. To facilitate this secure interaction, a self-signed certificate is used on inSync server. However, if a self-signed certificate is not used, inSync users see an untrusted certificate message on their Web browser when they initiate a restore.

To avoid this, inSync administrators should install an SSL certificate signed by a third-party Certificate Authority. Alternatively, you can educate your end-users about the untrusted certificate message.

Backing up system and application settings

The System, App Settings feature, introduced in version 5.2, enables inSync Server for backing up your system settings. To enable this feature, you must modify your profiles.

Configuring high availability of performance optimized storages

Starting with inSync 5.2, inSync administrators can create a secondary storage and map it to one of your performance optimized storages. The secondary storage ensures that data backups and restores continue even when the primary storage is down. This high availability functionality is not available for storages optimized for disk space savings. Also, with inSync 5.2, administrators can no longer create disk space saving storages.

Save storage node details

If you upgraded from inSync Private Cloud 5.0.1, the inSync administrator must manually save the ports defined for each storage node. The administrator need not make any change to the port numbers; just open the Edit Storage Node window and click Save.

Define time zones for administrators

For upgrades from version 5.0.1 or 5.1, inSync administrators must define their time zones on the inSync Admin Console. The time zone feature, introduced with version 5.1.1, enables administrators to view timestamps in the inSync Admin Console interface depending on their time zone settings. Administrators who do not configure their time zones, can only view timestamps following the UTC time zone.

Restart the Config Server Service on inSync master server

If you are upgrading to inSync Private Cloud 5.2.2 (installed on Windows OS) from version 5.0.1 or 5.1, and have created AD mappings on your existing installation, restart the Druva inSync Config Server service.

  • Was this article helpful?