The time required to back up data from the device depends on the amount of data that inSync is backing up, the number of files that inSync needs to back up, and also the folder hierarchy of the data. If it is the first backup from the user's device or if it is the first update after you changed the storage for the user, inSync takes a full backup. In such cases, it might take longer for the backup to complete.

However, if the normal backup process for a user’s endpoint device is taking longer than expected to complete, you may follow below best practices:

1. Large Data Volumes

• Initial Backup: The first backup usually takes the longest, as all selected files need to be transferred to the cloud, which can take time depending on the data volume.

Backup share that contains USB data: If the backup share contains data from a USB drive, the backup might fail.

• Incremental Backups: After the initial backup, Druva only backs up changes. However, if the endpoint has many frequently changed files or large files (like videos or virtual machines), it could increase backup time.

2. Network Bandwidth and Connectivity

• Internet Speed: Limited or slow internet bandwidth directly affects the time required to upload data to the Druva cloud.

• Network Latency: High latency or unstable connections can delay the backup process by causing interruptions that need reconnections.

• Network Policies: Firewalls, VPNs, or other network restrictions may slow down backup speeds.

3. Device Performance and Resources

• CPU and RAM: Backups may be slower on devices with limited processing power, as resources are shared between the backup process and other applications.

• Disk I/O: If the device is accessing data from an HDD instead of an SSD, or if other intensive applications are running, it can slow down read/write processes for backups.

4. Backup Configuration and Profile

• Backup Frequency: If frequent backups are configured, the device may back up smaller chunks but may appear to be backing up more often.

• Data Selection: User Profiles may be set to back up extensive file types and directories, including large folders or system directories, which can extend backup time, please refer to Profile Optimization steps as a best practice

For example: The inclusion of %userprofile% will back up all folders under the user profile. As a result, default folders such as Desktop, Documents, and Downloads can be excluded from the backup configuration to avoid redundancy. We do not want to backup the same data via separate containers as inSync will spend time scanning all containers separately.

5. Environmental and External Factors

• Heavy Endpoint Usage: If the device is in use during business hours, the backup may slow down to avoid interrupting productivity.

• Sleep/Hibernate Settings: Backup pauses if the device goes into sleep or hibernate mode, affecting overall backup duration.

• Throttling: Some organizations set bandwidth throttling policies to minimize network impact during peak hours, which can slow down backup transfers.

Mitigation Tips:

1. Set Backup Profiles Wisely: Limit the selection to necessary files and schedule backups during off-hours.

2. Optimize Network Settings: Check internet stability, bandwidth allocation, and adjust backup throttling if needed.

3. Regular Device Maintenance: Ensure endpoint devices have enough memory and are optimized for performance.

4. Monitor Endpoint Backup Logs: Check logs to identify frequent slowdowns or interruptions, which may need IT intervention.

By addressing these factors, organisations can improve the backup experience and reduce overall backup times for Druva endpoint devices.

Note: The CPU priority setting affects backup performance and system resources: a low priority may increase backup time, while a high priority can impact other applications’ performance. Default CPU priority configured by the inSync is 7.

To limit the network bandwidth consumption and CPU utilization click here

📝 Note

​You can set network bandwidth and CPU priority for inSync through profiles. You cannot do this on an individual user level.