Dima, I understood it differently: Petta would like to keep a surebackup job running for many days after it's started. This is not possible in normal circumstances as the new execution of a backup job involving the same backup set will shut down the surebackup job. A workaround quoted in other threads is to copy the backup set, import it as a new backup and use it as a source for surebackup, so that this set will not be used by any incoming backup job.
EMEA Cloud Architect @ Veeam Software
Veeam VMCE #1