Running forget/retention after copy

[lukavia]

Hi,
I have setup a copy of my main backup to another location, so I have 2 copies in different places. Since the second location is a little bit smaller I run snapshot:latest there and then run forget to cleanup the old staff.
I've done it in the yaml file like so:

profiles:
  ....:
  copy:
    snapshot:latest
    run-after: resticprofile --no-prio --noansi ....forget 

It works great, except I have the following warning in the journal each time:

apr 08 14:19:34 nspawn systemd[1]: [email protected]: Got notification message from PID 3893610, but reception only permitted for main PID 3866286
apr 08 14:19:34 nspawn systemd[1]: [email protected]: Killing process 3893643 (rclone) with signal SIGKILL.
apr 08 14:19:34 nspawn systemd[1]: [email protected]: Succeeded.
apr 08 14:19:34 nspawn systemd[1]: [email protected]: Consumed 28min 22.949s CPU time.

As far as I can deduce the Got notification ... mesage is just a warning, but I was wondering if there is another way of calling forget after copy, so I don't get that ?

Thank you

[creativeprojects]

No I'm afraid not yet 😢

I suppose we need new flags in the retention section: before-copy and after-copy 🤔