AW: TSM only reads from COPY1 during DB backup
I don´t think one can generally state that. If it were generally true than raid-1 controllers would have generally to be configured to read from one disk only in order , to paraphrase your words, not to cancell all gains obtained with disk-embedded read-ahead algorhytmus I believe such test results strongly depends on many different configuration issues, like raid implemented in one or two controllers, channel architecture used channel amount, read block size, raid buffer size, disk buffer size, read-ahead alghorythmus both on controller and on the disk, parameter setting etc.. Undoubtly, theoretical high performance limit reading from one disk is the disk´s streaming speed, theoretical high performance limit reading from two disks is twice as high. As always, in reality you only can converge to that limits but not reach them fully, and the more complicated the solution is (e.g. 2 disks against 1 disk) the larger the gap between real performance to the theoretical limit will be. The test mentioned by you apparently falls 50% under the theoretical performance limit, whis is rather bad, so I believe there either must have been a configuration issue, or one of the used components was of insufficient quality (maybe the raid firmware). best Juraj -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Paul van Dongen Gesendet: Mittwoch, 25. April 2007 21:55 An: ADSM-L@VM.MARIST.EDU Betreff: Re: TSM only reads from COPY1 during DB backup If it was't a dream, I remember reading something about this issue. It stated that this behaviour was by design, because reading blocks from both copies of a mirrored volume cancelled all gains obtained with controllers and disk subsistems read-ahead algorhythms. I even remember reading it was actually tested. Paul -Original Message- From: ADSM: Dist Stor Manager on behalf of Orville Lantto Sent: Wed 4/25/07 16:22 To: ADSM-L@VM.MARIST.EDU Cc: Subject: Re: TSM only reads from COPY1 during DB backup Performance is the issue. As tapes get faster and faster, trying to get a db backup without shoe-shining the tape drive gets harder. Using storage sub-system mirroring is an option, but not the recommended one for TSM. Perhaps there is a sound technical reason that db reads cannot be made from both sides of the mirror, but it could be that it was just programmer convenience. Either way, I will have to design around this feature to squeeze a bit more performance out of my storage. Orville L. Lantto Glasshouse Technologies, Inc. From: ADSM: Dist Stor Manager on behalf of Richard Sims Sent: Wed 4/25/2007 10:49 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM only reads from COPY1 during DB backup On Apr 25, 2007, at 10:55 AM, Orville Lantto wrote: Reads should be safe from mirrored volumes and are commonly done in operating systems to load balance. Not taking advantage of the available IO resource is wasteful and puts an unnecessarily unbalanced load on an already IO stressed system. It slows down db backups too. Then your issue is performance, rather than database voracity. This is addressed by the disk architecturing chosen for the TSM database, where raw logical volumes and RAID on top of high performance disks accomplishes that. Complementary volume striping largely addresses TSM's symmetrical mirror writing and singular reading. Whereas TSM's mirroring is an integrity measure rather then performance measure, you won't get full equivalence from that. Another approach, as seen in various customer postings, is to employ disk subsystem mirroring rather than TSM's application mirroring. In that way you get full duality, but sacrifice the protections and recoverability which TSM offers. Richard Sims Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: 10 Gbit ethernet [backups to remote data centers]
Keith, I can't speak about 10Gb, but we use fibre-extended 1Gb ethernets between our A B data centers. TSM clients @ A backup over the 1Gb network to a TSM service @ B. Their backups are stored on disks and tapes @ B. Similarly TSM clients @ B backup to a TSM service @ A. Works well for us. -- [EMAIL PROTECTED] (203.432.6693) Orville Lantto wrote: Can 10 Gbit Ethernet go 60 miles? How are you writing to the remote tape devices? Orville L. Lantto Glasshouse Technologies, Inc. From: ADSM: Dist Stor Manager on behalf of Lawrence Clark Sent: Wed 4/25/2007 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 10 Gbit ethernet Well, On the IBM SP we ran backups over the internal switch which was 17GB(yte) if I recall. And we currently have fibre attachements to drives, so I don't know why the speed of the NIC should be a concern. The operation of the NIC is under the OS, not TSM. [EMAIL PROTECTED] 04/25/07 4:41 PM Is anyone running TSM over 10 Gbit ethernet? Is there any question that it would be supported? We have two data centers about 60 miles apart. We are planning to send backup files from each data center to a 3584 ATL in the other via a 10 Gbit ethernet link. The server hardware would be HP DL585- G2's with Myricom 10 Gbit NICs and 2.6 Ghz AMD processors. The operating system would be Redhat EL 4. If anyone else has experience with TSM and 10 Gbit ethernet we would be glad to hear about it. Thank you, Keith Arbogast Indiana University The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments.
TSM thinks I'm out of disk space when I'm not
I have lately been having trouble backing by db up to sequential file. I see messages like this: 25/04/2007 18:00:25 ANR8785E Out-of-space in file system for FILE volume E:\FILECLASS\77520420.DBB. even though the selected partition has plenty of space (currently 48GB, full DB backup is 9GB). I guess it's probably because the device class is improperly setup. What parameters should I be looking for to successfully backup a 9GB database to a sequential file devclass?
Re: Active Object not found
Dinesh - You can search on gtUpdateGroupAttr in http://www.mail-archive.com/adsm-l@vm.marist.edu/ for past discussions on this. A fundamental problem here is that you're running a TSM client with no maintenance - a big no-no. Go to ftp://ftp.software.ibm.com/ storage/tivoli-storage-management/maintenance/ for the latest client maintenance within your 5.2 client. Richard Sims On Apr 26, 2007, at 12:50 AM, Pahari, Dinesh P wrote: Hi All, I have tsm client 5.2.0 and Tsm server 5.2.2. I am getting following errors in the dsmerror.log file. 4/25/2007 23:10:49 gtUpdateGroupAttr() server error 4 on update SYSTEM STATE\SYSFILES 04/25/2007 23:10:55 ANS1802E Incremental backup of '\\vgaaunsw014\e$' finished with 0 failure 04/25/2007 23:10:55 ANS1802E Incremental backup of '\\vgaaunsw014\e$' finished with 0 failure 04/25/2007 23:10:55 ANS1304W Active object not found On the tsm server, I tried changing the filespace name and did the manaul ASR and System State backup that completed successfully. But when I tried again, it failed. Are there any fix available with out any upgrades. Appreciate your feedbacks. Dinesh Pahari
Re: AW: TSM only reads from COPY1 during DB backup
On Apr 26, 2007, at 4:02 AM, Salak Juraj wrote: Hello Richard! I understand your arguments are either veracity or performance. I believe the point you possibly oversee is that if db reads were made from both sides of the mirror then db backup performance would (with high probabilty) significantly rise without harming database veracity. However, this is theory only, as this is apparently not implemented in TSM DB, point. Consequently both your and Orville´s conclusions are correct. Combining reliability and speed in current designs would lead to implementig both HW mirroring and TSM mirroring, at extra costs$. Hi, Juraj - Oh, I definitely appreciate the potential gains possible if all mirrors were employed for reads. (In the disks world, the more arms, the better.) But, as we know, that is not TSM's current methodology. There is the possibility of this situation changing, however, as pondered in paper A Close-up Look at Potential Future Enhancements available at http://tsm-symposium.oucs.ox.ac.uk/ 2005contributions.html . Perhaps this year's Oxford Symposium will air further momentum in this direction. Richard Sims
Re: 10 Gbit ethernet
Can 10 Gbit Ethernet go 60 miles? How are you writing to the remote tape devices? Orville L. Lantto Glasshouse Technologies, Inc. Orville, Our supercomputer people are using 10 Gbit connections between tape silos on the two data centers already. We intend to write to virtual volumes on 'the other end'. Keith A.
Re: 10 Gbit Ethernet
I assume this is a server to server connection? What is the distance and what sort of performance do you get? Orville Lantto Glasshouse Technologies, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Keith Arbogast Sent: Thursday, April 26, 2007 8:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 10 Gbit ethernet Can 10 Gbit Ethernet go 60 miles? How are you writing to the remote tape devices? Orville L. Lantto Glasshouse Technologies, Inc. Orville, Our supercomputer people are using 10 Gbit connections between tape silos on the two data centers already. We intend to write to virtual volumes on 'the other end'. Keith A.
Re: 10 Gbit ethernet [backups to remote data centers]
Anther methodology we employ for our Offsite Backup Copy Process is a 12Gige Fibre over IP (FCIP using a Cisco 9513 w/FCIP Blade) that spans approx 12miles. So far we are seeing 20 to 75MBS per Tape Device. Tape Devices are Zoned across the FCIP link for the primary DC TSM Server to write the Offsite to. I don't know the distance that FCIP can go without issues. Regards, Charles James R Owen [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04/26/2007 04:28 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] 10 Gbit ethernet [backups to remote data centers] Keith, I can't speak about 10Gb, but we use fibre-extended 1Gb ethernets between our A B data centers. TSM clients @ A backup over the 1Gb network to a TSM service @ B. Their backups are stored on disks and tapes @ B. Similarly TSM clients @ B backup to a TSM service @ A. Works well for us. -- [EMAIL PROTECTED] (203.432.6693) Orville Lantto wrote: Can 10 Gbit Ethernet go 60 miles? How are you writing to the remote tape devices? Orville L. Lantto Glasshouse Technologies, Inc. From: ADSM: Dist Stor Manager on behalf of Lawrence Clark Sent: Wed 4/25/2007 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 10 Gbit ethernet Well, On the IBM SP we ran backups over the internal switch which was 17GB(yte) if I recall. And we currently have fibre attachements to drives, so I don't know why the speed of the NIC should be a concern. The operation of the NIC is under the OS, not TSM. [EMAIL PROTECTED] 04/25/07 4:41 PM Is anyone running TSM over 10 Gbit ethernet? Is there any question that it would be supported? We have two data centers about 60 miles apart. We are planning to send backup files from each data center to a 3584 ATL in the other via a 10 Gbit ethernet link. The server hardware would be HP DL585- G2's with Myricom 10 Gbit NICs and 2.6 Ghz AMD processors. The operating system would be Redhat EL 4. If anyone else has experience with TSM and 10 Gbit ethernet we would be glad to hear about it. Thank you, Keith Arbogast Indiana University The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments. This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Open file support for Unix clients ?
Hi, I am annoyed by the many skipped log files during the daily incremental backups of the Unix clients. I could offcourse bind all log files to a mgmt class with dynamic or shared dynamic serialization but before I do that I'd like to know if there is something like 'open file support' for Unix clients. I didn't find it in the Unix Installation and Users Guide. BTW, this question is not about whether we should or should not backup log files (that is another discussion :-) Best regards / Mit freundlichen Grüßen / Sincères salutations Ronald Le Large
Re: Open file support for Unix clients ?
On Thursday 26 April 2007, Ronald Le Large wrote: Hi, I am annoyed by the many skipped log files during the daily incremental backups of the Unix clients. Unix has no problem backing up open files. Are you sure the setting on the copygroup is ok ? SERialization Specifies how the server handles files or directories when they are modified during backup processing. This parameter is optional. Possible values are: SHRSTatic Specifies that the server backs up a file or directory only if it is not being modified during backup. The server attempts to perform a backup as many as four times, depending on the value specified for the CHANGINGRETRIES client option. If the file or directory is modified during each backup attempt, the server does not back it up. Specifies that the server backs up a file or directory only if it is not being modified during backup. The server attempts to perform the backup only once. Platforms that do not support the STATIC option default to SHRSTATIC. For unix client, I set this on this: DYnamic Specifies that the server backs up a file or directory on the first attempt, regardless of whether the file or directory is being modified during backup processing. Stef
Re: Open file support for Unix clients ?
On Apr 26, 2007, at 11:43 AM, Ronald Le Large wrote: I am annoyed by the many skipped log files during the daily incremental backups of the Unix clients. ... It's common practice to periodically cut off Unix log files, with a frequency dictated by practical sizing or useful intervals (weekly, monthly). With those written by Syslog, sending a HUP signal to syslogd causes opening a fresh instance of the log. We add a .MMDD timestamp suffix to the cut off file, to know when the deed was done; then we do 'gzip -9' on that to minimally compress, then shuffle that off to an HSM file system for five years. Richard Sims
Operational Reporting Extensions
All, Is there a repository for Operational Reporting extensions somewhere? I am looking specifically for extensions that would give me all the information in the canned Node Activity Summary and Missed File Details reports, but allow me to filter nodes (by Domain for instance), similar to the filter allowed in the Client Schedules report. Also, I want to be able to sort all these reports alphabetically. Has anyone written these extensions? If so, I would be deeply appreciative if you would share. Thanks! Nancy Brizuela, CPA Systems Programmer, Senior University of Wyoming IBM/Unix Systems Group Ivinson Room 238 (307)766-2958
Migration of TSM from zLinux to Intel Linux
Has anyone out there done this sort of migration by restoring the TSM database from the old server to the new server? I've never worked with zLinux before, but my understanding is that zLinux partitions use the same type of filespaces (EXT2, EXT3, ReiserFS, etc.) that stand-alone Linux does. That being true, the database restore should be a snap. -- Mark Stapleton ([EMAIL PROTECTED]) Senior consultant
