About running deduplication on a vFiler unit using the CLI

You can run deduplication on a vFiler unit using the command-line interface.

The following deduplication commands are available by using the command-line interface (CLI).

sis on
sis off
sis start
sis config
sis status
sis stop

All deduplication commands ensure vFiler boundary checks. This mechanism prevents any attempt to access storage that does not belong to the requesting vFiler unit. You must switch to vFiler context of the vFiler unit that owns the FlexVol volume to be deduplication enabled. This enables you to run a deduplication command on a FlexVol volume.

Example:

FlexVol volumes, vola and volb, are owned by vFiler units, vf1 and vf2, respectively. To switch context, issue the following commands.

vfiler context vf1
sis on /vol/vola
sis start -s /vol/vola

Now you can run deduplication commands on vf1and vola. But you cannot run commands on vf2 or volb, because their context is vf2, not vf1. Therefore, the following command would fail: vfiler context vf1 sis on /vol/volb

This command fails because the context is vf1.

The output of these commands will be vfiler context specific. These commands will display information about all volumes within the vFiler unit of the current vFiler context.

sis config—No volume name is specified.
sis status—No volume name is specified.

Using the vfiler run command, you can specify the target vFiler unit of the command as an argument. This ensures a proper vfiler context is assigned before running a deduplication command.

vfiler run runs the command following it in the specified vFiler context.

vfiler run [-q] vfilertemplate sis_command [args]

The run sub-command runs the command on the vFiler units specified in the vfilertemplate. If more than one vFiler unit is named, the command runs seperately for each vFiler unit. Any vFiler specific console command can be used. If the command is not vFiler specific, an error message is logged and the command fails.