MS-HSM from Caminosoft supports HSM on Windows and Netware servers
Managed Servers- The Servers that contain data that you want to manage with migration or deduplication. You create policies for every volume that you want to manage on these servers.
Storage Servers- Servers that host storage that contain migrated data. A server can be both a managed server and a storage server.
Source disks - the disks that contain data that you want to manage. These disks are hosted on Managed Servers.
Target disks- the disks that you will migrate data to. These are held on a Storage Server.
Stub files small placer files left behind on the source disk, that point to the migrated data on the target disk
Management GUI PC based control panels that let you manage MSHSM
Policies rules that decide when a file is migrated or deleted.
Configuration files files that contain the policies and target rules. These are held on each source disk.
MS-HSM works with Windows Server 2000, 2003, 2003 R2, 2008, 2008 R2,2012, 2012 R2 clusters (64-bit available for Windows 2003 /2008/2012). It also supports Apple-MAC, NetApp and OES Linux servers and still supports Netware 6.5 clusters.
Traditionally, MS-HSM used cheap disk for its backend datastore, but it also supports IBM's TSM, CA's Arcserve and EMC's Centerra as datastores.
In 2012, Caminosoft announced that they now support Primary Server Deduplication, where duplicate files on the primary server are replaced by small stub files, so that the original file data is accessed if the stub is referenced.
Windows installation is a simple process. Simply navigate to the setup.exe program on the installation CD, run it and follow the prompts. You will need to install an MSHSM agent on each server that you plan to manage and also a Windows PC management GUI which can run on one of the managed servers, or on a work station
To Instal the PC GUI, simply navigate to the GUI folder on the installation CD then run the 'setup.exe' program, following the prompts as required.
Once you install the code, you automatically get a 30 day trial license. The easiest way to licence the product is to send a screenshot of your product activation screen to CaminoSoft Support. This screen can be found on the administrator GUI. From the GUI, click Help, Product Activation.
If you are upgrading the code then some old configuration files can cause problems. Delete or rename the contents of the MSSCRIPT directory.
This process is a bit more complex and the information below is just intended to give an overview of what is required. Consult your Caminosoft documentation for full details.
On OES, MSHSM needs its own Caminosoft file system for archive retrieval to work. Basically, you need to create a new Caminosoft volume in the same storage pool as the volume that you want to manage, and within that new volume, create a mount point folder which you then map to the users volume. The new volume hardly uses any space as all file retrieves are redirected to the original user volume. However, if you don't setup the Caminosoft volume then your users will not be able to access their retrieved files.
If you want to manage several volumes in the same storage pool, you just need to create a mount point folder for each volume.
Once you complete the MSOES install, you then need to change your users drive mappings, so they map to the mount point folder rather then their original volume. They still access their data from the same physical volume as before, the mount point mapping takes care of that.
It is possible to avoid the need to change users drive mappings by renaming volumes, see the Caminosoft documentation for details.
The overall install process goes like this: