Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+No\s+devices\s+found\s+on\s+ACS$0$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+No\s+devices\s+found\s+on\s+ACS$0$\s*$/: 3 ]

Total 3 documents matching your query.

1. [Veritas-bu] No devices found on ACS(0) (score: 1): Author: steve AT warning DOT ca (Steve Mickeler); Date: Sat, 18 Oct 2003 16:24:57 -0400 (EDT); Using NBU 4.5 - FP5 I cant seem to get acsd started. It always quits with: Daemon terminating: No devices found on ACS(0) I can talk to the acsls server just fine via acstest if I manually start acss; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2003-10/msg00311.html (10,814 bytes)
2. [Veritas-bu] No devices found on ACS(0) (score: 1): Author: steve AT warning DOT ca (Steve Mickeler); Date: Mon, 20 Oct 2003 12:32:55 -0400 (EDT); Turns out when I used the GUI to configure my drives, it would always have the "Drive is under robotic control" section greyed out. Configure the drive via tpconfig and voila, it asks me if my drives; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2003-10/msg00329.html (11,704 bytes)
3. [Veritas-bu] No devices found on ACS(0) (score: 1): Author: gdrew AT deathstar DOT org (George Drew); Date: Mon, 20 Oct 2003 13:39:08 -0400 (EDT); Netbackup doesn't currently support drive serialization for ACS robot types, so the gui has no way of knowing where the drives are in the robot. Tpconfig doesn't care because you have to tell it wher; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2003-10/msg00330.html (12,630 bytes)

Current List: 1 - 3
Page: [1]