Re: D: drive not backed up on NT Server with v3.1.0.8
2000-03-10 16:12:32
Subject: |
Re: D: drive not backed up on NT Server with v3.1.0.8 |
From: |
James Thompson <mezron AT HOTMAIL DOT COM> |
Date: |
Fri, 10 Mar 2000 14:12:32 MST |
This normally is a permissions problem. Check the scheduler service via
control panel / services. See what account the service logs in as. If it
is the SYSTEM account, make sure that the d drive has permissions for the
SYSTEM account. A lot of NT Administrators remove EVERYONE from the
permissions, it also prevents the SYSTEM account from being able to do
backups.
James
From: Zeke Crater <adsmguy AT QUEENS DOT ORG>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: D: drive not backed up on NT Server with v3.1.0.8
Date: Fri, 10 Mar 2000 10:35:07 -1000
I have a new NT Server (BDC if that matters) with ADSM v3.1.0.8 client
installed. The ADSM server is MVS Version 3, Release 1, Level 2.0. When I
use the ADSM backup client manually both the C: and D: drives backup fine.
When the scheduler runs, though, only the C: drive is backed up. I back up
15 other NT servers with this setup and everything works great. All the NT
servers use the same policies, dsm.opt options, etc... I have reinstalled
the ADSM and ADSM Central Scheduler Service. I have added INCLUDEs in the
dsm.opt file. The scheduled backup still ignores the D: drive.
The only thing different about this NT server is the D: drive is 50GB. My
next largest D: drive is 38GB.
Any ideas?
Zeke Crater
ADSM Guy
The Queen's Medical Center
Honolulu, Hawaii
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
|
|
|