SnapLock Compliance volumes constantly track the retention information of all retained WORM files. Data ONTAP does not allow you to destroy any SnapLock volume that contains unexpired WORM content. Data ONTAP does allow you to destroy SnapLock Compliance volumes when all the WORM files have passed their retention dates, that is, expired.
Note
You can destroy SnapLock Enterprise volumes at any time.
You can destroy SnapLock Compliance aggregates only when they contain no volumes. The volumes contained by a SnapLock Compliance aggregate must be destroyed first.
To destroy a SnapLock volume, complete the following steps.
| 1 | |
| 2 |
Enter the following command to offline the volume: vol offline vol_name |
| 3 |
vol destroy vol_name |
If there are any unexpired WORM files in the SnapLock Compliance volume, Data ONTAP returns the following message:
vol destroy: Volume volname cannot be destroyed because it is a SnapLock Compliance volume.
To destroy a SnapLock aggregate, complete the following steps.
| 1 |
Using the steps outlined in Destroying SnapLock volumes, destroy all volumes contained by the aggregate you want to destroy. |
| 2 |
Take all FlexVol volumes offline and destroy them by entering the following commands for each volume: vol offline vol_name vol destroy vol_name |
| 3 |
Take the aggregate offline by entering the following command: aggr offline aggr_name aggr_name is the name of the aggregate that you intend to destroy and whose disks you are converting to hot spares. |
| 4 |
Destroy the aggregate by entering the following command: aggr destroy aggr_name aggr_name is the name of the aggregate that you intend to destroy and whose disks you are converting to hot spares. |
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01081_B0
File: snaploc6.htm
Last updated: 01-Dec-2005 16:36:23