Thx for the tip!

-----Ursprüngliche Nachricht-----
Von: Wei ZHOU <ustcweiz...@gmail.com> 
Gesendet: Montag, 20. Januar 2025 20:54
An: users@cloudstack.apache.org
Betreff: Re: Migrating management server to another server

Oh, sorry, it should be "mysqldump -R"

-Wei

On Mon, Jan 20, 2025 at 8:52 PM Wei ZHOU <ustcweiz...@gmail.com> wrote:

> Hi Swen,
>
> A quick tip, when you dump the database, please use "mysql -R" which 
> stores the procedures.
>
> -Wei
>
> On Mon, Jan 20, 2025 at 6:48 PM <m...@swen.io> wrote:
>
>> Thx, Wie for the quick reply! I will test this and if I did it 
>> successfully will add a workflow to the docu.
>>
>> Regards,
>> Swen
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Wei ZHOU <ustcweiz...@gmail.com>
>> Gesendet: Montag, 20. Januar 2025 18:44
>> An: users@cloudstack.apache.org
>> Betreff: Re: Migrating management server to another server
>>
>> The public and private keys are saved in the configuration table in DB.
>> When add a new management server, ACS will create key files in 
>> ~cloud/.ssh folder if the files do not exist. Of course you can 
>> backup the folder.
>> I think it is good enough if dump db and backup /etc/cloudstack folder.
>>
>> -Wei
>>
>>
>> On Monday, January 20, 2025, <m...@swen.io> wrote:
>>
>> > Hi all,
>> >
>> > I need to migrate the management-server (only one, db on the same
>> > server) to another VM with the same os (Ubuntu 22.04 LTS). We need 
>> > to change the hypervisor the VM is running on.
>> >
>> > I am aware to dump the database and copy custom configs, what I am 
>> > not aware of what keys we also need to copy. We added our KVM hosts 
>> > via user and password to CS, but as far as I understand CS did 
>> > create some key pairs to communicate with the hosts. Is this 
>> > correct and if so, I guess I need to copy them, too?
>> >
>> >
>> >
>> > The new management-server will use the same internal IP, but I will 
>> > restart all system VMs. Anything else I forgot? Thx everybody for help!
>> >
>> >
>> >
>> > Regards,
>> >
>> > Swen
>> >
>> >
>>
>>
>>


Reply via email to