There are 2 methods to using SmartDisk on DataDomain volumes. Both have 2 dependencies:
Dependency 1 – serve the DataDomain to a Windows machine as CIFS, or a Linux machine as CIFS or NFS.
Dependency 2 – make sure that the user you use to install/run SmartDisk has full read/write access to the share and everything underneath it.
The first way is if SmartDisk is not already installed. In this case, it is simply a matter of entering the path to the DataDomin disks when installing SmartDisk. This can be path to a mounted NFS share, or the UNC path to a CIFS share.
,
The second way is if SmartDisk is installed. In this case, add the path to the DataDomin disks using the CLI commands.
If the disks are mounted:
.../foundation/bin/smartdisk.sh config --add --volume /mnt/<newNVSDvolume>
For CIFS shares:
.../foundation/bin/smartdisk.sh config --add --volume //<IPaddress>/<NVSDvolume> --account <nonpriviledgedUser> --password <nonprivilegedUserPassword>
Both of these options will add a volume to be used for all roles.
,
You can also be more specific in roles, like:
.../foundation/bin/smartdisk.sh config --add --volume /mnt/<newNVSDvolume>/staging --deny storage --favour staging
To add a staging volume.
,
.../foundation/bin/smartdisk.sh config --add --volume /mnt/<newNVSDvolume>/staging --deny staging --favour store
To add a store volume.
,
Then, remove or deactivate the paths you had when SmartDisk was installed.
.../foundation/bin/smartdisk.sh config --update --volume /ORIGINAL/PATH --favour none --deny all
,
The final step after finishing one of the above 2 processes, is to disable SmartDisk de-duplication. The DataDomain will do that.
.../foundation/bin/smartdisk.sh config --dedupe-enable FALSE
