Hints and Tips

Getting information

You can find out what is happening with MSHSM by looking at three Netware console windows

• Managed Server HSM Error 5.1.0.5
• Managed Server HSM RTDM 5.1.0.5 (lists migrate and recall activity)
• Managed Server HSM Status 5.1.0.5

You can see the same information from the 'Monitor' screen on the MS-HSM GUI.

Migration will not work

Check that the Netware disk has its 'Migrate' flag which was set to 'on'.

Directory / File relocation

MSHSM will not recall any files if they are moved or the directories are re-organised. Directories can be renamed and stub files can be renamed without requiring recalls, and recalls will still work afterwards.
However, because the stub files contain the UNC name of the migrated file, the back-end migrated data cannot be relocated or renamed.

Virus Scan

Check that your virus scan product will not try to scan migrated files. Most products have something like a 'scan migrated files' flag which should be set to 'NO'.

Stubfile management

The stub files are critical to MSHSM operation. Caminosoft offer two routines for managing them, a STUBCHECK facility to check the integrity of the stubs, and a STUBSAVE utility to backup and recover the stubs. They recommend that you set MS-HSM up to do this by default after every migration. The Stubcheck utility runs as an NLM and writes out results into a log file in the DATA:/MSSCRIPT/MSSTUBCK.LOG.

The Stubcheck Utility can be invoked manually by running an undocumented Netware command

 MNG STUB CHECK diskname VERBOSE

Typical output looks like

Directory: DATA:\Documentation\AWDMTF\comments\SKCSD
Checking: FLDLINK1.CSD (31599 bytes)
  Success at target: HSMSERV1/SYS:\HSM\00\00\14\6E 

As far as I know, this is the only way to find out what files are migrated and the relationship between the physical location of the archived data and the stub file.

The Stubsave utility can also be run automatically or by using a Netware console command

MSSTUBV SAVE PATH data: FILE sys:/msscript/stubsave.sav FLAG /L

Stubs are recovered using the command

MSSTUBV RESTORE PATH data: FILE sys:/msscript/stubsave.sav FLAG /L

MSHSM will delete target data once the stub is purged from the Netware source disk. If you define Netware disks with purge immediate, so as soon as you delete a stub, the backend migrated data is also deleted. If you restore the stub then recall cannot work, as there is no data there to recall anymore.
It's advisable to change the Netware settings to retain purged data for a few hours to allow accidentally deleted stub files to be recovered. However even without purge immediate Netware will quickly purge stubs on a busy disk, so if a stub is accidentally deleted then it is possible that the migrated data will be lost too.

back to top

Copyright © Lascon Storage Ltd. 2000 to present date. By entering and using this site, you accept the conditions and limitations of use