which option describes a valid procedure for backing up the /data file system to a remote disk named /remote/backup?

View the exhibit to inspect the file system configuration on your server.

Your department’s backup policy is to perform a full backup to a remote system disk on Saturday.
On Sunday through Friday, you are to perform an incremental backup to the same remote system
disk.
• Each incremental backup will contain only data that has been modified since the previous
Saturday backup.
• The server file systems must remain available at all times and can never be taken offline,
• The backup must not only provide for the recovery of the most recent version of a file, but must
also allow recovery of previous versions of a file created since Saturday’s full backup.
Following your company policy, which option describes a valid procedure for backing up the /data
file system to a remote disk named /remote/backup?

View the exhibit to inspect the file system configuration on your server.

Your department’s backup policy is to perform a full backup to a remote system disk on Saturday.
On Sunday through Friday, you are to perform an incremental backup to the same remote system
disk.
• Each incremental backup will contain only data that has been modified since the previous
Saturday backup.
• The server file systems must remain available at all times and can never be taken offline,
• The backup must not only provide for the recovery of the most recent version of a file, but must
also allow recovery of previous versions of a file created since Saturday’s full backup.
Following your company policy, which option describes a valid procedure for backing up the /data
file system to a remote disk named /remote/backup?

A.
On Saturday:
zfs create snapshot pool1/data@sat.
zfs send pool1/data@sat > /remote/backup/full
On each weekday:
Remove the previous daily snapshot.
zfs snapshot pool1/data@daily
zfs send –i pool1/data@sat pool1/data@daily > /remote/backup/full

B.
On Saturday:
zfs create snapshot pool1/data@sat.
zfs send pool1/data@sat | zfs recv remote/backup/’date ‘+%m%d%Y’ ‘
On each weekday:
Remove the previous daily snapshot.
zfs create pool1/data@daily
zfs send –i pool1/data@sat pool1/data@daily | zfs recv remote/backup
d%y’ ‘

C.
On Saturday:
zfs snapshot pool1/data@sat
zfs send pool1/data@sat > /remote/backup/full
On each weekday:
Remove the previous daily snapshot.
zfs snapshot pool1/data@daily
zfs send –i pool1/data@sat pool1/data@daily > /remote/backup/daily

D.
On Saturday:
zfs create snapshot pool1/data@sat
zfs send pool1/data@sat | zfs recv remote/backup
On each weekday:
Remove the previous daily snapshot.
zfs create –i pool1/data@sat pool1/data@daily
zfs send pool1/data@daily | zfs recv remote/backup

E.
On Saturday:
zfs snapshot pool1/data@sat
zfs pool1/data@sat > /remote/backup/full
On each weekday:
Remove the previous daily snapshot.
zfs snapshot pool1/data@daily
zfs send –i pool1/data@sat pool1/data@daily > /remote/backup/full



Leave a Reply 1

Your email address will not be published. Required fields are marked *

fourteen + 7 =


iietam

iietam

Correct answer is C

There is no command zfs create snapshot for A,B and D
There is no subcommand for E – zfs pool1/data@sat > /remote/backup/full

Sending and Receiving Complex ZFS Snapshot Streams
This section describes how to use the zfs send –I and –R options to send and receive more complex snapshot streams.

Keep the following points in mind when sending and receiving complex ZFS snapshot streams:

Use the zfs send –I option to send all incremental streams from one snapshot to a cumulative snapshot. Or, use this option to send an incremental stream from the original snapshot to create a clone. The original snapshot must already exist on the receiving side to accept the incremental stream.

Use the zfs send –R option to send a replication stream of all descendent file systems. When the replication stream is received, all properties, snapshots, descendent file systems, and clones are preserved.

When using the zfs send –r option without the –c option and when using the zfs send –R option stream packages omit the origin of clones in some circumstances. For more information, see Identifying ZFS Snapshot Streams.

Use both options to send an incremental replication stream.

Changes to properties are preserved, as are snapshot and file system rename and destroy operations are preserved.

If zfs recv –F is not specified when receiving the replication stream, dataset destroy operations are ignored. The zfs recv –F syntax in this case also retains its rollback if necessary meaning.

As with other (non zfs send –R) –i or –I cases, if –I is used, all snapshots between snapA and snapD are sent. If –i is used, only snapD (for all descendents) are sent.

To receive any of these new types of zfs send streams, the receiving system must be running a software version capable of sending them. The stream version is incremented.

However, you can access streams from older pool versions by using a newer software version. For example, you can send and receive streams created with the newer options to and from a version 3 pool. But, you must be running recent software to receive a stream sent with the newer options.

Example 6-1 Sending and Receiving Complex ZFS Snapshot Streams
A group of incremental snapshots can be combined into one snapshot by using the zfs send –I option. For example:

# zfs send -I pool/fs@snapA pool/fs@snapD > /snaps/fs@all-I

Reference:
http://docs.oracle.com/cd/E36784_01/html/E36835/gfwqb.html#scrolltoc