ADSM'ers Just started using ADSM on the NT side. Have setup five NT 4.0 sp4 (IBM Netfinity 7000) servers to perform a nightly (incremental) backup via the ADSM Central Scheduler. All servers have mor
Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
Date: Fri, 13 Aug 1999 13:16:48 -0700
Probably a permissions problem try giving "Everyone" full control on the root drive on one of the drives not seen by ADSM, stop and restart the scheduler, and see if ADSM finds the drive. On Friday,
Author: "Prather, Wanda" <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
Date: Fri, 13 Aug 1999 17:02:40 -0400
It's probably a permissions thing. The Central Scheduler runs under the "system" id. You are running the ba/client under your own id. Try giving the "system" id access to the root of the E: drive.
Author: Craig Shreve <CShreve AT UNIONGAS DOT COM>
Date: Mon, 16 Aug 1999 08:11:08 -0400
I've had this happen with version 2 client, and it turned out that the drives did not have a label. I don't know whether drive labels are still required with the version 3 client.
Author: Steve Cartacki [mailto:cartacs AT PJM DOT COM]
Date: Sun, 04 Oct 2015 17:40:32 -0500
ADSM'ers Just started using ADSM on the NT side. Have setup five NT 4.0 sp4 (IBM Netfinity 7000) servers to perform a nightly (incremental) backup via the ADSM Central Scheduler. All servers have mor