Say I have a namespace called "PVE" where PVE cluster stores it's backups. In the same datastore, I have another namespace called "DELETED". When a VM is deleted from the PVE cluster, I move it's backups from namespace "PVE" to "DELETED" in order to keep them there for some time.
To make that work, currently I have to:
To make that work, currently I have to:
- Create a remote to 127.0.0.1 because local sync jobs only allow syncing between different datastores.
- Create a sync job using my 127.0.0.1 remote, filter by the VM I want to copy and start the task.
- Once sync has finished, delete the snapshot from "PVE" namespace.
- Why local sync are enabled between different datastores only?
- Why that sync takes a long time to finish? It doesn't have to copy barely any data, just copy the index for each snapshot. In fact, I can do the same operation simply by copying the snapshot directories on the file system from ns/PVE/vm to ns/DELETED/vm.
- Am I the only one in need of a "move backups from one namespace to another in the same datastore"?
