What is the best way of using systemd-run in place of a simple
sudo -u xxx at -f backupJ-447.cmd  03:10
Our org has gone systemd mad and no longer installs 'at', 'batch' and cron is depricated on our new systems. I need a way to scheule occasional "one-off" file copies to happen in the middle of the night. I tried the following
sudo systemd-run --unit=backupJ-477.cmd --on-calendar 03:10 sudo -u xxx  /home/me/backupJ-477.cmd
But the job is permanent and runs every night. If I delete the job its unit name is somehow still persistent and cant be reused. If I dont give it a unit name I end up with dozens of random unit or job numbers which I cant review to see what they do/did.

atthat contained a paragraph under BUGS to the effect of "atshould be implemented bycron". Therefore, use cron, and include code in the backup script that removes the crontab entry.cronjobs.--on-calendar 2021-07-14 03:10) to preventsystemd-runfrom running it repeatedly, according to reddit.com/r/linuxquestions/comments/du0zke/…