I'm trying to migrate a NCP2 based server to a server at a new facility. I've created a clone/snapshot of the current boot filesystem, compressed it, copied it to the new machine which is running the base NCP2 install and have received the filesystem something like the following:
On current machine "zedrick" # zfs send syspool/rootfs-nmu-...@20100111 | gzip > zedrick--syspool-rootfs-nmu-042.20100111.gzip Then installed base NCP2 on machine cwnexenta and copied via scp the gzip file to /tmp and received the filesystem # gunzip -c -d /tmp/zedrick--syspool-rootfs-nmu-042.20100111.gzip | zfs receive syspool/rootfs-nmu-042 On cwnexenta the filesystem appears properly # zfs list NAME USED AVAIL REFER MOUNTPOINT syspool 13.0G 119G 24.5K legacy syspool/rootfs-nmu-000 1.08G 119G 831M legacy syspool/rootfs-nmu-042 11.9G 119G 11.9G legacy but apt-clone doesn't list the new filesystem for activation/promotion with `apt-clone -a` # apt-clone -l A C BOOTFS TITLE o o rootfs-nmu-000 Nexenta Core Platform "Hardy" [initial] What do I need to do to make this filesystem bootable? Is my approach valid? -d ------------------------------------------------------------------------ Dan Shoop Computer Scientist [email protected] GoogleVoice: 1-646-402-5293 aim: iWiring twitter: @colonelmode _______________________________________________ gnusol-users mailing list [email protected] http://lists.sonic.net/mailman/listinfo/gnusol-users
