[no subject]
Good morning ! My tsm client on a w2k prof workstation does not work. The message is: Incremental backup of volume '\\pc01130\c$' Incremental backup of volume '\\bwi_1\user1\usr\bwihab' Incremental backup of volume '\\bwi_1\user1\edvdoc' ANS1999E Incremental processing of '\\pc01130\c$' stopped ANS1449E A required NT privilege is not held But: Any Systemobject is excluded. Only a few logfiles from drive C: should be saved, those files are owned by a user not by an administrator. The drives W: and H: are backed up propperly, but only if domain C: is excluded. So i think there is a problem with permissions on drive C: ?! Who has an idea to solve this problem? Thank you very much!
Client Backup Schedule - Object field.
Hi All, Using a client backup schedule, is it possible to backup a single directory with spaces in the name, and can the filename have more than 8 digits exampleC:\SQLServer Backups . I need to be more precise than C:\SQLServ* T.I.A Bill
Re: Client Backup Schedule - Object field.
Refer to client manual topic Handling spaces in file names in schedule definitions. I don't understand what you mean by 8 digits: there are no digits in your example; and there's no length restriction, per se, on filespecs. Richard Sims On Apr 26, 2005, at 6:19 AM, Bill Dourado wrote: Hi All, Using a client backup schedule, is it possible to backup a single directory with spaces in the name, and can the filename have more than 8 digits exampleC:\SQLServer Backups . I need to be more precise than C:\SQLServ*
Re: Exchange 2003 restore to another server. HELP!
While Del is on vacation, we'll depend upon his previous postings... See http://www.mail-archive.com/adsm-l@vm.marist.edu/msg49740.html for starters on approaching this error condition. Another hit is http://www.mail-archive.com/adsm-l@vm.marist.edu/msg46912.html . Richard Sims TDP amateur On Apr 25, 2005, at 7:26 PM, Coats, Jack wrote: I am using the TDP for Exchange GUI, and restoring to a similar leveled version of Exchange on the same base OS. I get the following manual from the client: 04/25/2005 17:57:03 ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. 04/25/2005 17:57:03 Total backups inspected: 1 From the error logs on the Exchange server, I get the impression that I am not restoring to the correct Exchange database. How can I restore one exchange server (or portions) to another server? If my answer is RTFM, that is OK, please let me know which Fine Manual to read and where! ... TIA Jack
Re: Client Backup Schedule - Object field.
You mentioned something here I was wondering about just an hour ago.. I noticed that the DB tables for backups and archives specifiy 1024chars for the pathname, and 512chars for the filename. Is this long enough to encompass the maximim path/filename length of all systems that TSM is able to backup? Matt. Computer says 'No'.. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, April 26, 2005 12:22 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Client Backup Schedule - Object field. Refer to client manual topic Handling spaces in file names in schedule definitions. I don't understand what you mean by 8 digits: there are no digits in your example; and there's no length restriction, per se, on filespecs. Richard Sims On Apr 26, 2005, at 6:19 AM, Bill Dourado wrote: Hi All, Using a client backup schedule, is it possible to backup a single directory with spaces in the name, and can the filename have more than 8 digits exampleC:\SQLServer Backups . I need to be more precise than C:\SQLServ* ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Exchange 2003
Does anybody know what version of TDP for mail is needed to backup Exchange 2003? Thanks Jim Murray Senior Systems Engineer Liberty Bank 860.638.2919 [EMAIL PROTECTED] There are only 10 kinds of people in this world - those that know binary and those that do not. Unless you have received this email through the Liberty bank secure email system, before you respond, please consider that any unencrypted e-mail that is sent to us is not secure. If you send regular e-mail to Liberty Bank, please do not include any private or confidential information such as social security numbers, unlisted telephone numbers, bank account numbers, personal income information, user names, passwords, etc. If you need to provide us with such information, please telephone us at (888)570-0773 during business hours or write to us at 315 Main St. Middletown, CT 06457. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer without disclosing it. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Bank. Thank you.
Re: Exchange 2003
Jim, We're using 5.21 on a number of Exchange Exchange cluster boxes with no problems. Regards, Iain Barnetson IT Systems Administrator UKN Infrastructure Operations -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Murray, Jim Sent: 26 April 2005 14:20 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Exchange 2003 Does anybody know what version of TDP for mail is needed to backup Exchange 2003? Thanks Jim Murray Senior Systems Engineer Liberty Bank 860.638.2919 [EMAIL PROTECTED] There are only 10 kinds of people in this world - those that know binary and those that do not. Unless you have received this email through the Liberty bank secure email system, before you respond, please consider that any unencrypted e-mail that is sent to us is not secure. If you send regular e-mail to Liberty Bank, please do not include any private or confidential information such as social security numbers, unlisted telephone numbers, bank account numbers, personal income information, user names, passwords, etc. If you need to provide us with such information, please telephone us at (888)570-0773 during business hours or write to us at 315 Main St. Middletown, CT 06457. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer without disclosing it. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Bank. Thank you.
Re: Client Backup Schedule - Object field.
On Apr 26, 2005, at 8:56 AM, Warren, Matthew (Retail) wrote: You mentioned something here I was wondering about just an hour ago.. I noticed that the DB tables for backups and archives specifiy 1024chars for the pathname, and 512chars for the filename. Is this long enough to encompass the maximim path/filename length of all systems that TSM is able to backup? Hi, Matt - Now, would the developers not accommodate the maximum path length of all supported client systems? :-) From what I've seen, the actual length limit for modern file system paths is 1023. The AIX limit is defined on PATH_MAX in /usr/include/sys/limits.h. The Windows limit is confusing, as you would expect in Windows, but seems to be 1023. (See http://www.osronline.com/lists_archive/ntfsd/thread5355.html) Sims, Richard (Educational pricing)
Re: TSM causing client disk contention
At 07:33 PM 4/25/2005, Coats, Jack wrote: Our solutions: * Start backups when users have supposedly gone home. Thanks for the suggestions so far. I should have mentioned that this is for an application server who's performance is important 24x7. We do already schedule during off-peak, but even so the performance degradation caused by the TSM backup is noticed and is perceived as a problem. ..Paul -- Paul Zarnowski Ph: 607-255-4757 719 Rhodes Hall, Cornell UniversityFx: 607-255-8521 Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
Re: TSM causing client disk contention
Paul, Have you tried other backup methods and found they don't impact performance? Maybe you could try using one of the applications listed here http://www.sun.com/bigadmin/content/submitted/backup_recovery.html and see if the performance impact is less than with TSM. I suspect it won't be. If the native backup applications cause the same issues as the TSM backup, I'd say it's time for more resources. If not, then TSM tuning might be in order. curtis Paul Zarnowski [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04/26/2005 09:52 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: TSM causing client disk contention At 07:33 PM 4/25/2005, Coats, Jack wrote: Our solutions: * Start backups when users have supposedly gone home. Thanks for the suggestions so far. I should have mentioned that this is for an application server who's performance is important 24x7. We do already schedule during off-peak, but even so the performance degradation caused by the TSM backup is noticed and is perceived as a problem. ..Paul -- Paul Zarnowski Ph: 607-255-4757 719 Rhodes Hall, Cornell UniversityFx: 607-255-8521 Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
Re: TSM causing client disk contention
Paul - In Unix, at least, a less important process (the backup, in this case) can be reniced to reduce its impact, giving the more important processes a higher relative priority in accessing resources. There may be a similar mechanism for Windows. Incremental backups have a considerable impact because of the Active Files list they have to juggle. You could evaluate whether a -INCRBYDate type backup would be viable for the involved systems, where there is no list overhead. Richard Sims On Apr 26, 2005, at 10:52 AM, Paul Zarnowski wrote: At 07:33 PM 4/25/2005, Coats, Jack wrote: Our solutions: * Start backups when users have supposedly gone home. Thanks for the suggestions so far. I should have mentioned that this is for an application server who's performance is important 24x7. We do already schedule during off-peak, but even so the performance degradation caused by the TSM backup is noticed and is perceived as a problem.
Disk gone bad, need help
Good Morning. We are running AIX 4.3.3 with TSM 4.1.3 (going into retirement soon) We have a DB that is made up of 6 disk which are mirrored. We had a disk go bad that was part of that pool of disk. My question is what do I need to do after the disk is replaced to recover, TSM stayed up no problem(very small DB, being retired soon). Do I (logical volume/DB name on disk that went bad -- /dbaa1dk2/db mirrored to /dbaa1dk8/db) * DSMFMT -m -db /dbaa1dk2/db 3404 * (not sure what to do about the DSMSERV FORMAT) * define dbcopy /dbaa1dk3/db /dbaa1dk8/db Have a Great Day, Eric Jones * [EMAIL PROTECTED] *: 607-751-4133 Cell : 607-972-7621
Re: TSM causing client disk contention
There is a way to do that. Just set the backup process to BelowNormal or Low priority. Troy Frank Network Services University of Wisconsin Medical Foundation 608.829.5384 [EMAIL PROTECTED] 4/26/2005 10:15:24 AM Paul - In Unix, at least, a less important process (the backup, in this case) can be reniced to reduce its impact, giving the more important processes a higher relative priority in accessing resources. There may be a similar mechanism for Windows. Incremental backups have a considerable impact because of the Active Files list they have to juggle. You could evaluate whether a -INCRBYDate type backup would be viable for the involved systems, where there is no list overhead. Richard Sims On Apr 26, 2005, at 10:52 AM, Paul Zarnowski wrote: At 07:33 PM 4/25/2005, Coats, Jack wrote: Our solutions: * Start backups when users have supposedly gone home. Thanks for the suggestions so far. I should have mentioned that this is for an application server who's performance is important 24x7. We do already schedule during off-peak, but even so the performance degradation caused by the TSM backup is noticed and is perceived as a problem. 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: TSM causing client disk contention
Other than lowering the backup process prioritys another way to cause TSM to use less resources is to set 'MEMORYEFFICIENT YES' in the options. This will cause TSM to use less memory, and also slow down it's disk scanning. Also check TSM's 'copy group' serialization parameters, the default of 'shared static' could cause a file in use by an appliation to be backed up 4 times before giving up. It may be better to use 'static' or 'dynamic' to reduce the amount of disk activity during a backup at the expense of having 'fuzzy' backups. Finally, from what I have seen, many appliation servers are normally quite idle and not doing anything cpu/disk/network at all, even 24x7 ones. It's the 'backup' that uses the most cpu/disk/network Just because it has to scan all the files every day, and this happens to be more than the application server does in a day. So the 'performance monitor' spike during the backup and people perceive this as a problem, when really it is not. Matt G.
Re: Disk gone bad, need help
Eric, I am going to assume you know the syntax of the following commands so I will just give my answer at a high level if not post back and I will give the exact syntax, 1. Remove the failed volume from tsm by doing either a del dbv. 2. Then define a new DB vol with the def dbv command, you can use the f=XXX to format it to the size you need. 3. I know this sounds funny by now you need to delete the volume you just created. This will leave the formatted file on the OS file system. 4. Now you can use the def dbc command to get your self remirrored. BTW, as an alternative to steps 2 and 3 you could go to the OS level and do a dsmfmt command to create the DB volume as well, but I generally like to do it all with in TSM. As I said before, if you need the exact syntax please repost. I will need the exact filenames of the bad volume, the volume name it was mirrored to, and the name of the new volume. I hope that helps. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Good Morning. We are running AIX 4.3.3 with TSM 4.1.3 (going into retirement soon) We have a DB that is made up of 6 disk which are mirrored. We had a disk go bad that was part of that pool of disk. My question is what do I need to do after the disk is replaced to recover, TSM stayed up no problem(very small DB, being retired soon). Do I (logical volume/DB name on disk that went bad -- /dbaa1dk2/db mirrored to /dbaa1dk8/db) * DSMFMT -m -db /dbaa1dk2/db 3404 * (not sure what to do about the DSMSERV FORMAT) * define dbcopy /dbaa1dk3/db /dbaa1dk8/db Have a Great Day, Eric Jones * [EMAIL PROTECTED] *: 607-751-4133 Cell : 607-972-7621
Re: Disk gone bad, need help
Thanks. Would you mind the full syntax. This is my 1st time through this and nobody around me seems to know about it. 1: The disk that went bad is being replaced as I write 2: I was going to keep the logical volume/db name(/dbaa1dk3/db) the same so all the documentation stays the same. 3: The bad logical volume/file was -- /dbaa1dk3/db and it was mirrored to /dbaa1dk7/db This is the 1st failure we have seen. thanks for all your help, Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I am going to assume you know the syntax of the following commands so I will just give my answer at a high level if not post back and I will give the exact syntax, 1. Remove the failed volume from tsm by doing either a del dbv. 2. Then define a new DB vol with the def dbv command, you can use the f=XXX to format it to the size you need. 3. I know this sounds funny by now you need to delete the volume you just created. This will leave the formatted file on the OS file system. 4. Now you can use the def dbc command to get your self remirrored. BTW, as an alternative to steps 2 and 3 you could go to the OS level and do a dsmfmt command to create the DB volume as well, but I generally like to do it all with in TSM. As I said before, if you need the exact syntax please repost. I will need the exact filenames of the bad volume, the volume name it was mirrored to, and the name of the new volume. I hope that helps. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Good Morning. We are running AIX 4.3.3 with TSM 4.1.3 (going into retirement soon) We have a DB that is made up of 6 disk which are mirrored. We had a disk go bad that was part of that pool of disk. My question is what do I need to do after the disk is replaced to recover, TSM stayed up no problem(very small DB, being retired soon). Do I (logical volume/DB name on disk that went bad -- /dbaa1dk2/db mirrored to /dbaa1dk8/db) *DSMFMT -m -db /dbaa1dk2/db 3404 * (not sure what to do about the DSMSERV FORMAT) * define dbcopy /dbaa1dk3/db /dbaa1dk8/db Have a Great Day, Eric Jones * [EMAIL PROTECTED] *: 607-751-4133 Cell : 607-972-7621
Re: IMPORT NODE - now having problems restoring data - authentication problems?
Scott, The Exchange Server is getting information it wasn't prepared for. Did you get this one resolved yet? How? If not, did you place a call with IBM Service? Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 04/14/2005 02:27:33 PM: We did an 'import node' and are trying to restore that imported data to another machine. Using the TDP Exchange Client I can go out, see the correct Storage Group data and select what I wish for restore. However, a few tenths of a second after kicking the restore off, we receive an error message in the GUI.. ACN0151E Errors occurred while processing the request. and Restore failed. Error returned from c callback function call (0x8004010f). The TSM server log looks like this.. 04/14/05 11:41:08 ANR0406I Session 12054 started for node WDBLABEX3TDP22 (TDP MSExchgV2 NT) (Tcp/Ip 172.16.144.9(1478)). 04/14/05 11:41:09 ANE4991I (Session: 12054, Node: WDBLABEX3TDP22) TDP MSExchgV2 NT ACN3504 TDP for Microsoft Exchange: Starting restore for server WDBLABEX03. 04/14/05 11:41:09 ANE4991I (Session: 12054, Node: WDBLABEX3TDP22) TDP MSExchgV2 NT ACN3506 TDP for Microsoft Exchange: Starting full restore of storage group NYC SG Mbxs NYC to server WDBLABEX03. 04/14/05 11:41:09 ANE4993E (Session: 12054, Node: WDBLABEX3TDP22) TDP MSExchgV2 NT ACN3508 TDP for Microsoft Exchange: full restore of storage group NYC SG Mbxs NYC to server WDBLABEX03 failed, rc = 425. 04/14/05 11:41:09 ANE4991I (Session: 12054, Node: WDBLABEX3TDP22) TDP MSExchgV2 NT ACN3505 TDP for Microsoft Exchange: Restore from server to WDBLABEX03 is complete. Total backups restored: 0 Total bytes transferred: 0 Elapsed processing time: 0.06 Secs Throughput rate: 0.00 Kb/Sec 04/14/05 11:41:09 ANR0403I Session 12054 ended The dsierror log looks like this... 04/14/2005 09:24:37 ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 . 04/14/2005 09:24:37 ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 . 04/14/2005 09:24:37 sessOpen: Error 137 from signon authentication. 04/14/2005 09:24:37 ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 . 04/14/2005 09:24:37 ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 . 04/14/2005 09:24:37 sessOpen: Error 137 from signon authentication. If we try to run a backup we see these types of messages in the tdpexc log 04/14/2005 14:18:06 = 04/14/2005 14:18:06 Request : Backup 04/14/2005 14:18:06 SG List : NYC SG Mbxs NYC 04/14/2005 14:18:06 Backup Type : FULL 04/14/2005 14:18:06 Database Name : 04/14/2005 14:18:06 Buffers : 3 04/14/2005 14:18:06 Buffersize: 1024 04/14/2005 14:18:06 Exchange Server : (Local Machine) 04/14/2005 14:18:06 TSM Node Name : WDBLABEX3TDP22 04/14/2005 14:18:06 TSM Options File : C:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt 04/14/2005 14:18:06 Mount Wait: Yes 04/14/2005 14:18:06 Quiet : No 04/14/2005 14:18:06 - 04/14/2005 14:18:07 Backup of storage group NYC SG Mbxs NYC failed. 04/14/2005 14:18:07 Instance not found 04/14/2005 14:18:08 Retrying failed backups... 04/14/2005 14:18:08 Backup of storage group NYC SG Mbxs NYC failed. 04/14/2005 14:18:08 Instance not found 04/14/2005 14:18:08 Retrying failed backups... 04/14/2005 14:18:09 Backup of storage group NYC SG Mbxs NYC failed. 04/14/2005 14:18:09 Instance not found 04/14/2005 14:18:09 Retrying failed backups... 04/14/2005 14:18:10 Backup of storage group NYC SG Mbxs NYC failed. 04/14/2005 14:18:10 Instance not found 04/14/2005 14:18:10 Retrying failed backups... 04/14/2005 14:18:10 Backup of storage group NYC SG Mbxs NYC failed. 04/14/2005 14:18:10 Instance not found 04/14/2005 14:18:11 Retrying failed backups... 04/14/2005 14:18:11 Total storage groups requested for backup: 1 04/14/2005 14:18:11 Total storage groups backed up: 0 04/14/2005 14:18:11 Total storage groups expired: 0 04/14/2005 14:18:11 Total storage groups excluded: 0 04/14/2005 14:18:11 Throughput rate:0.00 Kb/Sec 04/14/2005 14:18:11 Total bytes transferred:0 04/14/2005 14:18:11 Elapsed processing time:0.01 Secs Has anyone seen anything similar? We are
Re: Disk gone bad, need help
Eric, Here you go, from a TSM command prompt issue the following. del dbv /dbaa1dk3/db def dbv /dbaa1dk3/db f=/size_in_MB/ del dbv /dbaa1dk3/db def dbc /dbaa1dk7/db /dbaa1dk3/db That should do it. The only thing you need to decide is how big to make it in the second command. Remember it is in MBs and it most be as big as the /dbaa1dk7/db volume. NOTE: I have noticed that you are not consistent as to which volume was on the failed drive as well as which volumes were mirrored. Please be certain about this before you proceed. If you are not sure then repost the output of the following commands: q dbv f=d q db f=d -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. Would you mind the full syntax. This is my 1st time through this and nobody around me seems to know about it. 1: The disk that went bad is being replaced as I write 2: I was going to keep the logical volume/db name(/dbaa1dk3/db) the same so all the documentation stays the same. 3: The bad logical volume/file was -- /dbaa1dk3/db and it was mirrored to /dbaa1dk7/db This is the 1st failure we have seen. thanks for all your help, Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I am going to assume you know the syntax of the following commands so I will just give my answer at a high level if not post back and I will give the exact syntax, 1. Remove the failed volume from tsm by doing either a del dbv. 2. Then define a new DB vol with the def dbv command, you can use the f=XXX to format it to the size you need. 3. I know this sounds funny by now you need to delete the volume you just created. This will leave the formatted file on the OS file system. 4. Now you can use the def dbc command to get your self remirrored. BTW, as an alternative to steps 2 and 3 you could go to the OS level and do a dsmfmt command to create the DB volume as well, but I generally like to do it all with in TSM. As I said before, if you need the exact syntax please repost. I will need the exact filenames of the bad volume, the volume name it was mirrored to, and the name of the new volume. I hope that helps. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Good Morning. We are running AIX 4.3.3 with TSM 4.1.3 (going into retirement soon) We have a DB that is made up of 6 disk which are mirrored. We had a disk go bad that was part of that pool of disk. My question is what do I need to do after the disk is replaced to recover, TSM stayed up no problem(very small DB, being retired soon). Do I (logical volume/DB name on disk that went bad -- /dbaa1dk2/db mirrored to /dbaa1dk8/db) * DSMFMT -m -db /dbaa1dk2/db 3404 * (not sure what to do about the DSMSERV FORMAT) * define dbcopy /dbaa1dk3/db /dbaa1dk8/db Have a Great Day, Eric Jones * [EMAIL PROTECTED] *: 607-751-4133 Cell : 607-972-7621
Re: Disk gone bad, need help
Thanks. The logical volume that went bad was /dbaa1dk3 so I assumed since /dbaa1dk3/db was on the bad disk I could use the naming convention. The bottom note was from initial information from 1 of the UNIX admins, I went in and verified the information myself and found it to be different. Last questions since I'm a little confused but I'm sure that will pass. Why do you delete the volume before you mirror the data from the other disk? Also I see the GUI under Database volumes and there is a create data base volume, delete database volume and copy database volume. Is it better to use the command line over the GUI or does it not matter. Thanks again, this has been a great help. Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 1:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, Here you go, from a TSM command prompt issue the following. del dbv /dbaa1dk3/db def dbv /dbaa1dk3/db f=/size_in_MB/ del dbv /dbaa1dk3/db def dbc /dbaa1dk7/db /dbaa1dk3/db That should do it. The only thing you need to decide is how big to make it in the second command. Remember it is in MBs and it most be as big as the /dbaa1dk7/db volume. NOTE: I have noticed that you are not consistent as to which volume was on the failed drive as well as which volumes were mirrored. Please be certain about this before you proceed. If you are not sure then repost the output of the following commands: q dbv f=d q db f=d -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. Would you mind the full syntax. This is my 1st time through this and nobody around me seems to know about it. 1: The disk that went bad is being replaced as I write 2: I was going to keep the logical volume/db name(/dbaa1dk3/db) the same so all the documentation stays the same. 3: The bad logical volume/file was -- /dbaa1dk3/db and it was mirrored to /dbaa1dk7/db This is the 1st failure we have seen. thanks for all your help, Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I am going to assume you know the syntax of the following commands so I will just give my answer at a high level if not post back and I will give the exact syntax, 1. Remove the failed volume from tsm by doing either a del dbv. 2. Then define a new DB vol with the def dbv command, you can use the f=XXX to format it to the size you need. 3. I know this sounds funny by now you need to delete the volume you just created. This will leave the formatted file on the OS file system. 4. Now you can use the def dbc command to get your self remirrored. BTW, as an alternative to steps 2 and 3 you could go to the OS level and do a dsmfmt command to create the DB volume as well, but I generally like to do it all with in TSM. As I said before, if you need the exact syntax please repost. I will need the exact filenames of the bad volume, the volume name it was mirrored to, and the name of the new volume. I hope that helps. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Good Morning. We are running AIX 4.3.3 with TSM 4.1.3 (going into retirement soon) We have a DB that is made up of 6 disk which are mirrored. We had a disk go bad that was part of that pool of disk. My question is what do I need to do after the disk is replaced to recover, TSM stayed up no problem(very small DB, being retired soon). Do I (logical volume/DB name on disk that went bad -- /dbaa1dk2/db mirrored to /dbaa1dk8/db) * DSMFMT -m -db /dbaa1dk2/db 3404 * (not sure what to do about the DSMSERV FORMAT) * define dbcopy /dbaa1dk3/db /dbaa1dk8/db Have a Great Day, Eric Jones * [EMAIL PROTECTED] *: 607-751-4133 Cell : 607-972-7621
TSM Server shutdown due to log full
Last night this happened to me and after struggling to get it back up I don't understand why what I had in place to help with this seems to be worthless or I just don't understand why I am getting what I am. Maybe someone can explain to me why it seems the extend gives an error even though there is space available. This is what I have available for logs: [EMAIL PROTECTED]:dsmserv display logvol 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 7100 megabytes. ANR0201I Database assigned capacity is 83000 megabytes. Volume Name (Copy 1): /adsmlog2/log001.dsm Copy Status: Sync'd Volume Name (Copy 2): /adsmlog2_m/log001_m.dsm Copy Status: Sync'd Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 5,000 Allocated Space (MB): 2,100 Free Space (MB): 2,900 Volume Name (Copy 1): /adsmlog2/log003.dsm Copy Status: Sync'd Volume Name (Copy 2): /adsmlog2_m/log003_m.dsm Copy Status: Sync'd Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 500 Allocated Space (MB): 0 Free Space (MB): 500 Volume Name (Copy 1): /adsmlog2/log002.dsm Copy Status: Sync'd Volume Name (Copy 2): /adsmlog2_m/log002_m.dsm Copy Status: Sync'd Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 5,000 Allocated Space (MB): 5,000 Free Space (MB): 0 This is what happened when I tried to extend. The question is did it work or not. If not why? There is plenty of unused space available. Did I define the command wrong? [EMAIL PROTECTED]:dsmserv extend log /adsmlog2/log001.dsm 500 ANR0900I Processing options file dsmserv.opt. ANR7811I Direct I/O will be used for all eligible disk files. ANR0200I Recovery log assigned capacity is 7000 megabytes. ANR0201I Database assigned capacity is 83000 megabytes. ANR0306I Recovery log volume mount in progress. ANRD admstart.c(3463): ThreadId26 Error 21 from lvmAddVol. ANR7835I The server thread 25 terminated in response to server shutdown. ANR7835I The server thread 26 terminated in response to server shutdown. ANR0991I Server shutdown complete. What I finally had to do is create a new volume of 100mb. [EMAIL PROTECTED]:dsmfmt -log /adsmlog2/log004.dsm 100 ANR0900I Processing options file dsmserv.opt. ANR7811I Direct I/O will be used for all eligible disk files. ANR0200I Recovery log assigned capacity is 7000 megabytes. ANR0201I Database assigned capacity is 83000 megabytes. ANR0306I Recovery log volume mount in progress. ANR0984I Process 1 for EXTEND LOG started in the BACKGROUND at 09:21:23. ANR0307I Recovery log extend in progress; 4 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 8 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 12 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 16 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 20 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 24 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 28 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 32 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 36 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 40 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 44 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 48 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 52 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 56 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 60 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 64 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 68 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 72 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 76 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 80 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 84 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 88 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 92 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 96 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 100 megabytes of 100 formatted. ANR2268I Recovery log assigned capacity has been extended. ANR0988I Process 1 for EXTEND LOG running in the BACKGROUND processed 104,857,600 bytes with a completion state of SUCCESS at 09:21:42. ANR7835I The server thread 25 terminated in response to server shutdown. ANR7835I The server thread 26 terminated in response to server shutdown. ANR0991I
Re: TSM Server shutdown due to log full
The rc 21 means that the volume is already added to TSM. You need to format a *new* log volume, then use the dsmserv extend log command to add it. 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-04-26 10:47:36: Last night this happened to me and after struggling to get it back up I don't understand why what I had in place to help with this seems to be worthless or I just don't understand why I am getting what I am. Maybe someone can explain to me why it seems the extend gives an error even though there is space available. This is what I have available for logs: [EMAIL PROTECTED]:dsmserv display logvol 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 7100 megabytes. ANR0201I Database assigned capacity is 83000 megabytes. Volume Name (Copy 1): /adsmlog2/log001.dsm Copy Status: Sync'd Volume Name (Copy 2): /adsmlog2_m/log001_m.dsm Copy Status: Sync'd Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 5,000 Allocated Space (MB): 2,100 Free Space (MB): 2,900 Volume Name (Copy 1): /adsmlog2/log003.dsm Copy Status: Sync'd Volume Name (Copy 2): /adsmlog2_m/log003_m.dsm Copy Status: Sync'd Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 500 Allocated Space (MB): 0 Free Space (MB): 500 Volume Name (Copy 1): /adsmlog2/log002.dsm Copy Status: Sync'd Volume Name (Copy 2): /adsmlog2_m/log002_m.dsm Copy Status: Sync'd Volume Name (Copy 3): Copy Status: Undefined Available Space (MB): 5,000 Allocated Space (MB): 5,000 Free Space (MB): 0 This is what happened when I tried to extend. The question is did it work or not. If not why? There is plenty of unused space available. Did I define the command wrong? [EMAIL PROTECTED]:dsmserv extend log /adsmlog2/log001.dsm 500 ANR0900I Processing options file dsmserv.opt. ANR7811I Direct I/O will be used for all eligible disk files. ANR0200I Recovery log assigned capacity is 7000 megabytes. ANR0201I Database assigned capacity is 83000 megabytes. ANR0306I Recovery log volume mount in progress. ANRD admstart.c(3463): ThreadId26 Error 21 from lvmAddVol. ANR7835I The server thread 25 terminated in response to server shutdown. ANR7835I The server thread 26 terminated in response to server shutdown. ANR0991I Server shutdown complete. What I finally had to do is create a new volume of 100mb. [EMAIL PROTECTED]:dsmfmt -log /adsmlog2/log004.dsm 100 ANR0900I Processing options file dsmserv.opt. ANR7811I Direct I/O will be used for all eligible disk files. ANR0200I Recovery log assigned capacity is 7000 megabytes. ANR0201I Database assigned capacity is 83000 megabytes. ANR0306I Recovery log volume mount in progress. ANR0984I Process 1 for EXTEND LOG started in the BACKGROUND at 09:21:23. ANR0307I Recovery log extend in progress; 4 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 8 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 12 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 16 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 20 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 24 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 28 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 32 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 36 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 40 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 44 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 48 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 52 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 56 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 60 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 64 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 68 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 72 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 76 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 80 megabytes of 100 formatted. ANR0307I Recovery log extend in progress; 84 megabytes of 100 formatted. ANR0307I Recovery log extend in
Re: Exchange 2003 restore to another server. HELP!
Jack, As Richard suggested... Before doing the restore, on the Exchange server to which you will perform the restore to, you need to create the Storage Groups and databases exactly as they appeared on the original server (the upper/lower casing of the names also needs to exactly match). You may also need to mark the databases as: This database can be overwritten by a restore. Then you should be able to perform the restore. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 04/25/2005 07:26:52 PM: I am using the TDP for Exchange GUI, and restoring to a similar leveled version of Exchange on the same base OS. I get the following manual from the client: 04/25/2005 17:57:03 ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1f42 - Database not found. 04/25/2005 17:57:03 Total backups inspected: 1 From the error logs on the Exchange server, I get the impression that I am not restoring to the correct Exchange database. How can I restore one exchange server (or portions) to another server? If my answer is RTFM, that is OK, please let me know which Fine Manual to read and where! ... TIA Jack
Re: Disk gone bad, need help
Eric, I like the command line but it can be done from the Web Admin tool if you like. The reason for the second and third commands is to create the file on the OS filesystem which will become the mirrored volume. As I said in an earlier note you could skip steps 2 and 3 by going to the OS command line and running a dsmfmt command to create the file that will become the DB copy volume. Since, I am often doing this remotely through the web admin tool and I don't always have access to an OS level prompt I use this method which allows me to do it entirely from within TSM. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. The logical volume that went bad was /dbaa1dk3 so I assumed since /dbaa1dk3/db was on the bad disk I could use the naming convention. The bottom note was from initial information from 1 of the UNIX admins, I went in and verified the information myself and found it to be different. Last questions since I'm a little confused but I'm sure that will pass. Why do you delete the volume before you mirror the data from the other disk? Also I see the GUI under Database volumes and there is a create data base volume, delete database volume and copy database volume. Is it better to use the command line over the GUI or does it not matter. Thanks again, this has been a great help. Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 1:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, Here you go, from a TSM command prompt issue the following. del dbv /dbaa1dk3/db def dbv /dbaa1dk3/db f=/size_in_MB/ del dbv /dbaa1dk3/db def dbc /dbaa1dk7/db /dbaa1dk3/db That should do it. The only thing you need to decide is how big to make it in the second command. Remember it is in MBs and it most be as big as the /dbaa1dk7/db volume. NOTE: I have noticed that you are not consistent as to which volume was on the failed drive as well as which volumes were mirrored. Please be certain about this before you proceed. If you are not sure then repost the output of the following commands: q dbv f=d q db f=d -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. Would you mind the full syntax. This is my 1st time through this and nobody around me seems to know about it. 1: The disk that went bad is being replaced as I write 2: I was going to keep the logical volume/db name(/dbaa1dk3/db) the same so all the documentation stays the same. 3: The bad logical volume/file was -- /dbaa1dk3/db and it was mirrored to /dbaa1dk7/db This is the 1st failure we have seen. thanks for all your help, Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I am going to assume you know the syntax of the following commands so I will just give my answer at a high level if not post back and I will give the exact syntax, 1. Remove the failed volume from tsm by doing either a del dbv. 2. Then define a new DB vol with the def dbv command, you can use the f=XXX to format it to the size you need. 3. I know this sounds funny by now you need to delete the volume you just created. This will leave the formatted file on the OS file system. 4. Now you can use the def dbc command to get your self remirrored. BTW, as an alternative to steps 2 and 3 you could go to the OS level and do a dsmfmt command to create the DB volume as well, but I generally like to do it all with in TSM. As I said before, if you need the exact syntax please repost. I will need the exact filenames of the bad volume, the volume name it was mirrored to, and the name of the new volume. I hope that helps. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM
snapshot issue
Hello Everyone! I was wondering what might cause the following error to occur? I had the owner of hmch1134, which is a WinNT 5.0 server at the TSM 5.2.2.0 client level ask why they are receiving the errors. I don't have anything set on the TSM server and they are not aware of what might be causing snapshots to be tried. Does anyone have any ideas? I am sorry for my ignorance of Windows servers, but I really do not have any knowledge of that OS. Thank you in advance! Node Name: HMCH1134 Session established with server TSMPROD: AIX-RS/6000 Server Version 5, Release 2, Level 2.5 Data compression forced off by the server Server date/time: 04/05/2005 01:45:01 Last access: 04/05/2005 01:44:49 ANS1380W The snapshot operation failed. The filesystem write activity prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options. ANS1377W Unable to perform operation using a point-in-time copy of the filesystem on '\\hmch1134\e$'. The backup/archive operation will continue without snapshot support. Normal File--40,159,744 \\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak [Sent] Archive processing of '\\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak' finished without failure. Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: Disk gone bad, need help
Mark: Is the original mirror broken when you delete the volume? Thanks Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 2:01 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I like the command line but it can be done from the Web Admin tool if you like. The reason for the second and third commands is to create the file on the OS filesystem which will become the mirrored volume. As I said in an earlier note you could skip steps 2 and 3 by going to the OS command line and running a dsmfmt command to create the file that will become the DB copy volume. Since, I am often doing this remotely through the web admin tool and I don't always have access to an OS level prompt I use this method which allows me to do it entirely from within TSM. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. The logical volume that went bad was /dbaa1dk3 so I assumed since /dbaa1dk3/db was on the bad disk I could use the naming convention. The bottom note was from initial information from 1 of the UNIX admins, I went in and verified the information myself and found it to be different. Last questions since I'm a little confused but I'm sure that will pass. Why do you delete the volume before you mirror the data from the other disk? Also I see the GUI under Database volumes and there is a create data base volume, delete database volume and copy database volume. Is it better to use the command line over the GUI or does it not matter. Thanks again, this has been a great help. Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 1:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, Here you go, from a TSM command prompt issue the following. del dbv /dbaa1dk3/db def dbv /dbaa1dk3/db f=/size_in_MB/ del dbv /dbaa1dk3/db def dbc /dbaa1dk7/db /dbaa1dk3/db That should do it. The only thing you need to decide is how big to make it in the second command. Remember it is in MBs and it most be as big as the /dbaa1dk7/db volume. NOTE: I have noticed that you are not consistent as to which volume was on the failed drive as well as which volumes were mirrored. Please be certain about this before you proceed. If you are not sure then repost the output of the following commands: q dbv f=d q db f=d -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. Would you mind the full syntax. This is my 1st time through this and nobody around me seems to know about it. 1: The disk that went bad is being replaced as I write 2: I was going to keep the logical volume/db name(/dbaa1dk3/db) the same so all the documentation stays the same. 3: The bad logical volume/file was -- /dbaa1dk3/db and it was mirrored to /dbaa1dk7/db This is the 1st failure we have seen. thanks for all your help, Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I am going to assume you know the syntax of the following commands so I will just give my answer at a high level if not post back and I will give the exact syntax, 1. Remove the failed volume from tsm by doing either a del dbv. 2. Then define a new DB vol with the def dbv command, you can use the f=XXX to format it to the size you need. 3. I know this sounds funny by now you need to delete the volume you just created. This will leave the formatted file on the OS file system. 4. Now you can use the def dbc command to get your self remirrored. BTW, as an alternative to steps 2 and 3 you could go to the OS level and do a dsmfmt command to create the DB volume as well, but I generally like to do it all with in TSM. As I said before, if you need the exact syntax please repost. I will need the exact filenames
Re: snapshot issue
Please refer to page 638 in the Messages manual for TSM version 5.2, or by running help from the TSM command-line client and paging down to message number ANS1380E. (You may have a typo in your posting below.) Your problem is likely being caused by an overly large SQL backup file that is for some reason open during your backup, thus invoking the snapshot technology in an attempt to perform a backup of it. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, April 26, 2005 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: snapshot issue Hello Everyone! I was wondering what might cause the following error to occur? I had the owner of hmch1134, which is a WinNT 5.0 server at the TSM 5.2.2.0 client level ask why they are receiving the errors. I don't have anything set on the TSM server and they are not aware of what might be causing snapshots to be tried. Does anyone have any ideas? I am sorry for my ignorance of Windows servers, but I really do not have any knowledge of that OS. Thank you in advance! Node Name: HMCH1134 Session established with server TSMPROD: AIX-RS/6000 Server Version 5, Release 2, Level 2.5 Data compression forced off by the server Server date/time: 04/05/2005 01:45:01 Last access: 04/05/2005 01:44:49 ANS1380W The snapshot operation failed. The filesystem write activity prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options. ANS1377W Unable to perform operation using a point-in-time copy of the filesystem on '\\hmch1134\e$'. The backup/archive operation will continue without snapshot support. Normal File--40,159,744 \\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak [Sent] Archive processing of '\\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak' finished without failure. Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
? TSM STGpools on Nexsan ATABeast or EqualLogic PS200 or similar ?
Hi all, Are you using a Nexsan ATABeast or EqualLogic PS200 or similar box of disks for TSM STGpool space?? If so, we would like to talk with you about your experiences. We are now considering moving 40TB of TSM backups from 3590E tapes to sequential files on one/more of these boxes (or perhaps onto the vendor's box that you like best?) If you have experience to share, please reply directly, with your phone# and best time(s) to call, and we'll call you back. Thanks for your help. I'll summarize what we learn, back to the list. -- [EMAIL PROTECTED] (203.432.6693)
Re: snapshot issue
Hi Mark, When you say that it is most likely a large SQL backup file being open when I do a backup, could you be referring to a .tar file that is used to backup the SQL database? And if so, because the .tar file is open it is trying to invoke the snaphot technology? If so, is there a way to turn off snapshot capabilities? Thanks again! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] Stapleton, Mark [EMAIL PROTECTED] ERBEE.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: snapshot issue 04/26/2005 02:41 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Please refer to page 638 in the Messages manual for TSM version 5.2, or by running help from the TSM command-line client and paging down to message number ANS1380E. (You may have a typo in your posting below.) Your problem is likely being caused by an overly large SQL backup file that is for some reason open during your backup, thus invoking the snapshot technology in an attempt to perform a backup of it. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, April 26, 2005 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: snapshot issue Hello Everyone! I was wondering what might cause the following error to occur? I had the owner of hmch1134, which is a WinNT 5.0 server at the TSM 5.2.2.0 client level ask why they are receiving the errors. I don't have anything set on the TSM server and they are not aware of what might be causing snapshots to be tried. Does anyone have any ideas? I am sorry for my ignorance of Windows servers, but I really do not have any knowledge of that OS. Thank you in advance! Node Name: HMCH1134 Session established with server TSMPROD: AIX-RS/6000 Server Version 5, Release 2, Level 2.5 Data compression forced off by the server Server date/time: 04/05/2005 01:45:01 Last access: 04/05/2005 01:44:49 ANS1380W The snapshot operation failed. The filesystem write activity prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options. ANS1377W Unable to perform operation using a point-in-time copy of the filesystem on '\\hmch1134\e$'. The backup/archive operation will continue without snapshot support. Normal File--40,159,744 \\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak [Sent] Archive processing of '\\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak' finished without failure. Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: snapshot issue
No. From your message: \\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak [Sent] This is an SQL backup file. It appears that this could have been the culprit, since it is mentioned in the scheduled backups log. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, April 26, 2005 1:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: snapshot issue Hi Mark, When you say that it is most likely a large SQL backup file being open when I do a backup, could you be referring to a .tar file that is used to backup the SQL database? And if so, because the .tar file is open it is trying to invoke the snaphot technology? If so, is there a way to turn off snapshot capabilities? Thanks again! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] Stapleton, Mark [EMAIL PROTECTED] ERBEE.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: snapshot issue 04/26/2005 02:41 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Please refer to page 638 in the Messages manual for TSM version 5.2, or by running help from the TSM command-line client and paging down to message number ANS1380E. (You may have a typo in your posting below.) Your problem is likely being caused by an overly large SQL backup file that is for some reason open during your backup, thus invoking the snapshot technology in an attempt to perform a backup of it. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, April 26, 2005 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: snapshot issue Hello Everyone! I was wondering what might cause the following error to occur? I had the owner of hmch1134, which is a WinNT 5.0 server at the TSM 5.2.2.0 client level ask why they are receiving the errors. I don't have anything set on the TSM server and they are not aware of what might be causing snapshots to be tried. Does anyone have any ideas? I am sorry for my ignorance of Windows servers, but I really do not have any knowledge of that OS. Thank you in advance! Node Name: HMCH1134 Session established with server TSMPROD: AIX-RS/6000 Server Version 5, Release 2, Level 2.5 Data compression forced off by the server Server date/time: 04/05/2005 01:45:01 Last access: 04/05/2005 01:44:49 ANS1380W The snapshot operation failed. The filesystem write activity prevented the Logical Volume Snapshot Agent from satisfying the SNAPSHOTFSIDLEWait and SNAPSHOTFSIDLERetries options. ANS1377W Unable to perform operation using a point-in-time copy of the filesystem on '\\hmch1134\e$'. The backup/archive operation will continue without snapshot support. Normal File--40,159,744 \\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak [Sent] Archive processing of '\\hmch1134\e$\MSSQL\BACKUP\Highmark_prod_2005.bak' finished without failure. Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: Disk gone bad, need help
On Apr 26, 2005, at 2:03 PM, Jones, Eric J wrote: Is the original mirror broken when you delete the volume? Disk failure itself usually breaks TSM mirroring. Query DBVolume will show you the status. Richard Sims
Re: Disk gone bad, need help
Mark: Thank you very much. Life is good again in TSM land. I walked through the steps and it worked perfect. Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 2:01 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I like the command line but it can be done from the Web Admin tool if you like. The reason for the second and third commands is to create the file on the OS filesystem which will become the mirrored volume. As I said in an earlier note you could skip steps 2 and 3 by going to the OS command line and running a dsmfmt command to create the file that will become the DB copy volume. Since, I am often doing this remotely through the web admin tool and I don't always have access to an OS level prompt I use this method which allows me to do it entirely from within TSM. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. The logical volume that went bad was /dbaa1dk3 so I assumed since /dbaa1dk3/db was on the bad disk I could use the naming convention. The bottom note was from initial information from 1 of the UNIX admins, I went in and verified the information myself and found it to be different. Last questions since I'm a little confused but I'm sure that will pass. Why do you delete the volume before you mirror the data from the other disk? Also I see the GUI under Database volumes and there is a create data base volume, delete database volume and copy database volume. Is it better to use the command line over the GUI or does it not matter. Thanks again, this has been a great help. Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 1:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, Here you go, from a TSM command prompt issue the following. del dbv /dbaa1dk3/db def dbv /dbaa1dk3/db f=/size_in_MB/ del dbv /dbaa1dk3/db def dbc /dbaa1dk7/db /dbaa1dk3/db That should do it. The only thing you need to decide is how big to make it in the second command. Remember it is in MBs and it most be as big as the /dbaa1dk7/db volume. NOTE: I have noticed that you are not consistent as to which volume was on the failed drive as well as which volumes were mirrored. Please be certain about this before you proceed. If you are not sure then repost the output of the following commands: q dbv f=d q db f=d -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Jones, Eric J wrote: Thanks. Would you mind the full syntax. This is my 1st time through this and nobody around me seems to know about it. 1: The disk that went bad is being replaced as I write 2: I was going to keep the logical volume/db name(/dbaa1dk3/db) the same so all the documentation stays the same. 3: The bad logical volume/file was -- /dbaa1dk3/db and it was mirrored to /dbaa1dk7/db This is the 1st failure we have seen. thanks for all your help, Eric -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Rodriguez Sent: Tuesday, April 26, 2005 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Disk gone bad, need help Eric, I am going to assume you know the syntax of the following commands so I will just give my answer at a high level if not post back and I will give the exact syntax, 1. Remove the failed volume from tsm by doing either a del dbv. 2. Then define a new DB vol with the def dbv command, you can use the f=XXX to format it to the size you need. 3. I know this sounds funny by now you need to delete the volume you just created. This will leave the formatted file on the OS file system. 4. Now you can use the def dbc command to get your self remirrored. BTW, as an alternative to steps 2 and 3 you could go to the OS level and do a dsmfmt command to create the DB volume as well, but I generally like to do it all with in TSM. As I said before, if you need the exact syntax please
Re: How to find out all drives in NT2000 using command line? Thanks
I had talked to several people and found that dumpcfg utility would
generate the data I am looking for.
Thanks for all your help and effort.
Frank Tsao
[EMAIL PROTECTED]
PAX 25803, 626-302-5803
FAX 626-302-7131
Andrew Raibeck
[EMAIL PROTECTED]
OMTo
Sent by: ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor cc
Manager
[EMAIL PROTECTED] Subject
.EDU Re: How to find out all drives in
NT2000 using command line? Thanks
04/25/2005 09:16
AM
Please respond to
ADSM: Dist Stor
Manager
[EMAIL PROTECTED]
.EDU
Hi Frank,
There is no command that I can think of that does this; you'd have to write
a program or script to do it. Here are sample script and C++ program (they
both do the same thing). If these are useful, tailor as you wish.
Regards,
Andy
WMI SCRIPT
' ListDrives.vbs
' Invoke by running
'
'cscript ListDrives.vbs
'
' from an OS command prompt.
strComputer = .
set objWMIService = GetObject(winmgmts: _
{impersonationLevel=impersonate}!\\ _
strComputer \root\cimv2)
set disks = objWMIService.ExecQuery (select * from Win32_LogicalDisk)
for each objDisk in disks
select case objDisk.DriveType
case 0
' I would not normally expect to see this.
Wscript.Echo objDisk.DeviceID Unknown
case 1
Wscript.Echo objDisk.DeviceID Invalid root path
case 2
Wscript.Echo objDisk.DeviceID Removable
case 3
Wscript.Echo objDisk.DeviceID Fixed
case 4
Wscript.Echo objDisk.DeviceID Remote
case 5
Wscript.Echo objDisk.DeviceID CD-ROM
case 6
Wscript.Echo objDisk.DeviceID RAM disk
case Else
' I would not normally expect to see this.
Wscript.Echo objDisk.DeviceID ??
end select
next
C++ PROGRAM
/*
ListDrive.cpp
Compiled with Visual Studio .Net 2003 from an OS prompt as follows:
cl /GX /Zi /O1 ListDrives.cpp /link /debug
*/
#include windows.h
#include cstdio
#include cmath
#include iostream
using namespace std;
int main()
{
char driveLetter[] = *:\\;
DWORD drives= GetLogicalDrives();
DWORD bit = 0;
if (!drives)
{
cout ERROR: GetLogicalDrives() failed with rc
GetLastError() endl;
return -1;
}
for (int i = 0, bit = 1; i != 26; i++, bit *= 2)
{
if (drives bit)
{
cout char('A' + i) : ;
driveLetter[0] = 'A' + i;
switch (GetDriveType(driveLetter))
{
case DRIVE_UNKNOWN:
// I would not normally expect to see this.
cout Unknown;
break;
case DRIVE_NO_ROOT_DIR:
cout Invalid root path;
break;
case DRIVE_REMOVABLE:
cout Removable;
break;
case DRIVE_FIXED:
cout Fixed;
break;
case DRIVE_REMOTE:
cout Remote;
break;
case DRIVE_CDROM:
cout CD-ROM;
break;
case DRIVE_RAMDISK:
cout RAM disk;
break;
default:
// I would not normally expect to see this.
cout ??;
break;
} // switch (...)
cout endl;
} // if (drives bit)
} // for (...)
cout endl;
return 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-04-22
14:05:23:
Frank Tsao
[EMAIL PROTECTED]
PAX 25803, 626-302-5803
FAX 626-302-7131[attachment ListDrives.cpp deleted by Frank
Tsao/SCE/EIX]
Attachment ListDrives.vbs contains a potentially harmful file type
extension and was removed in accordance with IBM IT content security
practices.
Re: Multiple automated libraries in one storage pool
I tried opening a problem with Tivoli as to how to do this. He was wondering if, since the 3581 has two ports on the back, if you could hook one 3581 up to another. I told him what traditionally those ports were used for (two 400's taking turns with the one tape drive). He's not sure if it can be done, but that might be the only method. Is there any hope to this? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Rob Berendt [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04/26/2005 03:18 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Multiple automated libraries in one storage pool I have a Copy Storage Pool set up called LTO_3581_WEEK1. It currently uses Device class 3581DEV. The device class 3581DEV currently uses library TAPMLB01. I've added another physical media library to this machine, TAPMLB02. I would like the storage pool LTO_3581_WEEK1 to use both of these. How do I set them up? I want to back up to both devices at the same time. When I used manual libraries, with manual drives, it wasn't too hard to set up. However I can't figure out how to do multiple automated libraries. tsm 5.2.2 iSeries version V5R3M0 Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
