This will depend on the amount data you have selected and the performance of your connection. You should consider seeding if the time required to back up all the data on a Cloud Backup's first run would be too long and impact other processes. Your backup job will then detect the data in the container the first time it runs, and only back up data that has changed. Seeding involves putting the data on a removable drive and sending it to your cloud provider so they can copy the data to your cloud container. When you create a Cloud Backup job, you can seed the data to the cloud destination if there is too much data to send across the internet in the first full backup. Note: If you manually cancel a Cloud Backup job in BackupAssist, the next time that job runs (either manually or scheduled), the backup job will resume from the point at which it was canceled. If the backup job can resume after skipping data chunks that could not be backed up, the backup job will continue without those files and add a warning to the backup report to advise what files were not backed up.If the backup job cannot resume, it will not create a backup and the job will fail.If the backup job can resume, it will complete the backup.If a problem interrupts the backup job, BackupAssist will try several times to continue backing up, and if this does not work, it will try the next chunk to be backed up in case the problem is with specific chunks of data. This means if the backup jobs stops or is interrupted, for example due to a network or internet outage, the backup job can resume and does not need to restart. Cloud Backup backs up files in chunks and keeps track of what files have been sent to the cloud destination.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |