Disk sanitization is not supported for all disk types. In addition, there are times when disk sanitization cannot be performed.
You should be aware of the following facts about the disk sanitization process:
- It is not supported on all SSD part numbers.
For information about which SSD part numbers support disk sanitization, see the Hardware Universe at hwu.netapp.com.
- It is not supported in takeover mode for systems in an HA pair.
- It cannot be performed on disks that were failed due to readability or writability problems.
- It cannot be performed on disks that belong to an SEC 17a-4-compliant SnapLock volume until the expiration periods on all files have expired--that is, all of the files have reached their retention dates.
- It does not perform its formatting phase on ATA drives.
- If you are using the random pattern, it cannot be performed on more than 100 disks at one time.
- It is not supported on array LUNs.
- If you sanitize both SES disks in the same ESH shelf at the same time, you see errors on the console about access to that shelf, and shelf warnings are not reported for the duration of the sanitization.
However, data access to that shelf is not interrupted.
- You can perform disk sanitization on disks using Storage Encryption.
However, there are other methods to obliterate data on disks using Storage Encryption that are faster and do not require an operational storage system.
