Rename a backup group

[Tacioandrade]

Hello everybody! Some time ago I saw someone commenting in a Telegram or WhatsApp group about carrying out this process, but I couldn't find it again and I forgot to document this in my small personal process documentation, so I came to the group to request this help.

In this case, I have a place where I recreated the cluster from scratch, to correct the previous team's implementation errors and to implement HA in the environment, then in this process, we ended up renaming the VMID that was placed randomly by the previous team, but I realized that This will cause us problems with our PBS.

Currently the backup jobs are named vm/100, vm/1212, vm/202, among others, I would like to rename these backup groups to: vm/10100, vm/10101, which is based on the VMs IP: 10,100, 10.101, etc.

Thank you in advance for your help.

 

[Chris]

Hello everybody! Some time ago I saw someone commenting in a Telegram or WhatsApp group about carrying out this process, but I couldn't find it again and I forgot to document this in my small personal process documentation, so I came to the group to request this help.

In this case, I have a place where I recreated the cluster from scratch, to correct the previous team's implementation errors and to implement HA in the environment, then in this process, we ended up renaming the VMID that was placed randomly by the previous team, but I realized that This will cause us problems with our PBS.

Currently the backup jobs are named vm/100, vm/1212, vm/202, among others, I would like to rename these backup groups to: vm/10100, vm/10101, which is based on the VMs IP: 10,100, 10.101, etc.

Thank you in advance for your help.

Hi,
the recommended way to handle naming conflicts are namespaces [0]. You can create a new namespace and sync the old data to that namespace via a local sync job [1], then remove the source. Or even create a new namespace, using the correct VMIDs as group names to begin with. Since namespaces are located on the same datastore, you will also get deduplication.

[0] https://pbs.proxmox.com/docs/managing-remotes.html#namespace-support
[1] https://pbs.proxmox.com/docs/managing-remotes.html

 

[Tacioandrade]

Oi,
a maneira recomendada de lidar com conflitos de nomenclatura são namespaces [0]. Você pode criar um novo namespace e sincronizar os dados antigos com esse namespace por meio de um trabalho de sincronização local [1] e, em seguida, remover a origem. Ou até mesmo crie um novo namespace, usando os VMIDs corretos como nomes de grupo para começar. Como os namespaces estão localizados no mesmo armazenamento de dados, você também obterá desduplicação.

[0] https://pbs.proxmox.com/docs/managing-remotes.html#namespace-support
[1] https://pbs.proxmox.com/docs/managing-remotes.html

Thanks for the explanation! I thought there was a way to rename the groups, but I'm going to stick with this option, thank you very much!