Skip to main content

Understanding Delay in Restore

Thread needs solution

I'm a new customer to Acronis and I'm trying to understand a little bit more about timing in backup and restore processes in regards to deduplication. My question mainly is this. Can I not run a restore from an archive until all indexing of that particular job is finished? I only ask because I have a recovery job submitted for a 10MB file that has been sitting for over a half hour at 6%. I took the first full backup of the disk to a dedup. Vault yesterday, but I know all indexing is not done. When I look at Res. Monitor on the machine I see the storage server looking at .loc files and the unified.ds, but no network traffic to the target system for the restore in question. What kind of performance expectation should I have with new backups? Out storage server is very powerful with fast disk and over 64GB of memory. It seems like indexing should be faster and I am worried about needing to constantly wait for indexing to actually use the system for restores. Thanks!

0 Users found this helpful