Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jan 2017 06:27:22 -0700 (MST)
From:      Warren Block <wblock@wonkity.com>
To:        David Christensen <dpchrist@holgerdanske.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD 11.0-RELEASE-p7 i386 system drive imaging and migration
Message-ID:  <alpine.BSF.2.20.1701290622500.13432@wonkity.com>
In-Reply-To: <df0c81d7-fd2b-852f-4007-5fb4b24100e0@holgerdanske.com>
References:  <df0c81d7-fd2b-852f-4007-5fb4b24100e0@holgerdanske.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sat, 28 Jan 2017, David Christensen wrote:

> What is the proper way to clone a FreeBSD system image from one drive to 
> another?

On encrypted ZFS?  I'm not sure there is a brute-force way that is 
trustworthy.  Using higher-level commands to recreate the partitions, 
GELI encryption, and then zfs send | recv are certain safer and won't 
duplicate supposedly unique IDs.

> What is the proper way to move a HDD or SSD with a FreeBSD system image from 
> one computer to another computer?

Provided the binaries have not been optimized for one CPU, just move the 
drive.  Disk drive names can change, which is not a problem when labels 
are used.  Ethernet interface names can change.  If there is only one 
interface, use ifconfig_DEFAULT in /etc/rc.conf.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1701290622500.13432>