Library Table of Contents Index Previous Next Comments

Copying volumes

Command to use to copy volumes  Top

You use the vol copy start command to generate volume copy operations, which produce screen messages that show the progress of the operations.

Each vol copy start command generates two volume copy operations, each of which is assigned a number:

When to use the volume copy operation number  Top

You need the volume copy operation number if you want to stop a volume copy operation or change the volume copy operation speed.

For information about obtaining the volume copy operation number, see Checking the status of a volume copy operation.

Number of vol copy operations supported  Top

Each filer supports a given number of simultaneous volume copy operations. For the number of copy operations supported per filer type, see Maximum number of simultaneous replications on a filer.

Whether Data ONTAP can execute a vol copy start command depends on how many volume copy operations are already in progress on the filers specified in the vol copy start command, as illustrated in the following examples.

Example

To copy volumes locally, you can enter the following two vol copy start commands on an F85 filer, which supports four simultaneous copy operations:

vol copy start vol0 vol1
vol copy start vol2 vol3

When these commands are in progress, if you enter additional vol copy start commands, they will fail, because four volume copy operations are already running on the filer. Two of the operations are for reading the vol0 and vol2 volumes, and two of the operations are for writing the vol1 and vol3 volumes.

Example

Suppose you enter the following three vol copy start commands on an F85 filer named filerA to copy volumes to another F85 filer named filerB:

vol copy start vol0 filerB:vol0
vol copy start vol1 filerB:vol1
vol copy start vol2 filerB:vol2

When these commands are in progress, filerA runs three volume copy operations to read the volumes, and filerB runs three volume copy operations to write the volumes.

An additional vol copy start command to copy between filerA and filerB will succeed because the command adds one more volume copy operation to each filer.

However, if you enter an additional vol copy start command to copy volumes locally on either filerA or filerB, it will fail. This is because the additional command creates two volume copy operations, one for reading and one for writing, on the filer that performs the local copying.

Copying snapshots with the vol copy start command  Top

The following table describes the snapshots that will be copied from the source volume and the resulting snapshots on the destination volume, depending on the option you use with the vol copy start command.

Option

Snapshots to copy from the source volume

Snapshots in the snapshot file system of the destination volume

None

No snapshots in the file system will be copied. Only the snap-shot taken after you enter the vol copy start command will be copied.

A snapshot named snapshot_for_volcopy.n, where n is a number starting at 0 and incrementing by one whole number with each vol copy operation

-S

All snapshots in the snapshot file system of the source volume and the snapshot taken after you enter the vol copy start command will be copied.

All snapshots in the source volume and snapshot_for_volcopy.n, where n is a number starting at 0 and incrementing by one whole number with each vol copy operation.

-s followed by the name of the snapshot

The specified snapshot will be copied.

The specified snapshot

Note
The vol copy start -S command does not copy any snapshots that are created while the copying is in progress. For example, if the copying lasts from 11:45 p.m. to 1:00 a.m. the next day and Data ONTAP creates a snapshot named nightly.0 at midnight, Data ONTAP does not copy the nightly.0 snapshot.

Copying one volume to another  Top

To copy one volume to another, complete the following step.

Step

Action

1

Enter the following command:

vol copy start [-S | -s snapshot_name] source_volume 
dest_volume

The -S and -s arguments specify the snapshots to copy.

source_volume and dest_volume are the names of the source and destination volumes. If a volume is on a different filer, precede the volume name with the filer name and a colon. For examples illustrating how to specify volume names, see Examples of the vol copy start command in the following table.

Note
If the copying takes place between two filers, you can enter the vol copy start command on either the source or destination filer. You cannot, however, enter the command on a third filer that does not contain the source or destination volume.

Examples of the vol copy start command  Top

The following table shows several examples of the vol copy start command.

If you want to...

Use...

Copy all snapshots from the vol0 volume to the vol1 volume on the same filer

vol copy start -S vol0 vol1

Copy a nightly snapshot from the vol0 volume to the vol1 volume on the same filer

vol copy start -s nightly.1 vol0 vol1

Create a snapshot in the vol0 volume to be copied to the vol1 volume on the same filer

vol copy start vol0 vol1

Copy all snapshots from the vol0 volume to the vol1 volume on a different filer named filerA

vol copy start -S vol0 filerA:vol1

Error messages generated by vol copy start commands  Top

If your filer does not meet the requirements for copying a volume, the vol copy start command generates one or more error messages. The following table explains the possible error messages and their meanings.

Error message

Meaning

Permission denied.

 
VOLCOPY: Could not connect to 
filer filerB

The source filer does not have permission to copy to the destination filer.

Action

Make sure that the filers have a trust relationship with each other.

VOLCOPY: volcopy restore: 
volume is online, aborting

The destination volume is online.

Action

Take the destination volume offline.

VOLCOPY: volcopy restore: 
volume is too small, aborting

The destination volume is smaller than the source volume.

Action

Add more disk space to the destination volume or choose another destination volume of sufficient capacity.

write: setting up STDERR broken 
pipe

A local volume copy tried to start, but Remote Shell access is not enabled on the filer.

Action

Enable Remote Shell access on the filer so that it can receive rsh commands.

Library Table of Contents Index Previous Next Comments