What should I check before cloning a VPS into another instance?
A raw copy of a configured VPS can carry machine identity, host keys, network settings and application credentials into the clone. Prepare an image using the platform and operating system’s supported process, then validate the new instance in an isolated context.
Instructions
1. Separate reusable software from instance identity
Identify hostnames, machine IDs, SSH host keys, static addresses, scheduled jobs, monitoring agents and application secrets. Decide which must be regenerated or re-enrolled on the new instance.
2. Follow the image’s first-boot preparation procedure
For cloud-init images, first-boot detection and cache handling determine whether per-instance configuration runs again. Do not execute cloud-init clean on the active source just as a routine troubleshooting command; image preparation has specific sequencing and shutdown requirements.
3. Validate the clone before live traffic
Confirm a new provider identifier, unique host identity, correct network assignment and authorised account. Keep duplicate scheduled jobs, message consumers and outbound mail disabled until their ownership is deliberately assigned. Verify that the new server does not accidentally impersonate the original.
Check the result
- The clone has unique server identity and approved credentials.
- No unintended duplicate production jobs or conflicting network assignments are active.
Troubleshooting
- The clone skipped initialisation
- Review cloud-init instance detection and the source image’s cache preparation.
- Both servers use the same SSH host key
- Correct the image-generation process and verify replacement host identity through a trusted console before use.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.