BackPak H4.00 Troubleshooting and Messages Manual

Troubleshooting
16 BackPak H4.00 Troubleshooting & Messages
12. Stop any BackPak program instance
VOLUME <backpak-installation-subvol>
STATUS *, PROG * (to check processes that will be stopped by next command)
STATUS *, PROG *, STOP
13. Reboot the VTC servers
14. Wait for EMS message reporting the starting of Emulator Windows service from
all VTCs
15. Restart ZSERVER and $XDMS
$XDMS is usually restarted by the obey file starting $ZSVR
Sample obey file for $ZSVR, provided just as indication.
run $system.system.zserver &
/name $zsvr,nowait,in $zhome,out $zhome,term $zhome, &
pri 199,cpu 0/1
delay 5 seconds
mediasrv /name $xdms,nowait, in $zhome,out $zhome, &
term $zhome, cpu 0 /autostop -1
16. Restart all devices
SCF START TAPE $*
17. Check EMS for normal starting of tape drives
18. Verify that MEDIACOM is working properly
mediacom info mediadefs
mediacom status
mediacom info volcat *
mediacom info filecat *
19. Access the detailed status of each node in the BackPak GUI
(on the home page, node name link)
On the detailed status page, verify the tape drives are FREE from both point of
views: NonStop and BackPak.
20. Start the EMS Extractor(s)
21. Start a tape application
Procedure complements for other nodes
If the BackPak domain manager also serves peripheral nodes, the only component to
reset on these other nodes is:
• the EMS Extractor connected to the local BackPak domain
If VTCs emulating tape drives are also emulating tape drives on other nodes, the
components to reset on these other nodes are:
• the tape applications using tapes managed by the local BackPak
domain
• the EMS Extractor connected to the local BackPak domain