Hi everyone,
I have a Proxmox 2.3-3 Backup Server running on a HPE Microserver. The operating system is running on a single 120Gb SSD that's showing a wear level of 93%. I have purchased a better quality Samsung 250Gb SSD to replace the tired 120Gb SSD.
I'm after advice on the preferred way to replace the OS disk, hoping to keep the entire server "intact" and not have to vanilla build the box again. I'm thinking about taking an image of the tired 120Gb SSD and dropping that image onto the 250Gb SSD with Clonezilla or similar.
Is there a way to capture the PVE Backup Svr entire configuration so the config could be "deployed" to a vanilla PVE Backup Server?
Are there any "gotcha's" I may fall fowl of using the disk cloning process? I'm concerned about the UUID's of the /dev/ partitions and how these will mount (or not mount) in /etc/fstab
(I did several searches for "PVE Backup configuration" and similar. Needless to say there were many many hits to my queries.)
I have a Proxmox 2.3-3 Backup Server running on a HPE Microserver. The operating system is running on a single 120Gb SSD that's showing a wear level of 93%. I have purchased a better quality Samsung 250Gb SSD to replace the tired 120Gb SSD.
I'm after advice on the preferred way to replace the OS disk, hoping to keep the entire server "intact" and not have to vanilla build the box again. I'm thinking about taking an image of the tired 120Gb SSD and dropping that image onto the 250Gb SSD with Clonezilla or similar.
Is there a way to capture the PVE Backup Svr entire configuration so the config could be "deployed" to a vanilla PVE Backup Server?
Are there any "gotcha's" I may fall fowl of using the disk cloning process? I'm concerned about the UUID's of the /dev/ partitions and how these will mount (or not mount) in /etc/fstab
(I did several searches for "PVE Backup configuration" and similar. Needless to say there were many many hits to my queries.)
Last edited: