Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 11.1 Administration: ZFS File Systems Oracle Solaris 11.1 Information Library |
1. Oracle Solaris ZFS File System (Introduction)
2. Getting Started With Oracle Solaris ZFS
3. Managing Oracle Solaris ZFS Storage Pools
4. Managing ZFS Root Pool Components
5. Managing Oracle Solaris ZFS File Systems
6. Working With Oracle Solaris ZFS Snapshots and Clones
7. Using ACLs and Attributes to Protect Oracle Solaris ZFS Files
8. Oracle Solaris ZFS Delegated Administration
9. Oracle Solaris ZFS Advanced Topics
10. Oracle Solaris ZFS Troubleshooting and Pool Recovery
11. Archiving Snapshots and Root Pool Recovery
Overview of ZFS Recovery Process
ZFS Pool Recovery Requirements
Recreating Your Root Pool and Recovering Root Pool Snapshots
How to Recreate the Root Pool on the Recovery System
12. Recommended Oracle Solaris ZFS Practices
Before you create the ZFS root pool snapshot, consider saving the following information:
Capture the root pool properties.
sysA# zpool get all rpool
Identify the size and current capacity of the root pool disk.
sysA# zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT rpool 74G 5.42G 68.6G 7% 1.00x ONLINE -
Identify the root pool components.
sysA# zfs list -r rpool NAME USED AVAIL REFER MOUNTPOINT rpool 13.8G 53.1G 73.5K /rpool rpool/ROOT 3.54G 53.1G 31K legacy rpool/ROOT/solaris 3.54G 53.1G 3.37G / rpool/ROOT/solaris/var 165M 53.1G 163M /var rpool/VARSHARE 37.5K 53.1G 37.5K /var/share rpool/dump 8.19G 53.4G 7.94G - rpool/export 63K 53.1G 32K /export rpool/export/home 31K 53.1G 31K /export/home rpool/swap 2.06G 53.2G 2.00G -
The following steps describe how to create a recursive snapshot of the root pool that will include all file systems in the root pool. Other non-root pools can be archived in this same way.
Consider the following points:
For complete system recovery, send the snapshots to a pool on a remote system.
Create an NFS share from the remote system and also configure ssh to allow privileged access, if necessary.
The recursive root pool snapshot is sent as one large snapshot file to a remote system, but you could send the recursive snapshots to be stored as individual snapshots on a remote system.
In the steps that follow, the recursive snapshot is named rpool@snap1. The local system to be recovered is sysA and the remote system is sysB. Note that rpool is the default root pool name and might be different on your system.
sysA# zfs snapshot -r rpool@rpool.snap1
sysA# zfs destroy rpool/dump@rpool.snap1 sysA# zfs destroy rpool/swap@rpool.snap1
The swap volume does not contain data that is relevant to a system migration or recovery. Do not remove the dump volume snapshot if you wish to preserve any crash dumps.
In the following steps, the /tank/snaps file system is shared for storing the recursive root snapshot.
sysB# zfs set share.nfs=on tank/snaps sysB# zfs set share.nfs.sec.default.root=sysA tank/snaps
Send the recursive snapshot to the remote file system that was shared in the previous step.
sysA# zfs send -Rv rpool@rpool.snap1 | gzip > /net/sysB/tank/snaps/ rpool.snap1.gz sending from @ to rpool@rpool.snap1 sending from @ to rpool/VARSHARE@rpool.snap1 sending from @ to rpool/export@rpool.snap1 sending from @ to rpool/export/home@rpool.snap1 sending from @ to rpool/ROOT@rpool.snap1 sending from @ to rpool/ROOT/solaris@install sending from @install to rpool/ROOT/solaris@rpool.snap1 sending from @ to rpool/ROOT/solaris/var@install sending from @install to rpool/ROOT/solaris/var@rpool.snap1