克里斯克兰茨 的一天克兰茨生活克里斯

SnapMirror快照镜像

目录

名称

SnapMirror快照镜像 - 活动日志的SnapMirror快照镜像

故事大纲

/等/日志/ SnapMirror快照镜像

描述

该SnapMirror快照镜像日志文件包含SnapMirror快照镜像本菲勒活动日志。 和目的地档案库的文件生命在/ etc /原记录在根量两者。 当选项snapmirror.log.enable设置为 ON时，所有的SnapMirror快照镜像活动将被记录在此日志文件。 请参阅有关如何启用详细的选项和禁用此选项。 每个周日00:00 /等/日志/ SnapMirror快照镜像移动到/ etc/log/snapmirror.0，/ etc/log/snapmirror.0被移动到/ etc/log/snapmirror.1，等等。 后缀可以上升到5。 这个过程被称为旋转。 SnapMirror快照镜像日志条目保存为六个星期。

每个文件入境的/ etc /日志/ SnapMirror快照镜像是一个单一的线场组成的空间分隔。 首先，所有的日志项类型字段和一个时间戳字段。 最后一栏可以围封括号，在这种情况下，它可能包含空格。 时间戳字段包含固定数量的空格，因此可以作为五个空间分隔的领域进行分析。 哪些领域出现，而在它们出现在什么顺序，是由日志项（类型字段确定这是第一个字段）。

以下是每个字段的描述。

类型说明的项类型的项，这也决定了该格式的休息。 它可以是以下值之一：

日志

日志设施活动

格式： 类型时间戳event_info ...

sys

全系统活动

格式： 类型时间戳event_info ...

tgt

snapvault target activity

Format: type timestamp volume target event_info…

src

source activity

Format: type timestamp source destination event_info…

dst

destination activity

Format: type timestamp source destination event_info…

cmd

user command activity

Format: type timestamp source destination event_info…

scn

replication check source activity

Format: type timestamp source destination event_info…

chk

replication check destination activity.

Format: type timestamp source destination event_info…

vol

volume-wide activity

Format: type timestamp volume event_info…

slk

softlock addition-deletion activity

Format: type timestamp softlock event_info…

timestamp
Displayed in ctime() format, eg Fri Jul 17 20:41:09 GMT. Indicates the time this event is recorded.

volume Specifies the name of the volume to which this entry applies.

target This is the name and type of the target for this entry. Targets are volume-wide actions, typically snapshot creations. It is displayed as two colonseparated fields, as follows:

target_type : target_name

The target name may be an empty string.

source This is the name of the source filer and the volume name or qtree path to be mirrored. The name is specified as two colon-separated fields, as follows:

host : path

This field may be `-' when not applicable for the event.

destination
This is the name of the destination filer and the volume name or qtree path of the destination. The name is specified as two colon-separated fields, same as in the source field.

This field may be `-' when not applicable for the event.

event_info
This field contains the event which is being logged. Some events may have extra information in parentheses.

Request ( IP address | transfer type ) A transfer request has been sent (destination) or received (source). On source side, the IP address of the destination filer that made the request is included in parentheses. On destination side, the transfer type is included in the parentheses.

Start The beginning of a transfer.

