Skip to main content
Druva Documentation

Post-upgrade configurations

Modifying the quota assigned to users

The versions earlier than 5.2 defined quota as the space within a storage that was allocated to a user. With every backup or synchronization operation from a user 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, reduce quota assigned to each user.

Loading an SSL certificate for restores

Starting with version 5.3, you can choose to enable web restores (via inSync Web) for users of your organization. inSync Web interacts with the Master server over a secure HTTP connection. The Master server uses a self-signed certificate to authentication access. That is why users see an untrusted certificate message on their Web browsers every time initiate a restore.

To avoid the untrusted certificate message, load an SSL certificate of the .pem type. 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, backs up system and application settings. For more information about this feature, see Backing up system and app settings (Persona Backup)

To enable this feature, you must modify your profiles.

Configuring high availability of performance optimized storages

Version 5.2 introduced the high availability feature for storage optimized for performance. You can ensure high availability of such storage by defining primary storage, and a secondary storages for each such primary storage. The secondary storage ensures that backups and restores continue even when the primary storage is down.

Note: You cannot create storages optimized for disk space savings. However, existing storages optimized for disk space savings will continue to be supported. 

If you must, configure high availability for your existing storages that are optimized for "performance". 

Saving storage node details

If you upgraded from inSync Private Cloud 5.0.1, manually save the ports defined for each storage node. A manual save ensures that port definitions from earlier versions are saved as is in version 5.3.1. 

To do this, open the Edit Storage Node window and click Save

Defining time zones for your administrator account

For upgrades from version 5.0.1 or 5.1, define the time zones for your Master server. The time zone feature, introduced with version 5.1.1, enables administrators to view timestamps from the inSync Admin Console interface. If you do not configure time zones, you can only view timestamps following the UTC time zone.

To know how you can define time zones, see Defining your time zone

Restarting the Druva inSync Master Config Server Service

If you are upgrading to inSync Private Cloud 5.3.1 (installed on Windows) from version 5.0.1 or 5.1, and have created AD mappings on your existing installation, make sure that the AD mappings setting apply to the upgrade. 

To do this, restart the Druva inSync Master Config Server service. For a full list of configuration files, see inSync Log and Configuration files

  • Was this article helpful?