Migrating to a new Proxmox VM installation

[RLR19]

I am new to the XPEnology scene and set up aninstall using Proxmox and transfeered all my data over, and started settinp all my Dock Containers.  It was aout thn I started to realise that the expeerncce was slow as the software and Containers were all ruing on th spinning drives.  So afteersome research I saw that ifyou run the initial installation off a single drive SSD you can then essentially have all the software run off this drive.  The part I am not clear on is how to migrate th existing spinning drives across to this install.  Can anyone assist? 

 

Both machines ar DS923+, and I know I'll need to re-install new Containees to have them run on the SSD. I'd eally like to not have to transfer the 9TB of data from my backups aain however.

[blindspot]

Hi. I would use @007revad backup scripts to backup all apps and settings and clone actual VM on ssd and start restore apps. How do you have your data located on drives? One single/multiple disk/s passtrough? 

[007revad]

https://github.com/007revad/Synology_app_mover

[RLR19]

On 2/15/2025 at 12:14 AM, blindspot said:

Hi. I would use @007revad backup scripts to backup all apps and settings and clone actual VM on ssd and start restore apps. How do you have your data located on drives? One single/multiple disk/s passtrough? 

Cheers I'll check it out.  The 4 drives are currently passed through using their serial numbers.  When connecting them to the new VM it doesn't seem to recognise the existing volumes

[007revad]

If you want to move your VMs to the new volume

 

First add the new volume as Storage in Virtual Machine Manager

1. Open Virtual Machine Manager.
2. Click Storage and Click Add.
3. Complete the steps to add to the new volume.

Then move the VM to new volume

1. Click on Virtual Machine.
2. Click on the VM to move.
3. Shut Down the VM.
4. Click Action then click Migrate.
5. Make sure Change Storage is selected.
6. Click Next.
7. Complete the steps to migrate the VM.

[blindspot]

Hi. My guess is that you don't have enough SSD storage space to move all your data.

If you want to keep actual configuration, I would separate the DS apps, config and settings from data which is located on spinning drives. Add the SSD to your actual VM. Make new volume and move applications and containers to SSD using @007revad script.

Or start fresh with a new VM, install DSM and apps on SSD, then add the drives. The DSM will tell you that it found a storage pool and will give you the possibility to get it online.

@007revad Is it possible to make a script that can change the name of a volume and storage pool?

Edited February 16 by blindspot

[007revad]

I looked into changing the volume number a year ago and it was possible in DSM 6. In DSM 7 it changes back after a reboot. And there's 12 packages I know of that have the volume number in a file or symlink that would have to also be changed. Then there's docker containers and VMM storage locations.

[RLR19]

19 hours ago, 007revad said:

If you want to move your VMs to the new volume

 

First add the new volume as Storage in Virtual Machine Manager

1. Open Virtual Machine Manager.
2. Click Storage and Click Add.
3. Complete the steps to add to the new volume.

Then move the VM to new volume

1. Click on Virtual Machine.
2. Click on the VM to move.
3. Shut Down the VM.
4. Click Action then click Migrate.
5. Make sure Change Storage is selected.
6. Click Next.
7. Complete the steps to migrate the VM.

Mate you are a legend!  This saved me from screwing around with the original Volume1 data pool.  I just exposed the SSD to the original DSM install, created a new Volume(2), then backed up and moved the Containers!  It is running so much faster now.  

 

Thanks ALL, I really appreciate the help!