Configuring MS-HSM

Working with the HSM Engine

An HSM Engine must be installed on every server that you want to manage with MSHSM. It is used to manage the archive and recall functions. Caminosoft recommends that an HSM Engine on windows be installed to run as a service so it starts automatically when the server is booted. This service is called CsManager and it must be configured with a logon userid that has administrator provileges on the local managed server and also write access to the target servers that will host the migrated data. If the target server or device supports the CIFS protocol then it will be accessible if the HSM Engine runs as a service.

The migration and profile information is stored in a database and that database can be either MS Access or MSSQL. If you run in 64 bit mode then you must use MSSQL. If you use MS Access, then you do not need any additional configuration. If you use MSSQL then the Windows logon used at the time of installation must have administrative database privileges on the specified SQL server, using Windows authentication.

You can start and stop the HSM engine from the Windows Start menu; navigate to Programs, Caminosoft, HSM 5.2, bin, then use csstart.bat or csstop.bat as appropriate.

You use the HSM Administration GUI to set up your MSHSM environment, including selecting which servers are to be managed, but first you need some source servers in your list. MSHSM will search for all source servers which have a CsManager service running, or you can add servers manually. The Select Server Tab looks like this.

The Select Server Tab

To search for online servers use the search server dialog

The Select Server Tab

If you want to add a server in manually you can use the add server dialog

The Select Server Tab

Once you have servers in your list, you must select one to manage and provide an Administrator GUI password before you can specify migration policies and assign the server’s files to a storage pool for migration. The other tabs in the interface are not available until you select a server to manage. After you select a server, the other tabs are available for specifying migration rules, policies, and sources, and to monitor migration activity.

Set Global Migration rules and policies

You use the MSHSM GUI to set up your migration rules and policies. You should restrict access to this GUI and make sure your screen resolution is set to a minimum of 1024 by 768 pixels otherwise you will not be able to see all the options. The Rules and Policies tab is quite busy, it looks like this

The rules and policies tab

Starting from the top left of the screen, the first options are for times when you want migration to be restricted. Peak times are the hours when you would prefer no migration, but will accept it if emergency thresholds are reached. Peak hours are set in the screen above to between 8 am and 5 pm. You can also specify a time when you don't want any migration at all, here set to between 01:00 and 04:00.

The next block of options are for schedules, and you have three options. Never run a schedule, run them during off-peak hours, or run them anytime. Here, migration and deduplication can run anytime on a Saturday or Sunday (except the nomig period between 01:00 and 04:00, but only during off-peak hours Monday to Friday. Deletion will never happen as the deletion schedules are all set to 'off'.

MSHSM will only migrate data if that is necessary to maintain freespace on a volume. It does this by checking the amount of freespace on a volume and comparing this with three migration thresholds.

  1. Goal threshold
    MSHAM will start migrating during an allowable schedule window, if the used volume capacity is higher than this threshold, and stop migration when it reaches it.
  2. Emergency threshold
    This threshold will allow migration to happen during peak hours and is used when it looks like a volume will run out of space. This threshold value will be higher than the goal threshold.
  3. Safety threshold
    When a volume reaches the safety threshold level, the emergency threshold migration stops. This avoids unwanted server overhead during peak hours.

The lower left section of the rules/policies tab shows the threshold values that are set for this volume. You change the values from the Edit Volume Rule screen

Edit volume screen

The right hand panel contains some other global values to manage the following

Finally, the Wildcard section is used to identify files that you never want to migrate.

Creating Policies and Profiles

Every managed drive or share on every managed server has a CsPolicy Folder which contains the Migration policy information for this drive. The files within these folders are never migrated and should never be deleted. You populate these files by using the Sources Tab from the Administration GUI. Within this tab you can define Profiles that describe how to manage the files you want to migrate, deduplicate or delete. You might not get all three options, depending on which features you have licensed.
The Sources Tab looks like this

The Sources Tsb

The upper panel displays existing profiles. Like most MSHSM constructs, you manage the profiles by clicking on the buttons to the right.
Click on this button to add a new profile -
on this button to edit an existing profile -
and on this button to delete an exisitng profile -

If you click on New or Edit you get the New/Edit Profile dialog, which looks like this

The Edit Profile dialog

If you are adding a new profile, you need to select a volume to manage, then state which kind of profile it is; migration, deletion or deduplication, then give it a name.
The Include/Exclude section lets you decide on a path by path basis exactly what you want to manage, then the Pool section lets you decide which target pool you want to store migrated data on.
On the right hand side, the filters section lets you exclude certain types of file from migration, while the Rules section lets you pick eligible files by size or last accessed date.

back to top

Open Systems HSM

Lascon latest major updates