> For the complete documentation index, see [llms.txt](https://system-development-services.gitbook.io/truesecure-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://system-development-services.gitbook.io/truesecure-guide/backup-format-overview/legacy-backup-format/hyper-v-vm-backup-legacy-step-1.-backup-route/step-9.-advanced-recurring-schedule.md).

# Step 9. Advanced Recurring Schedule

Specify the schedule for automatic running of a full backup.

![](https://1045802759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKVwxMpGGsUkYo2D86SKb%2Fuploads%2FvJ9x8NqwNRIrdoWXG361%2F5300da9d-fbda-4043-8c1b-9fb05c67e8bb.png?alt=media\&token=be14ffb8-694e-4810-a8c2-6f168ccd01ba)

As opposed to a full backup which uploads a complete copy of each file to a storage, a block-level backup uploads the full copy of your data only during the first execution of the backup plan by default.

We strongly recommend that you specify a schedule for automatic running of a full backup on this wizard page to ensure that the older versions of your files are always available in a storage that uses a block-level backup.

![](https://help.msp360.com/content/images/2c8254c2-5fdc-43d7-bc4d-76ea3f4de0bd.png)

If required, you can force the backup service to perform a full backup each time when the total size of previous block-level backups exceeds the specified proportion of the last full backup (**50**% by default).

In addition, you can make the backup service interrupt a backup process if it runs for too long by enabling a corresponding option on this wizard page.

When enabling this feature, please be informed that TrueSecure Backup is unable to predict the backup time which may vary depending on a variety of factors, and premature termination of a backup process may result in getting the backup data corrupted.

Click **Next** to proceed or **Back** to return to the previous step.