User's Manual

214 Troubleshooting
Description A recall job does not search for alternative copies if the FSE medium status is set to unusable
after the allocation.
Explanation This may happen in the following situation:
• A running FSE recall job has determined from which FSE medium the data will be recalled
but is still waiting for that medium to become available (probably because another FSE job
has allocated the same medium).
• During this waiting time, the medium status is set to unusable but the waiting recall-job is
not notified of this change.
The recall job will continue to wait for the medium to become good, and therefore it will not
search for available redundant copies migrated to other FSE media pools, if any exist.
Workaround Using the fsejob command, identify and terminate all FSE recall jobs that are waiting for the
unusable FSE medium to become good.
If there are alternative copies of the migrated data in other FSE media pools, the subsequent
FSE recall jobs will allocate an FSE medium from one of those pools, and recall the data from it.
Description Rename or move actions on offline files cause file recalls, if performed over a network share
from a Windows system with Norton AntiVirus installed (Windows FSE client-specific).
Explanation Norton AntiVirus ignores the offline file attribute of files located on remote HSM file systems on
the Windows FSE client. The rename or move operation causes the files to be recalled for
scanning against viruses.
Workaround In Norton AntiVirus, disable scanning of the network drives that are mapped to the remote
HSM file systems.
Description When you modify attributes of an offline file through a Samba share, the file is recalled from
the FSE media (Linux system-specific).
Explanation The customized Samba server running on a Linux system apparently reads part of the file
contents after a file attribute is changed remotely from a Samba client.
Workaround None
Description When you try to run an executable file located on an HSM file system and the file is currently
offline, the operation fails and reports an EBUSY error (Linux system-specific).
Explanation n/a
Workaround Before running an executable file that is currently offline, recall it manually to the HSM file
system using the fsefile --recall command.