Virtual TapeServer 6.04.01 Installation Guide

96 | Enabling Instant DR and AutoCopy
Instant DR and AutoCopy features have distinct advantages that may be specific to
individual sites or requirements. In general, Instant DR should be used if files do not change
much from day to day. AutoCopy is best used if files change often throughout the day. Keep
the following in mind when enabling these features:
To configure Instant DR and AutoCopy, you must configure network settings for all VTS
locations. Adhere to the following requirements and guidelines when configuring these
software modules:
• The VTS server provides two Ethernet ports (eth0 and eth1). These ports correspond to
ports 1 and 2 on the back of the server. Under normal circumstances, eth0 is used for local
IP traffic to access the user interface for the VTS operating system and for mounting
communication between VTS and hosts. When Instant DR is configured, eth1 is
configured with a routable address to communicate with additional VTS servers at remote
locations.
• The Event Management Service (EMS) is responsible for monitoring mounts and
dismounts relevant to AutoCopy. Therefore, EMS must be configured and running on the
VTS server as described in
Configuring EMS Communication on page 79.
Instant DR AutoCopy
How often is data copied? In batches Individually, as each virtual
tape is unmounted
When is data transmitted? Synchronized, once or more
per day
As each virtual tape is
unmounted
How is the feature initiated? By policy scheduling or the
Dispatch button on the
Instant DR page in the VTS
web interface
Automatically, virtual tapes
in the pool are monitored
and copied when necessary
At what level are changes
made (implementation
granularity)?
Vault, pool, or virtual tape Pool only
How much data is
transmitted?
Data difference only, which
may reduce data
transmission
Bit-for-bit (1:1) copy
operation
When is bandwidth
consumed?
Per schedule, usually off-
hours
Throughout the day, may
coincide with user activity
How many backup sites are
supported?
Multiple sites, from one site
to many based on setup
Single site, from one site to
another
Is tuning supported? Initiates multiple jobs to
overcome delays
Single job only