> Since the EOL announcement, I've been thinking of how > I should do the migration for my SOHO server.
I did just that yesterday on my office workstation-server machine. It has been running Nevada for some 18 months, up until snv_104 (when I screwed something with zones and damaged my LU database; knowing that I will eventually jump to OpenSolaris, I decided it was not worth the effort to repair). > This > V20z box provides all services for the external and > internal networks (file server, mail server, backup > server, etc.). Apart from being my main workstation, it usually runs some 5-6 VirtualBox machines, iSCSI ComStar targets, CIFS and NFS server etc. In other words, it takes some pounding... > It has been running OpenSolaris since > snv_49 and I've been happily using Live Upgrade > flawlessly over the years. I'm currently up to > snv_110. > > I have the setup this way... > > Two main drives,each having two identical partitions: > a small ufs one for root and the rest in a zfs mirror > pool holding the user home directories and /usr/local > where all of the home-built programs reside (xjed, > dirvish, most, qmail, mailfront, spanmdyke, web > pages, etc.). I have been on ZFS root since this became possible, was it around snv_90 or thereabouts, not so sure. I've got some 6 SATA disks in, but they are mostly different sizes (between 120 and 320 GB), so apart from the mirrored rpool, the rest is another three zpools (not bothered about redundancy or backups on this machine for now... until it breaks, that is!) > > The second zfs pool consists of 5 external drives in > raid-z. This holds the backups for all networked > machines. > > My thought is that I want to migrate to OpenSolaris > using a zfs root on the entire disk and minimize > downtime. My first thought is to do it this way: > > * stop the mail and web services > * do a "final" disaster backup to the raid-z pool > * export the raid-z pool. > * break the mirror (how?) and then export this pool. zpool detach poolname device2detach I didn't bother with this, just turned off the second disk with the key at this stage. > * install OpenSolaris on one full drive (At this > point there is no turning back) > * attach the old mirrored drive back as a mirror > (using the full disk) > * import the other pool > * copy all the appropriate files from the backup > * configure and start the services. I send/received the interesting ZFS from the old mirror to one of the data pools, so the contents of the old system disk was not important; in any case, I wanted to go through the configuration process again. > > Anyone see any flaws or can suggest improvements to > my approach? Not really. I had a little problem - installed OpenSolaris on disk 0, disk 1 still had the old pool on, and grub's findroot screwes - there are two pools named rpool... I had to break in the boot process and remove the findroot command. After that I was able to attach disk 1 to the rpool and resilver (still haven't out the bootblocks on the second disk, though - Monday). > > Is there a reason why I should wait for the next > OpenSolaris official release before starting this? Not as far as I know it. I am using the snv_118 respin from GenUnix. Seems fine so far (well, modulo getting rid of fcoe service, but that is documented). I still will have to configure CIFS in our AD and enable the iSCSI bits before importing the data pools. > > Thanks. > Gary Chavdar -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
