Weekly Full Backup with Incremental that Automatically erases.

Time-based retention schemes won't delete the only existing backup, leaving you with no backups at all, i.e. will not delete the only chain of full+incrementals before the next full is done. If you can afford to have two fulls in the vault, you can modify the retention rules to delete archives older than one day - in this case the whole previous chain will be retained until the next full backup is created.
If you need strictly one full, and you are using a personal vault as a storage (on a local disk or a a network folder), it's possible to do it
using simplified backup naming scheme - in this case you need to create two backup tasks, one for full backup and another for incrementals, and use external scripts to delete all of them before the next backup starts.
Custom scheme allows you to erase the only existing full archive if cleanup rule 'when there is insufficient space in the vault' set.

dev-anon wrote:

using simplified backup naming scheme - in this case you need to create two backup tasks, one for full backup and another for incrementals, and use external scripts to delete all of them before the next backup starts.

The simple incremental job creates a full backup too. If I run a simple full backup Monday at 1PM and a simple incremental Monday at 5PM, on a 500GB drive I will have two seperate 500GB backups. I think a simple incremental backup, with some type of pre-execution script to delete the last weeks backups will do what I want, since the simple incremental creates a full automatically.

Attached is what I am thinking for the script. J being the destination drive. WD500 is the backup name and volume name of the drive being backed up.

This will delete the backups every day, The script needs to be intelligent and only run one day per week/month. I could schedule the task using the OS and not Acronis which avoids the issue.

Incremental-only backup plan , backing up to the same archive as another job won't create a new full instead of incremental if there is a backup already. The 'simplified file naming' is not the same as 'simple incremental job', and is described in details here - http://www.acronis.com/support/documentation/ABR11.5/#10483.html