[DRBD-user] 200+ Resources Created, and Now I See My Mistake

[kvaps]

Hi Eric,

I have some experience with that.
I think the easiest way would be to make a database backup and remove
all `-repl` and `-REPL` suffixes from it.
Then upload it back.

Otherwise you can try to check my project which exports the LINSTOR
configuration as simple commands
https://github.com/kvaps/linstor-backup-script

I was using it to transfer a linstor database from H2 to postgress one
time. However the code is already 3 years old, it does not support
resource groups and require some rework.

Best Regards,
Andrei Kvapil

On Sun, Mar 27, 2022 at 9:34 AM Eric Robinson <eric.robinson at psmnv.com> wrote:
>
> We have created 200+ resources on our new a 5-node Linstor cluster. The database servers each have 4 NICs in 2 bonded sets. There’s a bond on the “front” (client-facing) side of the server and a bond on the “back” (replication network) side of the server. When I built the cluster, I didn’t know about NIC management. I wanted the servers to use their “back” bonds for DRBD traffic, so I created separate DNS names for the back bonds. For example, if a server is named “server-a,” then the DNS name “server-a” resolves to the IP address of the front bond, and “server-a-repl” resolves to the IP address of the back bond.
>
>
>
> When I created the cluster, I used node names server-a-repl, server-b-repl, server-c-repl, server-d-repl, because I thought that was the way to make sure DRBD used the back bonds. That was dumb. I should have left the node names alone and just created additional NICs and Linstor could have used PrefNic to assign the proper replication links.
>
>
>
> So here’s the question. Is there an easy, non-disruptive way to re-name cluster nodes and re-assign replication links without rebuilding almost everything from scratch?
>
>
>
> -Eric
>
>
>
>
>
>
>
>
>
>
>
> Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT
> drbd-user mailing list
> drbd-user at lists.linbit.com
> https://lists.linbit.com/mailman/listinfo/drbd-user