Skip to main content


 

 

How can we help you?

 

 
Druva Documentation

inSync Share Disaster Recovery

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

Overview

Disaster Recovery is critical for inSync Share users who share files and folders at device level as well as with other inSync users. This article provides information about the components in inSync Share, the disaster recovery scenarios, and the procedures related to recovering shared data in such scenarios.

inSync Share Key Components

inSync Master Server

The inSync Master Server contains the configuration details for the users and devices, as well as the inSync Server. It access ShareDB and ConfigDB and has the following attributes:

Config DB - users, devices, profiles, configurations
Share DB - users, collaborators, share details, owners, links, notifications

inSync Storage Node

 An inSync Storage Node is a server to which storage are connected. 

Storage DB and Storage itself.

inSync Share disaster recovery scenarios

Based on the architecture components that are available in the inSync Share architecture, the disaster recovery scenarios can be as follows:

  • The inSync Storage Node(s) has crashed, while the inSync Master and inSync Client are both residing at the latest timestamp.
  • The inSync Master has crashed, while the inSync Storage Node and inSync Client are both residing at the latest timestamp.
  • The inSync Storage Node(s) and the inSync Master has crashed, while the inSync Client is residing at the latest timestamp.

Procedure for inSync Share disaster recovery

 When insync Storage Nodes or the inSync Master crashes, you must ensure that inSync Client, inSync Master and inSync Storage Nodes are in a consistent state. The recommended resolutions in this topic will ensure that inSync Client resyncs all the files present in inSync Share.

NoteThe share information after the last backup is lost during a server crash or other disaster scenario and you must follow the manual steps mentioned in the following section.

Druva recommends that you follow these two main steps for Disaster Recovery:

  1. Backup inSync Storage Node(s) and inSync Master as a prerequisite.
  2. Restore inSync Storage Node and inSync Master as per the disaster scenario.

 Backup inSync Storage Node(s) and inSync Master as a prerequisite.

  1. After installing the inSync Master and configuring inSync Storage Nodes for the first time, you must take a backup of inSync Master and all the inSync Storage Nodes. It is a must to keep atleast one backup copy of the inSync Master and inSync Storage Nodes.

Note: If you do not follow this step, then you will not have any initial backed up copy of the inSync Storage Node(s) and inSync Master.

  1. For taking backup of the inSync Storage Node(s) situated across multiple locations, you must follow either of the following procedures.
  • Simultaneously take complete backup of all the inSync Storage Node(s) situated across multiple locations and inSync Master (C:\ProgramData\Druva\inSyncCloud\inSyncServer4)
  • You can take complete backup of all the inSync Storage Node(s) situated across multiple locations one at a time maintaining an order. Example: Take a backup of storage node situated at X location first, followed by those situated at Y location. After taking backup of the storage nodes, you must backup inSync Master.
  1. You can use third party softwares like Microsoft Hyper-V or Windows backup utility to take backup of inSync Storage Node(s) and inSync Master. 

For the procedure to take backup, refer to the Best Practices section.    

  Note:

  1.  If you follow step (1) and step (2),  it would be very easy to restore the state of the inSync Master and the inSync Storage Nodes to the same consistent state. For scenarios involving, inSync Master getting crashed, you must restore both the inSync Master and the inSync Storage Nodes at the same point. So, in this scenario, step (2) will definitely help.                    
  2.  If you follow step (1) and step (3), users would face some errors on client from server. You must  follow the resolutions listed later in this article.

Restore inSync Storage Node and inSync Master as per the disaster scenario

Scenario Impact Resolution

One or more than one inSync Storage Node(s) has crashed while inSync Master and inSync Client are at latest timestamp.

  • For all the users residing on those inSync Storage Node(s).
  • All the users who have synced the folders to their devices. 
  • All the users with whom a folder has been shared by one of the users residing in the crashed node.

Recommended solution in case of a inSync Storage Node crash only 

  • The inSync Master has crashed while inSync Storage Node(s) and the inSync Client are at latest timestamp.
  • Both the inSync Storage Node(s) and the inSync Master crashed while the inSync Client at latest timestamp.

For all the users residing on all the inSync Storage Nodes.

Recommended solution in case of inSync Master and inSync Storage Node crash 

Recommended solution in case only the inSync Storage Node crashes

Perform a recovery from the last snapshot of the inSync Storage node.

For additional steps that need to be performed on the end user devices contact Druva Technical Support.

If the Storage node goes down, contact Support.

Recommended solution in case of inSync Master crashes and in case inSync Storage Node(s) also crashes

Perform a recovery from the last snapshot of both inSync Master and on each of the inSync Storage nodes. Ensure the inSync Storage Node snapshot is older than the inSync Master's snapshot.

For additional steps that need to be performed on the end user devices contact Support.

Script to be provided by Escalation Team.

Additional steps on the end user devices

After performing the recommended solutions above, users might face the following issues:

  • Users will end up with multiple conflict files in their inSync Share folder - If local copies of the files exist that have not been synced to the server, inSync will create conflict copies of the same files. To resolve this issue, user can delete the original file and rename the conflict file with the original file name. 
  • A shared folder showing up in "All Content" and in "Shared Content" with different names - If a shared folder was renamed after last backup of the inSync Storage Node, then the renamed shared folder entry would be missing post restore of inSync Storage Node. This will cause original folder to be shown as unshared in 'All Content' listing on web and renamed folder to be shown in 'Shared Content' listing. To resolve this, user who renamed the shared folder can :                          
  1. Create another folder in one of the devices.
  2. Copy files manually inside that new folder from the earlier folder.
  3. Share the newly created folder with the same collaborators.
  • The files inside a shared folder are not getting synced to the server - If a folder was created and shared with other users after last backup of the inSync Storage Node, then files inside that shared folder will not get synced to the server. To resolve this, user who created the shared folder can:
  1. Create another folder in one of the devices.
  2. Copy files manually inside that new folder from the earlier folder.
  3. Share the newly created folder with the same collaborators.