Table of ContentsLibraryView in Frames

Enabling SnapValidator checks on volumes

You enable SnapValidator checks at the volume level.

Before You Begin

Ensure that SnapValidator has been licensed on the storage system.

Steps

  1. On the storage system command line, enable SnapValidator by entering the following command:vol options volume-name svo_enable on

    All SnapValidator checks are enabled on the volume, with the exception of checksums.

  2. Further configure SnapValidator at the volume level by doing some or all of the following steps:
    • If you want to enable data checksumming on the volume, enter the following command:vol options volume-name svo_checksum on
    • If you want to disable block number checks because the volume contains Oracle Recovery Manager (RMAN) backup data enter the following command:vol options volume-name svo_allow_rman on
    • If you want to set SnapValidator to return an error log to the host and storage system consoles for all invalid operations. You might want to do this when you are testing SnapValidator before you put your database into production enter the following command:vol options volume-name svo_reject_errors off

      When you set this option to Off, SnapValidator only logs errors but does not reject invalid operations.

    • If you want to set SnapValidator to reject all invalid operations and return an error log to the host and storage system consoles enter the following command:vol options volume-name svo_reject_errors on
      If this option is not set to On, then SnapValidator detects invalid operations but only logs them as errors. The following shows a SnapValidator error example displayed on the storage system console:
      Thu May 20 08:57:08 GMT [filer_1: wafl.svo.checkFailed:error]: SnapValidator: Validation error Bad Block Number:: v:9r2 vol:flextest inode:98 length:512 Offset: 1298432