Reactivate Accidentally Scratched Virtual Volume

Reactivate Accidentally Scratched Virtual Volume › Reactivate Accidentally Scratched Virtual Volume

Reactivate Accidentally Scratched Virtual Volume

When a Virtual Volume is scratched, CA Cloud Storage for System z renames the file on the Linux Server. Three days after the volume is scratched, executing the cacloud scr_sync command deletes these files from the Linux Server. You can reactivate an accidentally scratched Virtual Volume up until the point its file is permanently deleted from the Linux Server.

To reactivate a scratched Virtual Volume, follow these steps:

Issue the SVTn X vol_info volser* console command to determine what versions of the scratched VOLSER remain. If no versions are returned, the Virtual Volume cannot be reactivated. If one or more versions are returned, use the scratch date in the file name to identify the required version.
If the Virtual Volume has been reused, an active version is returned also:
```
SVT4X2205I cacloud vol_info 105979*  481       
Scanning /var/lib/cacloud/vault_01/vv_*/105979*
2.0G vv_105/105979.vve                  <- Active
2.0G vv_105/105979.scr-20131017-215934  <- Scratch 
```
Reactivate the Virtual Volume, if the required scratch version still exists.
Copy the data set to another Virtual Volume to free up the needed VOLSER, If an active version of the Virtual Volume exists.
Note: After copying the data sets to a new Virtual Volume, you may need to recatalog them.

Scratch the needed VOLSER in the Global VCAT by executing the SVTSUTIL batch command VVE_SCRATCH=volser where volser is the Virtual VOLSER.

Note: Now the Linux Server has two scratch versions of this VOLSER.

SVT4X2205I cacloud vol_info 105979*  481       
Scanning /var/lib/cacloud/vault_01/vv_*/105979*
2.0G vv_105/105979.scr-20131018-100738  <- Now scratched 
2.0G vv_105/105979.scr-20131017-215934  <- Scratch

Log on to the Linux system and enter the following command to change to the appropriate directory:
```
cd /var/lib/cacloud/vault_01/vv_xxx 
```
Where xxx is the first three characters of the VOLSER.
Enter the following command to display the scratched Virtual Volume files:
```
ls -lh volser*
```
Where volser is the Virtual VOLSER.
Enter the following command to rename the scratch Virtual Volume file to an active Virtual Volume file:
```
sudo mv volser.scr-yyyymmdd-hhmmss volser.vve
```
Where volser is the Virtual VOLSER, yyyymmdd is the date, and hhmmss is the time of the appropriate scratched version of this VOLSER.
Update the tape management system record for the reactivated Virtual Volume If needed, so that it reflects the correct data set name and other information. If the record is in scratch status, update it with an expiration date in the future to reactivate it.

Note: When a reactivated Virtual Volume is displayed in the ISPF Interface (SVTSMON), no data set name, group number, creation date, or other information is displayed. This information is not required for CA Vtape to read the Virtual Volume successfully and provide the application with its data set.