Administrator Guide

• Idle Time — lists the idle time for this client
• Connection — lists the number of connections for this client
• Mode — lists the mode types that can be set for this client:
– Auto
– Passthrough
– Dedupe (deduplication)
メモ: If an OST or RDS client has four or more CPU cores, it is considered to be dedupe-capable. However,
the OST or RDS client operating mode depends upon how it is configured in the DR Series system (Dedupe
is the default RDA client mode). If the administrator did not configure an OST or RDS client to operate in a
specific mode and it is dedupe-capable, it will run in the Dedupe mode. If an OST or RDS client is not
dedupe-capable (meaning the OST or RDS client has less than four CPU cores), and the administrator sets
it to run in the Dedupe mode, it will only run in the Passthrough mode. If an OST or RDS client is set to run
in Auto mode, the OST or RDS client will run in the mode setting determined by the media server. The
following table shows the relationship between the configured OST or RDS client mode types and the
supported client mode based on client architecture type and corresponding number of CPU cores.
表
3. Supported OST or RDS Client Modes and Settings
OST or RDS Client
Mode Settings
32–Bit OST or RDS
Client (4 or more
CPU cores)
64–Bit OST or RDS
Client (4 or more
CPU cores)
32–Bit OST or RDS
Client (Less than 4
CPU cores)
64–Bit OST or RDS
Client (Less than 4
CPU cores)
Auto Passthrough Dedupe Passthrough Passthrough
Dedupe Not Supported Supported Not Supported Not Supported
Passthrough Supported Supported Supported Supported
メモ: Click Select to identify the OST or RDS client on which you want to perform an action. For example, click
Select → Download Plug-In to display the Download Plug-Ins page for the client you selected. Select the plug-in
for the relevant client and protocol.
About the Schedules Page and Options
To display the Schedules page, click Dashboard → Schedules . This page displays any existing Replication or Cleaner
operations that have been set up for the DR Series system. If no times are listed, this indicates there are no scheduled
Replication or Cleaner operations. The Replication and Cleaner operations will automatically run whenever the DR
Series system detects a window of inactivity when there are no other major system operations running.
メモ: Replication schedules can only be set on individual replication-enabled source containers.
The Schedules page lets you create a new schedule for running Replication or Cleaner operations, or you can modify an
existing schedule for either of these operations. For more information about scheduling Replication or Cleaner
operations, see Creating a Cleaner Schedule and Creating a Replication Schedule.
メモ: Cleaner operations are system processes that reclaim disk space from containers where files were deleted.
When no Cleaner schedule is set, the Cleaner process will run as needed.
The Schedules page displays the following:
• System Time Zone: using the following format (US/Pacific, Tue May 1 10:33:45 2012)
• Scheduled Replication operations: with day of the week (Sunday through Saturday), start time, and stop time
• Scheduled Cleaner operations: with day of the week (Sunday through Saturday), start time, and stop time
メモ: Schedules only control the source container in scheduled Replication operations; the target container is
passive in these operations.
63