Druva is UMIACS supported backup software for your laptop that offers additional capabilities from your smartphone. Only laptops purchased through University funding (red tagged) are eligible for this service.
Data Retention Policy
- Backup retention is tiered based on the type of backup:
|Type||Retention Length||What is it?|
|Daily||7 days||The last backup before 11:59pm each day|
|Weekly||8 weeks||The last daily backup on each Saturday|
|Monthly||12 months||The last weekly backup of each month|
After 30 days of a device not backing up, you will receive email alerts from Druva regarding this issue. UMIACS staff will also create a ticket with you as a reminder.
Devices that have not backed up for 60 days after this alert is first received will be disabled. Once disabled, any associated data will expire 1-year after the last successful backup.
Could not connect to inSync service box pops up when Windows first launches
Druva's per-user configuration file may corrupt for a number of reasons:
- Antivirus scan
- Disk issue on the system
- Some other application having a handle
- Network interruption or system crash when the .cfg file was being modified
This will lead to the above error box popping up, or the taskbar status of inSync getting stuck on "Initializing...". The solution is to regenerate the configuration file by moving the old one aside and then reactivating Druva:
- Search for Services from the search bar, launch the application, and stop the Druva inSync Client Service service.
- Open up Task Manager by hitting CTRL+Shift+ESC and end any process beginning with inSync.
- Open up File Explorer and navigate to
C:\ProgramData\Druva\inSync4\users\<yourusername>and rename inSync.cfg to inSync.old. Note that
C:\ProgramDatais a hidden folder; please either follow these instructions to make hidden folders visible, or just type the path in the File Explorer address bar.
- Wait for around 30 seconds or so, and then start the Druva inSync Client Service in Services.
- Launch the Druva inSync client and log back in with the settings specified on our setup page.
- (Important) Choose Replace my Existing Device rather than Add as New Device. This ensures that Druva does not report the same device twice on the back end. Click Continue.
- Select the name of the device as the device to replace and do not check either of the boxes for data to restore. Otherwise you may end up overwriting your computer's local data with an out of date version from the Druva server. If you are unsure of your computer's name, open up a Command Prompt and type
hostname. Click Continue.
- Druva should now function as expected.