Assuming that
- you don't actually want to keep the first set of changes from day-2 (day-x + 1) to day-y after the 2nd full backup on day-z (you haven't actually said - I guess not, but you may have special requirements)
- you can cope with this being a 7-day (rather than 10-day) cycle (see 2nd-last para for why)
then all you need is a Mirror profile, also configured to use Fast Backup as per the examples in the contextual Help on Fast Backup (press F1 on FB settings page, scroll to End then start reading upwards). FB is leveraged to remember what was copied previously (until re-set) so that it only copies changes since a certain point ( > > > )
It's not clear if you want Incremental ('on day-3, only save changes since day-2; on day-4, save changes since day-3', and so on - uses minimum space) or Differential ('every day, save all changes since last-Full until next-Full backup' - uses more space but easier to Restore from). There are examples in the Help for both.
Both these examples use %DAYOFWEEK% as their governing Variable, because built-in Variables are calendar-based, and 'days in a week' is the longest constant-cycle Variable in the Earth calendar (really - think about it). If you truly do want '10' as your cycle, you'll need to investigate, edit, install and configure the profile to use the installable scripts IncVar.vbs or IncVarEx.vbs in your Pro program folder. IncVarEx is probably easiest because it adds a new settings page in the profile to configure it with (you may need to close/re-open both Pro and the profile after adding it to see this). Or, stick to '7-day', which is in fact much easier to visualize in your head, especially if you start it on Monday (=1). Otherwise you may have problems figuring out some time down the line which date is represented by any given arbitrary number (plus the fact that your Full backup (Mirror) will be happening on different days every time).
Another possibility (if you're using V7?) and much easier to configure is to use a Mirror profile set to use Versioning On Destination instead. Set it to keep C copies for D days of any detected changes (both C & D can be 7, 10 or whatever you like) and run it every day. This gives you a 'turnkey' most-recent/disaster-recovery Restore if needed, but you can also request Rollback (V7-only) in Differences window to a file-state <= the date you specify. This also stores Versions using minimum space (like Incremental)
- you don't actually want to keep the first set of changes from day-2 (day-x + 1) to day-y after the 2nd full backup on day-z (you haven't actually said - I guess not, but you may have special requirements)
- you can cope with this being a 7-day (rather than 10-day) cycle (see 2nd-last para for why)
then all you need is a Mirror profile, also configured to use Fast Backup as per the examples in the contextual Help on Fast Backup (press F1 on FB settings page, scroll to End then start reading upwards). FB is leveraged to remember what was copied previously (until re-set) so that it only copies changes since a certain point ( > > > )
It's not clear if you want Incremental ('on day-3, only save changes since day-2; on day-4, save changes since day-3', and so on - uses minimum space) or Differential ('every day, save all changes since last-Full until next-Full backup' - uses more space but easier to Restore from). There are examples in the Help for both.
Both these examples use %DAYOFWEEK% as their governing Variable, because built-in Variables are calendar-based, and 'days in a week' is the longest constant-cycle Variable in the Earth calendar (really - think about it). If you truly do want '10' as your cycle, you'll need to investigate, edit, install and configure the profile to use the installable scripts IncVar.vbs or IncVarEx.vbs in your Pro program folder. IncVarEx is probably easiest because it adds a new settings page in the profile to configure it with (you may need to close/re-open both Pro and the profile after adding it to see this). Or, stick to '7-day', which is in fact much easier to visualize in your head, especially if you start it on Monday (=1). Otherwise you may have problems figuring out some time down the line which date is represented by any given arbitrary number (plus the fact that your Full backup (Mirror) will be happening on different days every time).
Another possibility (if you're using V7?) and much easier to configure is to use a Mirror profile set to use Versioning On Destination instead. Set it to keep C copies for D days of any detected changes (both C & D can be 7, 10 or whatever you like) and run it every day. This gives you a 'turnkey' most-recent/disaster-recovery Restore if needed, but you can also request Rollback (V7-only) in Differences window to a file-state <= the date you specify. This also stores Versions using minimum space (like Incremental)