Question

1

How to create an image of an entire remote system for using on other (virtual) remote machines?

rated 0 times [ 1] [ 0] / answers: 1 / hits: 2904 / 1 Year ago, wed, december 28, 2022, 4:52:23

I have ordered several virtual machines from a hosting provider, which all need exactly the same setup:

same users

same programs installed

same config (except for hostname) including cron-jobs

Is it possible and save to create a tarball of my entire system, excluding /dev, /proc, /sys folders and the /etc/hostname file and just unpack it on the disk while the system is not running (using a repair mode, or a Live CD, in case of a physical server)?

What else do I have to consider?

Edit: Since I have no physical access to these machines, everything has to be done from the command line.

Edit 2: Also /etc/network/interfaces should not be copied.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

tialmes

Add To Favorites

Follow

Total Points: 14

Total Questions: 108

Total Answers: 102

Location: Oman

Member since Thu, Jun 16, 2022

2 Years ago

tialmes questions

1 Ubuntu 22.04 netns with veth connected to bridge unable to ping gateway

Mon, Jul 12, 21, 14:03, 3 Years ago

1 Make multiple copies of one file with different names

Tue, Feb 7, 23, 19:21, 1 Year ago

1 Removing cloud-init from Minimized Server marks important network packages for removal

Tue, Aug 9, 22, 14:12, 2 Years ago

1 How can I use bash to replace a string in a file from another file

Sat, Jun 19, 21, 05:11, 3 Years ago

1 Is it true that Snap has proprietary server?

Mon, Aug 23, 21, 16:53, 3 Years ago

View All

answered 1 Year ago suitman · Accepted Answer

Yes, you can.

Make sure the /etc/fstab is still correct, based on where you put partitions and what types they are. Make sure you run mkswap on any swap partition. If UUIDs are used, then you'll need to update these. The blkid command will give you the UUIDs of all the new partitions. If labels are used, then use the e2label command (or equivalent command for your filesystem) to make sure that the labels match.

Skip these, and make sure you create empty ones at the other end: /run (/var/run on older releases), /proc, /sys, /dev. Check /proc/mounts on the old (running) system for others (there are fewer on newer releases).

Update /etc/hostname and /etc/hosts (which also contains the hostname).

Check /etc/udev/rules.d/ for a 70-persistent-net.rules or similarly named file that contains any NIC MAC addresses. These are usually skipped for virtual machines though, and the only harm would be that you end up with an eth1 device instead of the usual eth0.

As you've mentioned, you should check /etc/network/interfaces for correctness, especially with respect to ethernet device names.

Re-run the bootloader installation. This is the awkward bit. It depends on how your VPS provider boots your instance. It's worth having a plan for this before you begin.