Last updated on FEBRUARY 13, 2017
Applies to:Solaris Operating System - Version 10 11/06 U3 and later
Solaris x64/x86 Operating System - Version 10 11/06 U3 and later
Information in this document applies to any platform.
Solaris 11 Note: The recommended approach is to use Unified Archives to clone the system or 'beadm -p' on Solaris 11.x systems to create a new Boot Environment on a different ZFS pool.
Unlike most other volume managers, when a device is detached from a ZFS Pool the data on the detached device is rendered inaccessible. The data on the detached device cannot be imported, mounted, or booted. The 'zpool split' sub-command was introduced to provide an ability to clone a mirrored zpool by creating a new pool using the detached device.
The ZFS Admin Guide for says the following:
Creating a New Pool By Splitting a Mirrored ZFS Storage Pool
A mirrored ZFS storage pool can be quickly cloned as a backup pool by using the zpool split command. You can use this feature to split a mirrored root pool, but the pool that is split off is not bootable until you perform some additional steps.
This document describes those 'additional steps'.
Caveats & Assumptions
- The new/split pool must be used on the same host or the same server family type and architecture. ie: If the source rpool is imported and split on a T5120, the new pool must also be used on the same server type (T5xx0). Moving or importing the new pool on a T3, T4, M5, M6, etc may cause the boot to fail or panic due to missing packages relating to the new platform type and architecture. This is not supported and beyond the scope for which this document was intended.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms