Configuring FDR/Upstream for Netware Migration

This page deals with the Upstream / Netware recall interface, and the various options for controlling the user messages. Netware is more or less dead of course, and Upstream does support HSM on Windows but there seems not to be any documentation for this at present.

Netware server - Automatic recall

The Netware recall settings are controlled by the nwrecall NLM To change them you need to log into the Netware server and open the FDRUPSTEAM Auto-Recall System window. If you cannot see the window, that means your userid does not have the correct security access. The window looks like -

An active nwrecall console screen

Hit 'esc' to halt auto recall, then confirm with a 'y'. You will then get the option to change the settings, reply 'y' to modify the config file. Most parameters should be left at the default. The things you will change will relate to user notification, wait on recall, and volumes to be migrated. You will also see this the first time nwrecall is loaded.

Once you change the settings, nwrecall is unloaded. To start it up again, type 'load usrecall' from the system console

The types of things you may need to change are -

Stub has Extension (Y or N)
It is possible to indicate that a file has been migrated by adding an .upstream-migrated extension to the end of every stub file. You specify this in your migration job, but if you did that then you must also state that you are using the stub extension in nwrecall.
If you do not add the file suffix, the only way you can tell the file is migrated is that the space used is 0KB.
If you add the suffix, then applications like Word and Excel will not see the migrated files when you do 'file' 'open' unless you change the 'files of type' to 'All files (*.*)' This could well cause problems for your users. Error message from windows - file not found
This is a decision that you have to make and get right, because once you start archiving real data, you cannot change between 'Stub has Extension' and 'Stub has no Extension'.
Wait for Recall (Y or N)
If you specify 'Y' then the application will wait until the recall completes. This is probably the best option if you are recalling from cheap disk, but the application could hang for several minutes, if the archived file is on tape and the drives are busy.
Support User Notification (Y or N)
This option requires that a program called usnotify.exe is installed and running on the user's PC. If the parameter is set to 'Y', and usnotify is running, the user will get a message like FDR/Upstream Netware recall progress messages
If you specify that the application will wait until the recall completes, it is not possible to also request the Netware messages that the recall is in progress.
User must accept (Y or N)
The user gets to say no, I don't want to bother recalling this file. This could be useful if the application is locked, and the user expects the recall to take several minutes. The message looks like - FDR/Upstream Windows recall progess message

Some parameter variations

If you specify

Wait for Recall 'N'

then the application will get an error message. The exact error will obviously depend on the application, but the Word message will look like

Windows error message

When the recall completes, you need to go back into Word and try to open the file again.

If you say that the user must accept the recall, and you say the application will not wait for the recall, you get a message like -

FDR/Upstream error message - application not waiting

In this case, Word hung until the message above was replied to.
You need to decide which types of message suit your site and users best.

back to top

Open Systems HSM

Lascon latest major updates

Welcome to Lascon Storage. This site provides hints and tips on how to manage your data, strategic advice and news items.