Skip to main content
Druva Documentation

Add new device for remote users

Overview

When an inSync administrator remotely marks the user's existing device for replacement, the existing device remains unprotected until the new device is configured and ready to be shipped to the user. In these scenarios, the user cannot take scheduled backups or use inSync Share on the existing device.

To avoid any instances of losing data updates made on the user's existing device while you configure the new device and prepare it for shipment, inSync has introduced the option of adding a new device to the user's inSync account, instead of replacing the existing device. The life cycles of both devices will be managed independently and will not result in any data loss for the user.

The capability of restoring the most recent data from the user's existing device onto the new device, while the new device is in transit is called Restore Delta Data.

 

  • Restore Delta Data is an on-demand feature. Contact Druva Support to enable this feature for your account.
  • Restore Delta Data feature for AD users is supported on inSync Client v6.5.0 and later and for non-AD users is supported on inSync Client v6.8.0 and later.

Advantages of adding a new device

  • The user's old device is protected without any loss of data.
  • The user can continue to take or schedule backups on the old device even when the new device is being activated and shipped.
  • System settings and MAPI data can now be restored from the latest snapshot when the user logs in to the new device.
  • The user can continue to use both the devices independently.

Limitations of adding a new device

  • The user will continue to have two inSync devices unless the administrator decides to deactivate or delete any one of them
  • The space consumed by the new device will be added to user’s usage quota. For example, if the data consumed by the old device was 20GB of inSync Cloud space. After backup starts on the new device, the user’s usage quota will change to 40GB.

Add new device workflow for AD users

The add new device workflow for AD users is as follows:

inSync Administrator actions:

  1. On the inSync Management console, marks the device which needs to be replaced and starts the add device process. 

System Administrator actions:

  1. Using IMD, installs inSync Client on the user's new device and logs into the new device.
  2. inSync Client restores all the data on the new device. Note: The data from the latest snapshot will be restored.

After this step, the new device is ready to be shipped to the user.

User actions:

  1. Using  Active Directory credentials, logs in to the new device.
  2.  The inSync Client restores system settings and MAPI data. inSync Client then moves the restored data which is saved at the temporary location to relevant paths and folders as required.  

The device is now ready to be used. 
The user can use both the devices till the administrator decides to deactivate the older device.

Add new device process for AD Users 

The following table describes the multi-step process for the integrated mass deployment (IMD) device replace.

Step Description
Step 1 Mark the device which needs to be replaced. For more information, see Mark old device for Replace
Step 2 Generate a mass deployment token. For more information, see Generate a mass deployment token.
Step 3

Run the IMD command with additional device replace parameters. For more information see Device Replace Parameter details.

Step 4 inSync Client restores all the data on the new device. For more information, see Temporary location directories for restored data.
Step 5 inSync Client moves the data from the temporary location to relevant folders and paths and ships the device to the user. For more information, see Device replace for AD users.
Step 6 The device is then shipped to the user. For actions performed by the user, see Manage data after remote device refresh.

Add new device workflow for non-AD users 

The add new device workflow for non-AD users is as follows:

inSync Administrator actions:

  1. On the inSync Management console, marks the device which needs to be replaced and start the add device process.

System Administrator actions:

  1. Login to the new device and create a local account.
  2. Using IMD, install inSync Client on the user's new device. An additional parameter FOR_LOCAL_USER is added while installing inSync Client
  3. Login as the user on the new device.
  4. inSyncAgent activates the new device for the inSync user if there is an existing device of the name provided in FOR_DEVICE schedule in OS migration restores.
  5. inSync Client restores all the data including system settings and MAPI data on the new device.
  6.  inSync Client moves the restored data which is saved at the temporary location to relevant paths and folders as required. 
    The device is ready to be shipped to the user.

User actions:

  1. Login to the new device which is ready to be used.
    The user can use both the devices until the administrator decides to deactivate the older device.

Device Replace process for non-AD Users 

The following table describes the multi-step process for the integrated mass deployment (IMD) device replace.

Step Description  
Step 1 Mark the device which needs to be replaced. For more information, see Mark old device for Refresh  
Step 2 Create a user account on the new device.  
Step 3 Generate a mass deployment token. For more information, see Generate a mass deployment token.  
Step 4 Run the IMD command with additional device replace parameters. For more information see Device Replace Parameter details.  
Step 5 Login as the user on the new device.  
Step 6  inSync Client restores all the data on the new device including system settings and MAPI data. For more information, see Temporary location directories for restored data.  
Step 7 inSync Client moves the data from the temporary location to relevant folders and paths and ships the device to the user. For more information, see Device replace for Non-AD users.  
Step 8 The device is then shipped to the user. For actions performed by the user, see Manage data after remote device refresh.