Using liveupgrade on single ZFS pool


 
Thread Tools Search this Thread
Operating Systems Solaris Using liveupgrade on single ZFS pool
# 8  
Old 11-16-2012
Quote:
Originally Posted by bartus11
The question is: why would you want to do that?
You might want to put your new BE on a different ZFS pool to avoid creating snapshots and clones. For a system with lots of non-sparse zones that gets upgraded about every three months or so by using LU on a new BE, all those snapshots and clones get really nasty to deal with.

If, on the other hand, every time you create a new BE using LU you do it on a different ZFS pool than the current live BE, you get a simple clean copy.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Opening up ZFS pool as writable

I have installed FreeBSD onto a raw image file using QEMU Emulator successfully. I have formatted the image file using the ZFS file system (ZFS POOL). Using the following commands below I have successfully mounted the image file ready to be opened by zpool sudo losetup /dev/loop0 .img sudo... (1 Reply)
Discussion started by: alphatron150
1 Replies

2. Solaris

ZFS - Dataset / pool name are the same...cannot destroy

I messed up my pool by doing zfs send...recive So I got the following : zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT rpool 928G 17.3G 911G 1% 1.00x ONLINE - tank1 928G 35.8G 892G 3% 1.00x ONLINE - So I have "tank1" pool. zfs get all... (8 Replies)
Discussion started by: eladgrs
8 Replies

3. Solaris

ZFS - overfilled pool

installed Solaris 11 Express on my server machine a while ago. I created a Z2 RAID over five HDDs and created a few ZFS filesystems on it. Once I (unintentionally) managed to fill the pool completely with data and (to my surprise) the filesystems stopped working - I could not read/delete any... (3 Replies)
Discussion started by: RychnD
3 Replies

4. Solaris

Best way to rename a ZFS Pool?

Other than export/import, is there a cleaner way to rename a pool without unmounting de FS? Something like, say "zpool rename a b"? Thanks. (2 Replies)
Discussion started by: verdepollo
2 Replies

5. Solaris

zfs pool migration

I need to migrate an existing raidz pool to a new raidz pool with larger disks. I need the mount points and attributes to migrate as well. What is the best procedure to accomplish this. The current pool is 6x36GB disks 202GB capacity and I am migrating to 5x 72GB disks 340GB capacity. (2 Replies)
Discussion started by: jac
2 Replies

6. Solaris

ZFS pool question

I created a pool the other day. I created a 10 gig files just for a test, then deleted it. I proceeded to create a few files systems. But for some reason the pool shows 10% full, but the files systems are both at 1%? Both files systems share the same pool. When I ls -al the pool I just... (6 Replies)
Discussion started by: mrlayance
6 Replies

7. Infrastructure Monitoring

zfs - migrate from pool to pool

Here are the details. cnjr-opennms>root$ zfs list NAME USED AVAIL REFER MOUNTPOINT openpool 20.6G 46.3G 35.5K /openpool openpool/ROOT 15.4G 46.3G 18K legacy openpool/ROOT/rds 15.4G 46.3G 15.3G / openpool/ROOT/rds/var 102M ... (3 Replies)
Discussion started by: pupp
3 Replies

8. Solaris

unable to import zfs pool

# zpool import pool: emcpool1 id: 5596268873059055768 state: UNAVAIL status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: Sun Message ID: ZFS-8000-3C config: emcpool1 ... (7 Replies)
Discussion started by: fugitive
7 Replies

9. Solaris

ZFS Pool Mix-up

Hi all I plan to install Solaris 10U6 on some SPARC server using ZFS as root pool, whereas I would like to keep the current setup done by VxVM: - 2 internal disks: c0t0d0 and c0t1d0 - bootable root-volume (mirrored, both disks) - 1 non-mirrored swap slice - 1 non-mirrored slices for Live... (1 Reply)
Discussion started by: blicki
1 Replies
Login or Register to Ask a Question
volmirror(8)						      System Manager's Manual						      volmirror(8)

NAME
volmirror - Mirrors volumes on a disk or control default mirroring SYNOPSIS
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] medianame [new_medianame...] /usr/sbin/volmirror [-g diskgroup] [-d yes|no] -a [new_medianame...] /usr/sbin/volmirror [-g diskgroup] [-d yes|no] /usr/sbin/volmirror [-g diskgroup] -D OPTIONS
The volmirror command supports the following options: Limits operation of the command to the given disk group, as specified by disk group ID or disk group name. The medianame operands will be evaluated relative to the given disk group. If no disk group is supplied to the volmirror command, rootdg is presumed. Changes the default for subsequent volume creation, depending on the option argument. If the option argument is yes, all subsequent volumes created using the volassist command will automatically be created as mirrored volumes. If the option argument supplied is no, mirroring will be turned off for future volumes by default. Displays current default status for mirroring. Mirrors all existing volumes for the specified disk group. DESCRIPTION
The volmirror command provides a mechanism to mirror all the contents of a specified disk, to mirror all currently unmirrored volumes in the specified disk group, or to change or display the current defaults for mirroring. All volumes that have only a single plex (mirror copy), will be mirrored by adding an additional plex. Volumes containing subdisks that reside on more than one disk will not be mirrored by volmirror. The volmirror command is generally called from the voldiskadm menus. It is not an interactive command and once called, will continue until completion of the operation or until a failure is detected. Note Due to the nature of generating mirror copies of volumes, this command may take a considerable time to complete. In the first listed form of the command, the disk media name is supplied on the command line to volmirror. That name is taken to be the only disk from which volumes should be mirrored. In the case of mirroring volumes from a specified disk, only simple single-subdisk volumes are mirrored. In the first and second listed forms of the command, the new_medianame ... parameter identifies a new disk media name (or set of names). The mirroring operation being performed will use these names as targets on which to allocate the mirrors. An error will result if the same disk is specified for both the source and target disk and if no other viable targets are supplied. EXAMPLES
The following are examples of the use of the volmirror command. The following command mirrors the contents of the disk named disk01 to any available space on any available disk. Subsequent calls to volassist will cause created volumes to be mirrored by default. volmirror -d yes disk01 The following command displays the current status of default mirroring. It prints the string yes if mirroring is currently enabled or no, if not. volmirror -D The following command mirrors any volumes on disk02 onto disk03. volmirror disk02 disk03 FILES
The defaults file for volassist parameters. SEE ALSO
volintro(8), volassist(8), volrootmir(8) volmirror(8)