Start (Snapshots to check=#num, level={data|checksum}, {check|fix}, {quick|full} mode)
The beginning of a replication check or fix session. The session options are included in the parentheses. All options appear on the destination side log but only the "snapshots to check" option appears in source side log.

Restart (@ num KB)
The beginning of a restarted transfer.

End ( num KB done)
The completion of a transfer. The total size of the transfer in KB is included in the parentheses.

End (src_only= num_1 , dst_only= num_2 , mismatch= num_3 ) The completion of a replication check or fix session. The summary of the session is included in the parentheses. The summary is present only on the destination side logs. Source side logs will not contain any summary information.

Abort ( error msg )
A transfer is aborted. The error message is included in the parentheses.

Defer ( reason )
Indicates a transfer is deferred because of a resource limitation. The reason for the deferment is included in the parentheses.

Wait_tape
A SnapMirror tape operation is waiting for next tape.

New_tape
A SnapMirror tape operation continued the operation with the new tape.

Sync_start
The start of synchronous mirroring mode for the SnapMirror relationship specified by this log entry.

Sync_end ( reason )
The end of synchronous mirroring mode for the SnapMirror relationship specified by this log entry. The reason for dropping out of synchronous mode is included in the parentheses.

Quiesce_start
The beginning of quiesce process.

Quiesce_end
The completion of quiesce process.

Quiesce_failed ( reason )
The failure of quiesce process. The reason for failure is included in the parentheses.

Rollback_start
The beginning of a rollback process for a qtree SnapMirror or SnapVault.

Rollback_end
The completion of a rollback process for a qtree SnapMirror or SnapVault.

Rollback_failed ( reason )
The failure of a rollback process for a qtree SnapMirror or SnapVault. The reason for failure is included in the parentheses.

Coalesce_start ( snapshot )
The beginning of a coalesce process for a SnapVault qtree. The base snapshot for the coalesce operation is included in the parentheses.

Coalesce_end
The completion of a coalesce process for a SnapVault qtree.

Coalesce_failed ( reason )
The failure of a coalesce process for a SnapVault qtree. The reason for failure is included in the parentheses.

Target_start
The beginning of a SnapVault target.

Target_end
The completion of a SnapVault target.

Target_failed ( reason )
The failure of a SnapVault target. The reason for failure is included in the parentheses.

Start_logging
SnapMirror log was enabled.

End_logging
SnapMirror log was disabled.

SnapMirror_on ( cause )
SnapMirror was enabled on this host. The operation or process that caused SnapMirror to become enabled is specified in the parentheses.

SnapMirror_off ( cause )
SnapMirror was disabled on this host. The operation or process that caused SnapMirror to become disabled is specified in the parentheses.

SnapVault_on ( cause )
SnapVault was enabled on this host. The operation or process that caused SnapVault to become enabled is specified in the parentheses.

SnapVault_off ( cause )
SnapVault was disabled on this host. The operation or process that caused SnapVault to become disabled is specified in the parentheses.

Resume_command
User issued snapmirror resume command.

Break_command
User issued snapmirror break command.

Release_command
User issued snapmirror release command.

Abort_command

Abort_command ( type )
User issued snapmirror abort command. The type will only be present if the abort was issued with additional options which changed the type of the abort.

Resync_command（ 普通快照 ）
用户发出的SnapMirror快照镜像重新同步命令。 为重新同步运行的共同快照包含在括号中。

Restore_resync_command（ 共同快照 ）用户发出snapvault恢复- r命令。 为重新同步运行的共同快照包含在括号中。

Migrate_command
用户发出的SnapMirror快照镜像迁移命令。

Request_check（snapshot_name）
会议期间复制的要求检查单快照。 这是源端日志项。 每个被检查的快照复制支票会议将有其入境。 快照名称在括号内。

Checking_snapshot 源snapshot_name（时间戳 ，cpcount = num_2，snapid = 身份证 ）到dest_snapshot_name（时间戳 ，cpcount = 计数 ，snapid = ID）的支票开始复制过程中一个比较单一的快照。 这是记录在源和目的地。

Abort_check
为SnapMirror快照镜像复制或SnapVault检查会议中止。 中止的原因是包含在括号中。

Abort_check_command
用户签发支票复制中止命令。 相应的日志文件项似乎与键入 cmd。

Data_differ（（块在file_path之VBN blk_num | VBN之））
复制一个数据块检查发现不匹配。 无论是块数和inode的路径或批量块号（VBN）之包含在括号中。

Unique_in_src（entry_path entry_type为）复制入境检查发现的唯一来源目前在。 该条目类型和入口路径包含在括号中。

Unique_in_dst（entry_path entry_type为）复制检查发现1项只存在于目的地 。 该条目类型和入口路径包含在括号中。

Size_differ（ 路径 ）
复制检查发现在指定的inode文件的大小不匹配。 该inode的路径是包含在括号中。

Type_differ（ 路径 ）
检查发现，复制的inode类型不匹配。 该inode的路径是包含在括号中。

UID_differ（ 路径 ）
复制检查发现一个用户的ID不匹配指定的inode。 该inode的路径是包含在括号中。

GID_differ（ 路径 ）
复制检查发现一组ID为指定的索引节点不匹配。 该inode的路径是包含在括号中。

Perm_differ（ 路径 ）
复制检查发现许可或指定的inode dosbit不匹配。 该inode的路径是包含在括号中。

Atime_differ ( path )
Replication check found a mismatch in the last access time for specified inode. The inode path is included in the parentheses.

Mtime_differ ( path )
Replication check found a mismatch in the last modification time for specified inode. The inode path is included in the parentheses.

Ctime_differ ( path )
Replication check found a mismatch in the last size/status change time for specified inode. The inode path is included in the parentheses.

Crtime_differ ( path )
Replication check found a mismatch in the creation time for specified inode. The inode path is included in the parentheses.

Rdev_differ ( path )
Replication check found a device number mismatch for specified inode. The inode path is included in the parentheses.

DOSbits_differ ( path )
Replication check found a DOS bits mismatch for specified inode. The inode path is included in the parentheses.

ACL_differ ( path )
Replication check found an NT or NFS V4 ACL mismatch for specified inode. The inode path is included in the parentheses.

Hardlink_differ ( path )
Replication check found a hardlink for specified inode, but the inode on destination doesn't match between the links. The inode path is included in the parentheses.

Qtree_oplock_differ ( path )
Replication check found oplock setting mismatch for a qtree. The qtree path is included in the parentheses.

Qtree_security_differ ( path )
Replication check found security setting mismatch for a qtree. The qtree path is included in the parentheses.

Hole_uses_disk_space ( path )
Replication check found unnecessary disk usage for specified inode, this however is not a mismatch. The inode path is included in the parentheses.

Convert_command
User issued snapmirror convert command.

Older_snapshot
Updating from a snapshot which is older than the current base snapshot.

Snapshot_delete ( snapshot name )
A snapshot is deleted from this volume. The snapshot name is included in the parentheses.

Snapshot_replace ( snapshot name )
A SnapVault snapshot has been replaced after a SIS operation with a newer snapshot of the same name. The snapshot name is included in the parentheses.

FILER_REBOOTED

The filer is rebooted.

WORM_LOG_FAIL ( reason )
Write to WORM log file failed. The reason for failure is included in the parentheses.

WORM_LOG_FAILURE_RECOVER_START

The beginning of the recovery of the failed WORM log entries.

WORM_LOG_FAILURE_RECOVER_END

The end of the recovery of the failed WORM log entries.

Softlock_add（ 操作 ）
阿softlock被添加。 在操作增加了softlock包含在括号中。

Softlock_add_pending（ 操作 ）
阿softlock添加为一个等待softlock。 在操作增加了softlock包含在括号中。

Softlock_delete（ 操作 ）
阿softlock被删除。 即删除了softlock操作是包含在括号中。

Softlock_delete_pending（ 操作 ）一个有待softlock被删除。 即删除了在括号内运作。

Softlock_mark_pending（ 操作 ）
阿softlock被标记为挂起。 该行动标志着这是在括号内。

实例

看起来像一个典型的条目在/ etc /日志SnapMirror快照镜像/：

  7月17日22时五十分18秒的DST周五格林尼治标准时间filer1：srcvol filer2：dstvol要求（更新） 

上面的例子显示了一个更新请求由一个目的地从菲勒SnapMirror快照镜像的关系方面：srcvol到filer2记载：dstvol，在录制的时候发生的。

一个典型的复制/等检查会议/日志/目的地SnapMirror快照镜像的样子：

  清洁香港周三格林尼治标准时间1月19日1时07分39秒伍尔夫：/ vol/vol1米尔顿：/ vol/vol1请求（检查）周三格林尼治标准时间1月19日1时07分39秒伍尔夫：/ vol/vol1米尔顿清洁香港：/ vol/vol1开始（快照检查= 2，水平=数据，检查，全）周三格林尼治标准时间1月19日1时07分39秒伍尔夫：/ vol/vol1米尔顿清洁香港：/ vol/vol1 Checking_snapshot米尔顿（0033587346）_vol1.5（清洁香港1月18日星期三... 1月19日格林尼治标准时间1时07分48秒伍尔夫：/ vol/vol1米尔顿：/ vol/vol1 Checking_snapshot nightly.0（1月18日00:00，cpcount = ...清洁香港1月19日星期三格林尼治标准时间1时07分57秒伍尔夫：/ vol/vol1米尔顿：/ vol/vol1结束（src_only = 0，dst_only = 0，不匹配= 0） 

一个典型的复制/等检查会议/日志/来源SnapMirror快照镜像的样子：

 营养问题常设委员会周三格林尼治标准时间1月19日0点58分27秒伍尔夫：/ vol/vol1米尔顿：/ vol/vol1请求（172.29.19.15）周三格林尼治标准时间1月19日零点58分27秒伍尔夫：/ vol/vol1米尔顿：/ vol/vol1营养问题常设委员会开始（快照检查= 2）星期三格林尼治标准时间1月19日零时58分27秒伍尔夫：/ vol/vol1米尔顿营养问题常设委员会：/ vol/vol1 Request_check（米尔顿（0033587346）_vol1.5）周三1月19日格林尼治标准时间0时58分27秒营养问题小组委员会伍尔夫：/ vol/vol1米尔顿：/ vol/vol1 Checking_snapshot米尔顿（0033587346）_vol1.5（1月18日星期三...营养问题常设委员会1月19日格林尼治标准时间0时58分36秒伍尔夫：/ vol/vol1米尔顿：/ vol/vol1 Request_check（nightly. 0）周三格林尼治标准时间1月19日0时58分36秒伍尔夫：/ vol/vol1米尔顿营养问题常设委员会：/ vol/vol1 Checking_snapshot nightly.1（1月18日00:00，cpcount = ...营养问题常设委员会周三格林尼治标准时间1月19日0点58分45秒伍尔夫： / vol/vol1米尔顿：/ vol/vol1完 

一个典型的softlock像测井在/ etc /日志/看起来SnapMirror快照镜像 ：

   SLK敞篷周三5月10日3时06分15秒格林尼治标准时间state.softlock.vol1.0000011e.054.filer1：vol3 Softlock_add（转让）星期三5月10日格林尼治标准时间3时06分15秒SLK的state.softlock.vol1.0000011b.054.filer1：vol3 Softlock_delete（转让）星期三5月10日3时06分15秒格林尼治标准时间state.softlock.vol1.0000011b.054.filer1：vol3 Softlock_delete（回复）星期三5月10日3时06分15秒格林尼治标准时间state.softlock.vol1.0000011b.054 SLK敞篷SLK敞篷。filer1：vol3 Softlock_delete（发布）星期三5月10日格林尼治标准时间3点06分15秒state.softlock.vol1.0000011b.054.filer1：vol3 Softlock_delete（Clean_softlocks）星期三5月10日3时06分15秒格林尼治标准时间state.softlock.vol1 SLK敞篷SLK敞篷0.0000011 b.054.filer1：vol3 Softlock_add（RSM_forward）星期三5月10日3时06分15秒格林尼治标准时间state.softlock.vol1.0000011b.054.filer1：vol3 Softlock_delete（RSM_forward）星期三5月10日格林尼治标准时间3点06分15秒的状态SLK敞篷SLK敞篷。softlock.vol1.0000011b.054.filer1：vol3 Softlock_delete（Snapmirror_destinations）SLK敞篷星期三5月10日格林尼治标准时间3点06分15秒state.softlock.vol1.0000011b.054.filer1：vol3 Softlock_delete_pending（转让）5月10日星期三03:06 SLK敞篷：15日格林尼治标准时间state.softlock.vol1.0000011b.054.filer1：vol3 Softlock_add_pending（转让）星期三5月10日3时06分15秒格林尼治标准时间state.softlock.vol1.0000011b.054.filer1：vol3 Softlock_mark_pending（转让SLK敞篷） 

锉刀

/等/日志/ SnapMirror快照镜像
SnapMirror快照镜像当前一周的日志文件。

/等/日志/ SnapMirror快照镜像。[0-5]
前几个星期SnapMirror快照镜像的日志文件。

见也

选项，SnapMirror快照镜像snapvault

---

目录

• 名称
• 故事大纲
• 描述
• 实例
• FILES
• 见也

Read more... (2235 words, estimated 8:56 mins reading time)

snapmirror

目录

NAME

snapmirror – volume, and qtree mirroring

SYNOPSIS

snapmirror { on | off }

snapmirror status [ options ] [ volume | qtree ... ]

snapmirror initialize [ options ] destination

snapmirror update [ options ] destination

snapmirror quiesce destination

SnapMirror快照镜像恢复 目的地

SnapMirror快照镜像打破 [ 选项 ] 目标

SnapMirror快照镜像重新同步 [ 选项 ] 目标

SnapMirror快照镜像目的地 [ 选项 ] [ 来源 ]

SnapMirror快照镜像释放 源目的地

SnapMirror快照镜像 （ 存储 | 检索 ） 体积tapedevices

SnapMirror快照镜像使用 目的地tapedevices

SnapMirror快照镜像油门 <n>的目的地

SnapMirror快照镜像中止 [ 选项 ] 目标 ...

SnapMirror快照镜像迁移 [ 选项 ] 源目的地

描述

该SnapMirror快照镜像命令是用来控制SnapMirror和1 qtrees镜像卷和方法。 它允许用户启用和禁用预定和手动数据传输，对信息传输的要求，开始初始化数据传输，启动一个更新的一面镜子，暂时暂停更新一面镜子，镜子打破关系，重新同步打破镜子，目的地信息列表，释放儿童镜，图像存储容量的磁带，从磁带容量图像检索，并中止正在进行的传输。

SnapMirror快照镜像功能，可用于复制卷或qtrees。 所涉及的过程和行为稍有（有时巧妙地）之间的数据的各种不同的镜像。

该SnapMirror快照镜像过程是目标驱动的。 该SnapMirror快照镜像初始化命令启动的第一个转由素数源目的地，所有的数据。 在此之前的初始转移，目的地必须随时准备与来自源的数据覆盖;目标卷必须加以限制（见第二卷），和目标qtrees必须尚未存在。

对于异步镜像，目标要求，从源头上定期更新，接受的数据传输，这些数据并写入到磁盘。 这些更新只传输包括自上次传送源所做的更改。 该SnapMirror快照镜像调度启动自动根据snapmirror.conf这些转让文件的时间表。

同步镜像最初将异步行为，但将过渡到同步模式在第一次机会。 这些镜子可以返回异步模式错误（例如一个镜像文件服务器之间的网络分区）或用户的要求。

该SnapMirror快照镜像更新命令可以用来发起snapmirror.conf从原定的个人转让分开。

经过初期的转移，目标是提供给客户，但在只读状态。 目的地的地位将显示它是snapmirrored（见细节上显示的目的地国家aggr更多，第一卷，或qtree）。

要使用/ qtree的目的地，以及阅读写作，这是一场灾难时非常有用，使源无法使用，或当你想使用目标作为测试卷，您可以结束break命令SnapMirror快照镜像的关系与SnapMirror快照镜像 。 此命令更改目的地的地位，从snapmirrored破碎过的 ，从而使可写的。 该SnapMirror快照镜像重新同步命令可以改变一个目的地前的地位，并会回到snapmirrored重新同步的内容与源。 （当应用到前源，SnapMirror快照镜像重新同步可以把它的目的地为前者的镜像。通过这种方式，和目的地的作用，可逆转的来源。）

阿菲勒保留了所有目的地的轨道，无论是直接或镜子镜子镜子，其来源为每个。 此列表可以显示目的地通过SnapMirror快照镜像命令。 该SnapMirror快照镜像释放命令可以用来告诉一个过滤器，直接反映一个特定的请求将不再更新。

为了节省网络带宽，磁带可用于一个新的镜像卷总理，而不是SnapMirror快照镜像初始化命令。 该SnapMirror快照镜像存储命令转储一源的形象，到磁带。 该SnapMirror快照镜像还原图像检索命令从磁带卷，并准备在更新网络传输的体积。 如果有多个磁带用于创建一个卷映像，SnapMirror快照镜像使用命令是用来指示等待存储或检索过程输出或写入新的磁带设备接受输入到/从。 在存储和检索命令不能用于qtrees。

该SnapMirror快照镜像迁移命令用于对现有的源和目标，使目标卷可写的“模仿源”的。 假设目标在NFS文件句柄源，帮助菲勒管理员，以避免NFS的重新在客户端安装。

根量snapmirror.conf文件在目的地菲勒的控制SnapMirror快照镜像目的地的配置和调度。 查看配置和日程安排的详情snapmirror.conf SnapMirror快照镜像。

访问控制源与源菲勒snapmirror.access选择权。 查看选项和protocolaccess设置选项（8）以供参考。

（如果snapmirror.access选项设置为“遗产”，访问控制的根体积snapmirror.allow文件源菲勒的。查看详细snapmirror.allow更多。）

SnapMirror快照镜像是一个领牌服务，并获得许可证之前，必须使用的SnapMirror快照镜像命令即可。 SnapMirror快照镜像功能上都必须领有牌照的源和目标文件服务器。 详情请参阅牌照。

SnapMirror快照镜像功能支持普通vfilers，以及物理菲勒命名vfiler0。 使用vfiler上下文或vfiler运行到问题的具体vfiler SnapMirror快照镜像命令的一个。 查看关于如何发出vfilers命令细节vfiler。 关于vfilers的SnapMirror快照镜像使用需要MultiStore许可证。

当一个vfiler，数限制使用的申请。 该vfiler必须植根于一个体积和SnapMirror快照镜像源和目的地不能在共享卷qtrees。 磁带设备和同步SnapMirror快照镜像不支持vfilers。 对于qtree SnapMirror和的vfiler必须拥有所Qtree含有量。

每个vfiler有自己的/ etc /根体积snapmirror.conf文件的。 SnapMirror快照镜像功能，可开启或关闭一个vfiler独立。 SnapMirror快照镜像命令发表的vfiler只能经营量或qtrees它独家拥有。

为了向后兼容性，物理菲勒（vfiler0）可以操作所有卷，所有qtrees，即使他们是由vfilers拥有。 这是高度，意见书，不过，所有（卷和qtrees）由任vfiler0或托管vfiler，而不是两个镜像存储单元。 当vfiler存储单元是通过vfiler0镜像，离开SnapMirror快照镜像的vfiler关闭。

用法

该SnapMirror快照镜像命令有许多子命令。 几乎每个命令需要一个目标参数。 这个论点有三个不同的形式。 为特定的形式调用使用取决于你指定一个卷或qtree。

卷是由他们指定的名称：

  vol1 

Qtrees由他们指定的完全限定路径：

  / vol/vol1/qtree 

有一个特殊的路径，可以用来SnapMirror快照镜像卷中不驻留在qtree的所有数据。 这条道路只能作为SnapMirror快照镜像源，从来没有一个SnapMirror快照镜像目的地。 指定的路径为：

  / vol/vol1/- 

所有的命令，不要说其他可以利用这些形式作为参数的。

子的SnapMirror快照镜像功能是：

关于

启用SnapMirror快照镜像数据传输和调度轮流在SnapMirror快照镜像。 此命令必须在启动前发出任何或检索子SnapMirror快照镜像数据传输的初始化 ， 更新 ， 重新同步 ， 存储 。 此命令还打开了SnapMirror快照镜像调度，从而启动更新转移到时匹配文件之一snapmirror.conf的时间表英寸 此命令必须发出关于备案人源端响应更新目的地的要求。

关闭

中止所有活动SnapMirror快照镜像数据传输和禁用命令，启动新的转移（ 初始化 ， 更新 ， 重新同步 ， 存储和检索 ），和曲折的SnapMirror快照镜像调度了。

坚持通过重新启动的SnapMirror快照镜像开/关状态的，是反映了snapmirror.enable选项。 此选项可以设置和关闭，而且这样做有确切的起飞命令相同的效果，作为SnapMirror快照镜像或SnapMirror快照镜像 。

地位[- 1 | -吨 | - Q表 ] [ 量 | qtree ... ]

报告所有与源和SnapMirror快照镜像的关系状态/或本菲勒目的地。 此命令还报告是否SnapMirror快照镜像功能是开启或关闭。 如果任何数量或qtree参数给命令，只有或目的地SnapMirror快照镜像的关系具有匹配源将被报告。 如果参数是无效的，不会有任何输出状态。

如果没有任何选项，每个关系中的地位短期形式显示。 这表明了这种关系的本地端的状态，无论是转移过程中，（如果是这样，则该转移的进步），和镜像滞后，即时间而镜子背后的源滞后量。 这是当前时间和上一次成功传送源端时间戳简单的区别。 滞后时间将是至少作为最后成功转让的时间不多，除非在源和目的地的时钟不同步（在这种情况下，它甚至可能是负数）。

如果- l选项，给出更详细的输出显示每个SnapMirror快照镜像关系的信息。 如果是一个*一起显示命令的关系地位已有SnapMirror快照镜像status的缩写形式输出，然后extra special的关系有关的信息可用，这是看得见的只与 - l选项。

如果- t选项给出的输出显示的关系是积极的。 阿关系被认为是积极的，如果源或目的地是参与：

1。 数据传输到或从网络上。 2。 读取或写入到磁带设备。 3。 等待一个磁带的变化。
4。 表演本地磁盘上的处理或清理。

如果- q选项，给出了输出显示的数量和qtrees是quiesced或quiescing。 见停顿命令，下面，为这意味着什么。

见SnapMirror快照镜像地位的例子更多信息一节。

在一个vfiler， 状态命令只显示相关的条目vfiler。 在物理滤波器，从所有vfilers积极转移项显示。 不活跃的转让只显示在有关vfiler。 的首选方式获得可读名单SnapMirror快照镜像转移全面，更是运行vfiler运行* SnapMirror快照镜像的状态 。 它通过迭代器，并列出其所有vfilers转移。

初始化[- S的 来源 ] [ 介电 千字节 ] [- S的 src_snap] [- C的 create_dest_snap] [-瓦特 ] 目的地

在网络上启动一个初步的转让。 据初步转移或者通过网络或从磁带之前，需要更新才能进行转让。 在初始化命令必须菲勒发表的目的地。 如果目标是一个体积，它必须加以限制（关于如何检查和限制数量的信息第一卷）。 如果目的地是一个qtree，它必须不存在（参见资料qtree如何列出qtrees）。 如果qtree已经存在，它必须重命名或删除（使用的NFS或CIFS客户端），或SnapMirror快照镜像初始化该qtree将无法工作。

如果SnapMirror快照镜像状态命令中止初步报告说，一移交检查点重新启动，将重新启动的初始化commmand转让时的位置。

- s选项指定一个源滤波器和体积or qtree的道路，在一个格式类似于ination这一论点的des_吨。 消息来源必须符合文件中的项为snapmirror.conf目标的。 如果它不匹配，操作打印一个错误信息和中止。 如果- S选项是没有设置，使用的是源文件中的一个snapmirror.conf在指定的目的地的入境的。 如果没有这样的项目，操作打印一个错误消息并中止。

- k选项设置最高速度的数据传输是第二个字节以上的网络研究。 它是用来油门磁盘，CPU和网络使用情况。 这个选项只是规定了传输速度最高值，它并不能保证将转移到这么快。 如果这个选项没有设置，传输数据的备案人按照文件的KBS电视台设置snapmirror.conf这种关系在（见snapmirror.conf）。 但是，如果不设置此选项，也没有KBS电视台文件设置snapmirror.conf这种关系中，备案人传输数据的速度，因为它可以。

- c选项仅可用于一初始化一个qtree。 使用此选项，SnapMirror快照镜像创建一个名为快照初始化create_dest_snap在目标后，已成功完成（所以它不与任何竞争不断更新）。 SnapMirror快照镜像不锁定或删除该快照。create_dest_snap不能hourly.x，nightly.x，或weekly.x，因为这些名称是快照预留计划。

- s选项仅可用于一初始化一个qtree。 它指定一个名为src_snap快照从中SnapMirror快照镜像转让qtree，而不是创建一个源快照和转让新快照qtree从。 这个选项是用于传输一个特定的快照的内容，例如，它可以将一个数据库而采取了在稳定的，一致的状态快照。 SnapMirror快照镜像不锁定或删除src_snap。src_snap不能hourly.x，nightly.x，weekly.x，snapshot_for_backup.x或snapshot_for_volcopy.x。

- w选项会导致命令不返回初始一旦开始传输。 相反，它会等待，直到传输完成（或失败），届时将打印的完成状态，然后返回。

更新[- S的 来源 ] [ 介电 千字节 ] [- S的 src_snap] [- C的 create_dest_snap] [-瓦特 ] 目的地

对于异步镜像，更新是立即开始从源到目标 ，以更新源的镜像与内容。

同步镜像，快照创建源量，成为可见的目的地大量的客户。

此更新必须发出命令在目标菲勒。

- s选项设置转移源 ，并为工程的更新一样，如同对初始化 。

- k选项设置油门，第二每千字节，在转移和工程的更新一样，作为它的初始化 。

- c选项仅可用于一qtree 更新 1。 使用此选项SnapMirror快照镜像创建一个快照名为目的地create_dest_snap上更新完成后，（所以它不与任何竞争不断更新）。 SnapMirror快照镜像不锁定或删除该快照。create_dest_snap不能hourly.x，nightly.x，或weekly.x，因为这些名称是快照预留计划。

The -s option only works for an update to a qtree. It designates a snapshot named src_snap from which SnapMirror transfers the qtree, instead of creating a source snapshot and transferring the qtree from the new snapshot. This option is used to transfer a specific snapshot's contents; for example, it can transfer a snapshot that was taken while a database was in a stable, consistent state. SnapMirror does not lock or delete the src_snap . src_snap cannot be hourly.x, nightly.x, weekly.x, snapshot_for_backup.x or snapshot_for_volcopy.x.

The -w option causes the command not to return once the incremental transfer starts. Instead, it will wait until the transfer completes (or fails), at which time it will print the completion status and then return.

quiesce destination

Allows in-progress transfers to destination to complete after which new transfers are not allowed to start. Synchronous mirrors will be taken out of synchronous mode. Any further requests to update this volume or qtree will fail until the snapmirror resume command is applied to it.

This command has special meaning to qtree destinations. A qtree destination which is being modified by SnapMirror during a transfer will have changes present in it. These changes will not be exported to NFS or CIFS clients. However, if a snapshot is taken during this time, the snapshot will contain the transitioning contents of the qtree. quiesce will bring that qtree out of a transitioning state, by either finishing or undoing any changes a transfer has made. snapmirror status can report whether a qtree is quiesced or not. The quiesce process can take some time to complete while SnapMirror makes changes to the qtree's contents. Any snapshot taken while a qtree is quiesced will contain an image of that qtree which matches the contents exported to NFS and CIFS clients.

resume destination

Resumes transfers to destination . The snapmirror resume command can be used either to abort a snapmirror quiesce in progress or undo a previously completed snapmirror quiesce . The command restores the state of the destination from quiescing or quiesced to whatever it was prior to the quiesce operation.

break [ -f ] destination

Breaks a SnapMirror relationship by turning a snapmirrored destination into a normal read/write volume or qtree. This command must be issued on the destination filer.

The -f option forces a snapmirror break between snaplocked volume relationship without prompting for conformation.

This command does not modify the snapmirror.conf file. Any scheduled transfers to a broken mirror will fail.

For volumes, this command has the same effect as the vol options snapmirrored off command, and will remove the snapmirrored option from a volume. The fs_size_fixed volume option will remain on; it must be manually removed from the volume to reclaim any disk space that SnapMirror may have truncated for replication. (See the Options section and vol for more information on these two volume options.)

A destination qtree must be quiesced before it can be broken.

resync [ -n ] [ -f ] [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c create_dest_snap ] [ -w ] destination

Resynchronizes a broken-off destination to its former source, putting the destination in the snapmirrored state and making it ready for update transfers. The resync command must be issued on the destination filer.

The resync command can cause data loss on the destination. Because it is effectively making desti_ n ation a replica of the source, any edits made to the destination after the break will be undone.

For formerly mirrored volumes, the resync command effectively performs a SnapRestore (see vol ) on the destination to the newest snapshot which is common to both the source and the destination. In most cases, this is the last snapshot transferred from the source to the destination, but it can be any snapshot which is on both the source and destination due to SnapMirror replication. If new data has been written to the destination since the newest common snapshot was created, that data will be lost during the resync operation.

For formerly mirrored qtrees, SnapMirror restores data to the file system from the latest SnapMirrorcreated snapshot on the destination volume. Unlike the volume case, it requires this last snapshot in order to perform a resync .

该命令启动一个重新同步后，SnapRestore数据更新或修复qtree传输完成。

- n选项报告什么命令执行的重新同步会做，但不执行命令。

使用- f选项强制操作不进行确认提示。

- s选项设置转移源 ，并重新同步工程一样，作为它的初始化 。

- k选项设置油门，第二每千字节，在转移和重新同步工程一样，作为它的初始化 。

- c选项仅可用于一qtree 重新同步到。 使用此选项SnapMirror快照镜像创建一个快照指定目的create_dest_snap在传输完成后，重新同步（所以它不与任何竞争不断更新）。 SnapMirror快照镜像不锁定或删除该快照。create_dest_snap不能hourly.x，nightly.x，或weekly.x，因为这些名称是快照预留计划。

The -s option only works for a resync to a qtree. It designates a snapshot named src_snap from which SnapMirror transfers the qtree, instead of creating a source snapshot and transferring the qtree from the new snapshot. This option is used to transfer a specific snapshot's contents; for example, it can transfer a snapshot that was taken while a database was in a stable, consistent state. SnapMirror does not lock or delete the src_snap . src_snap cannot be hourly.x, nightly.x, weekly.x, snapshot_for_backup.x or snapshot_for_volcopy.x.

The -w option causes the command not to return once the resync transfer starts. Instead, it will wait until the transfer completes (or fails), at which time it will print the completion status and then return. This option has no effect if the -n option is also specified.

destinations [ -s ] [ source ]

Lists all of the currently known destinations for sources on this filer. For volumes, this command also lists any cascaded destinations; these are any volumes which are replicas of direct destinations. This command will list all such descendants it knows about.

The -s option includes in the listing names of snapshots retained on the source volume for each destination.

If a specific source is specified, only destinations for that volume will be listed. The source may either be a volume name or a qtree path.

release source { filer : volume | filer : qtree }

Tell SnapMirror that a certain direct mirror is no longer going to request updates.

If a certain destination is no longer going to request updates, you must tell SnapMirror so that it will no longer retain a snapshot for that destination. This command will remove snapshots that are no longer needed for replication to that destination, and can be used to clean up SnapMirror-created snapshots after snapmirror break is issued on the destination side.

The source argument is the source volume or qtree that the destination is to be released from. The destination argument should be either the destination filer and destination volume name or the destination filer and destination qtree path. You can use a line from the output of the snapmirror destinations command as the set of arguments to this command.

store [ -g geometry ] destination tapedevices

Dumps an image of the destination volume to the tapedevices specified. This is much like the snapmirror initialize command, but from a source volume to a tape device. You can use the tapes and the retrieve command to perform the initial, priming transfer on any restricted volume.

使用- g选项存储在SnapMirror快照镜像将优化传统的磁带数量为特定的目的地。 的几何参数是一个字符串，它描述了预期的目标几何传统的音量。 它可以通过g命令收购上，传统的量的SnapMirror快照镜像检索-。 使用此选项可以大大提高SnapMirror快照镜像检索性能。 - g选项是唯一有效的与传统的卷。

只有卷可以被保存到磁带或检索。 Qtrees不能储存或从磁带中检索。

在此命令tapedevices领域是一个磁带设备commaseparated名单有效。 查看更多磁带磁带设备名称的详细信息。

磁带设备不支持vfilers。 此命令只运行在物理菲勒。

检索 （ 目的地tapedevices | - H的 tapedevice | - G的 音量）

恢复的图像在指定的tapedevices到desti_ ñ 款 。 这很像SnapMirror快照镜像初始化命令，而是从一个磁带设备到目标卷。 如果目的地是一个部分SnapMirror快照镜像的关系，在源网络容量从商店进行创建这些录音带，两卷可以被镜像，犹如转让货量录得初步通过了引物。

你可以使用- h标志读取头销单tapedevice指定。 这将提供在磁带上的源和索引信息。

- g选项提供指定数量的几何量字符串。 这个字符串，当给予SnapMirror快照镜像存储g命令，将极大地提高检索性能，这SnapMirror快照镜像 卷 。

在此命令tapedevices领域是一个磁带设备commaseparated名单有效。 查看更多磁带磁带设备名称的详细信息。

此功能仅适用于卷。 Qtrees不能储存或从磁带中检索。

磁带设备不支持vfilers。 此命令只运行在物理菲勒。

使用 目的地tapedevices

继续磁带传输到目的地指定tapedevices使用。

如果一个存储或检索操作运行的磁带，它会提示用户提供另一磁带。 再过提供了磁带， 使用命令调用告诉SnapMirror快照镜像过程在哪里可以找到它。

目标字段指定由菲勒 ： 检索 量的情况下， 及服务器： 存储 tapedevices在有关个案。

在此命令tapedevices领域是一个磁带设备commaseparated名单有效。 查看更多磁带磁带设备名称的详细信息。

磁带设备不支持vfilers。 此命令只运行在物理菲勒。

油门 <n>的目的地

Modifies the throttle value for the snapmirror transfer to the destination with the specified value in kilobytes per second. This sets the maximum speed at which the data is trasfered over the network for the current transfer. A value of zero can be used to disable throttling.

The new value will be used only for the current transfer. The next scheduled transfer will use the kbs value specified in the snapmirror.conf file. If the value for the kbs option in the snapmirror.conf is changed while transfer is going on, then the new value will take effect within two minutes.

abort [ -h ] destination …

Aborts currently executing transfers to all specified destination s. It may take a few minutes for a transfer to clean up and abort. This does not stop new updates from starting. If you are interested in stopping further updates use the snapmirror quiesce command.

Any transfer with a restart checkpoint (you can view this via the snapmirror status command) may be restartable; to clear out the restart checkpoint and force any subsequent transfer to start with a fresh snapshot on the source, you can use abort -h on the destination. The -h option specifies that this is a hard abort; the restart checkpoint will be cleared out in addition to the transfer being stopped.

The abort command can be invoked from either the source or the destination filer. However, the -h option is only effective on the destination filer. The option will be ignored if specified on the source filer.

migrate [ -n ] [ -f ] [ -k kilobytes ] [ source_filer :] source_volume [ destination_filer :] desti t ion_volume

snapmirror migrate is run on the filer which holds the source volume. It must be run on two volumes which are already the source and destination of a SnapMirror pair.

snapmirror migrate will transfer data and NFS filehandles from the source_volume to the desti t ion_filer ’s destination_volume (if no filer is specified, then migrate assumes the volume is local). If source_filer is specified, then the migrate destination will use that network interface to connect up to the source filer for the transfer of information.

The first thing migrate will do is check the source and destination sides for readiness. Then, it will stop NFS and CIFS service to the source. This will prevent changes to the source volume's data, which will make it appear to clients as though nothing has changed during the migration. It will run a regular SnapMirror transfer between the two volumes. At the end of the transfer, it will migrate the NFS filehandles, bring the source offline, and make the destination volume writable.

The -n flag will make a test run; that is, it will run all the pre-transfer checks, but stop short of transferring data. The -f flag will not prompt the user for confirmation. The -k flag will throttle the speed at which the transfer runs (at kilobytes kilobytes per second), in a manner similar to that used in the snapmirror update command.

CLUSTER CONSIDERATIONS

If one filer in a cluster failover pair goes down, any active transfers are aborted. The SnapMirror scheduler and services will continue for volumes on the downed filer. The configurations of the SnapMirror relationships are taken from the downed filer's snapmirror.access option or snapmirror.allow and snapmirror.conf files.

EXAMPLES

Here are a few examples of use of the snapmirror command:

The following example turns the scheduler on and off:

         toaster> snapmirror on          toaster> snapmirror status          Snapmirror is on. toaster> snapmirror off          toaster> snapmirror status          Snapmirror is off. toaster> 

下面的例子介绍了运行SnapMirror快照镜像功能 ， 状态转移。 两个人都从冰箱闲置目的地（）;其中一检查站已重新启动，并可能重新启动，如果在两卷格局没有改变，因为检查站了。 该vol1转移到arc2刚刚开始，转移是在初始阶段。 从烤面包机转移到冰箱是部分完成，在这里，我们可以看到转让兆字节数。

 电烤箱> SnapMirror快照镜像地位SnapMirror快照镜像上。 来源目的地国滞状态冰箱：家里烤面包机：arc1 Snapmirrored 22时09分58秒空闲电烤箱：vol1烤面包机：arc2 Snapmirrored 1时02分53秒转移电烤箱：vol2冰箱：保存未初始化 - 转移（128MB的完成）冰箱：用户电烤箱：arc3 Snapmirrored 10时14分36秒怠速重新启动检查点（12MB的完成）烤面包机> 

下面的例子列出上述SnapMirror快照镜像作为参数的命令中指定关系之一的详细情况。 它显示基地快照，传输类型，错误信息的额外信息，最后转移等

 电烤箱> SnapMirror快照镜像地位升arc1 SnapMirror快照镜像上。 来源：冰箱：首页目的地：烤面包机：arc1类型：卷状态：空闲进展： - 国家：Snapmirrored滞：22时09分58秒镜时间戳：周三格林尼治标准时间2001年8月8日16时53分04秒中的快照：烤面包机（0001234567）_arc1 0.1电流传输类型： - 电流传输错误： - 内容：副本最后传输类型：初始化最后传输大小：1120000 KB的最后传递时间：0时03分47秒最后传递者：冰箱：回家 

下面的示例显示了如何让所有的数量和qtrees是quiesced或本与状态命令菲勒quiescing。

 菲勒> SnapMirror快照镜像地位Q值SnapMirror快照镜像上。  vol1已quiesced / quiescing qtrees：/ vol/vol1/qt0是quiesced / vol/vol1/qt1是quiescing vol2是quiescing 

下面的例子开始写电烤箱vol1一个图片的rst0a磁带在磁带设备和rst1a继续与在磁带上。 当第二个磁带用完，该示例显示了如何恢复在存储上使用rst0a新的磁带。

         toaster> snapmirror store vol1 rst0a, rst1a          snapmirror: Reference Snapshot: snapmirror_tape_5.17.100_21:47:28          toaster>          SNAPMIRROR: store to toaster:rst0a, rst1a has run out of tape. toaster> snapmirror use toaster:rst0a, rst1a rst0a          toaster>          Wed May 17 23:36:31 GMT [worker_thread:notice]: snapmirror: Store from volume 'vol1′ to tape was successful (11 MB in 1:03 minutes,  3 tapes written). 

The following example retrieves the header of the tape on tape device rst0a . It then retrieves the image of vol1 from the tape on tape device rst0a .

         toaster> snapmirror retrieve -h rst0a          Tape Number:                    1          WAFL Version:                   12          BareMetal Version:              1          Source Filer:                   toaster          Source Volume:                  vol0          Source Volume Capacity:         16MB          Source Volume Used Size:        11MB          Source Snapshot:                snapmirror_tape_5.17.100_21:47:28          toaster>          toaster> snapmirror retrieve vol8 rst0a          SNAPMIRROR: retrieve from tape to toaster:vol8 has run out of tape. toaster> snapmirror use toaster:vol8 rst0a          SNAPMIRROR: retrieve from tape to toaster:vol8 has run out of tape. toaster> snapmirror use toaster:vol8 rst0a          toaster> snapmirror status          Snapmirror is on. Source               Destination   State    Lag  Status          toaster:rst1a, rst0a  toaster:dst1  Unknown  –    Transferring (17MB done)          toaster>          Wed May 17 23:54:29 GMT [worker_thread:notice]: snapmirror: Retrieve from tape to volume 'vol8′ was successful (11 MB in 1:30 minutes). 

The following example examines the status of all transfers, then aborts the transfers to volm1 and volm2 , and checks the status again. To clear the restart checkpoint, snapmirror abort is invoked again.

         toaster> snapmirror status          Snapmirror is on. Source        Destination    State          Lag       Status          fridge:home   toaster:volm1  Uninitialized  –         Transferring (10GB done)          fridge:mail   toaster:volm2  Snapmirrored   01:00:31  Transferring (4423MB done)          toaster> snapmirror abort toaster:volm1 volm2          toaster> snapmirror status          Snapmirror is on. Source        Destination    State          Lag       Status          fridge:home   toaster:volm1  Snapmirrored   00:01:25  Idle          fridge:mail   toaster:volm2  Snapmirrored   01:03:11  Idle with restart checkpoint (7000MB done)          toaster> snapmirror abort toaster:volm2          toaster> snapmirror status          Snapmirror is on. Source        Destination    State          Lag       Status          fridge:home   toaster:volm1  Snapmirrored   00:02:35  Idle          fridge:mail   toaster:volm2  Snapmirrored   01:04:21  Idle 

The following example examines the status of all transfers, then aborts the transfers to volm1 and volm2 with the -h option and checks the status again. No restart checkpoint is saved.

         toaster> snapmirror status          Snapmirror is on. Source        Destination    State          Lag       Status          fridge:home   toaster:volm1  Uninitialized  –         Transferring (10GB done)          fridge:mail   toaster:volm2  Snapmirrored   01:00:31  Transferring (4423MB done)          toaster> snapmirror abort -h toaster:volm1 toaster:volm2          toaster> snapmirror status          Snapmirror is on. Source        Destination    State          Lag       Status          fridge:home   toaster:volm1  Snapmirrored   00:02:35  Idle          fridge:mail   toaster:volm2  Snapmirrored   01:04:21  Idle 

Here is an example of the use of the snapmirror migrate command:

         toaster> snapmirror migrate home mirror          negotiating with destination…. 

This SnapMirror migration will take local source volume home and complete a final transfer to destination toaster:mirror using the interface named toaster. After that, open NFS filehandles on the source will migrate to the destination and any NFS filehandles open on the destination will be made stale. Clients will only see the migrated NFS filehandles if the destination is reachable at the same IP addresss as the source. The migrate process will not take care of renaming or exporting the destination volume.

作为这一进程的结果，将源卷回家脱机，和NFS服务，这菲勒将在转让停了下来。 CIFS的服务在量将终止和CIFS将要在目标设定了来源。

 你确定要这么做吗？ 是的nfs关闭从源头表演电烤箱最终转移菲勒：家中镜子...。  （监测“SnapMirror快照镜像地位”）从烤面包机转让：回家的进展，以反映从家里出发的NFS文件句柄成功迁移到镜像源卷家里带来的NFS文件句柄无效离线源目的地电烤箱：镜子确认移民迁移完成电烤箱>第一卷地位体积国地位选项根线上正常根，raidsize = 14镜子线上脱机正常家庭的正常电烤箱>第一卷重命名回家气温家更名为气温则可能需要更新/ etc /出口烤面包机>第一卷家镜镜重命名更名为家，您可能需要更新/ etc /出口烤面包机> exportfs - 1 

注意事项

如果源卷是比副本目标大，转移是不允许的。

SnapMirror快照镜像债券在迁移的命令：

The migrate command is only a partial step of the process. It is intended to work when an administrator desires to move the data of one volume to another, possibly because they want to move to a new set of disks, or to a larger volume without adding disks.

We intend that migrate be run in as controlled an environment as possible. It is best if there are no dumps or SnapMirror transfers going on during the migration.

The clients may see stale filehandles or unresponsive NFS service while migrate is running. This is expected behavior. Once the destination volume is made writable, the clients will see the data as if nothing has happened.

migrate will not change exports or IP addresses; the new destination volume must be reachable in the same way as the source volume once was.

CIFS service will need to be restarted on the migrate destination.

OPTIONS

Here are SnapMirror-related options (see options , protocolaccess , snapmirror , and snapmirror.allow for details on these options):

snapmirror.access
Controls SnapMirror access to a filer.

snapmirror.checkip.enable
Controls SnapMirror IP address checking using snapmirror.allow .

snapmirror.delayed_acks.enable
Controls a SnapMirror networking option.

replication.volume.transfer_limits
控制流计数增加。 这个选项是提供给流计数恢复到原有的限制。

replication.volume.reserved_transfers
Guarantees that specified number of volume SnapMirror source/destination transfers always start. This option will reduce the maximum limit on all other transfers types and will be equivalent to maximum number of transfers possible.

snapmirror.enable
Turns SnapMirror on and off. SnapMirror can only be enabled on vfilers which are rooted on volumes.

snapmirror.log.enable
Turns SnapMirror logging on and off.

replication.volume.use_auto_resync
Turns auto resync functionality on and off for Synchronous SnapMirror relations. This option if enabled on Synchronous SnapMirror, destination will update from the source using the latest common base snapshot deleting all destination side snapshots newer than the common base snapshot.

Here are SnapMirror-related volume pseudo-options (see vol for more details):

snapmirrored
Designates that the volume is read-only.

fs_size_fixed
Effectively truncates the filesystem on the destination volume to the size of the source.

Options snapmirror.access , snapmirror.checkip.enable , and snapmirror.enable can be manipulated independently on a per-vfiler basis.

FILES

/etc/snapmirror.allow
This file controls SnapMirror's access to a source filer. See snapmirror.allow , for details.

/etc/snapmirror.conf
This file controls SnapMirror schedules and relationships. See snapmirror.conf for details.

/etc/log/snapmirror
This file logs SnapMirror activity. See snapmirror for details.

SEE ALSO

   aggr    license    options    qtree    vol    tape(4)    protocolaccess(8)    snapmirror(5)    snapmirror.allow(5)    snapmirror.conf(5) 

---

Table of Contents

• NAME
• SYNOPSIS
• DESCRIPTION
• USAGE
• CLUSTER CONSIDERATIONS
• EXAMPLES
• NOTES
• OPTIONS
• FILES
• SEE ALSO

Read more... (6043 words, estimated 24:10 mins reading time)