Re: Backup larger than data on server
On 1/18/06, Paul Dudley <[EMAIL PROTECTED]> wrote: > We have TSM version 5.2. The client server I am referring to here is > Redhat linux. > > In the /var/log/tsm/dsmsched.log it lists > > Total number of bytes transferred:79.18 GB > > However there is only around 60 Gb of data on the server (see df below) > > FilesystemSize Used Avail Use% Mounted on > /dev/sda1 9.7G 2.1G 7.1G 23% / > /dev/sdb2 104G 57G 43G 58% /opt > > Can someone explain why the number of bytes transferred exceeds the > amount of data on the server? I think retransmits due to files changing during the backup (a common problem when backing up Linux boxes) will be counted each time even though only the last such transfer is actually kept by the server. It's been a while since I ran the TSM client on a Linux box, though, so I can't verify this, at least not yet. Kelly
Backup larger than data on server
We have TSM version 5.2. The client server I am referring to here is Redhat linux. In the /var/log/tsm/dsmsched.log it lists Total number of bytes transferred:79.18 GB However there is only around 60 Gb of data on the server (see df below) FilesystemSize Used Avail Use% Mounted on /dev/sda1 9.7G 2.1G 7.1G 23% / /dev/sdb2 104G 57G 43G 58% /opt Can someone explain why the number of bytes transferred exceeds the amount of data on the server? Thanks Paul Paul Dudley ANL IT Operations Dept. ANL Container Line [EMAIL PROTECTED] ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named addressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your system. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
Re: Restoring Novell Post offices
That's what it looked like to me too. The restore path was missing a colon and a trailing \ . >>> [EMAIL PROTECTED] 1/18/2006 2:02:07 PM >>> poa:restore/ ? >>> [EMAIL PROTECTED] 01/18/06 02:37PM >>> Troy thanks, If I wanted to restore a post office to a restore folder area on the same box using point-n-time (1/06/06) what would a command line restore look like? I have the the following which seems to be missing something restore pitd=1/06/2006 -pitt=07:00 -subdir=yes "docgw1/poa:\cohq*" poa/restore \01/062006 ?? Troy Frank wrote: > We have a separate "restore server" that we put all of our groupwise > restores onto. Because groupwise makes you restore the whole P.O. just > to get at one person's email, it would be a bit cumbersome for us to do > it on the live servers. On the groupwise servers themselves, I run a > "dsmc set access backup * * *" command to allow this. Since we retain > 60 versions, and backup once a day, I can go back to any point-in-time > within the last two months. When I want to run a restore, I type this > command on the restore server, from the dsmc commandline... > > restore -fromnode=srcserv -pitd=1/05/2006 -pitt=08:00:00 -subdir=yes > "srcserv/vol1:\apps\*" destserv/vol1:\srcservpo10506\ > > So the way I'm doing the point-in-time, if you want to restore the PO > from 1/4/2006, I do the point-in-time of the next morning, after the > backup would've run. The \srcservpo10506 is just the standard I use for > knowing which PO restore this is, you could just any folder you want. > > >>> [EMAIL PROTECTED] 1/13/2006 10:23 AM >>> > Hello, > > I am having trouble restoring a Novell Post office box using > point-n-time, > A client wants a restore using a specific data but the file structure > doesn't > for that date. But when I do normal restore without point n time I see > the file structure. Does anyone have a specific way they restore > post office mail boxes in Novell I have never had this problem > before. > > Novell 6.5 > TSM client 5.2.2 > > Confidentiality Notice follows: > > The information in this message (and the documents attached to it, if any) > is confidential and may be legally privileged. It is intended solely for > the addressee. Access to this message by anyone else is unauthorized. If > you are not the intended recipient, any disclosure, copying, distribution > or any action taken, or omitted to be taken in reliance on it is > prohibited and may be unlawful. If you have received this message in > error, please delete all electronic copies of this message (and the > documents attached to it, if any), destroy any hard copies you may have > created and notify me immediately by replying to this email. Thank you. - CONFIDENTIALITY NOTICE: This message is confidential, intended only for the named recipient(s) and may contain information that is privileged, or exempt from disclosure under applicable law. If you are not the intended recipient(s), you are notified that the dissemination, distribution or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender by reply e-mail, delete this e-mail from your computer, and destroy any copies in any form immediately. Receipt by anyone other than the named recipient(s) is not a waiver of any attorney-client, work product, or other applicable privilege. This message and all contents may be reviewed by authorized parties of the Catholic Health System other than those named in the message header. The contents of this message do not bind the Catholic Health System to any contract, position, or course of action unless the sender is specifically authorized to enter into contracts on behalf of the Catholic Health System. The contents of this message do not necessarily constitute an official representation of the Catholic Health System. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: acsls library client query path etc ...
I'm have a similar setup and it's true, the library client has no paths and no drives. So, q libv won't work either, only the library manager sees these volumes. Gerald Michalak [EMAIL PROTECTED] "ADSM: Dist Stor Manager" wrote on 01/18/2006 02:12:42 PM: > Just trying out library sharing, following documentation in the admin guide > > Configuring ACSLS-Managed Libraries > http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp? > topic=/com.ibm.itsmaixn.doc/anragd53147.htm > > Apparently working fine, as library client mounts/reads/writes tapes as > expected. My question: is it expected behavior that 'query path' info is > not available from the library client? For test purposes we've shared > three drives here: > > from library manager server ADSM: > > tsm: ADSM>query path > Source Name Source Type Destination Destination On-Line > NameType > --- --- --- --- --- > ADSMSERVER A1F0MT04DRIVE Yes > ADSMSERVER A1F0MT05DRIVE Yes > ADSMSERVER A1F1MT09DRIVE Yes > ADSMSERVER A0F0MT00DRIVE Yes > ADSMSERVER A0F0MT01DRIVE Yes > ADSMSERVER A0F0MT02DRIVE Yes > ADSMSERVER A0F0MT03DRIVE Yes > ADSMSERVER A0F1MT06DRIVE Yes > ADSMSERVER A0F1MT07DRIVE Yes > ADSMSERVER A0F1MT08DRIVE Yes > TSM SERVER A1F0MT04DRIVE Yes > TSM SERVER A1F0MT05DRIVE Yes > TSM SERVER A1F1MT09DRIVE Yes > > from library client server TSM: > > tsm: TSM>query path > ANR2034E QUERY PATH: No match found using this criteria. > ANS8001I Return code 11. > > thanks, > -Robert
Re: TDP for Domino error
Robert, Are you seeing these timeout errors in Domino? I thought this article was interesting. *** Brenda Stephenson Utah Retirement Systems Information Technology Phone: 801-366-7363 Email: [EMAIL PROTECTED] Steve S Lafrance <[EMAIL PROTECTED] M> To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: [ADSM-L] TDP for Domino error 01/18/2006 12:35 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> "Backup terminated due to timeout" message is coming from the Domino API. By default the Notes API functions (called by the TDP) allow 15 minutes for each backup unit to complete before timing out. This is to prevent any potential server hangs that could prevent the backup from completing. . To increase the timeout interval use the notes.ini parameter BACKUP_TIMEOUT=xx where xx is the number of minutes to allow for the backup before timing out. I would suggest to put 60 minutes. Best Regards, Steve Zoltan Forray/AC/VCU <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/18/2006 02:18:21 PM Please respond to "ADSM: Dist Stor Manager" Sent by:"ADSM: Dist Stor Manager" To:ADSM-L@VM.MARIST.EDU cc: Subject:Re: TDP for Domino error I am seeing the exact same problem. What TDP level are you on ? What platform ? Are you getting the rc=18 ? I don't know why it is going to tape since the storagepool is not full and there are no thresholds set that would force it. Mario Behring <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/18/2006 01:53 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] TDP for Domino error Hi list, When backing up .NSF files from Domino some boxes are being missed every time TSM asks for a new tape to be mounted (this is a manual tape unit), no matter how long the operator takes to put a scratch tape to be mounted. Please see the error message at the domssch.log below: 18-01-2006 03:04:54 Backup de sav\savquar.nsf failed 18-01-2006 03:04:54 Backup terminated due to timeout The error code at the actlog is ANE4993E and it simply says that the backup has failed. Any help is appreciated. Thanks. Mario - Yahoo! Photos ? Showcase holiday pictures in hardcover Photo Books. You design it and we?ll bind it!
EMC Centera
Hi team, We are in the process of testing an EMC Centera as a storage repository for TSM. We find the following snippet in: Technical Changes for Version 5 Release 2 -- January 2004 EMC Centera Support ... Centera devices can also be used as standard storage devices if no mandatory retention requirements exist for the data. ... We have no "mandatory retention requirements" We just want TSM to control retention like he always has on other devices. Now, by following the FM closely we are able to get data written to, read from, the Centera BUT when our storage admin types do their periodic housecleaning, unbeknown to TSM, all the TSM data is deleted. Apparently there is an attribute of "deleteable" or "not deleteable" somewhere in that box and TSM is not setting it. Anyone have any knowledge/advice on how to get TSM and EMC Centera to agree on retention controls? TIA, Ted Spendlove ATK Thiokol Propulsion
acsls library client query path etc ...
Just trying out library sharing, following documentation in the admin guide Configuring ACSLS-Managed Libraries http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmaixn.doc/anragd53147.htm Apparently working fine, as library client mounts/reads/writes tapes as expected. My question: is it expected behavior that 'query path' info is not available from the library client? For test purposes we've shared three drives here: from library manager server ADSM: tsm: ADSM>query path Source Name Source Type Destination Destination On-Line NameType --- --- --- --- --- ADSMSERVER A1F0MT04DRIVE Yes ADSMSERVER A1F0MT05DRIVE Yes ADSMSERVER A1F1MT09DRIVE Yes ADSMSERVER A0F0MT00DRIVE Yes ADSMSERVER A0F0MT01DRIVE Yes ADSMSERVER A0F0MT02DRIVE Yes ADSMSERVER A0F0MT03DRIVE Yes ADSMSERVER A0F1MT06DRIVE Yes ADSMSERVER A0F1MT07DRIVE Yes ADSMSERVER A0F1MT08DRIVE Yes TSM SERVER A1F0MT04DRIVE Yes TSM SERVER A1F0MT05DRIVE Yes TSM SERVER A1F1MT09DRIVE Yes from library client server TSM: tsm: TSM>query path ANR2034E QUERY PATH: No match found using this criteria. ANS8001I Return code 11. thanks, -Robert
Re: Restoring Novell Post offices
poa:restore/ ? >>> [EMAIL PROTECTED] 01/18/06 02:37PM >>> Troy thanks, If I wanted to restore a post office to a restore folder area on the same box using point-n-time (1/06/06) what would a command line restore look like? I have the the following which seems to be missing something restore pitd=1/06/2006 -pitt=07:00-subdir=yes "docgw1/poa:\cohq*" poa/restore \01/062006 ?? Troy Frank wrote: > We have a separate "restore server" that we put all of our groupwise > restores onto. Because groupwise makes you restore the whole P.O. just > to get at one person's email, it would be a bit cumbersome for us to do > it on the live servers. On the groupwise servers themselves, I run a > "dsmc set access backup * * *" command to allow this. Since we retain > 60 versions, and backup once a day, I can go back to any point-in-time > within the last two months. When I want to run a restore, I type this > command on the restore server, from the dsmc commandline... > > restore -fromnode=srcserv -pitd=1/05/2006 -pitt=08:00:00 -subdir=yes > "srcserv/vol1:\apps\*" destserv/vol1:\srcservpo10506\ > > So the way I'm doing the point-in-time, if you want to restore the PO > from 1/4/2006, I do the point-in-time of the next morning, after the > backup would've run. The \srcservpo10506 is just the standard I use for > knowing which PO restore this is, you could just any folder you want. > > >>> [EMAIL PROTECTED] 1/13/2006 10:23 AM >>> > Hello, > > I am having trouble restoring a Novell Post office box using > point-n-time, > A client wants a restore using a specific data but the file structure > doesn't > for that date. But when I do normal restore without point n time I see > the file structure. Does anyone have a specific way they restore > post office mail boxes in Novell I have never had this problem > before. > > Novell 6.5 > TSM client 5.2.2 > > Confidentiality Notice follows: > > The information in this message (and the documents attached to it, if any) > is confidential and may be legally privileged. It is intended solely for > the addressee. Access to this message by anyone else is unauthorized. If > you are not the intended recipient, any disclosure, copying, distribution > or any action taken, or omitted to be taken in reliance on it is > prohibited and may be unlawful. If you have received this message in > error, please delete all electronic copies of this message (and the > documents attached to it, if any), destroy any hard copies you may have > created and notify me immediately by replying to this email. Thank you. - CONFIDENTIALITY NOTICE: This message is confidential, intended only for the named recipient(s) and may contain information that is privileged, or exempt from disclosure under applicable law. If you are not the intended recipient(s), you are notified that the dissemination, distribution or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender by reply e-mail, delete this e-mail from your computer, and destroy any copies in any form immediately. Receipt by anyone other than the named recipient(s) is not a waiver of any attorney-client, work product, or other applicable privilege. This message and all contents may be reviewed by authorized parties of the Catholic Health System other than those named in the message header. The contents of this message do not bind the Catholic Health System to any contract, position, or course of action unless the sender is specifically authorized to enter into contracts on behalf of the Catholic Health System. The contents of this message do not necessarily constitute an official representation of the Catholic Health System.
Re: Restoring Novell Post offices
Troy thanks, If I wanted to restore a post office to a restore folder area on the same box using point-n-time (1/06/06) what would a command line restore look like? I have the the following which seems to be missing something restore pitd=1/06/2006 -pitt=07:00-subdir=yes "docgw1/poa:\cohq*" poa/restore \01/062006 ?? Troy Frank wrote: > We have a separate "restore server" that we put all of our groupwise > restores onto. Because groupwise makes you restore the whole P.O. just > to get at one person's email, it would be a bit cumbersome for us to do > it on the live servers. On the groupwise servers themselves, I run a > "dsmc set access backup * * *" command to allow this. Since we retain > 60 versions, and backup once a day, I can go back to any point-in-time > within the last two months. When I want to run a restore, I type this > command on the restore server, from the dsmc commandline... > > restore -fromnode=srcserv -pitd=1/05/2006 -pitt=08:00:00 -subdir=yes > "srcserv/vol1:\apps\*" destserv/vol1:\srcservpo10506\ > > So the way I'm doing the point-in-time, if you want to restore the PO > from 1/4/2006, I do the point-in-time of the next morning, after the > backup would've run. The \srcservpo10506 is just the standard I use for > knowing which PO restore this is, you could just any folder you want. > > >>> [EMAIL PROTECTED] 1/13/2006 10:23 AM >>> > Hello, > > I am having trouble restoring a Novell Post office box using > point-n-time, > A client wants a restore using a specific data but the file structure > doesn't > for that date. But when I do normal restore without point n time I see > the file structure. Does anyone have a specific way they restore > post office mail boxes in Novell I have never had this problem > before. > > Novell 6.5 > TSM client 5.2.2 > > Confidentiality Notice follows: > > The information in this message (and the documents attached to it, if any) > is confidential and may be legally privileged. It is intended solely for > the addressee. Access to this message by anyone else is unauthorized. If > you are not the intended recipient, any disclosure, copying, distribution > or any action taken, or omitted to be taken in reliance on it is > prohibited and may be unlawful. If you have received this message in > error, please delete all electronic copies of this message (and the > documents attached to it, if any), destroy any hard copies you may have > created and notify me immediately by replying to this email. Thank you.
Re: TDP for Domino error
"Backup terminated due to timeout" message is coming from the Domino API. By default the Notes API functions (called by the TDP) allow 15 minutes for each backup unit to complete before timing out. This is to prevent any potential server hangs that could prevent the backup from completing. . To increase the timeout interval use the notes.ini parameter BACKUP_TIMEOUT=xx where xx is the number of minutes to allow for the backup before timing out. I would suggest to put 60 minutes. Best Regards, Steve Zoltan Forray/AC/VCU <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/18/2006 02:18:21 PM Please respond to "ADSM: Dist Stor Manager" Sent by:"ADSM: Dist Stor Manager" To:ADSM-L@VM.MARIST.EDU cc: Subject:Re: TDP for Domino error I am seeing the exact same problem. What TDP level are you on ? What platform ? Are you getting the rc=18 ? I don't know why it is going to tape since the storagepool is not full and there are no thresholds set that would force it. Mario Behring <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/18/2006 01:53 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] TDP for Domino error Hi list, When backing up .NSF files from Domino some boxes are being missed every time TSM asks for a new tape to be mounted (this is a manual tape unit), no matter how long the operator takes to put a scratch tape to be mounted. Please see the error message at the domssch.log below: 18-01-2006 03:04:54 Backup de sav\savquar.nsf failed 18-01-2006 03:04:54 Backup terminated due to timeout The error code at the actlog is ANE4993E and it simply says that the backup has failed. Any help is appreciated. Thanks. Mario - Yahoo! Photos ? Showcase holiday pictures in hardcover Photo Books. You design it and we?ll bind it!
Re: TDP for Domino error
On Jan 18, 2006, at 1:53 PM, Mario Behring wrote: Hi list, When backing up .NSF files from Domino some boxes are being missed every time TSM asks for a new tape to be mounted (this is a manual tape unit), no matter how long the operator takes to put a scratch tape to be mounted. Please see the error message at the domssch.log below: 18-01-2006 03:04:54 Backup de sav\savquar.nsf failed 18-01-2006 03:04:54 Backup terminated due to timeout Mario - See IBM Technote 1168988 on this one: seems like a Domino issue. Richard Sims
Re: TDP for Domino error
I am seeing the exact same problem. What TDP level are you on ? What platform ? Are you getting the rc=18 ? I don't know why it is going to tape since the storagepool is not full and there are no thresholds set that would force it. Mario Behring <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/18/2006 01:53 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] TDP for Domino error Hi list, When backing up .NSF files from Domino some boxes are being missed every time TSM asks for a new tape to be mounted (this is a manual tape unit), no matter how long the operator takes to put a scratch tape to be mounted. Please see the error message at the domssch.log below: 18-01-2006 03:04:54 Backup de sav\savquar.nsf failed 18-01-2006 03:04:54 Backup terminated due to timeout The error code at the actlog is ANE4993E and it simply says that the backup has failed. Any help is appreciated. Thanks. Mario - Yahoo! Photos ? Showcase holiday pictures in hardcover Photo Books. You design it and we?ll bind it!
Re: Failed Attempt to Free Memory
On Jan 18, 2006, at 1:01 PM, Aaron Becar wrote: Here is the actual Error: ANRD Invalid attempt to free memory (invalid header); called from 8217515 (bfutil.c (4599)). ANRD Invalid attempt to free memory (invalid header); called from 8217515 (bfutil.c (4599)). Aaron - One cause of that kind of error has been when migration can't work because the its target storage pool is not writable. Check your Activity Log for any preceding ANR messages which may lend more info. If the server crashed, it may produce a dsmserv.err file with some failure-time info. Richard Sims
TDP for Domino error
Hi list, When backing up .NSF files from Domino some boxes are being missed every time TSM asks for a new tape to be mounted (this is a manual tape unit), no matter how long the operator takes to put a scratch tape to be mounted. Please see the error message at the domssch.log below: 18-01-2006 03:04:54 Backup de sav\savquar.nsf failed 18-01-2006 03:04:54 Backup terminated due to timeout The error code at the actlog is ANE4993E and it simply says that the backup has failed. Any help is appreciated. Thanks. Mario - Yahoo! Photos Showcase holiday pictures in hardcover Photo Books. You design it and well bind it!
IBM 3583 LTO issue/messages
Our wonderful 3583/3580 LTO2 drives/library have started to issue these strange messages. I have not been able to find anything (other than really old APARS) on what is causing it and why, much less what to do about it ? Is this a hardware problem ? The server is 5.3 on AIX ! 1/18/2006 12:27:32 PM ANRD mmsscsi.c(17625): ThreadId Could not find elements in lib IBM3583-L72-2: src = 257, tgt = 4103.
Re: dbcopy, logcopy; Copy Status: Off-Line/Sync
Thank you for your answer. Yes, I think, this command is the right one I am looking for. Best regards Christine John Monahan schrieb: If I understand correctly, I believe you are looking for the VARY ONLINE command. __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com Christiane Kühn <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/18/2006 11:38 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] dbcopy, logcopy; Copy Status: Off-Line/Sync Hallo, I have a question to the Status of dbcopy, logcopy: sync/off-line. I don`t find a command to get the status from off-line to sync (for example: update dbcopy.) The situation: I want to make a copy-synconisation of the db and log - Files (3 times) No problem: define dbcopy/logcopy works wonderful. The Server is a Windows 2003 with tsm 5.3.2.2 One Copy is on the disk D: the other 2 Copies are on a raid-system. Now the problem: If one disk has no connection to the system (hardware-error, net-problems...) the tsm-system works wonderful further with the disk, which is accessible for the system. And the non accessible disks changed the status from sync to off-line. To change the status from off-line to sync, we need two commands: delete dbvol ... and define dbcopy ... The same problem is with the log-files. I need the command update dbcopy/logcopy ... Can somebody help me by this wish? Christiane Kühn -- Institut für Informatik Christiane Kühn Tel.: 0228/73-4200 Römerstraße 164 Fax.: 0228/7360304 53117 Bonn Email: [EMAIL PROTECTED]
dbcopy, logcopy; Copy Status: Off-Line/Sync
Hallo, I have a question to the Status of dbcopy, logcopy: sync/off-line. I don`t find a command to get the status from off-line to sync (for example: update dbcopy.) The situation: I want to make a copy-synconisation of the db and log - Files (3 times) No problem: define dbcopy/logcopy works wonderful. The Server is a Windows 2003 with tsm 5.3.2.2 One Copy is on the disk D: the other 2 Copies are on a raid-system. Now the problem: If one disk has no connection to the system (hardware-error, net-problems...) the tsm-system works wonderful further with the disk, which is accessible for the system. And the non accessible disks changed the status from sync to off-line. To change the status from off-line to sync, we need two commands: delete dbvol ... and define dbcopy ... The same problem is with the log-files. I need the command update dbcopy/logcopy ... Can somebody help me by this wish? Christiane Kühn -- Institut für Informatik Christiane Kühn Tel.: 0228/73-4200 Römerstraße 164 Fax.: 0228/7360304 53117 Bonn Email: [EMAIL PROTECTED]
Re: Failed Attempt to Free Memory
Here is the actual Error: ANRD Invalid attempt to free memory (invalid header); called from 8217515 (bfutil.c (4599)). ANRD Invalid attempt to free memory (invalid header); called from 8217515 (bfutil.c (4599)). . . . . . . . . . . CAPOOT goes TSM * Orig. Message.. Hey all, I kind of have a serious question. I have been looking at a specific error that we have been receiving. I understand that there have been some problems with offsite reclamation, that if the data is not moved off the disk there is a possibility of TSM crashing. However, I have disabled all the automated schedules, and perform migration myself to make sure that all the data is moved off the disk onto the tapepool. I then proceed to do a reclamation of our offsite tapes (copypool) and sure enough I see error after error that there is a failed attempt to free memory, and capoot goes TSM. I hear this is because of an un initialized variable. I made sure that everything is moved off disk and onto tape. IBM did a diagnostics on our server and came and replaced the controller card, so pretty sure this is not a hardware issue. Here are the specs: Box: IBM x346 OS: RH EL 4 TSM: 5.2.6 Lib: IBM 3583 w/ 3 LTO 2 drives. There error mentions the bufutil.c (something like that). Thanks! Aaron
Re: dbcopy, logcopy; Copy Status: Off-Line/Sync
If I understand correctly, I believe you are looking for the VARY ONLINE command. __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com Christiane Kühn <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/18/2006 11:38 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] dbcopy, logcopy; Copy Status: Off-Line/Sync Hallo, I have a question to the Status of dbcopy, logcopy: sync/off-line. I don`t find a command to get the status from off-line to sync (for example: update dbcopy.) The situation: I want to make a copy-synconisation of the db and log - Files (3 times) No problem: define dbcopy/logcopy works wonderful. The Server is a Windows 2003 with tsm 5.3.2.2 One Copy is on the disk D: the other 2 Copies are on a raid-system. Now the problem: If one disk has no connection to the system (hardware-error, net-problems...) the tsm-system works wonderful further with the disk, which is accessible for the system. And the non accessible disks changed the status from sync to off-line. To change the status from off-line to sync, we need two commands: delete dbvol ... and define dbcopy ... The same problem is with the log-files. I need the command update dbcopy/logcopy ... Can somebody help me by this wish? Christiane Kühn -- Institut für Informatik Christiane Kühn Tel.: 0228/73-4200 Römerstraße 164 Fax.: 0228/7360304 53117 Bonn Email: [EMAIL PROTECTED]
Re: Ports used by DSMCAD
Ok, dsmcad uses ephemeral port to listen into, unless specified by webports option. webports but is seems that using dsmcad, it ignores tcpclientport option, as I tried tcpclientport 1501 webports 1501 1581 and had no conflict problems. http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmc.doc/update/ans1197.htm On 1/18/06, Helder Garcia <[EMAIL PROTECTED]> wrote: > Hi all, > > I have > TSM Server 5.3.2 - AIX 5.1 > TSM Client 5.2.2 - Windows NT > > After first installation of client using dsmcad I have on client options file > > TCPCLIENTPORT1501 > HTTPPORT 1581 > MANAGEDSERVICE WEBCLIENT SCHEDULE > > First schedule missed and got below message on server console: > > ANR2716E Schedule prompter was not able to contact client > using type 1 (xxx.xxx.xxx.xxx 1803). > > After a restart of dsmcad same schedule (actually a client action) > restarted and had success. > > The question is: WHY server was trying to connect client on port 1803??? > > A netstat -an on windows machine just gave me a LISTEN state for port > 1581, not 1501. > > Any help? > Thanks. > -- > Helder Garcia > -- Helder Garcia
ANR0150E: Password Error: decrypting password
Hallo, We have a Windows System Server 2003 (ServicePack 1) with TSM-Server: 5.3.2.2 We need an Server to Server connection. The other Server is a AIX-RS/6000: TSM 5.1.10 sytem. We get the Error: ANR0150E Failed to open Server RHRZ_TSM. There was an error decrypting the Virtual Volumes password. (SESSION: 2358, PROCESS: 17) 16.01.2006 10:43:13 ANR1651E Server information for RHRZ_TSM is not available. (SESSION: 2358, PROCESS: 17) 16.01.2006 10:43:13 ANR4374E Session failure, source server detected an internal error. (SESSION: 2358, PROCESS: 17) 16.01.2006 10:43:13 ANR4578E Database backup/restore terminated - required volume was not mounted. (SESSION: 2358, PROCESS: 17) Can somebody help me, to handle this error. I have get an note, that this error will be fixed in Version: 5.3.3 Is there an patch for the TSM-Server: Windows: Version 5.3.2.2 Thank you for your help. Best regards Christiane Kühn Institut für Informatik Christiane Kühn Tel.: 0228/73-4200 Römerstraße 164 Fax.: 0228/7360304 53117 Bonn Email: [EMAIL PROTECTED] -- Institut für Informatik Christiane Kühn Tel.: 0228/73-4200 Römerstraße 164 Fax.: 0228/7360304 53117 Bonn Email: [EMAIL PROTECTED]
Re: Ports used by DSMCAD
Ok, dsmcas uses ephemeral port to listen into, unless specified by webports option. webports but is seems that using dsmcad, it ignores tcpclientport option, as I tried tcpclientport 1501 webports 1501 1581 and had no conflict problems. http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmc.doc/update/ans1197.htm On 1/18/06, Helder Garcia <[EMAIL PROTECTED]> wrote: > Hi all, > > I have > TSM Server 5.3.2 - AIX 5.1 > TSM Client 5.2.2 - Windows NT > > After first installation of client using dsmcad I have on client options file > > TCPCLIENTPORT1501 > HTTPPORT 1581 > MANAGEDSERVICE WEBCLIENT SCHEDULE > > First schedule missed and got below message on server console: > > ANR2716E Schedule prompter was not able to contact client > using type 1 (xxx.xxx.xxx.xxx 1803). > > After a restart of dsmcad same schedule (actually a client action) > restarted and had success. > > The question is: WHY server was trying to connect client on port 1803??? > > A netstat -an on windows machine just gave me a LISTEN state for port > 1581, not 1501. > > Any help? > Thanks. > -- > Helder Garcia > -- Helder Garcia
Re: -nodename no longer there for UNIX...
Eric, yes, I have already forwarded this to our doc folks. Like -nodename, -tcpserveraddress has never been supported from the Unix command line. 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" wrote on 01/18/2006 09:03:46 AM: > Hi Andy! > Thank you very much for your reply! > Bummer... This requires me to alter (add the stanza) the dsm.sys which > was something I wanted to prevent for an occasional restore... > I didn't see this listed in the APAR, but that parameter also seems to > be incorrectly documented then, right? > Kindest regards, > Eric van Loon > > > -Original Message- > From: Andrew Raibeck [mailto:[EMAIL PROTECTED] > Sent: woensdag 18 januari 2006 16:50 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: -nodename no longer there for UNIX... > > Hi Eric, > > Nope, -tcpserveraddress is also not valid from the command line. > > Instead, use the -SERVERNAME option, which refers to a stanza in dsm.sys > that identifies the TSM server. > > 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/IBMTivoliStorag > eManager.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" wrote on 01/18/2006 > 08:43:42 AM: > > > Hi Andy (and of course Richard!)! > > Thank you very much for your reply! > > I thought that all parameters were equal across all clients, but I was > > wrong. > > The VIRTUALNODE parameter appears to do exactly what I want, but now > > another issue arises. I would like to create a single line command to > do > > a cross client restore and my clients are spread across two TSM > servers. > > So I thought of using the -TCPSERVERADDRESS parameter to cover this. > > I issue the following command: > > Dsmc -virtualnode= -tcpserveradddress= > > This results in a: > > ANS1108E Invalid option (-TCPSERVERADDRESS) for the LOOP command > > The manual GC32-0789-05 states that it is a valid option... > > Thank you very much for your help! > > Kindest regards, > > Eric van Loon > > > > -Original Message- > > From: Andrew Raibeck [mailto:[EMAIL PROTECTED] > > Sent: woensdag 18 januari 2006 14:50 > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: -nodename no longer there for UNIX... > > > > Hi Eric, > > > > Of course, NODENAME remains a valid option for the dsm.sys file. It > has > > never been valid from the command line. IC46024 seems to refer to only > a > > doc error. > > > > You can try -VIRTUALNODENAME from the command line > > > > 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/IBMTivoliStorag > > eManager.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" wrote on 01/18/2006 > > 06:32:15 AM: > > > > > Hi *SM-ers! > > > Does anybody know why IBM decided to drop the -nodename parameter > for > > > the UNIX clients? > > > I discovered that this parameter no longer works in 5.3. It's > > documented > > > in the manuals but that's not correct (IC46024). > > > I'm trying to find a way to give our standby a way to restore data > > from > > > another node, without the help of a TSM admin. I know there is a > > > -fromnode parameter, but that requires a lot of extra work > (accessing > > > the source node, updating the node access list, restoring the file > on > > > the target server, again accessing the source server, removing the > > node > > > from the access list). It would be so much easier when one could use > > the > > > -nodename parameter! And I really cannot think of any reason why it > > was > > > dropped! > > > I would like to know how other people solve this. Thanks in advance > > for > > > any reply! > > > Kindest regards, > > > Eric van Loon > > > > > > > > > > ** > > > For information, services and offers, please visit our web site: > > > http://www.klm.com. This e-mail and any attachment may contain > > > confide
Antwort: Re: Windows HSM experiences?
hello allen, you describe mixed solution with tsm and hsm, let us view tsm: you will only have two sorts of files on the filesystem: the original file or (after hsm migration) the stub (or not, it depends on the hsm configuration) so tsm will have the stub and the original file in its storage, how many of them depends on the copygroup parameters. often the active version will be the stub file hsm: hsm migrates the file and the file is in the tsm storage, stub file is left. so you have to mention both hsm and tsm parameters very carefuly, that no data is lost. when you restore the filesystem, you can decide to do it with tsm, then a mix of stub files and original files is restored (this is exact the filesystem as it was at last tsm backup), or you can restore with hsm, then all original files are restored. with best regards stefan savoric
Re: -nodename no longer there for UNIX...
Hi Andy! Thank you very much for your reply! Bummer... This requires me to alter (add the stanza) the dsm.sys which was something I wanted to prevent for an occasional restore... I didn't see this listed in the APAR, but that parameter also seems to be incorrectly documented then, right? Kindest regards, Eric van Loon -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: woensdag 18 januari 2006 16:50 To: ADSM-L@VM.MARIST.EDU Subject: Re: -nodename no longer there for UNIX... Hi Eric, Nope, -tcpserveraddress is also not valid from the command line. Instead, use the -SERVERNAME option, which refers to a stanza in dsm.sys that identifies the TSM server. 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/IBMTivoliStorag eManager.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" wrote on 01/18/2006 08:43:42 AM: > Hi Andy (and of course Richard!)! > Thank you very much for your reply! > I thought that all parameters were equal across all clients, but I was > wrong. > The VIRTUALNODE parameter appears to do exactly what I want, but now > another issue arises. I would like to create a single line command to do > a cross client restore and my clients are spread across two TSM servers. > So I thought of using the -TCPSERVERADDRESS parameter to cover this. > I issue the following command: > Dsmc -virtualnode= -tcpserveradddress= > This results in a: > ANS1108E Invalid option (-TCPSERVERADDRESS) for the LOOP command > The manual GC32-0789-05 states that it is a valid option... > Thank you very much for your help! > Kindest regards, > Eric van Loon > > -Original Message- > From: Andrew Raibeck [mailto:[EMAIL PROTECTED] > Sent: woensdag 18 januari 2006 14:50 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: -nodename no longer there for UNIX... > > Hi Eric, > > Of course, NODENAME remains a valid option for the dsm.sys file. It has > never been valid from the command line. IC46024 seems to refer to only a > doc error. > > You can try -VIRTUALNODENAME from the command line > > 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/IBMTivoliStorag > eManager.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" wrote on 01/18/2006 > 06:32:15 AM: > > > Hi *SM-ers! > > Does anybody know why IBM decided to drop the -nodename parameter for > > the UNIX clients? > > I discovered that this parameter no longer works in 5.3. It's > documented > > in the manuals but that's not correct (IC46024). > > I'm trying to find a way to give our standby a way to restore data > from > > another node, without the help of a TSM admin. I know there is a > > -fromnode parameter, but that requires a lot of extra work (accessing > > the source node, updating the node access list, restoring the file on > > the target server, again accessing the source server, removing the > node > > from the access list). It would be so much easier when one could use > the > > -nodename parameter! And I really cannot think of any reason why it > was > > dropped! > > I would like to know how other people solve this. Thanks in advance > for > > any reply! > > Kindest regards, > > Eric van Loon > > > > > > ** > > 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. > > ** > > > ** > For information, services and offers, please visit our web site: > http://
Re: -nodename no longer there for UNIX...
Hi Eric, Nope, -tcpserveraddress is also not valid from the command line. Instead, use the -SERVERNAME option, which refers to a stanza in dsm.sys that identifies the TSM server. 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" wrote on 01/18/2006 08:43:42 AM: > Hi Andy (and of course Richard!)! > Thank you very much for your reply! > I thought that all parameters were equal across all clients, but I was > wrong. > The VIRTUALNODE parameter appears to do exactly what I want, but now > another issue arises. I would like to create a single line command to do > a cross client restore and my clients are spread across two TSM servers. > So I thought of using the -TCPSERVERADDRESS parameter to cover this. > I issue the following command: > Dsmc -virtualnode= -tcpserveradddress= > This results in a: > ANS1108E Invalid option (-TCPSERVERADDRESS) for the LOOP command > The manual GC32-0789-05 states that it is a valid option... > Thank you very much for your help! > Kindest regards, > Eric van Loon > > -Original Message- > From: Andrew Raibeck [mailto:[EMAIL PROTECTED] > Sent: woensdag 18 januari 2006 14:50 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: -nodename no longer there for UNIX... > > Hi Eric, > > Of course, NODENAME remains a valid option for the dsm.sys file. It has > never been valid from the command line. IC46024 seems to refer to only a > doc error. > > You can try -VIRTUALNODENAME from the command line > > 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/IBMTivoliStorag > eManager.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" wrote on 01/18/2006 > 06:32:15 AM: > > > Hi *SM-ers! > > Does anybody know why IBM decided to drop the -nodename parameter for > > the UNIX clients? > > I discovered that this parameter no longer works in 5.3. It's > documented > > in the manuals but that's not correct (IC46024). > > I'm trying to find a way to give our standby a way to restore data > from > > another node, without the help of a TSM admin. I know there is a > > -fromnode parameter, but that requires a lot of extra work (accessing > > the source node, updating the node access list, restoring the file on > > the target server, again accessing the source server, removing the > node > > from the access list). It would be so much easier when one could use > the > > -nodename parameter! And I really cannot think of any reason why it > was > > dropped! > > I would like to know how other people solve this. Thanks in advance > for > > any reply! > > Kindest regards, > > Eric van Loon > > > > > > ** > > 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. > > ** > > > ** > 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. Koninkli
Re: -nodename no longer there for UNIX...
Hi Andy (and of course Richard!)! Thank you very much for your reply! I thought that all parameters were equal across all clients, but I was wrong. The VIRTUALNODE parameter appears to do exactly what I want, but now another issue arises. I would like to create a single line command to do a cross client restore and my clients are spread across two TSM servers. So I thought of using the -TCPSERVERADDRESS parameter to cover this. I issue the following command: Dsmc -virtualnode= -tcpserveradddress= This results in a: ANS1108E Invalid option (-TCPSERVERADDRESS) for the LOOP command The manual GC32-0789-05 states that it is a valid option... Thank you very much for your help! Kindest regards, Eric van Loon -Original Message- From: Andrew Raibeck [mailto:[EMAIL PROTECTED] Sent: woensdag 18 januari 2006 14:50 To: ADSM-L@VM.MARIST.EDU Subject: Re: -nodename no longer there for UNIX... Hi Eric, Of course, NODENAME remains a valid option for the dsm.sys file. It has never been valid from the command line. IC46024 seems to refer to only a doc error. You can try -VIRTUALNODENAME from the command line 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/IBMTivoliStorag eManager.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" wrote on 01/18/2006 06:32:15 AM: > Hi *SM-ers! > Does anybody know why IBM decided to drop the -nodename parameter for > the UNIX clients? > I discovered that this parameter no longer works in 5.3. It's documented > in the manuals but that's not correct (IC46024). > I'm trying to find a way to give our standby a way to restore data from > another node, without the help of a TSM admin. I know there is a > -fromnode parameter, but that requires a lot of extra work (accessing > the source node, updating the node access list, restoring the file on > the target server, again accessing the source server, removing the node > from the access list). It would be so much easier when one could use the > -nodename parameter! And I really cannot think of any reason why it was > dropped! > I would like to know how other people solve this. Thanks in advance for > any reply! > Kindest regards, > Eric van Loon > > > ** > 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. > ** ** 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: Failed Attempt to Free Memory
Sounds like its time for a Severity 1 call to Tivoli Support. >>> [EMAIL PROTECTED] 01/17/06 4:57 PM >>> Hey all, I kind of have a serious question. I have been looking at a specific error that we have been receiving. I understand that there have been some problems with offsite reclamation, that if the data is not moved off the disk there is a possibility of TSM crashing. However, I have disabled all the automated schedules, and perform migration myself to make sure that all the data is moved off the disk onto the tapepool. I then proceed to do a reclamation of our offsite tapes (copypool) and sure enough I see error after error that there is a failed attempt to free memory, and capoot goes TSM. I hear this is because of an un initialized variable. I made sure that everything is moved off disk and onto tape. IBM did a diagnostics on our server and came and replaced the controller card, so pretty sure this is not a hardware issue. Here are the specs: Box: IBM x346 OS: RH EL 4 TSM: 5.2.6 Lib: IBM 3583 w/ 3 LTO 2 drives. There error mentions the bufutil.c (something like that). Thanks! Aaron
Re: Windows HSM experiences?
>> On Tue, 17 Jan 2006 13:28:36 -0500, Richard Rhodes <[EMAIL PROTECTED]> said: > We are a Novell shop that has made a decision to migrate to Windows > for file and print serving. There is talk about implementing the > HSM client for Windows to help "solve" disk space problems. > Is anyone using Windows HSM client and what are your experiences > with it - good and bad. I had a bad experience with it; it was the presentation about it in Oxford. The Windows HSM implementation is very very different from the unix one. One example: If you have a HSM filesystem, and you put a file down: Day 1: You run an incr, and back up the file. Day 1.1: HSM decides to migrate your file. A stub is left. Day 2: You run an incr, and back up the stub. (!) Yes, your actual backup is now inactive. I asked about this three times. HSM might not migrate the file immediately, of course. But whenever it does, you'll cut a new copy of the (from your perspective 'unchanged') file, and make the complete version inactive. If you later retrieve the (in your opinion unchanged) file, the next incr will make another new version, and for a while your active version will be the full file. The long and short of it was that the presenter felt the Windows HSM client was appropriate for very, very static filespaces; perhaps PDF output repositories or report holding bins? But it seemed clear to me that it was not suitable for the kinds of tasks I've been accustomed to deploying on UNIX HSM. - Allen S. Rout - Apologies for the double 'very very'.
Ports used by DSMCAD
Hi all, I have TSM Server 5.3.2 - AIX 5.1 TSM Client 5.2.2 - Windows NT After first installation of client using dsmcad I have on client options file TCPCLIENTPORT1501 HTTPPORT 1581 MANAGEDSERVICE WEBCLIENT SCHEDULE First schedule missed and got below message on server console: ANR2716E Schedule prompter was not able to contact client using type 1 (xxx.xxx.xxx.xxx 1803). After a restart of dsmcad same schedule (actually a client action) restarted and had success. The question is: WHY server was trying to connect client on port 1803??? A netstat -an on windows machine just gave me a LISTEN state for port 1581, not 1501. Any help? Thanks. -- Helder Garcia
BACKUPSET full Voluume ARCHIVAL
Hello, I am trying to do a Full weekly Archival of a Novell clients Volume. using a backup set I have the following command but I keep getting the failures. Can I just do the filespace and get all the data I need from their? Command generate backupset Doiapps poi_arc /poa devclass=3592class retention=31 scratch=yes ANR0985I Process 527 for GENERATE BACKUPSET running in the BACKGROUND completed with completion state FAILURE at 10:45:19. (SESSION: 80675, PROCESS: 527) Novell OS 6.5 TSM client 5.2.2
Re: -nodename no longer there for UNIX...
Hi Eric, Of course, NODENAME remains a valid option for the dsm.sys file. It has never been valid from the command line. IC46024 seems to refer to only a doc error. You can try -VIRTUALNODENAME from the command line 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" wrote on 01/18/2006 06:32:15 AM: > Hi *SM-ers! > Does anybody know why IBM decided to drop the -nodename parameter for > the UNIX clients? > I discovered that this parameter no longer works in 5.3. It's documented > in the manuals but that's not correct (IC46024). > I'm trying to find a way to give our standby a way to restore data from > another node, without the help of a TSM admin. I know there is a > -fromnode parameter, but that requires a lot of extra work (accessing > the source node, updating the node access list, restoring the file on > the target server, again accessing the source server, removing the node > from the access list). It would be so much easier when one could use the > -nodename parameter! And I really cannot think of any reason why it was > dropped! > I would like to know how other people solve this. Thanks in advance for > any reply! > Kindest regards, > Eric van Loon > > > ** > 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: -nodename no longer there for UNIX...
Eric - The proper option to use for that purpose is -VIRTUALNodename. See "Restore or retrieve files to another workstation" in the client manual. Richard Sims On Jan 18, 2006, at 8:32 AM, Loon, E.J. van - SPLXM wrote: Hi *SM-ers! Does anybody know why IBM decided to drop the -nodename parameter for the UNIX clients? I discovered that this parameter no longer works in 5.3. It's documented in the manuals but that's not correct (IC46024). I'm trying to find a way to give our standby a way to restore data from another node, without the help of a TSM admin. I know there is a -fromnode parameter, but that requires a lot of extra work (accessing the source node, updating the node access list, restoring the file on the target server, again accessing the source server, removing the node from the access list). It would be so much easier when one could use the -nodename parameter! And I really cannot think of any reason why it was dropped! I would like to know how other people solve this. Thanks in advance for any reply! Kindest regards, Eric van Loon
Re: Upgrade mystery
Hi Robert, You're running client 5.2.3.0 according to the below - I believe that 'DISKBUFFSIZE' only came in with TSM Client version 5.3. Rgds, David McClelland Storage and Systems Management Specialist IBM Tivoli Certified Deployment Professional (ITSM 5.2) SSO UK Service Delivery – Storage Services IBM Global Services – IBM United Kingdom Robert Ouzen <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 18/01/2006 13:00 Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Upgrade mystery Hi to all I try this on my dsm.opt in the TDP folder but got this: 01/18/2006 14:50:10 ANS1036S Invalid option 'DISKBUFFSIZE' found in options file 'C:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt' at line number : 28 Invalid entry : 'DISKBUFFSIZE 32' My version of TDP for Exchange is 5.2.1.0 and client version is 5.2.3.0 Regards Robert Ouzen -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of LeBlanc, Patricia Sent: Wednesday, January 18, 2006 2:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrade mystery I applied the change to 2 of my windows exchange servers.here are the results... Without the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 01:21 Server 05 started at 20:00 and completed at 00:22 WITH the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 23:07 Server 05 started at 20:00 and completed at 22:35. I will make the change on the rest of the exchange servers today to see the result in the overall run time of the backups. Thanks!! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steven Harris Sent: Tuesday, January 17, 2006 8:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrade mystery FWIW Del I applied this change to my SAP nodes and lo-and-behold restore throughput just about quadrupled. But, I applied it to my exchange nodes and there was no discernable difference. YMMV Steve. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Del Hoobler > Sent: Tuesday, 17 January 2006 11:47 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Upgrade mystery > > > Patricia, > > See if this append I made last month helps at all: > > http://msgs.adsm.org/cgi-bin/get/adsm0512/204.html > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on > 01/17/2006 08:38:42 AM: > > > I just upgraded my windows2k and w2k3 servers from tsm > backup client > > 5.2 to 5.3.0.8. These servers also run the tdp for exchange > v5.2.1.0. > > > > Since then, my exchange backups take an hour longer to complete. > > > > Does anyone know of a conflict with the software? Or a > setting I need > > to set?? > > >
-nodename no longer there for UNIX...
Hi *SM-ers! Does anybody know why IBM decided to drop the -nodename parameter for the UNIX clients? I discovered that this parameter no longer works in 5.3. It's documented in the manuals but that's not correct (IC46024). I'm trying to find a way to give our standby a way to restore data from another node, without the help of a TSM admin. I know there is a -fromnode parameter, but that requires a lot of extra work (accessing the source node, updating the node access list, restoring the file on the target server, again accessing the source server, removing the node from the access list). It would be so much easier when one could use the -nodename parameter! And I really cannot think of any reason why it was dropped! I would like to know how other people solve this. Thanks in advance for any reply! Kindest regards, Eric van Loon ** 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: Upgrade mystery
DISKBUFFSIZE came with TSM Client version 5.3 and this option replaces the largecommbuffers option. Best Regards, Gokhan YILDIRIM -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Robert Ouzen Sent: Wednesday, January 18, 2006 3:01 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Upgrade mystery Hi to all I try this on my dsm.opt in the TDP folder but got this: 01/18/2006 14:50:10 ANS1036S Invalid option 'DISKBUFFSIZE' found in options file 'C:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt' at line number : 28 Invalid entry : 'DISKBUFFSIZE 32' My version of TDP for Exchange is 5.2.1.0 and client version is 5.2.3.0 Regards Robert Ouzen -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of LeBlanc, Patricia Sent: Wednesday, January 18, 2006 2:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrade mystery I applied the change to 2 of my windows exchange servers.here are the results... Without the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 01:21 Server 05 started at 20:00 and completed at 00:22 WITH the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 23:07 Server 05 started at 20:00 and completed at 22:35. I will make the change on the rest of the exchange servers today to see the result in the overall run time of the backups. Thanks!! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steven Harris Sent: Tuesday, January 17, 2006 8:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrade mystery FWIW Del I applied this change to my SAP nodes and lo-and-behold restore throughput just about quadrupled. But, I applied it to my exchange nodes and there was no discernable difference. YMMV Steve. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Del Hoobler > Sent: Tuesday, 17 January 2006 11:47 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Upgrade mystery > > > Patricia, > > See if this append I made last month helps at all: > >http://msgs.adsm.org/cgi-bin/get/adsm0512/204.html > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on > 01/17/2006 08:38:42 AM: > > > I just upgraded my windows2k and w2k3 servers from tsm > backup client > > 5.2 to 5.3.0.8. These servers also run the tdp for exchange > v5.2.1.0. > > > > Since then, my exchange backups take an hour longer to complete. > > > > Does anyone know of a conflict with the software? Or a > setting I need > > to set?? > > > This message and attachments are confidential and intended solely for the individual(s) stated in this message.If you received this message although you are not the addressee you are responsible to keep the message confidential .The sender has no responsibility for the accuracy or correctness of the information in the message and its attachments.Our company shall have no liability for any changes or late receiving,loss of integrity and confidentiality,viruses and any damages caused in anyway to your computer system. Bu mesaj ve ekleri mesajda gonderildigi belirtilen kisi/kisilere ozeldir ve gizlidir.Bu mesajin muhatabi olmamaniza ragmen tarafiniza ulasmis olmasi halinde mesaj iceriginin gizliligi ve bu gizlilik yukumlulugune uyulmasi zorunlulugu tarafiniz icin de soz konusudur.Mesaj ve eklerinde yer alan bilgilerin dogrulugu ve guncelligi konusunda gonderenin ya da sirketimizin herhangi bir sorumlulugu bulunmamaktadir.Sirketimiz mesajin ve bilgilerinin size degisiklige ugrayarak veya gec ulasmasindan, butunlugunun ve gizliliginin korunamamasindan, virus icermesinden ve bilgisayar sisteminize verebilecegi herhangi bir zarardan sorumlu tutulamaz.
Re: Upgrade mystery
Hello Robert, as far as I know 'DISKBIFSIZE' is an option for TSM 5.3 and above client versions. Rainer > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Robert Ouzen > Sent: Wednesday, January 18, 2006 2:01 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Upgrade mystery > > Hi to all > > I try this on my dsm.opt in the TDP folder but got this: > > 01/18/2006 14:50:10 ANS1036S Invalid option 'DISKBUFFSIZE' found in > options file 'C:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt' >at line number : 28 >Invalid entry : 'DISKBUFFSIZE 32' > > My version of TDP for Exchange is 5.2.1.0 and client version is > 5.2.3.0 > > Regards Robert Ouzen > > > > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of LeBlanc, Patricia > Sent: Wednesday, January 18, 2006 2:44 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Upgrade mystery > > I applied the change to 2 of my windows exchange servers.here are > the results... > > Without the DISKBUFFSIZE 32 > Server 04 started at 20:00 and completed at 01:21 Server 05 started at > 20:00 and completed at 00:22 > > WITH the DISKBUFFSIZE 32 > Server 04 started at 20:00 and completed at 23:07 Server 05 started at > 20:00 and completed at 22:35. > > I will make the change on the rest of the exchange servers today to > see the result in the overall run time of the backups. > Thanks!! > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Steven Harris > Sent: Tuesday, January 17, 2006 8:12 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Upgrade mystery > > FWIW Del > > I applied this change to my SAP nodes and lo-and-behold restore > throughput just about quadrupled. > > But, I applied it to my exchange nodes and there was no discernable > difference. YMMV > > Steve. > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf > > Of Del Hoobler > > Sent: Tuesday, 17 January 2006 11:47 PM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] Upgrade mystery > > > > > > Patricia, > > > > See if this append I made last month helps at all: > > > >http://msgs.adsm.org/cgi-bin/get/adsm0512/204.html > > > > Thanks, > > > > Del > > > > > > > > "ADSM: Dist Stor Manager" wrote on > > 01/17/2006 08:38:42 AM: > > > > > I just upgraded my windows2k and w2k3 servers from tsm > > backup client > > > 5.2 to 5.3.0.8. These servers also run the tdp for exchange > > v5.2.1.0. > > > > > > Since then, my exchange backups take an hour longer to complete. > > > > > > Does anyone know of a conflict with the software? Or a > > setting I need > > > to set?? > > > > > >
Re: Upgrade mystery
Hi to all I try this on my dsm.opt in the TDP folder but got this: 01/18/2006 14:50:10 ANS1036S Invalid option 'DISKBUFFSIZE' found in options file 'C:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt' at line number : 28 Invalid entry : 'DISKBUFFSIZE 32' My version of TDP for Exchange is 5.2.1.0 and client version is 5.2.3.0 Regards Robert Ouzen -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of LeBlanc, Patricia Sent: Wednesday, January 18, 2006 2:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrade mystery I applied the change to 2 of my windows exchange servers.here are the results... Without the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 01:21 Server 05 started at 20:00 and completed at 00:22 WITH the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 23:07 Server 05 started at 20:00 and completed at 22:35. I will make the change on the rest of the exchange servers today to see the result in the overall run time of the backups. Thanks!! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steven Harris Sent: Tuesday, January 17, 2006 8:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrade mystery FWIW Del I applied this change to my SAP nodes and lo-and-behold restore throughput just about quadrupled. But, I applied it to my exchange nodes and there was no discernable difference. YMMV Steve. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Del Hoobler > Sent: Tuesday, 17 January 2006 11:47 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Upgrade mystery > > > Patricia, > > See if this append I made last month helps at all: > >http://msgs.adsm.org/cgi-bin/get/adsm0512/204.html > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on > 01/17/2006 08:38:42 AM: > > > I just upgraded my windows2k and w2k3 servers from tsm > backup client > > 5.2 to 5.3.0.8. These servers also run the tdp for exchange > v5.2.1.0. > > > > Since then, my exchange backups take an hour longer to complete. > > > > Does anyone know of a conflict with the software? Or a > setting I need > > to set?? > > >
Re: Upgrade mystery
I applied the change to 2 of my windows exchange servers.here are the results... Without the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 01:21 Server 05 started at 20:00 and completed at 00:22 WITH the DISKBUFFSIZE 32 Server 04 started at 20:00 and completed at 23:07 Server 05 started at 20:00 and completed at 22:35. I will make the change on the rest of the exchange servers today to see the result in the overall run time of the backups. Thanks!! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steven Harris Sent: Tuesday, January 17, 2006 8:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrade mystery FWIW Del I applied this change to my SAP nodes and lo-and-behold restore throughput just about quadrupled. But, I applied it to my exchange nodes and there was no discernable difference. YMMV Steve. > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Del Hoobler > Sent: Tuesday, 17 January 2006 11:47 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Upgrade mystery > > > Patricia, > > See if this append I made last month helps at all: > >http://msgs.adsm.org/cgi-bin/get/adsm0512/204.html > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on > 01/17/2006 08:38:42 AM: > > > I just upgraded my windows2k and w2k3 servers from tsm > backup client > > 5.2 to 5.3.0.8. These servers also run the tdp for exchange > v5.2.1.0. > > > > Since then, my exchange backups take an hour longer to complete. > > > > Does anyone know of a conflict with the software? Or a > setting I need > > to set?? > > >
Re: TSM Server Stop Working
Hi I don't believe the service pack is an issue as we are running the same library on W2K3 Sp1 with 3 LTO3 drives without problems. I would suggest to use the TSM windows Management plugin (MMC) go to the device page under the tsm server instance and compare your path definition with what windows can see. It looks funny to me that the library manager doesnt have the lowest SCSI address. Are the library and drives online? Kind Regards Marco Malgarini -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Wednesday, 18 January 2006 17:28 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server Stop Working I´m not an expert on your HW but your output says "24.0/6.0 IBM 4560SLX 04250429Out of date" . Maybe you should try to upgrade the library firmware and check that drive and path definitions are ok. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ridvan Aktas Sent: 17. januar 2006 18:30 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Server Stop Working I guess so; do you think SP1 for Windows cause the problem? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Sandeep Jain Sent: Tuesday, January 17, 2006 4:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Server Stop Working Hi, Have u applied this service pack (sp1) recently...? With Best Regards, Sandeep Jain ** Legal Disclaimer * "This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you." * -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ridvan Aktas Sent: Tuesday, January 17, 2006 12:43 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Server Stop Working Hello TSM Users, My TSM server recently stops working and my guess is hardware issue because I am getting SCSI error messages. It is possible that it can be software issue as well but not sure. Your help greatly appreciated. LTO Library: IBM 4560SLX 2 Drives Server: IBM 345 xSeries OS: Windows Server 2003 SP1 Ram: 1.5 GB Processor: Intel Xeon 2.8GHz Error Message: ANR8840E Unable to open device lb6.0.0.4 with error 592532. Device Manager: In device manager everything seems to be OK. -Medium Changer oIBM Tivoli Storage Manager for Medium Changers, OK -Tape Drivers oIBM ULTRIUM-TD2 SCSI Sequential Device, OK oIBM ULTRIUM-TD2 SCSI Sequential Device, OK -SCSI and RAID controllers oAdaptec SCSI Card 29320LP - Ultra320 SCSI, OK oLSI Logic 1020/1030 Ultra320 SCSI Adapter, OK oLSI Logic 1020/1030 Ultra320 SCSI Adapter, OK Disk Space: Plenty free disk space Example: I use IBM TapeTool program to inquire SCSI; *** TAPETOOL MENU *** --- | | | 1. Update Firmware on the 4560-SLX library and drives.| | 2. Install Library and Tape tools diagnostic | | 3. Run xTalk diagnostic on SDLT drive | | 4. Install LTO drive Diagnostics | | 5. SCSI Inquiry | | 6. Serial Number of tape backup unit | | 7. Exit | | | --- Enter choice : [1,2,3,4,5,6,7,] : 5 tapedrv -- IBM Tape Device Firmware Utility - v1.08.22 Copyright (c) 2000-2004 IBM Corporation Device Address: Port_Number.Bus_Number/SCSI_Device_ID.Logical_Unit_Number Tape DeviceDevice Update Unit Address Device Inquiry Version Version Device Firmware State --- --- --- - 04.0/1.0 IBM ULTRIUM-TD2 47704770Up to date 14.0/2.0 IBM ULTRIUM-TD2 47704770Up to date 24.0/6.0 IBM 4560SLX 04250429Out of date -- Above tape drive inaccessible -- TAPEDRV8276 error: Tape device inaccessible: "\\.\lb6.0.0.4": SCSI Input/Output: Operating system error 87: The parameter is incorrect. - Press any key to continue . . . Thanks, Ridvan Aktas IT Manager - US Datamonitor Inc. 212-652-2646
