Creating And Managing Volumecopy Copies; Understanding Volumecopy - IBM DS3000 Introduction And Implementation Manual

System storage
Hide thumbs Also See for DS3000:
Table of Contents

Advertisement

7065Admin_Configure.fm
storage system. This provides an opportunity to move data to larger drives (for example, 73
GB to 300 GB).
Backing up data
The VolumeCopy function can create a backup of a logical drive by copying data from one
logical drive to another logical drive in the same storage system. The target logical drive can
be used as a backup of the source logical drive, for system testing, or to do a backup to
another device, such as a tape drive.
Restoring FlashCopy logical drive data to the base logical drive
If you need to restore data to the base logical drive from its associated FlashCopy logical
drive, the VolumeCopy function can be used to copy the data from the FlashCopy logical drive
to the base logical drive. You can create a VolumeCopy of the data on the FlashCopy logical
drive, then copy the data to the base logical drive.

8.5.3 Creating and managing VolumeCopy copies

A VolumeCopy can be made and managed using the IBM DS3000 Storage Manager or with
command-line interface (CLI) commands and scripts.

8.5.4 Understanding VolumeCopy

A VolumeCopy operation will invalidate (fail) all FlashCopy logical drives associated with the
target logical drive, if any exist. If you select a base logical drive of a FlashCopy logical drive,
you must disable all FlashCopy logical drives associated with the base logical drive before
you can select it as a target logical drive. Otherwise, the base logical drive cannot be used as
a target logical drive.
Important: A VolumeCopy overwrites data on the target logical drive and automatically
makes the target logical drive
If there are eight logical drive copies with a status of In Progress, any subsequent
VolumeCopy will have a status of Pending until one of the eight logical drive copies
completes.
VolumeCopy and modification operations
If a modification operation is running on a source logical drive or target logical drive, and the
VolumeCopy has a status of In Progress, Pending, or Failed, then the VolumeCopy will not
take place. If a modification operation is running on a source logical drive or target logical
drive after a VolumeCopy has been created, then the modification operation must complete
before the VolumeCopy can start. If a VolumeCopy has a status of In Progress, then any
modification operation will not take place.
Modification operations include:
Defragmenting an array
Copy back to a drive that is part of an array
Initialization of a logical drive
Dynamic Segment Sizing (DSS) change for a logical drive
Dynamic Reconstruction Rate (DRR) of a drive that is part of an array
Dynamic RAID Level Migration (DRM) change for an array
186
IBM System Storage DS3000: Introduction and Implementation Guide
Draft Document for Review August 30, 2007 12:59 am
read-only
to hosts.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents