Possible reasons for "Missed" backups?
2000-08-17 14:58:54
Subject: |
Possible reasons for "Missed" backups? |
From: |
Linda Seeba <seeba AT US.IBM DOT COM> |
Date: |
Thu, 17 Aug 2000 13:58:21 -0500 |
Others reasons for backups not completing on UNIX servers are:
The O/S on the client has been reloaded and the TSM/ADSM software is
missing
Stale NFS handles - this is usually when a filesystem was mounted to
something that no longer exists.
There is a hardware problem on the client filesystem that it is trying to
back up.
Linda Seeba Phone: (314) 234-5190
I/T Specialist - Sr Fax: (314) 232-4581
IBM Global Services E-Mail:seeba AT us.ibm DOT com
---------------------- Forwarded by Linda Seeba/St Louis/IBM on 08/17/2000
01:50 PM ---------------------------
01:50 PM ---------------------------
Daniel Swan/TM <Daniel.Swan AT TELUS DOT COM>@VM.MARIST.EDU> on 08/17/2000
10:47:20 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Possible reasons for "Missed" backups?
Using the QUERY EVENT command, I see a list of completed, missed, and
failed
backups.
I assume that the 'missed' are due to a defunct/inactive client scheduler,
or a loss of connectivity to the host.
Are there other possible reasons, perhaps scheduling oriented or otherwise,
to explain why a client is 'missed'?
|
|
|