Enabling and disabling logical block protection

You can specify logical block protection for read and write operations, or only for write operations. You can also disable logical block protection if it is enabled. By default, logical block protection is disabled because of performance effects that result from CRC validation on the server and the tape drive.

About this task

Read/write operations to empty or filling volumes depend on whether the volumes have logical block protection. Protected and unprotected data blocks cannot be mixed on the same volume. If you change the setting for logical block protection, the change applies only to empty volumes. Filling and full volumes maintain their status of logical block protection until they are empty and ready to be refilled. For example, suppose that you disable logical block protection. If the server selects a volume that is associated with a device class that has logical block protection, the server continues writing protected data to the volume.

To enable logical block protection, specify the LBPROTECT parameter on the DEFINE DEVCLASS or the UPDATE DEVCLASS command for the 3592, LTO, and ECARTRIDGE device types:


What to do next

To determine whether a volume has logical block protection, issue the QUERY VOLUME command and verify the value in the field Logical Block Protection.