If a snapshot fails for any reason, the backup must be restarted. Nor can a Backup to Disk be recovered if it fails. While a Backup to Cloud can be paused and resumed, it cannot recover from complete failure. For more details on this behavior, please review the Knowledgebase article: Direct Backups to Cloud Fail. In general, this means that Backups to Disk and Cloud are more stable overall than a Backup to Cloud only, especially for large, long-running operations. A machine under a heavy load will cause the snapshot to break faster. If a snapshot grows larger than this allocated space, it breaks and the backup fails.īackups to Cloud keep the snapshot open for a long time, long enough that even a light load on the machine can cause the snapshot to break. Snapshots are allocated a limited amount of space by Windows. The more data is written, the larger the snapshot grows. While a snapshot is active, it must account for all data written to the disk. This can be a very long time, especially for large backups on a slow connection. Your machine must keep the snapshot intact during the entire duration of your backup.ĭuring a Backup to Cloud operation, the snapshot must be active and intact for the entire duration of the backup. Once the backup to disk is complete, CSSB will upload the resulting archive to the cloud at full speed as there will not be any more blocks of data waiting to be compressed or encrypted.ĬSSB uses Volume Shadow Copy (VSS) snapshots to perform backups. However, this is done during the backup to disk phase. It still takes time to compress/encrypt the data during a Backup to Disk and Cloud. Although CSSB compresses/encrypts several blocks of data at a time, this delay can bring average transfer speeds down. In other words, it is possible that CSSB can upload a block of data so fast that the next block of data isn't ready yet. It is possible for compression and/or encryption of a block of data to take longer than uploading that block of data - especially on older machines. The power of the CPU, the type of data, and the load on the CPU will all play a part in how long it takes to compress and/or encrypt data. The time it takes to compress and/or encrypt will vary. It takes time to do the compression and/or encryption, and both encryption and compression are CPU-intensive processes. If enabled, CSSB has to compress and/or encrypt each block of data before it is uploaded. Encryption and compression can have a large effect on upload speed during a Backup to Cloud operation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |