I''m new to ZFS and a scenario recently came up that I couldn''t figure out. We are used to using Veritas Volume Mgr so that may affect our thinking to this approach. Here it is. 1. ServerA was originally built let''s say in January ''09 with the Solaris 10 build from 10/08 with zfs as its default filesystem and was setup to mirror. So zpool status might show something like this: pool: rpool state: ONLINE config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c1t0d0s0 ONLINE 0 0 0 c1t1d0s0 ONLINE 0 0 0 errors: No known data errors 2. Now lets say someone came in and thought that this box was no longer needed, and reinstalled with the Solaris 10 build from 05/09 with zfs but didn''t mirror it but the root pool is also called rpool. Now looking like this: pool: rpool state: ONLINE config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 c1t0d0s0 ONLINE 0 0 0 errors: No known data errors 3. Now the part I can''t figure out. It was discovered that there is data you need from the system before it was rebuilt. How do you get the data off c1t1d0s0 keeping all your current build, yet pulling off the old data you need? I was thinking it might be as simple as doing a zfs import but how do you do that when your root filesystem is already called rpool? --- Jon Whitehouse Systems Engineer - IT, Server Support MS 5221 1800 W. Center Street Warsaw, IN 46580 (574) 371-8684 (574) 377-2829 (cell) jonathan.whitehouse at zimmer.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20090908/c23bba1e/attachment.html>
On Tue, 8 Sep 2009 15:09:24 -0400, Jon Whitehouse <Jonathan.Whitehouse at zimmer.com> wrote:>I''m new to ZFS and a scenario recently came up that I couldn''t figure out. We are used to using Veritas Volume Mgr so that may affect our thinking to this approach. > >Here it is. > > >1. ServerA was originally built let''s say in January ''09 with the Solaris 10 build from 10/08 with zfs as its default filesystem and was setup to mirror. So zpool status might show something like this: > >pool: rpool >state: ONLINE >config: > >NAME STATE READ WRITE CKSUM >rpool ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c1t0d0s0 ONLINE 0 0 0 > c1t1d0s0 ONLINE 0 0 0 > >errors: No known data errors > > >2. Now lets say someone came in and thought that this box was no longer needed, and reinstalled with the Solaris 10 build from 05/09 with zfs but didn''t mirror it but the root pool is also called rpool. Now looking like this: > >pool: rpool >state: ONLINE >config: > >NAME STATE READ WRITE CKSUM >rpool ONLINE 0 0 0 > c1t0d0s0 ONLINE 0 0 0 > >errors: No known data errors > > >3. Now the part I can''t figure out. > It was discovered that there is data > you need from the system before it was rebuilt. > How do you get the data off c1t1d0s0 keeping > all your current build, yet pulling off the > old data you need? > > I was thinking it might be as simple as doing a > zfs import but how do you do that when your > root filesystem is already called rpool?zfs import without any argument will tell you which pools can be imported, not only by name but also with their unique ID''s. It can then be imported using its unique ID, and renamed by the import subcommand. Also, you can provide an alternative mountpoint (altroot). For details see: man zpool -- ( Kees Nuyt ) c[_]
Hi Jon, If the zpool import command shows the old rpool and associated disk (c1t1d0s0), then you might able to import it like this: # zpool import rpool rpool2 Which renames the original pool, rpool, to rpool2, upon import. If the disk c1t1d0s0 was overwritten in any way then I''m not sure this operation will work. Cindy On 09/08/09 13:09, Jon Whitehouse wrote:> I''m new to ZFS and a scenario recently came up that I couldn''t figure > out. We are used to using Veritas Volume Mgr so that may affect our > thinking to this approach. > > > > Here it is. > > > > 1. ServerA was originally built let''s say in January ''09 with the > Solaris 10 build from 10/08 with zfs as its default filesystem and was > setup to mirror. So zpool status might show something like this: > > pool: rpool > state: ONLINE > config: > > NAME STATE READ WRITE CKSUM > rpool ONLINE 0 > 0 0 > mirror ONLINE 0 > 0 0 > c1t0d0s0 ONLINE 0 0 0 > c1t1d0s0 ONLINE 0 0 0 > > errors: No known data errors > > 2. Now lets say someone came in and thought that this box was no > longer needed, and reinstalled with the Solaris 10 build from 05/09 with > zfs but didn''t mirror it but the root pool is also called rpool. Now > looking like this: > > pool: rpool > state: ONLINE > config: > > NAME STATE READ WRITE CKSUM > rpool ONLINE 0 > 0 0 > c1t0d0s0 ONLINE 0 0 0 > > errors: No known data errors > > 3. Now the part I can''t figure out. It was discovered that there > is data you need from the system before it was rebuilt. How do you get > the data off c1t1d0s0 keeping all your current build, yet pulling off > the old data you need? > > > > I was thinking it might be as simple as doing a zfs import but how do > you do that when your root filesystem is already called rpool? > > > > --- > > Jon Whitehouse > > Systems Engineer - IT, Server Support > > MS 5221 > > 1800 W. Center Street > > Warsaw, IN 46580 > > (574) 371-8684 > > (574) 377-2829 (cell) > > jonathan.whitehouse at zimmer.com > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Tue, Sep 8, 2009 at 3:09 PM, Jon Whitehouse<Jonathan.Whitehouse at zimmer.com> wrote:> I''m new to ZFS and a scenario recently came up that I couldn''t figure out. > We are used to using Veritas Volume Mgr so that may affect our thinking to > this approach. > > > > Here it is. > > > > 1.?????? ?ServerA was originally built let''s say in January ''09 with the > Solaris 10 build from 10/08 with zfs as its default filesystem and was setup > to mirror.? So zpool status might show something like this: > > pool: rpool > state: ONLINE > config: > > NAME?? STATE??? ??????????????? ??????????????? READ???? WRITE?? CKSUM > rpool???? ??????????????? ONLINE??????????????? 0 > 0????????????? 0 > ?mirror? ??????????????? ONLINE??????????????? 0????????????? 0 > 0 > ?? c1t0d0s0?????????? ONLINE??????????????? 0????????????? 0????????????? 0 > ?? c1t1d0s0?????????? ONLINE??????????????? 0????????????? 0????????????? 0 > > errors: No known data errors > > 2.?????? Now lets say someone came in and thought that this box was no > longer needed, and reinstalled with the Solaris 10 build from 05/09 with zfs > but didn''t mirror it but the root pool is also called rpool.? Now looking > like this: > > pool: rpool > state: ONLINE > config: > > NAME?? STATE??? ??????????????? ??????????????? READ???? WRITE?? CKSUM > rpool???? ??????????????? ONLINE??????????????? 0 > 0????????????? 0 > ?? c1t0d0s0?????????? ONLINE??????????????? 0????????????? 0????????????? 0 > > errors: No known data errors > > 3.?????? Now the part I can''t figure out.? It was discovered that there is > data you need from the system before it was rebuilt.? How do you get the > data off c1t1d0s0 keeping all your current build, yet pulling off the old > data you need? > > > > I was thinking it might be as simple as doing a zfs import but how do you do > that when your root filesystem is already called rpool?Do a ''zpool import'' with no options and if it is still viable it will list it''s ID #. You can then import it with a: # zpool import -R /oldrpool ID# oldrpool -Ross