Re: Is TSM for VE 7.1.1.1 pagefile aware? Is it contrained to a single process per datamover? What constitutes a successful backup?
There's no mention of pagefile 'awareness' in the documentation, so it's safe to say that the backup will consist of all changed blocks, regardless of what's stored on them. Ditto. We've found that that the backup GB per day for VE can be significantly higher than it would be if the machines were physical servers because you pick up all changed blocks. That includes pagefile.sys, and all the Windows temporary crud that you can usually exclude on a physical machine. Where we have really gotten burned is double-dipping on MS-SQL - DB's were set up with maintenance plans that backup to a /BACKUPS directory, then after a P to V conversion ended up on the same hdisk as the DB itself. With VE you then get double the changed blocks - blocks for the DB itself, and changed blocks for the /BACKUPS directory. And machines created with big work directories on hdisks that can't be excluded. etc. etc. You'll want to have a conversation with your VM team about how to create VM's that are backup friendly, by splitting into more hdisks and identifying those that can be excluded from backups. As for threaded behavior, I've pinned all the cores on my datamover during heavy parallel backups using deduplication, so while it may only register as a single process in the Task Manager, it seems clear that TSM is acting like a multi-threaded application. Yup. Pins all the cores we give it, and we aren't using dedup. Wanda Prather TSM Consultant ICF International Enterprise and Cybersecurity Systems Division From:Schaub, Steve steve_sch...@bcbst.commailto:steve_sch...@bcbst.com To:ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU Date:03/02/2015 11:24 AM Subject:[ADSM-L] Is TSM for VE 7.1.1.1 pagefile aware? Is it contrained to a single process per datamover? What constitutes a successful backup? Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU 1. Is VE pagefile aware? I.E. is it smart enough to know not to bother backing up changed blocks from within the pagefile.sys file? 2. It appears to me that a given datamover only uses a single Windows process, even for multiple concurrent backups. That would seem to constrain it to a single core. Can someone confirm/deny? If it is, does it make sense to define multiple datamovers per proxy server in order to take advantage of multi-core machines? 3. Why do schedules with failed VM backups show successful? 02/28/2015 02:37:11 Total number of virtual machines failed: 4 02/28/2015 02:37:11 Total number of virtual machines processed: 375 02/28/2015 02:37:11 Scheduled event 'VE_INCR_N01_BCBST_DM02' completed successfully. Thanks, Steve Schaub Systems Engineer II, Backup/Recovery Blue Cross Blue Shield of Tennessee - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Is TSM for VE 7.1.1.1 pagefile aware? Is it contrained to a single process per datamover? What constitutes a successful backup?
1. Is VE pagefile aware? I.E. is it smart enough to know not to bother backing up changed blocks from within the pagefile.sys file? 2. It appears to me that a given datamover only uses a single Windows process, even for multiple concurrent backups. That would seem to constrain it to a single core. Can someone confirm/deny? If it is, does it make sense to define multiple datamovers per proxy server in order to take advantage of multi-core machines? 3. Why do schedules with failed VM backups show successful? 02/28/2015 02:37:11 Total number of virtual machines failed: 4 02/28/2015 02:37:11 Total number of virtual machines processed: 375 02/28/2015 02:37:11 Scheduled event 'VE_INCR_N01_BCBST_DM02' completed successfully. Thanks, Steve Schaub Systems Engineer II, Backup/Recovery Blue Cross Blue Shield of Tennessee - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: Is TSM for VE 7.1.1.1 pagefile aware? Is it contrained to a single process per datamover? What constitutes a successful backup?
Hello Steve, There's no mention of pagefile 'awareness' in the documentation, so it's safe to say that the backup will consist of all changed blocks, regardless of what's stored on them. As for threaded behavior, I've pinned all the cores on my datamover during heavy parallel backups using deduplication, so while it may only register as a single process in the Task Manager, it seems clear that TSM is acting like a multi-threaded application. As for your last point, I don't know why IBM changed the status codes for VM schedules from 'Failed' to 'Completed' but I suspect it has something to do with VMWare's abysmal ability to create quiesced snapshots on a consistent basis. We backup ~500 VMs on a daily basis and usually have 4-5 failures, all due to quiescing errors. I guess IBM got tired of customer complaints that their VM backup schedules 'always failed' and quietly changed the status code to make the product look a little better. __ Matthew McGeary Technical Specialist - Operations PotashCorp T: (306) 933-8921 www.potashcorp.com From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@VM.MARIST.EDU Date: 03/02/2015 11:24 AM Subject:[ADSM-L] Is TSM for VE 7.1.1.1 pagefile aware? Is it contrained to a single process per datamover? What constitutes a successful backup? Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 1. Is VE pagefile aware? I.E. is it smart enough to know not to bother backing up changed blocks from within the pagefile.sys file? 2. It appears to me that a given datamover only uses a single Windows process, even for multiple concurrent backups. That would seem to constrain it to a single core. Can someone confirm/deny? If it is, does it make sense to define multiple datamovers per proxy server in order to take advantage of multi-core machines? 3. Why do schedules with failed VM backups show successful? 02/28/2015 02:37:11 Total number of virtual machines failed: 4 02/28/2015 02:37:11 Total number of virtual machines processed: 375 02/28/2015 02:37:11 Scheduled event 'VE_INCR_N01_BCBST_DM02' completed successfully. Thanks, Steve Schaub Systems Engineer II, Backup/Recovery Blue Cross Blue Shield of Tennessee - Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Move data successful, but volume still has data.
TSM 5.5 on AIX. I'm freeing up some (primary) disk storage pool volumes out of mostly empty pools on old TSM servers, in order to free up the volume groups and raw logical volumes and LUNs. I've been setting the disk storage pool volumes to access=readonly and then using the move data command to empty them back into the same pool. Occasionally, once a move data has completed successfully, a particular volume will not be deletable via del vol as it still contains some data. (Running an audit vol shows that 7 files remain.) Cycles of successful move data don't clear the volume. (I've also tried these steps with the volume set to access=readw ) Waiting a while and trying the cycle again, sometimes does work, but not in this case. Any tips? Does anyone know a method or trick for getting the last objects to move? Thanks, [RC] U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. -
Re: Move data successful, but volume still has data.
Indeed, that happens too often with TSM 5. Do Audit Volume ... Fix=Yes. Richard Sims
Re: Move data successful, but volume still has data.
I found similar problems as well and investigation showed a part of file which was writen to other olmost full volume and tail of the file was written to the next volume. Move data for the first volume will clean this tail. Try to audit volume as well. Sometimes it helps. - Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?
Thanks Richard, I suspected as much - even within the same server looking at the same data in different storage pools (i.e. fully synchronised primary and copy stgpools) I see the same number of objects but a different logical space value reported. /DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: 21 April 2009 13:45 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences? David - The Admin Ref manual description of the Physical and Logical Space report element from Query OCCupancy is superficial, leading the customer to believe that the Logical value is just the amount of space occupied by client files. According to info I've seen, logical space also includes headers housing control information for each file, such as magic numbers, CRC info, segment numbering, server ID, etc. The size of the header info can vary as TSM evolves, and so may differ across TSM releases. The header size can be seen in the output of the SHow INVObject command for a given ObjectID. Richard Sims http://people.bu.edu/rbs No virus found in this incoming message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.12.0/2068 - Release Date: 19/04/2009 20:04 No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.12.0/2068 - Release Date: 19/04/2009 20:04
Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?
Hi Team, I’ve performed an EXPORT NODE operation from a source TSM server (Windows 5.4.3.2) to a target server (AIX 5.5.1.1) over TCP/IP with the TOSERVER option. All appears to have completed successfully, the processes on both TSM Servers report SUCCESS with no errors. However, being of a cautious nature (particularly with others’ data) I’m doing some additional verification, and it’s a comparison of the `Q OCC` output on the two servers that I want to double-check as there's something which has me a little concerned. On the source server (i.e. that from which I issued the EXPORT NODE) the relevant exported filespace looks like this: tsm: CENTSM02q occ CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT Node Name Type Filespace FSID StorageNumber of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) -- -- - -- - - - NODENAME Bkup FILESPACE 5 LTOCONTC 85,299 16,119.97 16,119.97 On the target server it looks like this: tsm: ARCTSM01q occ CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT ANR2017I Administrator DAVID.MCCLELLAND issued command: QUERY OCCUPANCY CENCONMGR02_CONT /ICM/RMDB/1/CSXMGMT Node Name Type Filespace FSID StorageNumber of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) -- -- - -- - - - NODENAME Bkup FILESPACE 2 CONT_DISK85,299 16,098.71 16,098.71 Apols if this doesn't come out clearly when converted to plain text, but in summary the NUMBER OF FILES reported is identical (85,299) between source and target, and the PHYSICAL SPACE OCCUPIED (MB) is not - which is down to empty space in aggregates on the source. However, what I want to double check is why the LOGICAL SPACE OCCUPIED (MB) isn't the same - I'd have expected that these would have identical. There's a 20MB difference between the source and target, with less on the target. The variables that I can immediately think of are different TSM Server code and platform, and the storage media (LTO2 on source, DISK on target). Any ideas? I'm certainly happy that the number of files adds up and that the EXPORT/IMPORT NODE commands completed apparently successfully, but I'd like to be able to explain the difference in LOGICAL SPACE OCCUPIED, or understand if this figure is indeed definitive or subject to rounding etc. Thanks Rgds, David Mc London, UK No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.12.0/2068 - Release Date: 19/04/2009 20:04
Re: Verifying EXPORT NODE is successful with Q OCC - LOGICAL SPACE OCCUPIED (MB) differences?
David - The Admin Ref manual description of the Physical and Logical Space report element from Query OCCupancy is superficial, leading the customer to believe that the Logical value is just the amount of space occupied by client files. According to info I've seen, logical space also includes headers housing control information for each file, such as magic numbers, CRC info, segment numbering, server ID, etc. The size of the header info can vary as TSM evolves, and so may differ across TSM releases. The header size can be seen in the output of the SHow INVObject command for a given ObjectID. Richard Sims http://people.bu.edu/rbs
Re: NDMP backup successful but incomplete
I'm not familiar with celerra, but on Netapp, TSM ignores the snapshot directories unless they are specifically mapped. Are you sure the data that is being reported by TSM:q fi and the nas command are not snapshots? Maybe there is something special about the data on vol0 that is excluding it? Also, run QUERY VIRTUALFSMAPPING and see if there is anything strange in there. Maybe /vol0 is being redirected to a subfolder Regards, Shawn Shawn Drew Internet [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 06/12/2008 05:42 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] NDMP backup successful but incomplete I've got an NDMP client (Celerra) with two file systems - /vol0, and /vol1. When I run the backup (fulls only), /vol1 gets a complete backup, but /vol0 backs up only a few kilobytes, and the process ends as Successful. To be more specific: 06/12/08 10:17:12 ANR2017I Administrator RNLEAF issued command: BACKUP NODE SVGMN14GLBSM07 /vol0 mode=full (SESSION: 36846) 06/12/08 10:17:14 ANR1063I Full backup of NAS node SVGMN14GLBSM07, file system /vol0, started as process 552 by administrator RNLEAF. (SESSION: 36846, PROCESS: 552) ... 06/12/08 10:17:37 ANR0988I Process 552 for BACKUP NAS (FULL) running in the BACKGROUND processed 43,482 bytes with a completion state of SUCCESS at 10:17:37. (SESSION: 36846, PROCESS: 552) and... 06/12/08 10:17:14 ANR2017I Administrator RNLEAF issued command: BACKUP NODE SVGMN14GLBSM07 /vol1 mode=full (SESSION: 36846, PROCESS: 552) 06/12/08 10:17:16 ANR1063I Full backup of NAS node SVGMN14GLBSM07, file system /vol1, started as process 553 by administrator RNLEAF. (SESSION: 36846, PROCESS: 553) ... 06/12/08 15:26:39 ANR0988I Process 553 for BACKUP NAS (FULL) running in the BACKGROUND processed 620,126,384,679 bytes with a completion state of SUCCESS at 15:26:39. (SESSION: 36846, PROCESS: 553) Now, the administrator of the Celerra can demonstrate that /vol0 has plenty of data in it: [EMAIL PROTECTED] nasadmin]$ nas_fs -size vol0 total = 1578910 avail = 900497 used = 678412 ( 42% ) (sizes in MB) ( blockcount = 3283714048 ) volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 )) [EMAIL PROTECTED] nasadmin]$ nas_fs -size vol1 total = 1578910 avail = 985584 used = 593326 ( 37% ) (sizes in MB) ( blockcount = 3283714048 ) volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 )) I see something similar when I look at the information TSM has about that file space: q filespace SVGMN14GLBSM07 /vol0 f=d Node Name: SVGMN14GLBSM07 Filespace Name: /vol0 Hexadecimal Filespace Name: FSID: 2 Platform: DartOS Filespace Type: uxfs Is Filespace Unicode?: No Capacity (MB): 1,578,910.2 Pct Util: 43.0 Last Backup Start Date/Time: 06/12/08 10:17:13 Days Since Last Backup Started: 1 Last Backup Completion Date/Time: 06/12/08 10:17:36 Days Since Last Backup Completed: 1 Last Full NAS Image Backup Completion Date/Time: 06/12/08 10:17:36 Days Since Last Full NAS Image Backup Completed: 1 I don't know what kind of settings he might have on his end that might affect how TSM accesses, or fails to access, a file system on the Celerra. As you can see, the commands issued to invoke the backups are identical. No client option sets are applied to the node. TSM server is ver 5.3.5.2 on AIX 5.3; backing up to a VTL emulating a 3584 with LTO drives. If the version of DART on the Celerra matters, I'll dig it up. Does anyone have a theory as to why the /vol0 backup isn't backing up the data that's there, while the backups of /vol1 are working fine?, Thanks in advance! Robben Leaf - This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
NDMP backup successful but incomplete
I've got an NDMP client (Celerra) with two file systems - /vol0, and /vol1. When I run the backup (fulls only), /vol1 gets a complete backup, but /vol0 backs up only a few kilobytes, and the process ends as Successful. To be more specific: 06/12/08 10:17:12 ANR2017I Administrator RNLEAF issued command: BACKUP NODE SVGMN14GLBSM07 /vol0 mode=full (SESSION: 36846) 06/12/08 10:17:14 ANR1063I Full backup of NAS node SVGMN14GLBSM07, file system /vol0, started as process 552 by administrator RNLEAF. (SESSION: 36846, PROCESS: 552) ... 06/12/08 10:17:37 ANR0988I Process 552 for BACKUP NAS (FULL) running in the BACKGROUND processed 43,482 bytes with a completion state of SUCCESS at 10:17:37. (SESSION: 36846, PROCESS: 552) and... 06/12/08 10:17:14 ANR2017I Administrator RNLEAF issued command: BACKUP NODE SVGMN14GLBSM07 /vol1 mode=full (SESSION: 36846, PROCESS: 552) 06/12/08 10:17:16 ANR1063I Full backup of NAS node SVGMN14GLBSM07, file system /vol1, started as process 553 by administrator RNLEAF. (SESSION: 36846, PROCESS: 553) ... 06/12/08 15:26:39 ANR0988I Process 553 for BACKUP NAS (FULL) running in the BACKGROUND processed 620,126,384,679 bytes with a completion state of SUCCESS at 15:26:39. (SESSION: 36846, PROCESS: 553) Now, the administrator of the Celerra can demonstrate that /vol0 has plenty of data in it: [EMAIL PROTECTED] nasadmin]$ nas_fs -size vol0 total = 1578910 avail = 900497 used = 678412 ( 42% ) (sizes in MB) ( blockcount = 3283714048 ) volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 )) [EMAIL PROTECTED] nasadmin]$ nas_fs -size vol1 total = 1578910 avail = 985584 used = 593326 ( 37% ) (sizes in MB) ( blockcount = 3283714048 ) volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 )) I see something similar when I look at the information TSM has about that file space: q filespace SVGMN14GLBSM07 /vol0 f=d Node Name: SVGMN14GLBSM07 Filespace Name: /vol0 Hexadecimal Filespace Name: FSID: 2 Platform: DartOS Filespace Type: uxfs Is Filespace Unicode?: No Capacity (MB): 1,578,910.2 Pct Util: 43.0 Last Backup Start Date/Time: 06/12/08 10:17:13 Days Since Last Backup Started: 1 Last Backup Completion Date/Time: 06/12/08 10:17:36 Days Since Last Backup Completed: 1 Last Full NAS Image Backup Completion Date/Time: 06/12/08 10:17:36 Days Since Last Full NAS Image Backup Completed: 1 I don't know what kind of settings he might have on his end that might affect how TSM accesses, or fails to access, a file system on the Celerra. As you can see, the commands issued to invoke the backups are identical. No client option sets are applied to the node. TSM server is ver 5.3.5.2 on AIX 5.3; backing up to a VTL emulating a 3584 with LTO drives. If the version of DART on the Celerra matters, I'll dig it up. Does anyone have a theory as to why the /vol0 backup isn't backing up the data that's there, while the backups of /vol1 are working fine?, Thanks in advance! Robben Leaf U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. -
Re: write failed using tsm but write successful vi tar command
I managed to label the tape. I managed to checkin the volume. While the
migration processes start, the volume is mounted in the drive. I can see
from console that the volume is mounted in the drive. The problem is while
writing.
Anyway, thanks for your idea.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
CAYE PIERRE
Sent: Friday, December 21, 2007 11:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar
command
Had you labeled the tapes ?
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De
la part de hshahizul
Envoyé : vendredi 21 décembre 2007 16:26
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] write failed using tsm but write
successful vi tar command
No, but I will try to do that. Anyway, no harm trying.
Thanks for the idea
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
On Behalf Of Helder Garcia
Sent: Friday, December 21, 2007 3:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] write failed using tsm but write
successful vi tar command
hi, did you tried using mt0 instead of rmt0?
On Dec 17, 2007 1:27 PM, hshahizul [EMAIL PROTECTED] wrote:
Some one pleases help. I'm stuck more then a week for this error.
TSM Server 5.4.0.0
AIX 5.3
Tape Library TS3100 (single drive)
Atape Driver 9.7.5.0
dev type : LTO
devc format : ultrium3c
Drive Ultrium3
# lsdev -Cc tape
rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive
smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer
# lscfg -vl rmt0
rmt0 U787B.001.DNWG37G-P1-C5-T1-L4-L0 IBM
3580 Ultrium Tape
Drive
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
# lscfg -vl smc0
smc0 U787B.001.DNWG37G-P1-C5-T1-L4-L1 IBM 3573 Tape
Medium Changer
ManufacturerIBM
Machine Type and Model..3573-TL
Serial Number...00L2U78C2421_LL0
Device Specific.(FW)3.70
I have tried to migrate from diskpool to tapepool but failed with
error
ANR8311E An I/O error occurred while accessing drive
DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5.
I tried to write via tar command [ tar -cvf /dev/rmt0 /tmp ]. It
successfull write to tape
I tried to used tapeutil facility (halt TSM Server)
Without lto3 tape inside tape drive : option 37 (write)
.
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 46: Device not ready
Residual count: 4125543
Error Sense Data, Length 96
With lto3 tape mount inside tape drive : option 37 (write)
..
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 5: I/O error
Residual count: 4125543
I have tried to install TSM 5.5 and Atape 10.3.7.0 but the
result is
still the same.
I also tried to update devclass class=drive , but still the
same output.
The question here, why via tar command , tape can be written but
cannot via TSM
Tq.
Additional Info
One more things, while the process of migration take place
AIX error
report produce as below:
LABEL: TAPE_ERR4
IDENTIFIER: 5537AC5F
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2782
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:PERM
Resource Name: rmt0
Resource Class: tape
Resource Type: 3580
Location:U787B.001.DNWG37G-P1-C5-T1-L4-L0
VPD:
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
Description
TAPE DRIVE FAILURE
Probable Causes
ADAPTER
TAPE DRIVE
Failure Causes
ADAPTER
TAPE DRIVE
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
SENSE DATA
0604 0A00 0400 0200 0200
--
-
LABEL: SCSI_ERR10
Re: write failed using tsm but write successful vi tar command
No, but I will try to do that. Anyway, no harm trying.
Thanks for the idea
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Helder Garcia
Sent: Friday, December 21, 2007 3:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar
command
hi, did you tried using mt0 instead of rmt0?
On Dec 17, 2007 1:27 PM, hshahizul [EMAIL PROTECTED] wrote:
Some one pleases help. I'm stuck more then a week for this error.
TSM Server 5.4.0.0
AIX 5.3
Tape Library TS3100 (single drive)
Atape Driver 9.7.5.0
dev type : LTO
devc format : ultrium3c
Drive Ultrium3
# lsdev -Cc tape
rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive
smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer
# lscfg -vl rmt0
rmt0 U787B.001.DNWG37G-P1-C5-T1-L4-L0 IBM 3580 Ultrium Tape
Drive
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
# lscfg -vl smc0
smc0 U787B.001.DNWG37G-P1-C5-T1-L4-L1 IBM 3573 Tape Medium Changer
ManufacturerIBM
Machine Type and Model..3573-TL
Serial Number...00L2U78C2421_LL0
Device Specific.(FW)3.70
I have tried to migrate from diskpool to tapepool but failed with error
ANR8311E An I/O error occurred while accessing drive
DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5.
I tried to write via tar command [ tar -cvf /dev/rmt0 /tmp ]. It
successfull
write to tape
I tried to used tapeutil facility (halt TSM Server)
Without lto3 tape inside tape drive : option 37 (write)
.
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 46: Device not ready
Residual count: 4125543
Error Sense Data, Length 96
With lto3 tape mount inside tape drive : option 37 (write)
..
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 5: I/O error
Residual count: 4125543
I have tried to install TSM 5.5 and Atape 10.3.7.0 but the result is
still
the same.
I also tried to update devclass class=drive , but still the same output.
The question here, why via tar command , tape can be written but cannot
via
TSM
Tq.
Additional Info
One more things, while the process of migration take place AIX error
report
produce as below:
LABEL: TAPE_ERR4
IDENTIFIER: 5537AC5F
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2782
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:PERM
Resource Name: rmt0
Resource Class: tape
Resource Type: 3580
Location:U787B.001.DNWG37G-P1-C5-T1-L4-L0
VPD:
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
Description
TAPE DRIVE FAILURE
Probable Causes
ADAPTER
TAPE DRIVE
Failure Causes
ADAPTER
TAPE DRIVE
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
SENSE DATA
0604 0A00 0400 0200 0200
---
LABEL: SCSI_ERR10
IDENTIFIER: 0BA49C99
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2781
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:TEMP
Resource Name: scsi2
Resource Class: driver
Resource Type: sisscsi
Location:U787B.001.DNWG37G-P1-C5-T1
VPD:
ROM Level.(alterable)...05080092
Product Specific.(CC)...5702
Description
SCSI BUS ERROR
Probable Causes
CABLE
CABLE TERMINATOR
DEVICE
ADAPTER
Failure Causes
CABLE LOOSE OR DEFECTIVE
DEVICE
ADAPTER
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
CHECK CABLE AND ITS CONNECTIONS
Detail Data
SENSE DATA
1900 00F0 0629 0301 0508 0092 00FF 5702
E210 0080 FF00 0310 0010 0D5A 89F9 03E8 0629
1025 3380 28E2 0300 0003 8300 8000 8000
.
---
LABEL
Re: write failed using tsm but write successful vi tar command
Errno 5 mean I/O Error for AIX So try : rmdev -l rmt0 mkdev -l rmt0 Then retry a migration -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de hshahizul Envoyé : vendredi 21 décembre 2007 16:36 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] write failed using tsm but write successful vi tar command I managed to label the tape. I managed to checkin the volume. While the migration processes start, the volume is mounted in the drive. I can see from console that the volume is mounted in the drive. The problem is while writing. Anyway, thanks for your idea. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of CAYE PIERRE Sent: Friday, December 21, 2007 11:32 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar command Had you labeled the tapes ? -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de hshahizul Envoyé : vendredi 21 décembre 2007 16:26 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] write failed using tsm but write successful vi tar command No, but I will try to do that. Anyway, no harm trying. Thanks for the idea -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Helder Garcia Sent: Friday, December 21, 2007 3:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar command hi, did you tried using mt0 instead of rmt0? On Dec 17, 2007 1:27 PM, hshahizul [EMAIL PROTECTED] wrote: Some one pleases help. I'm stuck more then a week for this error. TSM Server 5.4.0.0 AIX 5.3 Tape Library TS3100 (single drive) Atape Driver 9.7.5.0 dev type : LTO devc format : ultrium3c Drive Ultrium3 # lsdev -Cc tape rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer # lscfg -vl rmt0 rmt0 U787B.001.DNWG37G-P1-C5-T1-L4-L0 IBM 3580 Ultrium Tape Drive ManufacturerIBM Machine Type and Model..ULT3580-TD3 Serial Number...1210283884 Device Specific.(FW)73P5 # lscfg -vl smc0 smc0 U787B.001.DNWG37G-P1-C5-T1-L4-L1 IBM 3573 Tape Medium Changer ManufacturerIBM Machine Type and Model..3573-TL Serial Number...00L2U78C2421_LL0 Device Specific.(FW)3.70 I have tried to migrate from diskpool to tapepool but failed with error ANR8311E An I/O error occurred while accessing drive DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5. I tried to write via tar command [ tar -cvf /dev/rmt0 /tmp ]. It successfull write to tape I tried to used tapeutil facility (halt TSM Server) Without lto3 tape inside tape drive : option 37 (write) . Writing file to tape... Write terminated, 0 total bytes written... Operation failed with errno 46: Device not ready Residual count: 4125543 Error Sense Data, Length 96 With lto3 tape mount inside tape drive : option 37 (write) .. Writing file to tape... Write terminated, 0 total bytes written... Operation failed with errno 5: I/O error Residual count: 4125543 I have tried to install TSM 5.5 and Atape 10.3.7.0 but the result is still the same. I also tried to update devclass class=drive , but still the same output. The question here, why via tar command , tape can be written but cannot via TSM Tq. Additional Info One more things, while the process of migration take place AIX error report produce as below: LABEL: TAPE_ERR4 IDENTIFIER: 5537AC5F Date/Time: Mon Dec 17 22:06:25 WAUST 2007 Sequence Number: 2782 Machine Id: 000535C7D600 Node Id: db3 Class: H Type:PERM Resource Name: rmt0 Resource Class: tape Resource Type: 3580 Location:U787B.001.DNWG37G-P1-C5-T1-L4-L0 VPD: ManufacturerIBM Machine Type and Model..ULT3580-TD3 Serial Number...1210283884 Device Specific.(FW)73P5 Description TAPE DRIVE FAILURE Probable Causes ADAPTER TAPE DRIVE Failure Causes ADAPTER TAPE DRIVE Recommended Actions PERFORM
Re: write failed using tsm but write successful vi tar command
Had you labeled the tapes ?
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De
la part de hshahizul
Envoyé : vendredi 21 décembre 2007 16:26
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] write failed using tsm but write
successful vi tar command
No, but I will try to do that. Anyway, no harm trying.
Thanks for the idea
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
On Behalf Of Helder Garcia
Sent: Friday, December 21, 2007 3:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] write failed using tsm but write
successful vi tar command
hi, did you tried using mt0 instead of rmt0?
On Dec 17, 2007 1:27 PM, hshahizul [EMAIL PROTECTED] wrote:
Some one pleases help. I'm stuck more then a week for this error.
TSM Server 5.4.0.0
AIX 5.3
Tape Library TS3100 (single drive)
Atape Driver 9.7.5.0
dev type : LTO
devc format : ultrium3c
Drive Ultrium3
# lsdev -Cc tape
rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive
smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer
# lscfg -vl rmt0
rmt0 U787B.001.DNWG37G-P1-C5-T1-L4-L0 IBM
3580 Ultrium Tape
Drive
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
# lscfg -vl smc0
smc0 U787B.001.DNWG37G-P1-C5-T1-L4-L1 IBM 3573 Tape
Medium Changer
ManufacturerIBM
Machine Type and Model..3573-TL
Serial Number...00L2U78C2421_LL0
Device Specific.(FW)3.70
I have tried to migrate from diskpool to tapepool but failed with
error
ANR8311E An I/O error occurred while accessing drive
DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5.
I tried to write via tar command [ tar -cvf /dev/rmt0 /tmp ]. It
successfull write to tape
I tried to used tapeutil facility (halt TSM Server)
Without lto3 tape inside tape drive : option 37 (write)
.
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 46: Device not ready
Residual count: 4125543
Error Sense Data, Length 96
With lto3 tape mount inside tape drive : option 37 (write)
..
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 5: I/O error
Residual count: 4125543
I have tried to install TSM 5.5 and Atape 10.3.7.0 but the
result is
still the same.
I also tried to update devclass class=drive , but still the
same output.
The question here, why via tar command , tape can be written but
cannot via TSM
Tq.
Additional Info
One more things, while the process of migration take place
AIX error
report produce as below:
LABEL: TAPE_ERR4
IDENTIFIER: 5537AC5F
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2782
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:PERM
Resource Name: rmt0
Resource Class: tape
Resource Type: 3580
Location:U787B.001.DNWG37G-P1-C5-T1-L4-L0
VPD:
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
Description
TAPE DRIVE FAILURE
Probable Causes
ADAPTER
TAPE DRIVE
Failure Causes
ADAPTER
TAPE DRIVE
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
SENSE DATA
0604 0A00 0400 0200 0200
--
-
LABEL: SCSI_ERR10
IDENTIFIER: 0BA49C99
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2781
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:TEMP
Resource Name: scsi2
Resource Class: driver
Resource Type: sisscsi
Location:U787B.001.DNWG37G-P1-C5-T1
VPD:
ROM Level.(alterable)...05080092
Product Specific.(CC)...5702
Description
SCSI BUS ERROR
Probable Causes
CABLE
Re: write failed using tsm but write successful vi tar command
Thanks Mr. Caye Pierre. I will try this again. I have done it as well. I'm suspecting error come from SCSI cable or terminator. (wild guest while looking at error report). I will post the result next week since I will be on leave for a week. My local time (Malaysia) is midnight. Mercy. Zul. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of CAYE PIERRE Sent: Friday, December 21, 2007 11:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar command Errno 5 mean I/O Error for AIX So try : rmdev -l rmt0 mkdev -l rmt0 Then retry a migration -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de hshahizul Envoyé : vendredi 21 décembre 2007 16:36 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] write failed using tsm but write successful vi tar command I managed to label the tape. I managed to checkin the volume. While the migration processes start, the volume is mounted in the drive. I can see from console that the volume is mounted in the drive. The problem is while writing. Anyway, thanks for your idea. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of CAYE PIERRE Sent: Friday, December 21, 2007 11:32 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar command Had you labeled the tapes ? -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de hshahizul Envoyé : vendredi 21 décembre 2007 16:26 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] write failed using tsm but write successful vi tar command No, but I will try to do that. Anyway, no harm trying. Thanks for the idea -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Helder Garcia Sent: Friday, December 21, 2007 3:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] write failed using tsm but write successful vi tar command hi, did you tried using mt0 instead of rmt0? On Dec 17, 2007 1:27 PM, hshahizul [EMAIL PROTECTED] wrote: Some one pleases help. I'm stuck more then a week for this error. TSM Server 5.4.0.0 AIX 5.3 Tape Library TS3100 (single drive) Atape Driver 9.7.5.0 dev type : LTO devc format : ultrium3c Drive Ultrium3 # lsdev -Cc tape rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer # lscfg -vl rmt0 rmt0 U787B.001.DNWG37G-P1-C5-T1-L4-L0 IBM 3580 Ultrium Tape Drive ManufacturerIBM Machine Type and Model..ULT3580-TD3 Serial Number...1210283884 Device Specific.(FW)73P5 # lscfg -vl smc0 smc0 U787B.001.DNWG37G-P1-C5-T1-L4-L1 IBM 3573 Tape Medium Changer ManufacturerIBM Machine Type and Model..3573-TL Serial Number...00L2U78C2421_LL0 Device Specific.(FW)3.70 I have tried to migrate from diskpool to tapepool but failed with error ANR8311E An I/O error occurred while accessing drive DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5. I tried to write via tar command [ tar -cvf /dev/rmt0 /tmp ]. It successfull write to tape I tried to used tapeutil facility (halt TSM Server) Without lto3 tape inside tape drive : option 37 (write) . Writing file to tape... Write terminated, 0 total bytes written... Operation failed with errno 46: Device not ready Residual count: 4125543 Error Sense Data, Length 96 With lto3 tape mount inside tape drive : option 37 (write) .. Writing file to tape... Write terminated, 0 total bytes written... Operation failed with errno 5: I/O error Residual count: 4125543 I have tried to install TSM 5.5 and Atape 10.3.7.0 but the result is still the same. I also tried to update devclass class=drive , but still the same output. The question here, why via tar command , tape can be written but cannot via TSM Tq. Additional Info One more things, while the process of migration take place AIX error report produce as below: LABEL: TAPE_ERR4 IDENTIFIER: 5537AC5F Date/Time: Mon Dec 17 22:06:25 WAUST 2007 Sequence Number: 2782 Machine Id: 000535C7D600 Node Id: db3 Class: H Type:PERM Resource Name: rmt0
Re: write failed using tsm but write successful vi tar command
hi, did you tried using mt0 instead of rmt0?
On Dec 17, 2007 1:27 PM, hshahizul [EMAIL PROTECTED] wrote:
Some one pleases help. I'm stuck more then a week for this error.
TSM Server 5.4.0.0
AIX 5.3
Tape Library TS3100 (single drive)
Atape Driver 9.7.5.0
dev type : LTO
devc format : ultrium3c
Drive Ultrium3
# lsdev -Cc tape
rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive
smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer
# lscfg -vl rmt0
rmt0 U787B.001.DNWG37G-P1-C5-T1-L4-L0 IBM 3580 Ultrium Tape
Drive
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
# lscfg -vl smc0
smc0 U787B.001.DNWG37G-P1-C5-T1-L4-L1 IBM 3573 Tape Medium Changer
ManufacturerIBM
Machine Type and Model..3573-TL
Serial Number...00L2U78C2421_LL0
Device Specific.(FW)3.70
I have tried to migrate from diskpool to tapepool but failed with error
ANR8311E An I/O error occurred while accessing drive
DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5.
I tried to write via tar command [ tar -cvf /dev/rmt0 /tmp ]. It
successfull
write to tape
I tried to used tapeutil facility (halt TSM Server)
Without lto3 tape inside tape drive : option 37 (write)
.
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 46: Device not ready
Residual count: 4125543
Error Sense Data, Length 96
With lto3 tape mount inside tape drive : option 37 (write)
..
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 5: I/O error
Residual count: 4125543
I have tried to install TSM 5.5 and Atape 10.3.7.0 but the result is
still
the same.
I also tried to update devclass class=drive , but still the same output.
The question here, why via tar command , tape can be written but cannot
via
TSM
Tq.
Additional Info
One more things, while the process of migration take place AIX error
report
produce as below:
LABEL: TAPE_ERR4
IDENTIFIER: 5537AC5F
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2782
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:PERM
Resource Name: rmt0
Resource Class: tape
Resource Type: 3580
Location:U787B.001.DNWG37G-P1-C5-T1-L4-L0
VPD:
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
Description
TAPE DRIVE FAILURE
Probable Causes
ADAPTER
TAPE DRIVE
Failure Causes
ADAPTER
TAPE DRIVE
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
SENSE DATA
0604 0A00 0400 0200 0200
---
LABEL: SCSI_ERR10
IDENTIFIER: 0BA49C99
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2781
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:TEMP
Resource Name: scsi2
Resource Class: driver
Resource Type: sisscsi
Location:U787B.001.DNWG37G-P1-C5-T1
VPD:
ROM Level.(alterable)...05080092
Product Specific.(CC)...5702
Description
SCSI BUS ERROR
Probable Causes
CABLE
CABLE TERMINATOR
DEVICE
ADAPTER
Failure Causes
CABLE LOOSE OR DEFECTIVE
DEVICE
ADAPTER
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
CHECK CABLE AND ITS CONNECTIONS
Detail Data
SENSE DATA
1900 00F0 0629 0301 0508 0092 00FF 5702
E210 0080 FF00 0310 0010 0D5A 89F9 03E8 0629
1025 3380 28E2 0300 0003 8300 8000 8000
.
---
LABEL: TAPE_ERR4
IDENTIFIER: 5537AC5F
Date/Time: Mon Dec 17 22:05:42 WAUST 2007
Sequence Number: 2780
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:PERM
Resource Name: rmt0
Resource Class: tape
Resource Type: 3580
Location:
write failed using tsm but write successful vi tar command
Some one pleases help. I'm stuck more then a week for this error.
TSM Server 5.4.0.0
AIX 5.3
Tape Library TS3100 (single drive)
Atape Driver 9.7.5.0
dev type : LTO
devc format : ultrium3c
Drive Ultrium3
# lsdev -Cc tape
rmt0 Available 07-08-00-4,0 IBM 3580 Ultrium Tape Drive
smc0 Available 07-08-00-4,1 IBM 3573 Tape Medium Changer
# lscfg -vl rmt0
rmt0 U787B.001.DNWG37G-P1-C5-T1-L4-L0 IBM 3580 Ultrium Tape
Drive
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
# lscfg -vl smc0
smc0 U787B.001.DNWG37G-P1-C5-T1-L4-L1 IBM 3573 Tape Medium Changer
ManufacturerIBM
Machine Type and Model..3573-TL
Serial Number...00L2U78C2421_LL0
Device Specific.(FW)3.70
I have tried to migrate from diskpool to tapepool but failed with error
ANR8311E An I/O error occurred while accessing drive
DRIVE1 (/dev/rmt0) for WRITE operation, errno = 5.
I tried to write via tar command [ tar -cvf /dev/rmt0 /tmp ]. It successfull
write to tape
I tried to used tapeutil facility (halt TSM Server)
Without lto3 tape inside tape drive : option 37 (write)
.
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 46: Device not ready
Residual count: 4125543
Error Sense Data, Length 96
With lto3 tape mount inside tape drive : option 37 (write)
..
Writing file to tape...
Write terminated, 0 total bytes written...
Operation failed with errno 5: I/O error
Residual count: 4125543
I have tried to install TSM 5.5 and Atape 10.3.7.0 but the result is still
the same.
I also tried to update devclass class=drive , but still the same output.
The question here, why via tar command , tape can be written but cannot via
TSM
Tq.
Additional Info
One more things, while the process of migration take place AIX error report
produce as below:
LABEL: TAPE_ERR4
IDENTIFIER: 5537AC5F
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2782
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:PERM
Resource Name: rmt0
Resource Class: tape
Resource Type: 3580
Location:U787B.001.DNWG37G-P1-C5-T1-L4-L0
VPD:
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
Description
TAPE DRIVE FAILURE
Probable Causes
ADAPTER
TAPE DRIVE
Failure Causes
ADAPTER
TAPE DRIVE
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
SENSE DATA
0604 0A00 0400 0200 0200
---
LABEL: SCSI_ERR10
IDENTIFIER: 0BA49C99
Date/Time: Mon Dec 17 22:06:25 WAUST 2007
Sequence Number: 2781
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:TEMP
Resource Name: scsi2
Resource Class: driver
Resource Type: sisscsi
Location:U787B.001.DNWG37G-P1-C5-T1
VPD:
ROM Level.(alterable)...05080092
Product Specific.(CC)...5702
Description
SCSI BUS ERROR
Probable Causes
CABLE
CABLE TERMINATOR
DEVICE
ADAPTER
Failure Causes
CABLE LOOSE OR DEFECTIVE
DEVICE
ADAPTER
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
CHECK CABLE AND ITS CONNECTIONS
Detail Data
SENSE DATA
1900 00F0 0629 0301 0508 0092 00FF 5702
E210 0080 FF00 0310 0010 0D5A 89F9 03E8 0629
1025 3380 28E2 0300 0003 8300 8000 8000
.
---
LABEL: TAPE_ERR4
IDENTIFIER: 5537AC5F
Date/Time: Mon Dec 17 22:05:42 WAUST 2007
Sequence Number: 2780
Machine Id: 000535C7D600
Node Id: db3
Class: H
Type:PERM
Resource Name: rmt0
Resource Class: tape
Resource Type: 3580
Location:U787B.001.DNWG37G-P1-C5-T1-L4-L0
VPD:
ManufacturerIBM
Machine Type and Model..ULT3580-TD3
Serial Number...1210283884
Device Specific.(FW)73P5
Description
TAPE DRIVE FAILURE
Probable
ALst successful backup status
Hi All, Is there any command to find out the last successful backup for a node in the past 20 days? Regards, Srinath G This e-mail has been scanned for viruses by the Cable Wireless e-mail security system - powered by MessageLabs. For more information on a proactive managed e-mail security service, visit http://www.cw.com/uk/emailprotection/ The information contained in this e-mail is confidential and may also be subject to legal privilege. It is intended only for the recipient(s) named above. If you are not named above as a recipient, you must not read, copy, disclose, forward or otherwise use the information contained in this email. If you have received this e-mail in error, please notify the sender (whose contact details are above) immediately by reply e-mail and delete the message and any attachments without retaining any copies. Cable and Wireless plc Registered in England and Wales.Company Number 238525 Registered office: 7th Floor, The Point, 37 North Wharf Road, London W2 1LA
Re: ALst successful backup status
On Feb 22, 2007, at 6:50 AM, Gopinathan, Srinath wrote: Hi All, Is there any command to find out the last successful backup for a node in the past 20 days? Query EVent, and Query FIlespace ... Format=Detailed.
Re: ALst successful backup status
Hi, I would like to find only the date o the successful backup. The other details of misses/failed are not interested. Thanks and Regards Srinath G IT Analyst Cable and Wireless Enterprise Support Services Comnet : Nil email:[EMAIL PROTECTED] Ph:91-988 667 9265 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 22 February 2007 12:01 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ALst successful backup status On Feb 22, 2007, at 6:50 AM, Gopinathan, Srinath wrote: Hi All, Is there any command to find out the last successful backup for a node in the past 20 days? Query EVent, and Query FIlespace ... Format=Detailed. This e-mail has been scanned for viruses by the Cable Wireless e-mail security system - powered by MessageLabs. For more information on a proactive managed e-mail security service, visit http://www.cw.com/uk/emailprotection/ The information contained in this e-mail is confidential and may also be subject to legal privilege. It is intended only for the recipient(s) named above. If you are not named above as a recipient, you must not read, copy, disclose, forward or otherwise use the information contained in this email. If you have received this e-mail in error, please notify the sender (whose contact details are above) immediately by reply e-mail and delete the message and any attachments without retaining any copies. Cable and Wireless plc Registered in England and Wales.Company Number 238525 Registered office: 7th Floor, The Point, 37 North Wharf Road, London W2 1LA
Re: ALst successful backup status
On Feb 22, 2007, at 7:06 AM, Gopinathan, Srinath wrote: Hi, I would like to find only the date o the successful backup. The other details of misses/failed are not interested. The commands that I cited provide the information you seek: if uninterested in other information reported, you can ignore it, or you may instead employ Select commands on the EVENTS and FILESPACES tables to go after individual data elements. You can also perform a Select on the SUMMARY table, to go after ACTIVITY=BACKUP and SUCCESSFUL='YES' - but I usually don't recommend the SUMMARY table because of its historic problems. Richard Sims
select command for Successful / Failed backups
Hi, 1) Is there any command to find the list of all failed backups in a server? 2) Is there any command to find the list of all successful backups in a server? Regards, Srinath G This e-mail has been scanned for viruses by the Cable Wireless e-mail security system - powered by MessageLabs. For more information on a proactive managed e-mail security service, visit http://www.cw.com/uk/emailprotection/ The information contained in this e-mail is confidential and may also be subject to legal privilege. It is intended only for the recipient(s) named above. If you are not named above as a recipient, you must not read, copy, disclose, forward or otherwise use the information contained in this email. If you have received this e-mail in error, please notify the sender (whose contact details are above) immediately by reply e-mail and delete the message and any attachments without retaining any copies.
Re: select command for Successful / Failed backups
Q event -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gopinathan, Srinath Sent: woensdag 10 januari 2007 6:25 To: ADSM-L@VM.MARIST.EDU Subject: select command for Successful / Failed backups Hi, 1) Is there any command to find the list of all failed backups in a server? 2) Is there any command to find the list of all successful backups in a server? Regards, Srinath G This e-mail has been scanned for viruses by the Cable Wireless e-mail security system - powered by MessageLabs. For more information on a proactive managed e-mail security service, visit http://www.cw.com/uk/emailprotection/ The information contained in this e-mail is confidential and may also be subject to legal privilege. It is intended only for the recipient(s) named above. If you are not named above as a recipient, you must not read, copy, disclose, forward or otherwise use the information contained in this email. If you have received this e-mail in error, please notify the sender (whose contact details are above) immediately by reply e-mail and delete the message and any attachments without retaining any copies. ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t
Re: select command for Successful / Failed backups
On Jan 10, 2007, at 7:50 AM, Bos, Karel wrote: Q event Amen. This TSM tracking of Backup event success is one of the great benefits of using TSM client scheduling, as opposed to having an operating system scheduling subsystem perform backups. Centralized reporting and control. Richard Sims
Re: select command for Successful / Failed backups
- Original Message - From: Richard Sims [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Wednesday, January 10, 2007 2:20 PM Subject: Re: select command for Successful / Failed backups On Jan 10, 2007, at 7:50 AM, Bos, Karel wrote: Q event Amen. This TSM tracking of Backup event success is one of the great benefits of using TSM client scheduling, as opposed to having an operating system scheduling subsystem perform backups. Centralized reporting and control. Richard Sims absolutely agree, even my SOX reports are generated with q event :-) goran
Re: select command for Successful / Failed backups
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gopinathan, Srinath 1) Is there any command to find the list of all failed backups in a server? 2) Is there any command to find the list of all successful backups in a server? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Q event Well, let's narrow that down some: Q EVENT * * EXCEPT=YES will show only the failed and missed backups Q EVENT * * will show all backups, successful, failed, or missed. -- Mark Stapleton ([EMAIL PROTECTED]) Senior consultant
Re: select command for Successful / Failed backups
Yes, but only for today...since midnight last night until midnight today. Most backup windows span midnight..starting early evening and running through the morning. Use the BEGIND=,BEGINT=, ENDD= and ENDT= to get the range you need. Q EV * * BEGINT=-24 ENDD=+0 ENDT=NOW EX=YES Will show the missed/failed schedules for the last 24-hours. Bill Boyer -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Wednesday, January 10, 2007 11:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: select command for Successful / Failed backups From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gopinathan, Srinath 1) Is there any command to find the list of all failed backups in a server? 2) Is there any command to find the list of all successful backups in a server? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Q event Well, let's narrow that down some: Q EVENT * * EXCEPT=YES will show only the failed and missed backups Q EVENT * * will show all backups, successful, failed, or missed. -- Mark Stapleton ([EMAIL PROTECTED]) Senior consultant
Re: select command for Successful / Failed backups
Here's a nice select command to see more detailed information . So I don't take all the credit, this select was posted while back one time or other. You can play around with date # to increase or decrease # of days of report. select entity as node_name, date(start_time) as date, cast(activity as varchar(10)) as activity, - time(start_time) as start,time(end_time) as end, - cast(substr(cast(end_time-start_time as char(20)),3,8) as char(8)) as Length,- cast(bytes/1024/1024/1024 as decimal(6,2)) as - Gigabytes,cast(affected as decimal(7,0)) as files, successful from summary where - start_time=current_timestamp - 1 day and activity='BACKUP' - order by successful, node_name I dont' think q event is a select statement. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/10/2007 12:25:10 AM: Hi, 1) Is there any command to find the list of all failed backups in a server? 2) Is there any command to find the list of all successful backups in a server? Regards, Srinath G This e-mail has been scanned for viruses by the Cable Wireless e- mail security system - powered by MessageLabs. For more information on a proactive managed e-mail security service, visit http://www. cw.com/uk/emailprotection/ The information contained in this e-mail is confidential and may also be subject to legal privilege. It is intended only for the recipient(s) named above. If you are not named above as a recipient, you must not read, copy, disclose, forward or otherwise use the information contained in this email. If you have received this e- mail in error, please notify the sender (whose contact details are above) immediately by reply e-mail and delete the message and any attachments without retaining any copies.
Restores showing as successful but are not.
Recently we had a drive on one of our servers accidentally deleted, and so a TSM restore process was started to recover the information that was lost. The restore was thought to be a success, but as days went by, more and more users were reporting that files were missing. I queried the summery tables for the restore sessions of that particular server and noticed that even though it says it was successful, it did not finish because for whatever reason the session was lost (network outage, etc). We did not think to look and see if there was a restartable restore at the time, because the restore was reported as being successful. When we opened a ticket IBM support, this is what we got: If the restore process stops because of a power outage or network failure, the server records the point at which this occurred. This record is known to the client as a restartable restore. -IBM TSM My question is how does the client inform you that there is a restartable restore that needs to be done, and why in the database, is it showing that the restore session was successful, when in fact this is false. Is there something that we missed? Any help in this regards would be greatly appreciated. Mel Dennis
Re: Restores showing as successful but are not.
For client operations, don't use that SUMMARY table field to assess status. That field comes from a related account log field, and has no bearing on the real outcome of the operation. If the operation was initiated manually, then monitoring the client itself should give you status. If the operation was scheduled via the scheduler, then QUERY EVENT with F=D will show you the results. I would not expect a completed status with RC 0 in the situation you describe. See the client manual chapter on Automating tasks for further info about the client return codes for the command line and scheduled events. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2006-03-07 14:24:08: Recently we had a drive on one of our servers accidentally deleted, and so a TSM restore process was started to recover the information that was lost. The restore was thought to be a success, but as days went by, more and more users were reporting that files were missing. I queried the summery tables for the restore sessions of that particular server and noticed that even though it says it was successful, it did not finish because for whatever reason the session was lost (network outage, etc). We did not think to look and see if there was a restartable restore at the time, because the restore was reported as being successful. When we opened a ticket IBM support, this is what we got: If the restore process stops because of a power outage or network failure, the server records the point at which this occurred. This record is known to the client as a restartable restore. -IBM TSM My question is how does the client inform you that there is a restartable restore that needs to be done, and why in the database, is it showing that the restore session was successful, when in fact this is false. Is there something that we missed? Any help in this regards would be greatly appreciated. Mel Dennis
Fw: Restores showing as successful but are not.
Forgot to mention... Have a look in the client manual for information on restartable restore. If you open up the PDF version, do a search for restartable restore, it should take you to the right place. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. - Forwarded by Andrew Raibeck/Tucson/IBM on 2006-03-07 15:34 - Andrew Raibeck/Tucson/[EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 2006-03-07 15:31 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Restores showing as successful but are not. For client operations, don't use that SUMMARY table field to assess status. That field comes from a related account log field, and has no bearing on the real outcome of the operation. If the operation was initiated manually, then monitoring the client itself should give you status. If the operation was scheduled via the scheduler, then QUERY EVENT with F=D will show you the results. I would not expect a completed status with RC 0 in the situation you describe. See the client manual chapter on Automating tasks for further info about the client return codes for the command line and scheduled events. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2006-03-07 14:24:08: Recently we had a drive on one of our servers accidentally deleted, and so a TSM restore process was started to recover the information that was lost. The restore was thought to be a success, but as days went by, more and more users were reporting that files were missing. I queried the summery tables for the restore sessions of that particular server and noticed that even though it says it was successful, it did not finish because for whatever reason the session was lost (network outage, etc). We did not think to look and see if there was a restartable restore at the time, because the restore was reported as being successful. When we opened a ticket IBM support, this is what we got: If the restore process stops because of a power outage or network failure, the server records the point at which this occurred. This record is known to the client as a restartable restore. -IBM TSM My question is how does the client inform you that there is a restartable restore that needs to be done, and why in the database, is it showing that the restore session was successful, when in fact this is false. Is there something that we missed? Any help in this regards would be greatly appreciated. Mel Dennis
All Inspected Files Failing Yet Backup Is Successful?
Hello all, Has anyone seen backups complete with all files inspected also failing, yet the expected amount of data is backed up into TSM? We also only see this on a few clients, not all. Any ideas? TSM server version: 5.2.3.2 Server OS: Windows 2003 TSM Client version: 5.2.3.4 Client OS: Windows 2000 2003 Thanks, Rob
Re: All Inspected Files Failing Yet Backup Is Successful?
Maybe I just have a high density, but I do not understand the question. It sure would help if you could provide actual TSM log data (or other documentation) that illustrates the problem, calling out the specific bits that you have in question. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-03-21 08:20:33: Hello all, Has anyone seen backups complete with all files inspected also failing, yet the expected amount of data is backed up into TSM? We also only see this on a few clients, not all. Any ideas? TSM server version:5.2.3.2 Server OS: Windows 2003 TSM Client version:5.2.3.4 Client OS: Windows 2000 2003 Thanks, Rob
Re: All Inspected Files Failing Yet Backup Is Successful?
I had a case last week. We had moved a storage pool to DEVC=FILE. Clients with MAXNUMMP=0 were not backing up. At 09:20 AM 3/21/2005 -0600, you wrote: Hello all, Has anyone seen backups complete with all files inspected also failing, yet the expected amount of data is backed up into TSM? We also only see this on a few clients, not all. Any ideas? TSM server version: 5.2.3.2 Server OS: Windows 2003 TSM Client version: 5.2.3.4 Client OS: Windows 2000 2003 Thanks, Rob Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: All Inspected Files Failing Yet Backup Is Successful?
The backup will inspect X amount of files and fail with the same X amount of files (stating that zero files were backed up). However the bytes transferred is about where we would expect it to be with a successful incremental. My confusion may be that I thought if a file fails, it is not actually backed up. Is this the case with failed files? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Monday, March 21, 2005 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: All Inspected Files Failing Yet Backup Is Successful? Maybe I just have a high density, but I do not understand the question. It sure would help if you could provide actual TSM log data (or other documentation) that illustrates the problem, calling out the specific bits that you have in question. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-03-21 08:20:33: Hello all, Has anyone seen backups complete with all files inspected also failing, yet the expected amount of data is backed up into TSM? We also only see this on a few clients, not all. Any ideas? TSM server version:5.2.3.2 Server OS: Windows 2003 TSM Client version:5.2.3.4 Client OS: Windows 2000 2003 Thanks, Rob
Re: All Inspected Files Failing Yet Backup Is Successful?
My confusion may be that I thought if a file fails, it is not actually backed up. Is this the case with failed files? Well, yes, if a file fails to back up, then it is not backed up. But this is just stating the obvious. Without more hard documentation, I cannot give you a more specific answer as to why you are seeing what you are seeing (since I do not know what you are seeing). Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-03-21 08:40:50: The backup will inspect X amount of files and fail with the same X amount of files (stating that zero files were backed up). However the bytes transferred is about where we would expect it to be with a successful incremental. My confusion may be that I thought if a file fails, it is not actually backed up. Is this the case with failed files? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Monday, March 21, 2005 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: All Inspected Files Failing Yet Backup Is Successful? Maybe I just have a high density, but I do not understand the question. It sure would help if you could provide actual TSM log data (or other documentation) that illustrates the problem, calling out the specific bits that you have in question. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-03-21 08:20:33: Hello all, Has anyone seen backups complete with all files inspected also failing, yet the expected amount of data is backed up into TSM? We also only see this on a few clients, not all. Any ideas? TSM server version:5.2.3.2 Server OS: Windows 2003 TSM Client version:5.2.3.4 Client OS: Windows 2000 2003 Thanks, Rob
Re: All Inspected Files Failing Yet Backup Is Successful?
Your posting doesn't say if you've checked your dsmerror.log and Activity Log. It's probable that the data did not actually get transmitted to the server. Do a reasonableness check of your backup's summary statistics. (When posting problems like this, PLEASE include sample data from the problem.) You may be encountering a problem as in APAR PQ91276. Richard Sims
AW: AW: TSM 5.3 and ISC install - successful on W2K Server under VMWare
Hallo Joerg! Your tip/hint was absolutely right. I followed your instructions -- and all went OK Thanks a lot for your help Michael Malitz e-mail: [EMAIL PROTECTED] -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Joerg Pohlmann Gesendet: Samstag, 05. Februar 2005 21:48 An: ADSM-L@VM.MARIST.EDU Betreff: Re: AW: TSM 5.3 and ISC install Michael, make sure that the amount of memory the virtual machine sees (as RAM) is 1GB. Also, I found that on some installs, the process wants to go to SUN's java site and download/install bits and pieces of java, but this varies with what's installed on your W2K machine. It just means that you will need to let the install process access the internet. Joerg Pohlmann 604-535-0452 Michael Malitz [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 2005-02-05 11:17 Please respond to ADSM: Dist Stor Manager To ADSM-L@VM.MARIST.EDU cc Subject AW: TSM 5.3 and ISC install Hi all, I?m also struggling with the new ISC and can not get over 66 %!!. I'm using Windows XP Host with VMWare and installed W2K Advanced Server SP4. My assigned physical memory to that W2K machine is 700 MB . During install a maximum of around 520 MB is used by ISCinstall processes. I increased the virtual Memory min 500 max 2000 MB and have 2,3 GB free disk space When I reach 66 % I get an error: Help is very much appreciated ? thanks and rgds Mikel Contents of ISCRuntimeInstallProgress.properties + #Sat Feb 05 22:33:17 CET 2005 ISC_FAILURE_MESSAGE=CheckDeployPageFail status=FAILED timestamp=Sat Feb 05 22\:33\:17 CET 2005 +++ end of log Contents of - the last entries of ISCRuntimeInstall.log (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.RemovePasswordsAction, msg2, Password replacement complete (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.RemovePasswordsAction, msg2, RemovePasswordsAction exit. (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.FailAndExitAction, wrn, CheckDeployPageFail (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.FailAndExitAction, wrn, (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.FailAndExitAction, msg2, status=FAILED,timestamp=Sat Feb 05 22:33:17 CET 2005,progress=(unchanged) +++ end of log Thanks again Michael Malitz e-mail: [EMAIL PROTECTED] -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Steve Harris Gesendet: Montag, 31. Jänner 2005 03:04 An: ADSM-L@VM.MARIST.EDU Betreff: Re: TSM 5.3 and ISC install Hi all For what its worth, I installed all the ISC stuff without incident on a newly installed (just TSM and MSSQL) generic brand win20003 server with 2GB of memory. The only issue that I had was that to begin with I was attempting to install from a remotely mounted file specified as UNC ie \\remoteservername\drive\etc When I mapped the drive and tried again everything went swimmingly. Now learning to use it is another matter, but the install part wasn't too bad for me. Regards Steve. Steve Harris TSM Admin Queensland Health, Brisbane Australia. [EMAIL PROTECTED] 29/01/2005 1:24:48 Well, I decided to try it again, trying this suggestion. I increased my virtual-storage to 2.2GB (it was at 700MB + 512MB real). Same results. I fired up Window Task Manager and watched the install the whole time. Memory usage never went above 425MB. The install gets to 10% and sits there for around 10-minutes. Then jumps to 15%sits there a while and then BOOM - Install Failed - Uninstall Failed. Oh well.time to call for support ! David Wellington [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 01/28/2005 03:11 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: TSM 5.3 and ISC install - won't Hi, I've just spent 3 weeks or so trying to install ISC on a virtual machine and have experience many problems. The install would fail at the 15% mark everytime. Each time the install failed I looked in the logs that it told me too, and like you, it was full of rubbish. At no stage was there ever an error message that told me what the problem was. In the end, after trying many different things, including upgrading Java, I increased the memory allocation to the virtual machine and it installed up to 66% complete before failing. I then increased the memory again, and after yet another 4 hours, the install finally completed. In the end, I had some 2Gb of memory allocated to the virtual machine. Hopefully, this information
Re: AW: AW: TSM 5.3 and ISC install - successful on W2K Server under VMWare
Was it the memory or having access to SUN's website that helped? Michael Malitz [EMAIL PROTECTED] wrote:Hallo Joerg! Your tip/hint was absolutely right. I followed your instructions -- and all went OK Thanks a lot for your help Michael Malitz e-mail: [EMAIL PROTECTED] -Urspr|ngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Joerg Pohlmann Gesendet: Samstag, 05. Februar 2005 21:48 An: ADSM-L@VM.MARIST.EDU Betreff: Re: AW: TSM 5.3 and ISC install Michael, make sure that the amount of memory the virtual machine sees (as RAM) is 1GB. Also, I found that on some installs, the process wants to go to SUN's java site and download/install bits and pieces of java, but this varies with what's installed on your W2K machine. It just means that you will need to let the install process access the internet. Joerg Pohlmann 604-535-0452 Michael Malitz Sent by: ADSM: Dist Stor Manager 2005-02-05 11:17 Please respond to ADSM: Dist Stor Manager To ADSM-L@VM.MARIST.EDU cc Subject AW: TSM 5.3 and ISC install Hi all, I?m also struggling with the new ISC and can not get over 66 %!!. I'm using Windows XP Host with VMWare and installed W2K Advanced Server SP4. My assigned physical memory to that W2K machine is 700 MB . During install a maximum of around 520 MB is used by ISCinstall processes. I increased the virtual Memory min 500 max 2000 MB and have 2,3 GB free disk space When I reach 66 % I get an error: Help is very much appreciated ? thanks and rgds Mikel Contents of ISCRuntimeInstallProgress.properties + #Sat Feb 05 22:33:17 CET 2005 ISC_FAILURE_MESSAGE=CheckDeployPageFail status=FAILED timestamp=Sat Feb 05 22\:33\:17 CET 2005 +++ end of log Contents of - the last entries of ISCRuntimeInstall.log (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.RemovePasswordsAction, msg2, Password replacement complete (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.RemovePasswordsAction, msg2, RemovePasswordsAction exit. (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.FailAndExitAction, wrn, CheckDeployPageFail (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.FailAndExitAction, wrn, (Feb 5, 2005 10:33:17 PM), Setup.product.install, com.ibm.pvc.we.care.ismp.FailAndExitAction, msg2, status=FAILED,timestamp=Sat Feb 05 22:33:17 CET 2005,progress=(unchanged) +++ end of log Thanks again Michael Malitz e-mail: [EMAIL PROTECTED] -Urspr|ngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Steve Harris Gesendet: Montag, 31. Jdnner 2005 03:04 An: ADSM-L@VM.MARIST.EDU Betreff: Re: TSM 5.3 and ISC install Hi all For what its worth, I installed all the ISC stuff without incident on a newly installed (just TSM and MSSQL) generic brand win20003 server with 2GB of memory. The only issue that I had was that to begin with I was attempting to install from a remotely mounted file specified as UNC ie \\remoteservername\drive\etc When I mapped the drive and tried again everything went swimmingly. Now learning to use it is another matter, but the install part wasn't too bad for me. Regards Steve. Steve Harris TSM Admin Queensland Health, Brisbane Australia. [EMAIL PROTECTED] 29/01/2005 1:24:48 Well, I decided to try it again, trying this suggestion. I increased my virtual-storage to 2.2GB (it was at 700MB + 512MB real). Same results. I fired up Window Task Manager and watched the install the whole time. Memory usage never went above 425MB. The install gets to 10% and sits there for around 10-minutes. Then jumps to 15%sits there a while and then BOOM - Install Failed - Uninstall Failed. Oh well.time to call for support ! David Wellington Sent by: ADSM: Dist Stor Manager 01/28/2005 03:11 AM Please respond to ADSM: Dist Stor Manager To ADSM-L@VM.MARIST.EDU cc Subject Re: TSM 5.3 and ISC install - won't Hi, I've just spent 3 weeks or so trying to install ISC on a virtual machine and have experience many problems. The install would fail at the 15% mark everytime. Each time the install failed I looked in the logs that it told me too, and like you, it was full of rubbish. At no stage was there ever an error message that told me what the problem was. In the end, after trying many different things, including upgrading Java, I increased the memory allocation to the virtual machine and it installed up to 66% complete before failing. I then increased the memory again, and after yet another 4 hours, the install finally completed. In the end, I had some 2Gb of memory allocated to the virtual machine. Hopefully, this information maybe of some help. Regards. David Wellington
Error of startup after successful DB restore
After a successful restore, the server does not come up. Both the production and DR servers are at the same level, but I get this errors on startup: [tsmserv2] /usr/tivoli/tsm/server/bin # dsmserv ANRW Message repository for language AMENG does not match program level. ANRI Message repository's compile date: Tue Dec 16 08:49:40 2003 ANRI Program's message timestamp: Tue Jun 10 01:10:49 2003 ANR7800I DSMSERV generated at 10:00:19 on Jun 13 2003. Tivoli Storage Manager for AIX-RS/6000 Version 5, Release 2, Level 0.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1999,2003. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file dsmserv.opt. ANR7811I Direct I/O will be used for all eligible disk files. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 1960 megabytes. ANR0201I Database assigned capacity is 12784 megabytes. ANR0306I Recovery log volume mount in progress. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANR0352I Transaction recovery complete. ANR1635I The server machine GUID, d3.a8.5c.1a.63.e7.11.d9.8a.13.08.63.ac.1e.03 .4f, has initialized. ANRD tb.c(799): ThreadId0 Column count mismatch for table Nodes - expect ed 48, found 50 ANR0101E adminit.c(1112): Error 18 opening table Nodes. [tsmserv2] /usr/tivoli/tsm/server/bin # Any suggestions? [EMAIL PROTECTED] 01/28/2005 10:56:42 AM From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Clark We have set up a backup TSM server for DR purposes. TSM has been installed to the same level and a database created of a size larger than the production TSM database, all DB volumes are formatted. On the production side, the database is backed up to disk. This is then copied over to a 2nd AIX server...now the backup TSM server. Looking in the manual, it appears the database restore assumes the files will be on a cartridge. Questions: - should the server be down to restore the database? - what is the format of the command in an AIX environment to restore the db if the files are under /var/tsmdbbk/morning as so: -rw--- 1 root sys 9663676416 Jan 28 04:08 06902830.dbb -rw--- 1 root sys 2981181842 Jan 28 04:11 06903334.dbb Yes, the server must be down, and no, the backup(s) don't have to be on a cartridge. Assuming that there are intact and update volume history and device configuration files, the command is basically dsmserv restore db todate=today source=dbbackup If the volume history file is not present, the commands would be dsmserv restore db devc=file_device_class vol=/var/tsmdbbk/morning/06902830.dbb followed by dsmserv restore db devc=file_device_class vol=/var/tsmdbbk/morning/06903334.dbb commit=yes (All commands assume that you have a device configuration file present, and in the directory that your dsmserv.opt file points at.) The file_device_class is the same devclass that you use to run the db backups. Don't forget the commit flag for the last volume. If you don't put that in, you'll get to do the entire restore again. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Error of startup after successful DB restore
On Jan 28, 2005, at 2:17 PM, Lawrence Clark wrote: After a successful restore, the server does not come up. Both the production and DR servers are at the same level, but I get this errors on startup: [tsmserv2] /usr/tivoli/tsm/server/bin # dsmserv ANRW Message repository for language AMENG does not match program level. ... Looks to me that the alternate TSM server that you think is the same level as your production server, is in fact not. I would review all the filesets and files in detail. Something is amiss. Richard Sims
Re: Error of startup after successful DB restore
I say they are at the same level because the production server was migrated to 5.2, then upgraded to 5.2.2.0: Session established with server BACKUP: AIX-RS/6000 Server Version 5, Release 2, Level 2.0 tivoli.tsm.server.com 5.2.2.0C FIBM Tivoli Storage Manager Server common services tivoli.tsm.server.rte 5.2.2.0C FIBM Tivoli Storage Manager Server Runtime The backup DR server was installed from scratch at 5.2.0 and upgraded to 5.2.2.0: tivoli.tsm.server.com 5.2.2.0C FIBM Tivoli Storage Manager Server common services tivoli.tsm.server.rte 5.2.0.0C FIBM Tivoli Storage Manager Server Runtime [EMAIL PROTECTED] 01/28/2005 2:31:49 PM On Jan 28, 2005, at 2:17 PM, Lawrence Clark wrote: After a successful restore, the server does not come up. Both the production and DR servers are at the same level, but I get this errors on startup: [tsmserv2] /usr/tivoli/tsm/server/bin # dsmserv ANRW Message repository for language AMENG does not match program level. ... Looks to me that the alternate TSM server that you think is the same level as your production server, is in fact not. I would review all the filesets and files in detail. Something is amiss. Richard Sims
Re: Error of startup after successful DB restore
Yes, but look at the error messages you got from your ealier post. The include: Tivoli Storage Manager for AIX-RS/6000 Version 5, Release 2, Level 0.0 Note 5.2.0.0, not 5.2.2.0. Also, the TSM runtime (*.rte) file set for your DR server shows 5.2.0.0. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2005-01-28 12:52:25: I say they are at the same level because the production server was migrated to 5.2, then upgraded to 5.2.2.0: Session established with server BACKUP: AIX-RS/6000 Server Version 5, Release 2, Level 2.0 tivoli.tsm.server.com 5.2.2.0C FIBM Tivoli Storage Manager Server common services tivoli.tsm.server.rte 5.2.2.0C FIBM Tivoli Storage Manager Server Runtime The backup DR server was installed from scratch at 5.2.0 and upgraded to 5.2.2.0: tivoli.tsm.server.com 5.2.2.0C FIBM Tivoli Storage Manager Server common services tivoli.tsm.server.rte 5.2.0.0C FIBM Tivoli Storage Manager Server Runtime [EMAIL PROTECTED] 01/28/2005 2:31:49 PM On Jan 28, 2005, at 2:17 PM, Lawrence Clark wrote: After a successful restore, the server does not come up. Both the production and DR servers are at the same level, but I get this errors on startup: [tsmserv2] /usr/tivoli/tsm/server/bin # dsmserv ANRW Message repository for language AMENG does not match program level. ... Looks to me that the alternate TSM server that you think is the same level as your production server, is in fact not. I would review all the filesets and files in detail. Something is amiss. Richard Sims
Last successful backup completed
Hello All! I know that there are many different SQL select statements that can be run to find how much data was backed up, if it was successful, failed or missed, etc. ,but is there a way to run a command that will go out and query all of the TSM clients for their last successful backup date/time and how much data was transferred? I have not been successful in finding such an example as of yet. Thank you in advance for your help! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: Last successful backup completed
Hi Joni I'm running a batch file with this command (on a windows 2000 server). dsmadmc -id=batch -password=batch -displaymode=list q actlog search=ANE4961I begindate=-1 begintime=20:00 endtime=now C:\tsmout\datatransfer.txt Luc Joni Moyer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 2005-01-17 12:28 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Last successful backup completed Hello All! I know that there are many different SQL select statements that can be run to find how much data was backed up, if it was successful, failed or missed, etc. ,but is there a way to run a command that will go out and query all of the TSM clients for their last successful backup date/time and how much data was transferred? I have not been successful in finding such an example as of yet. Thank you in advance for your help! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: Need evidence of successful BRMS/TSM sharing 3494
We used to do the same thing, before moving the AS400 backups to BRMS/TSM. Just make sure you use different private and scratch catagories. [EMAIL PROTECTED] Steve Harris [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09/23/2004 09:23 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Need evidence of successful BRMS/TSM sharing 3494 When you use a 3494 you already *have* a library manager. Just allocate different categories for AS400 and TSM. I had a 3 bay 3494 with two 3590E drives SCSI connected to an AS400 and 4 drives connected to a P690 running TSM. Worked fine. Just had to do a little operator training to sort out the two sets of check-in/check out processes. Steve. [EMAIL PROTECTED] 24/09/2004 8:09:15 Currently, BRMS has a 3494 and TSM has its own (in different locations). We are bringing the AS/400s into this data centre. The AS/400 people WILL NOT share the library unless we get proof that it can be done successfully. (Sharing will take less floor space and give us high availability for the same cost.) Note, we are probably not interested in a TSM agent for BRMS. We still want to keep these two beasts off each other throats. So, we are simply looking for other datacentres that have BRMS and TSM sharing a PARTITIONED 3494. If TSM can act as a library manager for BRMS (i.e. easily share drives) that would be of interest also. If you can help, I'd appreciate it; and if you don't mind, the AS/400 people would probably like to converse with you later. Thanks in advance. Dan Giles 416.402.9744 [EMAIL PROTECTED] *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone or by return email. You should also delete this email and destroy any hard copies produced. ***
Need evidence of successful BRMS/TSM sharing 3494
Currently, BRMS has a 3494 and TSM has its own (in different locations). We are bringing the AS/400s into this data centre. The AS/400 people WILL NOT share the library unless we get proof that it can be done successfully. (Sharing will take less floor space and give us high availability for the same cost.) Note, we are probably not interested in a TSM agent for BRMS. We still want to keep these two beasts off each other throats. So, we are simply looking for other datacentres that have BRMS and TSM sharing a PARTITIONED 3494. If TSM can act as a library manager for BRMS (i.e. easily share drives) that would be of interest also. If you can help, I'd appreciate it; and if you don't mind, the AS/400 people would probably like to converse with you later. Thanks in advance. Dan Giles 416.402.9744 [EMAIL PROTECTED]
Re: Need evidence of successful BRMS/TSM sharing 3494
When you use a 3494 you already *have* a library manager. Just allocate different categories for AS400 and TSM. I had a 3 bay 3494 with two 3590E drives SCSI connected to an AS400 and 4 drives connected to a P690 running TSM. Worked fine. Just had to do a little operator training to sort out the two sets of check-in/check out processes. Steve. [EMAIL PROTECTED] 24/09/2004 8:09:15 Currently, BRMS has a 3494 and TSM has its own (in different locations). We are bringing the AS/400s into this data centre. The AS/400 people WILL NOT share the library unless we get proof that it can be done successfully. (Sharing will take less floor space and give us high availability for the same cost.) Note, we are probably not interested in a TSM agent for BRMS. We still want to keep these two beasts off each other throats. So, we are simply looking for other datacentres that have BRMS and TSM sharing a PARTITIONED 3494. If TSM can act as a library manager for BRMS (i.e. easily share drives) that would be of interest also. If you can help, I'd appreciate it; and if you don't mind, the AS/400 people would probably like to converse with you later. Thanks in advance. Dan Giles 416.402.9744 [EMAIL PROTECTED] *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone or by return email. You should also delete this email and destroy any hard copies produced. ***
POSTSCHEDULECMD failed, but event was successful
TSM Client 5.1.6.7 on Windows2000 SP4 TSM Server 5.1.7.1 on AIX 4.3.3 I have coded a PRE and POSTSCHEDULCMD that stops some Oracle services, backups up and then restarts the services. My POSTSCHEDULECMD keeps track of the highest return code and then EXIT %MAXCC%. Testing with this today, my POSTSCHEDULECMD did and EXIT 2, and you see that in the DSMSCHED.LOG file. The problem is that the event itself didn't Fail. Executing Operating System command or script: c:\progra~1\tivoli\tsm\scripts\orastart.cmd 09/24/2003 22:17:10 Finished command. Return code is: 2 09/24/2003 22:17:10 ANS1903W The POSTCHEDULECMD command failed. 09/24/2003 22:17:10 Scheduled event '@166' completed successfully. 09/24/2003 22:17:10 Sending results for scheduled event '@166'. 09/24/2003 22:17:10 Results sent to server for scheduled event '@166'. According to the TSM Client doc: For Windows NT, 2000, XP systems: If the postschedulecmd command does not complete with return code 0, the client will report that the scheduled event completed with return code 8 (unless the scheduled operation encounters a more severe error yielding a higher return code). Why didn't my schedule event finish with Fail?? Anyone seen this behavior? Bill Boyer Some days you are the bug, some days you are the windshield. - ??
Re: POSTSCHEDULECMD failed, but event was successful
Hi, Seen something like it and started to use pre- and postnschedulecmd for a client because of it. At this client it looked like it took to long to stop and start the services (non oracle). Regard, Karel -Oorspronkelijk bericht- Van: Bill Boyer [mailto:[EMAIL PROTECTED] Verzonden: donderdag 25 september 2003 16:33 Aan: [EMAIL PROTECTED] Onderwerp: POSTSCHEDULECMD failed, but event was successful TSM Client 5.1.6.7 on Windows2000 SP4 TSM Server 5.1.7.1 on AIX 4.3.3 I have coded a PRE and POSTSCHEDULCMD that stops some Oracle services, backups up and then restarts the services. My POSTSCHEDULECMD keeps track of the highest return code and then EXIT %MAXCC%. Testing with this today, my POSTSCHEDULECMD did and EXIT 2, and you see that in the DSMSCHED.LOG file. The problem is that the event itself didn't Fail. Executing Operating System command or script: c:\progra~1\tivoli\tsm\scripts\orastart.cmd 09/24/2003 22:17:10 Finished command. Return code is: 2 09/24/2003 22:17:10 ANS1903W The POSTCHEDULECMD command failed. 09/24/2003 22:17:10 Scheduled event '@166' completed successfully. 09/24/2003 22:17:10 Sending results for scheduled event '@166'. 09/24/2003 22:17:10 Results sent to server for scheduled event '@166'. According to the TSM Client doc: For Windows NT, 2000, XP systems: If the postschedulecmd command does not complete with return code 0, the client will report that the scheduled event completed with return code 8 (unless the scheduled operation encounters a more severe error yielding a higher return code). Why didn't my schedule event finish with Fail?? Anyone seen this behavior? Bill Boyer Some days you are the bug, some days you are the windshield. - ??
R: POSTSCHEDULECMD failed, but event was successful
Hi Bill, I saw the same behavior on schedules of type=command. I launched a backup script and even if the script exits with a return code of 8 (exit 8) the event is showed as COMPLETED instead of FAILED. The current versions are: TSM Server 5.1.6.0 on AIX 4.3.3 TSM Client 5.1 on AIX 4.3.3 I think that with the version 4 of TSM the event used to be considered FAILED when the launched command exited with a return code of 8. Regards, Mike Angels -Messaggio originale- Da: Bill Boyer [SMTP:[EMAIL PROTECTED] Inviato:giovedi 25 settembre 2003 16.33 A: [EMAIL PROTECTED] Oggetto:POSTSCHEDULECMD failed, but event was successful TSM Client 5.1.6.7 on Windows2000 SP4 TSM Server 5.1.7.1 on AIX 4.3.3 I have coded a PRE and POSTSCHEDULCMD that stops some Oracle services, backups up and then restarts the services. My POSTSCHEDULECMD keeps track of the highest return code and then EXIT %MAXCC%. Testing with this today, my POSTSCHEDULECMD did and EXIT 2, and you see that in the DSMSCHED.LOG file. The problem is that the event itself didn't Fail. Executing Operating System command or script: c:\progra~1\tivoli\tsm\scripts\orastart.cmd 09/24/2003 22:17:10 Finished command. Return code is: 2 09/24/2003 22:17:10 ANS1903W The POSTCHEDULECMD command failed. 09/24/2003 22:17:10 Scheduled event '@166' completed successfully. 09/24/2003 22:17:10 Sending results for scheduled event '@166'. 09/24/2003 22:17:10 Results sent to server for scheduled event '@166'. According to the TSM Client doc: For Windows NT, 2000, XP systems: If the postschedulecmd command does not complete with return code 0, the client will report that the scheduled event completed with return code 8 (unless the scheduled operation encounters a more severe error yielding a higher return code). Why didn't my schedule event finish with Fail?? Anyone seen this behavior? Bill Boyer Some days you are the bug, some days you are the windshield. - ??
Re: R: POSTSCHEDULECMD failed, but event was successful
You are probably seeing APAR IC35203. This is fixed in client version 5.1.6.0 and up. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Mike Angels [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09/25/2003 14:57 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:R: POSTSCHEDULECMD failed, but event was successful Hi Bill, I saw the same behavior on schedules of type=command. I launched a backup script and even if the script exits with a return code of 8 (exit 8) the event is showed as COMPLETED instead of FAILED. The current versions are: TSM Server 5.1.6.0 on AIX 4.3.3 TSM Client 5.1 on AIX 4.3.3 I think that with the version 4 of TSM the event used to be considered FAILED when the launched command exited with a return code of 8. Regards, Mike Angels -Messaggio originale- Da: Bill Boyer [SMTP:[EMAIL PROTECTED] Inviato:giovedi 25 settembre 2003 16.33 A: [EMAIL PROTECTED] Oggetto:POSTSCHEDULECMD failed, but event was successful TSM Client 5.1.6.7 on Windows2000 SP4 TSM Server 5.1.7.1 on AIX 4.3.3 I have coded a PRE and POSTSCHEDULCMD that stops some Oracle services, backups up and then restarts the services. My POSTSCHEDULECMD keeps track of the highest return code and then EXIT %MAXCC%. Testing with this today, my POSTSCHEDULECMD did and EXIT 2, and you see that in the DSMSCHED.LOG file. The problem is that the event itself didn't Fail. Executing Operating System command or script: c:\progra~1\tivoli\tsm\scripts\orastart.cmd 09/24/2003 22:17:10 Finished command. Return code is: 2 09/24/2003 22:17:10 ANS1903W The POSTCHEDULECMD command failed. 09/24/2003 22:17:10 Scheduled event '@166' completed successfully. 09/24/2003 22:17:10 Sending results for scheduled event '@166'. 09/24/2003 22:17:10 Results sent to server for scheduled event '@166'. According to the TSM Client doc: For Windows NT, 2000, XP systems: If the postschedulecmd command does not complete with return code 0, the client will report that the scheduled event completed with return code 8 (unless the scheduled operation encounters a more severe error yielding a higher return code). Why didn't my schedule event finish with Fail?? Anyone seen this behavior? Bill Boyer Some days you are the bug, some days you are the windshield. - ??
Re: POSTSCHEDULECMD failed, but event was successful
The doc you quoted explains the answer. The event is reported as completed (i.e. not failed) with return code 8. If you do a QUERY EVENT with FORMAT=DETAILED, I would expect you to see a status of Complete and a result code of 8. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Bill Boyer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09/25/2003 07:33 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:POSTSCHEDULECMD failed, but event was successful TSM Client 5.1.6.7 on Windows2000 SP4 TSM Server 5.1.7.1 on AIX 4.3.3 I have coded a PRE and POSTSCHEDULCMD that stops some Oracle services, backups up and then restarts the services. My POSTSCHEDULECMD keeps track of the highest return code and then EXIT %MAXCC%. Testing with this today, my POSTSCHEDULECMD did and EXIT 2, and you see that in the DSMSCHED.LOG file. The problem is that the event itself didn't Fail. Executing Operating System command or script: c:\progra~1\tivoli\tsm\scripts\orastart.cmd 09/24/2003 22:17:10 Finished command. Return code is: 2 09/24/2003 22:17:10 ANS1903W The POSTCHEDULECMD command failed. 09/24/2003 22:17:10 Scheduled event '@166' completed successfully. 09/24/2003 22:17:10 Sending results for scheduled event '@166'. 09/24/2003 22:17:10 Results sent to server for scheduled event '@166'. According to the TSM Client doc: For Windows NT, 2000, XP systems: If the postschedulecmd command does not complete with return code 0, the client will report that the scheduled event completed with return code 8 (unless the scheduled operation encounters a more severe error yielding a higher return code). Why didn't my schedule event finish with Fail?? Anyone seen this behavior? Bill Boyer Some days you are the bug, some days you are the windshield. - ??
Error when successful?
Hi *SM-ers! Today I found the following message in my actlog: ANE4993E TDP MSExchgV2 NT ACN3507 TDP for Microsoft Exchange: incr restore of storage group Information Store to server TS02 completed successfully. Completed successfully... Then why is TDP for Exchange writing an error (ANEE) message to the actlog? Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Error when successful?
Today I found the following message in my actlog: ANE4993E TDP MSExchgV2 NT ACN3507 TDP for Microsoft Exchange: incr restore of storage group Information Store to server TS02 completed successfully. Completed successfully... Then why is TDP for Exchange writing an error (ANEE) message to the actlog? Eric, Good point. I am looking into this and will try to get this changed to an I message in a future release. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Live your life as an exclamation, not an explanation. - Strive for excellence, not perfection.
Successful or not?
Hi TSM experts! What do you think about the following errors below in the offline db backup log? Is it successful or unsuccessful? What could cause this problem? At the firt attempt the backup is unsuccessful and the 2nd retry semms ok. Job number: 5023 Oracle sid: prod Timestamp : 20011227201003 Function : Offline database file level archive to TSM server Oracle Server Manager Release 3.0.5.0.0 - Production (c) Copyright 1997, Oracle Corporation. All Rights Reserved. Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production With the Objects option PL/SQL Release 8.0.5.2.0 - Production SVRMGR Connected. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR ORACLE instance started. Total System Global Area357439648 bytes Fixed Size 47264 bytes Variable Size 185417728 bytes Database Buffers167772160 bytes Redo Buffers 4202496 bytes Database mounted. Database opened. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR Server Manager complete. Datafile: /pdd/oradata/prod/control01.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:12:42 Last access: 12/27/2001 20:10:02 Directory-- 512 /pdd/oradata [Sent] Directory-- 2,560 /pdd/oradata/prod [Sent] Normal File--23,617,536 /pdd/oradata/prod/control01.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control01.ctl [Sent] Archive processing of '/pdd/oradata/prod/control01.ctl' finished without failure. Total number of objects inspected:3 Total number of objects archived: 3 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time: 61.36 sec Network data transfer rate: 751.76 KB/sec Aggregate data transfer rate:709.24 KB/sec Objects compressed by:0% Elapsed processing time: 00:01:05 Archived file: /pdd/oradata/prod/control01.ctl - Datafile: /pdd/oradata/prod/control02.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:13:47 Last access: 12/27/2001 20:12:42 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl [Sent] Archive processing of '/pdd/oradata/prod/control02.ctl' finished without failure. Total number of objects inspected:1 Total number of objects archived: 1 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time:2.09 sec Network data transfer rate:22,049.08 KB/sec Aggregate data transfer rate: 11,497.06 KB/sec Objects compressed by:0% Elapsed processing time: 00:00:04 Archived file: /pdd/oradata/prod/control02.ctl dv, Stonyi Attila mailto:[EMAIL PROTECTED] Rendszermrnk MV Informatika Kft. 06(1)457-9372
Re: Successful or not?
Hi, I'm not using disk primary stgpool, the backups are goes directly to tape in 3494 tape library with 3 drives. The error logs aren't contain any error messages regarding to these errors. Regards, Stonyi Attila mailto:[EMAIL PROTECTED] System Engineer MV Informatika Kft. I'm no expert, but I'd say they were successful. I saw a post from someone who suggested that perhaps you've got a limitation on your disk storage pool that won't accept a file larger than 'x' size and because of that, it's having to go to a different pool (tape?). However, you'd probably be seeing a lot of that since these files are only 23MB...Check the dsmerror.log file on the client and the dsmserv.err file on the server for more clues... - Original Message - From: Sotonyi Attila [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 07, 2002 2:16 AM Subject: Successful or not? Hi TSM experts! What do you think about the following errors below in the offline db backup log? Is it successful or unsuccessful? What could cause this problem? At the firt attempt the backup is unsuccessful and the 2nd retry semms ok. Job number: 5023 Oracle sid: prod Timestamp : 20011227201003 Function : Offline database file level archive to TSM server Oracle Server Manager Release 3.0.5.0.0 - Production (c) Copyright 1997, Oracle Corporation. All Rights Reserved. Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production With the Objects option PL/SQL Release 8.0.5.2.0 - Production SVRMGR Connected. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR ORACLE instance started. Total System Global Area357439648 bytes Fixed Size 47264 bytes Variable Size 185417728 bytes Database Buffers167772160 bytes Redo Buffers 4202496 bytes Database mounted. Database opened. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR Server Manager complete. Datafile: /pdd/oradata/prod/control01.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:12:42 Last access: 12/27/2001 20:10:02 Directory-- 512 /pdd/oradata [Sent] Directory-- 2,560 /pdd/oradata/prod [Sent] Normal File--23,617,536 /pdd/oradata/prod/control01.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control01.ctl [Sent] Archive processing of '/pdd/oradata/prod/control01.ctl' finished without failure. Total number of objects inspected:3 Total number of objects archived: 3 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time: 61.36 sec Network data transfer rate: 751.76 KB/sec Aggregate data transfer rate:709.24 KB/sec Objects compressed by:0% Elapsed processing time: 00:01:05 Archived file: /pdd/oradata/prod/control01.ctl - Datafile: /pdd/oradata/prod/control02.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:13:47 Last access: 12/27/2001 20:12:42 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl [Sent] Archive processing of '/pdd/oradata/prod/control02.ctl' finished without failure. Total number of objects inspected:1 Total number of objects archived: 1 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed
Re: Successful or not?
The archive was successful. The first errors happened while waiting for the tape to be mounted or to position to EOT Bill Smoldt STORServer, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Sotonyi Attila Sent: Monday, January 07, 2002 1:17 AM To: [EMAIL PROTECTED] Subject: Successful or not? Hi TSM experts! What do you think about the following errors below in the offline db backup log? Is it successful or unsuccessful? What could cause this problem? At the firt attempt the backup is unsuccessful and the 2nd retry semms ok. Job number: 5023 Oracle sid: prod Timestamp : 20011227201003 Function : Offline database file level archive to TSM server Oracle Server Manager Release 3.0.5.0.0 - Production (c) Copyright 1997, Oracle Corporation. All Rights Reserved. Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production With the Objects option PL/SQL Release 8.0.5.2.0 - Production SVRMGR Connected. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR ORACLE instance started. Total System Global Area357439648 bytes Fixed Size 47264 bytes Variable Size 185417728 bytes Database Buffers167772160 bytes Redo Buffers 4202496 bytes Database mounted. Database opened. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR Server Manager complete. Datafile: /pdd/oradata/prod/control01.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:12:42 Last access: 12/27/2001 20:10:02 Directory-- 512 /pdd/oradata [Sent] Directory-- 2,560 /pdd/oradata/prod [Sent] Normal File--23,617,536 /pdd/oradata/prod/control01.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control01.ctl [Sent] Archive processing of '/pdd/oradata/prod/control01.ctl' finished without failure. Total number of objects inspected:3 Total number of objects archived: 3 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time: 61.36 sec Network data transfer rate: 751.76 KB/sec Aggregate data transfer rate:709.24 KB/sec Objects compressed by:0% Elapsed processing time: 00:01:05 Archived file: /pdd/oradata/prod/control01.ctl - Datafile: /pdd/oradata/prod/control02.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:13:47 Last access: 12/27/2001 20:12:42 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl [Sent] Archive processing of '/pdd/oradata/prod/control02.ctl' finished without failure. Total number of objects inspected:1 Total number of objects archived: 1 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time:2.09 sec Network data transfer rate:22,049.08 KB/sec Aggregate data transfer rate: 11,497.06 KB/sec Objects compressed by:0% Elapsed processing time: 00:00:04 Archived file: /pdd/oradata/prod/control02.ctl \dv, Sstonyi Attila mailto:[EMAIL PROTECTED] Rendszermirnvk MAV Informatika Kft. 06(1)457-9372
Re: Successful or not?
I'm no expert, but I'd say they were successful. I saw a post from someone who suggested that perhaps you've got a limitation on your disk storage pool that won't accept a file larger than 'x' size and because of that, it's having to go to a different pool (tape?). However, you'd probably be seeing a lot of that since these files are only 23MB...Check the dsmerror.log file on the client and the dsmserv.err file on the server for more clues... - Original Message - From: Sotonyi Attila [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 07, 2002 2:16 AM Subject: Successful or not? Hi TSM experts! What do you think about the following errors below in the offline db backup log? Is it successful or unsuccessful? What could cause this problem? At the firt attempt the backup is unsuccessful and the 2nd retry semms ok. Job number: 5023 Oracle sid: prod Timestamp : 20011227201003 Function : Offline database file level archive to TSM server Oracle Server Manager Release 3.0.5.0.0 - Production (c) Copyright 1997, Oracle Corporation. All Rights Reserved. Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production With the Objects option PL/SQL Release 8.0.5.2.0 - Production SVRMGR Connected. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR ORACLE instance started. Total System Global Area357439648 bytes Fixed Size 47264 bytes Variable Size 185417728 bytes Database Buffers167772160 bytes Redo Buffers 4202496 bytes Database mounted. Database opened. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR Server Manager complete. Datafile: /pdd/oradata/prod/control01.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:12:42 Last access: 12/27/2001 20:10:02 Directory-- 512 /pdd/oradata [Sent] Directory-- 2,560 /pdd/oradata/prod [Sent] Normal File--23,617,536 /pdd/oradata/prod/control01.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control01.ctl [Sent] Archive processing of '/pdd/oradata/prod/control01.ctl' finished without failure. Total number of objects inspected:3 Total number of objects archived: 3 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time: 61.36 sec Network data transfer rate: 751.76 KB/sec Aggregate data transfer rate:709.24 KB/sec Objects compressed by:0% Elapsed processing time: 00:01:05 Archived file: /pdd/oradata/prod/control01.ctl - Datafile: /pdd/oradata/prod/control02.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:13:47 Last access: 12/27/2001 20:12:42 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl [Sent] Archive processing of '/pdd/oradata/prod/control02.ctl' finished without failure. Total number of objects inspected:1 Total number of objects archived: 1 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time:2.09 sec Network data transfer rate:22,049.08 KB/sec Aggregate data transfer rate: 11,497.06 KB/sec Objects compressed by:0% Elapsed processing time: 00:00:04 Archived file: /pdd/oradata/prod/control02.ctl \dv, Sstonyi Attila mailto:[EMAIL PROTECTED] Rendszermirnvk MAV Informatika Kft. 06
Re: Successful or not?
You have left the datafiles for the Database . Please archive all logfiles, datafiles and control files and parameter files . This is incomplete archive in terms od Database -Original Message- From: Bill Smoldt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 08, 2002 2:16 AM To: [EMAIL PROTECTED] Subject: Re: Successful or not? The archive was successful. The first errors happened while waiting for the tape to be mounted or to position to EOT Bill Smoldt STORServer, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Sotonyi Attila Sent: Monday, January 07, 2002 1:17 AM To: [EMAIL PROTECTED] Subject: Successful or not? Hi TSM experts! What do you think about the following errors below in the offline db backup log? Is it successful or unsuccessful? What could cause this problem? At the firt attempt the backup is unsuccessful and the 2nd retry semms ok. Job number: 5023 Oracle sid: prod Timestamp : 20011227201003 Function : Offline database file level archive to TSM server Oracle Server Manager Release 3.0.5.0.0 - Production (c) Copyright 1997, Oracle Corporation. All Rights Reserved. Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production With the Objects option PL/SQL Release 8.0.5.2.0 - Production SVRMGR Connected. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR ORACLE instance started. Total System Global Area357439648 bytes Fixed Size 47264 bytes Variable Size 185417728 bytes Database Buffers167772160 bytes Redo Buffers 4202496 bytes Database mounted. Database opened. SVRMGR Database closed. Database dismounted. ORACLE instance shut down. SVRMGR Server Manager complete. Datafile: /pdd/oradata/prod/control01.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:12:42 Last access: 12/27/2001 20:10:02 Directory-- 512 /pdd/oradata [Sent] Directory-- 2,560 /pdd/oradata/prod [Sent] Normal File--23,617,536 /pdd/oradata/prod/control01.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control01.ctl [Sent] Archive processing of '/pdd/oradata/prod/control01.ctl' finished without failure. Total number of objects inspected:3 Total number of objects archived: 3 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time: 61.36 sec Network data transfer rate: 751.76 KB/sec Aggregate data transfer rate:709.24 KB/sec Objects compressed by:0% Elapsed processing time: 00:01:05 Archived file: /pdd/oradata/prod/control01.ctl - Datafile: /pdd/oradata/prod/control02.ctl archive started. Tivoli Storage Manager *** Fixtest, Please see README file for more information *** Command Line Backup Client Interface - Version 4, Release 1, Level 2.20 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. Archive function invoked. Node Name: GIR05 Session established with server TSM01: AIX-RS/6000 Server Version 4, Release 1, Level 4.0 Server date/time: 12/27/2001 20:13:47 Last access: 12/27/2001 20:12:42 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File--23,617,536 /pdd/oradata/prod/control02.ctl [Sent] Archive processing of '/pdd/oradata/prod/control02.ctl' finished without failure. Total number of objects inspected:1 Total number of objects archived: 1 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:45.04 MB Data transfer time:2.09 sec Network data transfer rate:22,049.08 KB/sec Aggregate data transfer rate: 11,497.06 KB/sec Objects compressed by:0% Elapsed processing time: 00:00:04 Archived file: /pdd/oradata/prod/control02.ctl \dv, Sstonyi Attila
Successful event report, but failed backup
Has anyone run across an example of a client (NT, running TSM 4.1.0) reporting a successful backup, yet the schedule log indicates that the backup never ran: 12/12/2001 02:13:27 ANS1814E Unable to start scheduled event 'DAILY_INCR' 12/12/2001 02:13:27 ANS1815E Either the window has elapsed or the schedule has been deleted The TSM server is running version 4.1.2.1, and the event listing for the client says that it completed successfully. -- Mark Stapleton ([EMAIL PROTECTED])
Re: Successful event report, but failed backup
Mark: That client is buggy, check out this post from February: http://msgs.adsm.org/cgi-bin/get/adsm0102/202.html This is fixed in the latest versions. Tim Rushforth City of Winnipeg -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 8:46 AM To: [EMAIL PROTECTED] Subject: Successful event report, but failed backup Has anyone run across an example of a client (NT, running TSM 4.1.0) reporting a successful backup, yet the schedule log indicates that the backup never ran: 12/12/2001 02:13:27 ANS1814E Unable to start scheduled event 'DAILY_INCR' 12/12/2001 02:13:27 ANS1815E Either the window has elapsed or the schedule has been deleted The TSM server is running version 4.1.2.1, and the event listing for the client says that it completed successfully. -- Mark Stapleton ([EMAIL PROTECTED])
Re: Failed Schedules Show Completed Successful
That is the opposite of the bug that I mentionied. The bug I mentioned is if the schedule fails on 3.7 or 4.1 (fixed in 4.12) then the client will say the event completed successfully and send those results to the server. So this means that you could have schedules that are failing and not know it unless you are checking the local schedule and error logs. A simple test that anyone can do to see if they are affected by this is to setup a schedule to perform a selective backup of a filespace that does not exist on the client. TSM should report this as a failed event (and it does on 3.1.06 and 4.1.2) but reports as successfull with 3.7-4.11.16) 4.11.16 Client: - 02/08/2001 09:41:33 Selective Backup function invoked. 02/08/2001 09:41:38 ANS1228E Sending of object 'J:\*' failed 02/08/2001 09:41:38 ANS1063E Invalid path specification 02/08/2001 09:41:40 --- SCHEDULEREC STATUS BEGIN 02/08/2001 09:41:40 --- SCHEDULEREC OBJECT END @310 02/08/2001 09:44:19 02/08/2001 09:41:40 Scheduled event '@310' completed successfully. - 4.12 Client - 02/08/2001 09:44:43 Selective Backup function invoked. 02/08/2001 09:44:44 ANS1228E Sending of object 'J:\*' failed 02/08/2001 09:44:44 ANS1063E Invalid path specification 02/08/2001 09:44:46 --- SCHEDULEREC STATUS BEGIN 02/08/2001 09:44:46 --- SCHEDULEREC OBJECT END @309 02/08/2001 09:44:00 02/08/2001 09:44:46 ANS1512E Scheduled event '@309' failed. Return code = 4. - The above is just an example, but basically anything that will cause a schedule to fail will not report as failed on the buggy clients. Tim Rushforth City of Winnipeg -Original Message- From: George Lesho [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 07, 2001 2:52 PM To: [EMAIL PROTECTED] Subject: Re: Failed Schedules Show Completed Successful I am new to the list... I occasionally have shedules show failed when, in fact, they were sucessful. If these schedules used the SQL-BackTrack for Informix agent, I have debug turned on and it shows sucessful completion (exit=0) and the dsmaccnt.log shows a "1" for normal exit (sucsess) and the usual amount of backup data. Using 3.7.3.6 on 4.3.2 server and 3.7.2 clients on mostly 4.3.2 clients but also some NT / Novell clients. Thanks for any tips. George Lesho Storage Admin AFC Enterprises
Re: Failed Schedules Show Completed Successful
--Win2K: APAR IC27196 There are other cases where scheduled backups fail but are reported as COMPLETED successfully back to the server. This is fixed in 4.1.2. It is my understanding that basically anything that should cause a schedule to show up as failed will not. IE. the client will display message "Scheduled event 'DAILYBACKUP' completed successfully." and send that result to the server. See APARS, IC27409 AND IC28653 for more info. This definitely does not only apply to WIN2K - possibly all platforms. I have seen it on Solaris and NT as with WIN2K. Any ANSE message that you may get on the client may not show the schduled as failing. Some examples are, server out of storage space, i/o error reading file on client, archive a file in use I have seen this on 3.7.201 and 4.11.16. I think this is fixed on 4.12 - but I just did a test where I put an invalid Drive letter in the Domain Statment, ran a scheduled incremental and the schedule completed successfully. I have seen postings in the past that this should give a failed schedule. Can Tivoli comment on this? Can they clarify what the problems actually are, what versions they are fixed on etc? These are major issues for customers if schedules are showing as completed successfully but actually are not. The only workaround is to monitor each client's logs individually. Tim Rushforth City of Winnipeg
Re: Failed Schedules Show Completed Successful
I am new to the list... I occasionally have shedules show failed when, in fact, they were sucessful. If these schedules used the SQL-BackTrack for Informix agent, I have debug turned on and it shows sucessful completion (exit=0) and the dsmaccnt.log shows a "1" for normal exit (sucsess) and the usual amount of backup data. Using 3.7.3.6 on 4.3.2 server and 3.7.2 clients on mostly 4.3.2 clients but also some NT / Novell clients. Thanks for any tips. George Lesho Storage Admin AFC Enterprises "Rushforth, Tim" [EMAIL PROTECTED] on 02/07/2001 11:40:38 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: Failed Schedules Show Completed Successful --Win2K: APAR IC27196 There are other cases where scheduled backups fail but are reported as COMPLETED successfully back to the server. This is fixed in 4.1.2. It is my understanding that basically anything that should cause a schedule to show up as failed will not. IE. the client will display message "Scheduled event 'DAILYBACKUP' completed successfully." and send that result to the server. See APARS, IC27409 AND IC28653 for more info. This definitely does not only apply to WIN2K - possibly all platforms. I have seen it on Solaris and NT as with WIN2K. Any ANSE message that you may get on the client may not show the schduled as failing. Some examples are, server out of storage space, i/o error reading file on client, archive a file in use I have seen this on 3.7.201 and 4.11.16. I think this is fixed on 4.12 - but I just did a test where I put an invalid Drive letter in the Domain Statment, ran a scheduled incremental and the schedule completed successfully. I have seen postings in the past that this should give a failed schedule. Can Tivoli comment on this? Can they clarify what the problems actually are, what versions they are fixed on etc? These are major issues for customers if schedules are showing as completed successfully but actually are not. The only workaround is to monitor each client's logs individually. Tim Rushforth City of Winnipeg
