The storage pool configuration on your server is:
You back up the /pool1/data file system, creating a snapshot and copying that snapshot to tape
(/dev/rmt/0). You perform a full backup on Sunday night and Incremental backups on Monday
through Saturday night at 11:00 pm. Each incremental backup will copy only the data that has
been modified since the Sunday backup was started.
On Thursday, at 10:00 am, you had a disk failure. You replaced the disk drive (c4t0d0). You
created pool (pool1) on that disk.
Which option would you select to restore the data in the /pool1/data file system?
A.
zfs create pool1/data
Load the Monday tape and enter:
zfs recv pool1/data < /dev/rmt/0
Load the Wednesday tape and enter:
zfs recv –F pool1/data < /dev/rmt/0
B.
Load the Sunday tape and restore the Sunday snapshot:
zfs recv pooll/data < /dev/rmt/0
zfs rollback pool1/data@mon
Load the Wednesday tape and restore the Wednesday snapshot:
zfs recv –i pooll/data < /dev/rmt/0
zfs rollback pool1/data@wed
C.
zfs create pooll/data
Load the Wednesday tape and enter:
zfs recv -F pool1/data < /dev/rmt/0
D.
Load the Sunday tape and enter:
zfs recv pool1/data < /dev/rmt/0
Load the Wednesday tape and enter:
* commands missing*
Explanation:
First the full backup must be restored. This would be the Sunday backup.
Then the last incremental backup must be restored. This would be the Wednesday backup.Before restoring the Wednesday incremental file system snapshot, the most recent snapshot must
first be rolled back.
By exclusion D) would be best answer even though it is incomplete.
D?
-B is wrong, because you do not need rollback, as rollback rolls back all the changes to the previous snapshot, so you cannot use it on snapshots in the future.
-C is wrong, because you cannot restore an incremental backup, if there was no full restored. that will probably result in an empty filesystem.
-D is only a half. this *missing command* part should have the “zfs recv pool1/data ~/pool1.Full
root@sol11-ai:/pool1/data# touch inc
root@sol11-ai:/pool1/data# ls
fullbackup inc
root@sol11-ai:/pool1/data# ls -l
total 2
-rw-r–r– 1 root root 0 Apr 28 05:44 fullbackup
-rw-r–r– 1 root root 0 Apr 28 05:53 inc
root@sol11-ai:/pool1/data# zfs snapshot pool1/data@Inc
root@sol11-ai:/pool1/data# zfs list -t snapshot | grep pool1
pool1/data@Full 19K – 31K –
pool1/data@Inc 0 – 31K –
root@sol11-ai:/pool1/data#
root@sol11-ai:/pool1/data# zfs send -i pool1/data@Full pool1/data@Inc >~/pool1.inc
root@sol11-ai:/pool1/data# ls -l ~/pool*
-rw-r–r– 1 root root 49112 Apr 28 05:53 /root/pool1.Full
-rw-r–r– 1 root root 10856 Apr 28 05:55 /root/pool1.inc
root@sol11-ai:/# zpool destroy pool1
root@sol11-ai:/# zpool list pool1
cannot open ‘pool1’: no such pool
root@sol11-ai:/# zpool create pool1 c2t0d0
root@sol11-ai:/# zfs create pool1/data
root@sol11-ai:/#
root@sol11-ai:/# cd /pool1/data
root@sol11-ai:/pool1/data# ls
root@sol11-ai:/pool1/data# ls -al
total 6
drwxr-xr-x 2 root root 2 Apr 28 05:56 .
drwxr-xr-x 3 root root 3 Apr 28 05:56 ..
root@sol11-ai:/pool1/data#
root@sol11-ai:/pool1/data# cd ..
root@sol11-ai:/pool1# zfs recv -F pool1/data < ~/pool1.Full
root@sol11-ai:/pool1# cd data
root@sol11-ai:/pool1/data# ls
fullbackup
root@sol11-ai:/pool1/data#
root@sol11-ai:/pool1# zfs recv pool1/data < ~/pool1.inc
root@sol11-ai:/pool1# ls data
fullbackup inc
root@sol11-ai:/pool1#
root@sol11-ai:/pool1# zfs destroy -r pool1/data
root@sol11-ai:/pool1# zfs list| grep pool1
pool1 96.5K 1.95G 32K /pool1
root@sol11-ai:/pool1# zfs recv pool1/data < ~/pool1.Full
root@sol11-ai:/pool1# zfs list| grep pool1
pool1 137K 1.95G 31K /pool1
pool1/data 31K 1.95G 31K /pool1/data
root@sol11-ai:/pool1# cd data
root@sol11-ai:/pool1/data# ls
fullbackup
root@sol11-ai:/pool1/data# zfs recv -F pool1/data < ~/pool1.inc
root@sol11-ai:/pool1/data# ls
fullbackup inc
root@sol11-ai:/pool1/data# ls -la
total 8
drwxr-xr-x 2 root root 4 Apr 28 05:53 .
drwxr-xr-x 3 root root 3 Apr 28 06:01 ..
-rw-r–r– 1 root root 0 Apr 28 05:44 fullbackup
-rw-r–r– 1 root root 0 Apr 28 05:53 inc
root@sol11-ai:/pool1/data#
Wow, the system somehow cut out the half of my comment 🙁
So before the test: I think only [A] can be right. and it works also without the -F option.
Which is missing from the test:
root@sol11-ai:/pool1/data# zfs list | grep pool1
pool1 135K 1.95G 32K /pool1
pool1/data 31K 1.95G 31K /pool1/data
root@sol11-ai:/pool1/data#
root@sol11-ai:/pool1/data# zpool status pool1
pool: pool1
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
pool1 ONLINE 0 0 0
c2t0d0 ONLINE 0 0 0
errors: No known data errors
root@sol11-ai:/pool1/data#
root@sol11-ai:/pool1/data# zfs list -t snapshot | grep pool1
root@sol11-ai:/pool1/data# touch fullbackup
root@sol11-ai:/pool1/data# ls -l
total 1
-rw-r–r– 1 root root 0 Apr 28 05:44 fullbackup
root@sol11-ai:/pool1/data# zfs snapshot pool1/data@Full
root@sol11-ai:/pool1/data# zfs list -t snapshot | grep pool1
pool1/data@Full 0 – 31K –
root@sol11-ai:/pool1/data# zfs send pool1/data@Full >~/pool1.Full
root@sol11-ai:/pool1/data# touch inc
root@sol11-ai:/pool1/data# ls
Here continues the part in the previous comment.
So i vote on [A]
some addon for B, there is no -i option in zfs recv also.
Correct Answer is ‘D’ with missing last command zfs recv -F pool1/data >You replaced the disk drive (c4t0d0). You
created pool (pool1) on that disk.