Why a restore may take longer than expected

Restore duration can vary depending on the SaaS application, the amount and type of data being restored, and limitations imposed by the destination cloud provider.

This article explains the common factors that may cause a restore operation to take longer than usual. These conditions do not necessarily indicate that the restore has failed.

Common reasons for restore delays

Retrieving backup data from deep archive storage

Before a restore can begin, SysCloud may need to retrieve the required backup data from deep archive storage. Restores involving older data may take additional time because the data must first be retrieved and prepared for restoration.

Cloud-provider API limits and response times

Cloud providers control how frequently applications can submit API requests. Restore duration may be affected when these limits are reached or when the provider experiences temporary service issues or slower response times.

In such cases, SysCloud may temporarily pause or retry requests until the cloud provider accepts them. This can occur when restoring a large volume of data, a high number of items, or running multiple restore operations simultaneously.

Data volume and item count

Restores containing large files, many individual items, or an entire account may require additional processing. The restore duration can also depend on how quickly the destination cloud accepts and recreates the items.

Item structure and dependencies

Some applications require folders, fields, metadata, permissions, or other dependent objects to be recreated in a specific order. Complex or deeply nested structures can therefore take longer to restore.

Cloud-specific considerations

The common factors described above can affect restores across multiple cloud applications. The following applications have additional conditions that may influence the restore duration.

Cloud application	Service application	Additional consideration
Microsoft 365	SharePoint and Teams	SharePoint and Teams data can contain sites, folders, lists, fields, and item paths that depend on one another. SysCloud must recreate these items in the correct order, so restores involving complex or deeply nested structures may take longer.
Slack	Messages	Slack limits how frequently conversation history can be requested. Therefore, restoring channels or conversations with a large message history may require additional time.
QuickBooks Online	Company data and attachments	A full-company restore contains many connected records and may be more affected by QuickBooks API limits. If attachments are included, older attachments may also need to be retrieved from archive storage before they can be restored.

What to do if a restore is taking longer than expected

Allow the restore operation to continue while SysCloud processes the data and handles any temporary cloud-provider restrictions. Avoid initiating duplicate restore requests for the same data.

If the restore remains in progress for an unusually long period or displays a failure status, contact SysCloud Support. Include the cloud application, restore job details, approximate start time, and the status displayed in the restore report.