The purpose of this troubleshooter is to diagnose why volumes in TapeTrack are not being slotted.

The symptom of slotting not working is that when volumes are moved to a repository that has slotting enabled, the volume does not automatically get a slot assigned.

Yes, slotting was previously setup

If slotting was previously setup and has stopped working then something has changed.

Slotting was previously run manually

Slotting can be performed manually using several methods:

• By manually editing each volume and setting the slot.
• By selecting the repository and pasting volumes into free slots under the Repository Usage Map Tab.
• By running the slotting program manually from a command prompt or batch file.

If slotting is no longer working, the most probably cause is that it is not being manually run.

If slotting is run by manually calling the slotting program, you should check the output from the slotting program for the following conditions:

• That the program is connecting to the server successfully and that it is the right server.
• That the User-ID and Password are correct and that the program has been able to login.
• That there are sufficient slots available to slot all volumes that require a slot (i.e. if there are 10 volumes to slot, and only 8 free spaces, the slotting program will not slot any of the volumes).

Slotting was previously run automatically

*

No, slotting was not previously setup

Slotting is not setup to run by default, to enable slotting a number of setup tasks must be performed:

1. Slotting must be enabled in the options for the repository requiring slotting.
2. Zones must be assigned to the repository
3. There must be a sufficient number of free slots available to accommodate every volume that currently requires a slot.
4. The slotting program must be called, either manually or via a scheduler such as Windows Scheduler or crond
5. The slotting program must be called with the right arguments, including the right server name and valid credentials.