Re: Missed backups on Windows NT
Maybe you don't have stopped and started the ADSM Scheduler Service on WNT since those days. Once you have a modification in the disks configuration, you have to stop and start the service to let the ADSM to know about taht. Angel Antón IZFE. S.A. Plaza de Pinares, 1-3 Donostia 20001 Tlf.: +34 943.482.869/811 , Fax: +34 943.321.023 E-Mail : [EMAIL PROTECTED] -Mensaje original- De: Thomas Denier [SMTP:[EMAIL PROTECTED]] Enviado el: miércoles 1 de noviembre de 2000 22:59 Para: [EMAIL PROTECTED] Asunto: Missed backups on Windows NT We have a Windows NT client with C, D, and E drives. The central scheduler requests an incremental backup every night. The schedule has a null object list. We recently discovered that the E disk had not been backed up in several months. The system administrator and I logged in an attempt to discover the reason for this. There was nothing in the options file calling for backups to skip the E drive. There were no messages in the log files indicating that ADSM had been trying to backup the E drive and suffered errors. The GUI client listed all three drives and had no apparent difficulty backing up the E drive. The administrator did notice one oddity. The E drive no longer had the default share normally defined for drives on Windows NT systems. He was sure that the drive had once had such a default share, but could set only broad limits on the time at which the default share was removed (the person who probably removed the default share no longer works here). The date at which backups of the E drive stopped falls within these limits. Does the command line client need the default share to recognize drives as candidates for backup? The client OS level is 4.0. The ADSM client level is 3.1.0.6.
Re: Missed backups on Windows NT
you need to check the permissions on the E_Drive... -Original Message- From: Thomas Denier [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 4:59 PM To: [EMAIL PROTECTED] Subject: Missed backups on Windows NT We have a Windows NT client with C, D, and E drives. The central scheduler requests an incremental backup every night. The schedule has a null object list. We recently discovered that the E disk had not been backed up in several months. The system administrator and I logged in an attempt to discover the reason for this. There was nothing in the options file calling for backups to skip the E drive. There were no messages in the log files indicating that ADSM had been trying to backup the E drive and suffered errors. The GUI client listed all three drives and had no apparent difficulty backing up the E drive. The administrator did notice one oddity. The E drive no longer had the default share normally defined for drives on Windows NT systems. He was sure that the drive had once had such a default share, but could set only broad limits on the time at which the default share was removed (the person who probably removed the default share no longer works here). The date at which backups of the E drive stopped falls within these limits. Does the command line client need the default share to recognize drives as candidates for backup? The client OS level is 4.0. The ADSM client level is 3.1.0.6.
Missed backups on Windows NT
We have a Windows NT client with C, D, and E drives. The central scheduler requests an incremental backup every night. The schedule has a null object list. We recently discovered that the E disk had not been backed up in several months. The system administrator and I logged in an attempt to discover the reason for this. There was nothing in the options file calling for backups to skip the E drive. There were no messages in the log files indicating that ADSM had been trying to backup the E drive and suffered errors. The GUI client listed all three drives and had no apparent difficulty backing up the E drive. The administrator did notice one oddity. The E drive no longer had the default share normally defined for drives on Windows NT systems. He was sure that the drive had once had such a default share, but could set only broad limits on the time at which the default share was removed (the person who probably removed the default share no longer works here). The date at which backups of the E drive stopped falls within these limits. Does the command line client need the default share to recognize drives as candidates for backup? The client OS level is 4.0. The ADSM client level is 3.1.0.6.
