Hi
Push-back / drop-off-end applies (if you get that far).
Example: you have it set to keep [5] Versions for up to [30] days. You previously created the file Jan 7, then edited the file 5 times (and captured the creation and all the edits) roughly every 4 days, so that you have Versions dated (that is, modified, which includes 'created') on - let's say...
Jan 7
Jan 11
Jan 15
Jan 19
Jan 23
and a 'live' backup (not yet Versioned / in main Destination location) last modified (edited) yesterday Jan 27
If you deleted the file tomorrow (and ran the profile to replicate that, i.e. it is a Mirror), you would have Versions dated
Jan 11
Jan 15
Jan 19
Jan 23
Jan 27
and no live backup. The file dated Jan 7 would be pushed off the end (even though its 'expiry date' had not yet been reached) by the Versioning of the file dated Jan 27. If that represents all your edits (no further changes), but you wait for a while to delete it (!) till (say) Feb 12 (and run profile again, etc - as above), the Versions dated Jan 7 & 11 would have expired anyway (over 30 days old), but you would still have
Jan 19
Jan 23
Jan 27 < < < captured/versioned deletion
and so on.
If you don't care about mass roll-back (and are not in the habit of deleting multiple files en masse), Versioning sounds right for you as far as I can tell from here. Here endeth the lesson
Push-back / drop-off-end applies (if you get that far).
Example: you have it set to keep [5] Versions for up to [30] days. You previously created the file Jan 7, then edited the file 5 times (and captured the creation and all the edits) roughly every 4 days, so that you have Versions dated (that is, modified, which includes 'created') on - let's say...
Jan 7
Jan 11
Jan 15
Jan 19
Jan 23
and a 'live' backup (not yet Versioned / in main Destination location) last modified (edited) yesterday Jan 27
If you deleted the file tomorrow (and ran the profile to replicate that, i.e. it is a Mirror), you would have Versions dated
Jan 11
Jan 15
Jan 19
Jan 23
Jan 27
and no live backup. The file dated Jan 7 would be pushed off the end (even though its 'expiry date' had not yet been reached) by the Versioning of the file dated Jan 27. If that represents all your edits (no further changes), but you wait for a while to delete it (!) till (say) Feb 12 (and run profile again, etc - as above), the Versions dated Jan 7 & 11 would have expired anyway (over 30 days old), but you would still have
Jan 19
Jan 23
Jan 27 < < < captured/versioned deletion
and so on.
If you don't care about mass roll-back (and are not in the habit of deleting multiple files en masse), Versioning sounds right for you as far as I can tell from here. Here endeth the lesson
