Installation manual

Shadowing a Volume
Configuring a Shadow-Copy Rule (Source Switch)
CLI Storage-Management Guide 15-35
Truncating the Report
To conserve CPU cycles and/or internal-disk space, you may want to stop a
shadow-copy report before it is finished. An oversized, CPU-intensive report could
possibly have an effect on namespace performance. From priv-exec mode, use the
truncate-report command to stop all report processing and truncate the report file:
truncate-report name
where name (1-255 characters) specifies report to truncate.
This only stops the policy engine from writing to the report; the shadow-copy
processing continues.
For example, the following command finds a running shadow-copy report and
truncates it:
bstnA6k(gbl)# show reports
reports
Codes: At=Command Scheduler, Diag=Collect Diag-Info, Dstg=Destage,
ExMp=Export Mapping, Imp=Import, Inc=Inconsistencies,
MdO=Metadata Only, MdU=Metadata Upgrade, MgMd=Migrate Metadata,
NIS=NIS Update, Plc=Place Rule, Rbld=Rebuild, Rm=Remove,
RmNs=Remove Namespace, RmSh=Remove Share, RsD=Restore Data,
SCp=Shadow Copy, Snapshot=Snapshot,
SuEn=Enable Subshare Inconsistencies,
SuIn=Export Subshare Inconsistencies, Sum=Summary,
SuSh=Export Subshares, Sync=Sync Files/Dirs, SySh=Sync Shares
...
DRetc_200701240413.rpt Jan 24 04:25 2.3M SCp DONE: 4460 in 00:11:46
...
bstnA6k(gbl)# end
bstnA6k# truncate-report DRetc_200701240413.rpt
bstnA6k# ...