TSM 5.3 client support
Hi *SM-ers! We are forced to downgrade our server level on our new TSM Server environment because the hardware we are about to use (EMC DL700) is not 5.3 certified. We are already using several 5.3.0 clients, so in the new environment we will backup to a 5.2.4.0 server (on AIX) with 5.3.0.0 clients (AIX and Windows) and start from scratch. I cannot find any information about whether using 5.3 clients to a 5.2 server is supported. I would like to use 5.3 for the client because this level is required for System State backup on Windows 2003. Thank you very much for your reply in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: TSM 5.3 client support
Eric, We use TSM 5.3 clients on several of our Windows clients to back-up to a TSM 5.2.4.4 server on AIX without problems. Richard. Loon, E.J. van - SPLXM [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 08-06-2005 09:28 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:TSM 5.3 client support Hi *SM-ers! We are forced to downgrade our server level on our new TSM Server environment because the hardware we are about to use (EMC DL700) is not 5.3 certified. We are already using several 5.3.0 clients, so in the new environment we will backup to a 5.2.4.0 server (on AIX) with 5.3.0.0 clients (AIX and Windows) and start from scratch. I cannot find any information about whether using 5.3 clients to a 5.2 server is supported. I would like to use 5.3 for the client because this level is required for System State backup on Windows 2003. Thank you very much for your reply in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: TSM 5.3 client support
Hi Richard! That's not what I asked. I know it works, but I would like to know whether it is supported. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Richard van Denzel [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 08, 2005 10:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3 client support Eric, We use TSM 5.3 clients on several of our Windows clients to back-up to a TSM 5.2.4.4 server on AIX without problems. Richard. Loon, E.J. van - SPLXM [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 08-06-2005 09:28 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:TSM 5.3 client support Hi *SM-ers! We are forced to downgrade our server level on our new TSM Server environment because the hardware we are about to use (EMC DL700) is not 5.3 certified. We are already using several 5.3.0 clients, so in the new environment we will backup to a 5.2.4.0 server (on AIX) with 5.3.0.0 clients (AIX and Windows) and start from scratch. I cannot find any information about whether using 5.3 clients to a 5.2 server is supported. I would like to use 5.3 for the client because this level is required for System State backup on Windows 2003. Thank you very much for your reply in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: TSM 5.3 client support
Hi Eric, In response to your query is 5,2 server with 5,3 clients supported. This is a general answer because we are not yet on 5.3 IBM has always stated with TSM that one level down is supported and I have seen nothing to contradict this. It would make it very difficult to upgrade if this was not the case. However there might be some aspects of the 5,3 client that require 5.3 server for full function. For examplet with 5,1 server and 5.2 clients systemstate backup does not work and has to be excluded. regards, John ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. 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. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. Scottish Hydro-Electric, Southern Electric, SWALEC, S+S and SSE Power Distribution are trading names of the Scottish and Southern Energy Group. **
Re: TSM 5.3 client support
On Jun 8, 2005, at 4:25 AM, Loon, E.J. van - SPLXM wrote: I cannot find any information about whether using 5.3 clients to a 5.2 server is supported. Eric - That info is always in the front of the client manuals, under Upgrade path for clients and servers. Answer: Yes. The usual caveat is that you should not attempt to employ new features where a combined server-client accommodation is needed to support them. Richard Sims
Re: TSM 5.3 client support
Hi Richard! This is exactly what I was looking for. Thank you very much for pointing me to the right direction! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 08, 2005 13:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM 5.3 client support On Jun 8, 2005, at 4:25 AM, Loon, E.J. van - SPLXM wrote: I cannot find any information about whether using 5.3 clients to a 5.2 server is supported. Eric - That info is always in the front of the client manuals, under Upgrade path for clients and servers. Answer: Yes. The usual caveat is that you should not attempt to employ new features where a combined server-client accommodation is needed to support them. Richard Sims ** 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: Advice needed for EMC CX500 setup
Hi Brian, I wish I had a magic formula to tell you what to do, but there is none. My suggestion is to create a raid5 raidset for the db/log, put your db/log onto it and run an expiration and db backup to see if you get the performance you need. If it's not good enough, then blow away the raidset and make it bigger and try again. Or, just do what we ended up doing - create a couple big raid5 raidsets and put db/log/storage pool across all drives. If the db load isn't heavy it will work, but expect to have to move the db/log to dedicated volumes sometime. This is strictly stop-gap stuff. I think you will basically have to try a setup, knowing full well you may have to change it if performance isn't good. Rick PAC Brion Arnaud [EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ALPINA.COM cc: Sent by: ADSM: Subject: Re: Advice needed for EMC CX500 setup Dist Stor Manager [EMAIL PROTECTED] .EDU 06/07/2005 09:50 AM Please respond to ADSM: Dist Stor Manager Richard (Aaron too), Many thanks for taking some of your time trying to help me ! Yes, you're absolutely right, my mail was lacking some important information, but I did not really knew where to begin ... To answer some of your questions : - number of nodes : approx 200, equally split in Windows and AIX environments. Some of them also hosting Informix and DB2 databases. - backups/day : approx 400 GB AIX/Win data, and 500 to 750 GB informix/db2. No archiving (except db2 logical logs), no hsm. - db actual size : 30GB, 80% used; expected 50% increase within one year (proportional to the expected increase of nodes). Number of objects (from expiration process) : 610. Our actual performance for expiration is approx 160 obj/hr, not much, but due to time constraints space reclamation is running parallely and slows it. I would expect getting the same performance, or better ! - log size : 13 GB for security as I'm using rollforward mode - expected iops : well, no idea at all. Some formula to calculate this ? Do you need something else ? Regards. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Rhodes Sent: Tuesday, 07 June, 2005 14:46 To: ADSM-L@VM.MARIST.EDU Subject: Re: Advice needed for EMC CX500 setup Hi Brion, I see that no one else has responded . . . . . let me stir up the waters and see what shakes loose . . . You don't inidicate the the number of nodes, db objects (files), backup rate (gb/day), etc, etc that you expect. This is key. You indicate a db of 70 gb with a full sized log - this means to me that you expect heavy db activity. For the tsm db, or for any other db for that matter, the question is how many iops do you need? The 133gb fc disk drive can probably give you around 120+ iops. I'm afraid that a 3 spindle raid 5 probably is not enough iops to run tsm instance with the activity you might have. Before my time on the storage team, Emc sold a disk subsystem to us for one of our TSM servers. It was a Clariion with all big drives. Like most disk purchases, it was configured on capacity, not i/o load. There was no way to split the drives between db/log and staging pools and have enough disk space for staging pools, or, enough spindles for db/log. The only way to make it work was to spread db/log/pools across all the spindles. NOT good . . . . actually, it worked quite well for the first year. Rick PAC Brion Arnaud [EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ALPINA.COM cc: Sent by: ADSM: Subject: Advice needed for EMC CX500 setup Dist Stor Manager [EMAIL PROTECTED] .EDU 06/06/2005 01:13 PM Please respond to ADSM: Dist Stor Manager Hi list, I need some guidance for setup of a brand new EMC array, equipped with 10 FC drives, 133GB each. TSM server (5.3.1) will be running on AIX 5.3. My goal is to use those disks for following purposes : - TSM DB 70 GB - TSM log 13 GB - TSM primary pools : all of the remaining space Questions : 1) EMC recommands using
Solaris 10 support
Hi All, Has anyone heard when TSM will support Solaris 10? Thanks, Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564)
Re: Advice needed for EMC CX500 setup
If you've got enough disks for it you also might want to think about a RAID 0+1 for the DB/Log volumes, as this would give much better write performance than RAID5. [EMAIL PROTECTED] 6/8/2005 6:38:45 AM Hi Brian, I wish I had a magic formula to tell you what to do, but there is none. My suggestion is to create a raid5 raidset for the db/log, put your db/log onto it and run an expiration and db backup to see if you get the performance you need. If it's not good enough, then blow away the raidset and make it bigger and try again. Or, just do what we ended up doing - create a couple big raid5 raidsets and put db/log/storage pool across all drives. If the db load isn't heavy it will work, but expect to have to move the db/log to dedicated volumes sometime. This is strictly stop-gap stuff. I think you will basically have to try a setup, knowing full well you may have to change it if performance isn't good. Rick PAC Brion Arnaud [EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ALPINA.COM cc: Sent by: ADSM: Subject: Re: Advice needed for EMC CX500 setup Dist Stor Manager [EMAIL PROTECTED] .EDU 06/07/2005 09:50 AM Please respond to ADSM: Dist Stor Manager Richard (Aaron too), Many thanks for taking some of your time trying to help me ! Yes, you're absolutely right, my mail was lacking some important information, but I did not really knew where to begin ... To answer some of your questions : - number of nodes : approx 200, equally split in Windows and AIX environments. Some of them also hosting Informix and DB2 databases. - backups/day : approx 400 GB AIX/Win data, and 500 to 750 GB informix/db2. No archiving (except db2 logical logs), no hsm. - db actual size : 30GB, 80% used; expected 50% increase within one year (proportional to the expected increase of nodes). Number of objects (from expiration process) : 610. Our actual performance for expiration is approx 160 obj/hr, not much, but due to time constraints space reclamation is running parallely and slows it. I would expect getting the same performance, or better ! - log size : 13 GB for security as I'm using rollforward mode - expected iops : well, no idea at all. Some formula to calculate this ? Do you need something else ? Regards. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Rhodes Sent: Tuesday, 07 June, 2005 14:46 To: ADSM-L@VM.MARIST.EDU Subject: Re: Advice needed for EMC CX500 setup Hi Brion, I see that no one else has responded . . . . . let me stir up the waters and see what shakes loose . . . You don't inidicate the the number of nodes, db objects (files), backup rate (gb/day), etc, etc that you expect. This is key. You indicate a db of 70 gb with a full sized log - this means to me that you expect heavy db activity. For the tsm db, or for any other db for that matter, the question is how many iops do you need? The 133gb fc disk drive can probably give you around 120+ iops. I'm afraid that a 3 spindle raid 5 probably is not enough iops to run tsm instance with the activity you might have. Before my time on the storage team, Emc sold a disk subsystem to us for one of our TSM servers. It was a Clariion with all big drives. Like most disk purchases, it was configured on capacity, not i/o load. There was no way to split the drives between db/log and staging pools and have enough disk space for staging pools, or, enough spindles for db/log. The only way to make it work was to spread db/log/pools across all the spindles. NOT good . . . . actually, it worked quite well for the first year. Rick PAC Brion Arnaud [EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ALPINA.COM cc: Sent by: ADSM: Subject: Advice needed for EMC CX500 setup Dist Stor Manager [EMAIL PROTECTED] .EDU 06/06/2005 01:13 PM Please respond to ADSM: Dist Stor Manager Hi list, I need some guidance for setup of a brand new EMC array, equipped with 10 FC drives, 133GB each. TSM
Re: Advice needed for EMC CX500 setup
Richard, Frank I really would like to use RAID 0+1, unfortunately this would waste too much of the precious space I'm needing for primary pools. Richard's idea seems to be the right one : I'll try running some performance tests (expiration, db backup) on several possible settings and opt for the most satisfying one. Kind of an empirical way of doing things, but the lack of precise documentation and/or advices leaves me no other way ... Thanks again ! Regards. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Wednesday, 08 June, 2005 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: Advice needed for EMC CX500 setup If you've got enough disks for it you also might want to think about a RAID 0+1 for the DB/Log volumes, as this would give much better write performance than RAID5. [EMAIL PROTECTED] 6/8/2005 6:38:45 AM Hi Brian, I wish I had a magic formula to tell you what to do, but there is none. My suggestion is to create a raid5 raidset for the db/log, put your db/log onto it and run an expiration and db backup to see if you get the performance you need. If it's not good enough, then blow away the raidset and make it bigger and try again. Or, just do what we ended up doing - create a couple big raid5 raidsets and put db/log/storage pool across all drives. If the db load isn't heavy it will work, but expect to have to move the db/log to dedicated volumes sometime. This is strictly stop-gap stuff. I think you will basically have to try a setup, knowing full well you may have to change it if performance isn't good. Rick PAC Brion Arnaud [EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ALPINA.COM cc: Sent by: ADSM: Subject: Re: Advice needed for EMC CX500 setup Dist Stor Manager [EMAIL PROTECTED] .EDU 06/07/2005 09:50 AM Please respond to ADSM: Dist Stor Manager Richard (Aaron too), Many thanks for taking some of your time trying to help me ! Yes, you're absolutely right, my mail was lacking some important information, but I did not really knew where to begin ... To answer some of your questions : - number of nodes : approx 200, equally split in Windows and AIX environments. Some of them also hosting Informix and DB2 databases. - backups/day : approx 400 GB AIX/Win data, and 500 to 750 GB informix/db2. No archiving (except db2 logical logs), no hsm. - db actual size : 30GB, 80% used; expected 50% increase within one year (proportional to the expected increase of nodes). Number of objects (from expiration process) : 610. Our actual performance for expiration is approx 160 obj/hr, not much, but due to time constraints space reclamation is running parallely and slows it. I would expect getting the same performance, or better ! - log size : 13 GB for security as I'm using rollforward mode - expected iops : well, no idea at all. Some formula to calculate this ? Do you need something else ? Regards. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Rhodes Sent: Tuesday, 07 June, 2005 14:46 To: ADSM-L@VM.MARIST.EDU Subject: Re: Advice needed for EMC CX500 setup Hi Brion, I see that no one else has responded . . . . . let me stir up the waters and see what shakes loose . . . You don't inidicate the the number of nodes, db objects (files), backup rate (gb/day), etc, etc that you expect. This is key. You indicate a db of 70 gb with a full sized log - this means to me that you expect heavy db activity. For the tsm db, or for any other db for that matter, the question is how many iops do you need? The 133gb fc disk drive can probably give you around 120+ iops. I'm afraid that a 3 spindle raid 5 probably is not enough iops to run tsm instance with the activity you might have. Before my time on the storage team, Emc sold a disk subsystem to us for one of our TSM servers. It was a Clariion with all big drives. Like
ISC/AC questions
We have taken the jump into testing for our TSM v5.1.6 to V5.3 upgrade. We got ISC/AC installed on a AIX server and are going through the learning curve for it, for which I've got some questions (like everyone else!) . . . . 1) On the table lists that AC creates there is a icon for enable/disable inline action bar. When I select it, it does . . . I'm not sure. The icon action switches from enable to disable (or back), but nothing changes in the table. I can't find any info on it in the help. What does this do? 2) Under the Settings tabs the portlets have an extra window icon for configure (along with minimize/maximize/help) where you can select the number of rows to show in tables. This does not appear on the portlet windows for Work items or Status. Is there no way to select the rows displayed for these tabs, or, is it just well hidden? 3) Is there anyway to set the default for tables to always set the Show row filter option so that the column filter buttons show up by default? 4) We want to have a second ISC/AC ready to go. (We have 2 datacenters - each is the DR site for the other, and a TSM server at each). What files need copied from one ISC/AC to another to keep the configuration (users defined and their TSM server that are defined)? 5) Do you have to shutdown ISC/AC to back it up (backing up isc-root directory structure)? We are using a AIX as our server which will let you backup open files, but that doesn't mean they are any good. 6) Has anyone implemeted SSL communications? Our security folks want us to implement this. I've read the info on doing this in the Ref Guide. Any wisdom/comments/problems with the procedure as layed out in appendix D? We do not have WebSphere in house and none of us in the storage area has any experience with web servers, let alone SSL. For example, it indicates that we need to get a certificate but never says what to do with it. It just refers you to the webSphere Security manual. Thanks Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Buggy exclude?
Hi, I've got a problem with a 5.2.x client on Linux talking to a 5.2.1.3 Windows-based TSM server This a client option is set on the server: EXCLUDE /tmp/.../* The following error gets logged: ANS1042S Include/Exclude pattern has a '...' without beginning/ending directory delimiter I don't see anything wrong, or have I been staring at it for too long? Kind regards, Rick Harderwijk Systems Administrator Factotum Media B.V. Postbus 335, 1200 AH Hilversum Oosterengweg 44, 1212 CN Hilversum The Netherlands Phone: +31-(0)35-6881166 Fax: +31-(0)35-6881199 Cell: +31-(0)6-551 64 64 5 E-mail: [EMAIL PROTECTED] www.factotummedia.nl http://www.factotummedia.nl/
Re: Advice needed for EMC CX500 setup
At the recent EMC conference at a session about Clariions, they indicated several things about Clariions that I thought I would share. From my notes . . . . 1) Raid 0+1 is better for writes, but doesn't help with reads. It will only/mostly use just one copy for reads. It's not as smart as a dmx/symm, which will perform reads from both copies. Raid 5 random reads are just as good as 0+1 random reads. 2) Raid 3. The way I heard it explained, r3 was recommended for big block sequential processing (like tsm staging pools) for ATA drives. The reasoning was that ATA drives don't currently have command tag queueing. Since they can only do one i/o op at a time, r3 fits real well with this. They recommended this for up to around 10 concurrent data streams to the raidset. The quote went something like this: ATA drives are brain dead, and raid 3 optimizes their brain-deadness. 3) Raid 5 on Fiber Channel drives is very good with large block sequential I/O. Raid 3 is not needed here. 4) Raid5 definitely has the write performance penality, which requires 4 i/o's per random write (not writing a full strip). This is hidden behind the write cache and performed later. They gave a rule of thumb of using raid5 for random I/O up to a write/read ratios of around 25-30%. That is, a random access pattern where there is 70% reads and 25% writes. 5) Leave the raidset strip size at the default (I think it's 64k, or 128 blocks). They have performed all kinds of internal testing and this is the optimum size for Clariion raid 5 raidsets. Period. The internal processing logic of the Clariion is optimized for this strip size - don't mess with it unless you reallly know what you are doing. 6) 15k rpm fc drives give around a 30% increase in small block random iops than 10k drives. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Solaris 10 support
For SPARC, we are currently targetting end of 2Q05 or beginning of 3Q05. Note that this is not a formal announcement or commitment, and is subject to change at the discretion of IBM. If you need a more formal answer, you should consult with your IBM marketing or account representative. There are no plans for x386 support at this time. 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-06-08 05:01:53: Hi All, Has anyone heard when TSM will support Solaris 10? Thanks, Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564)
Re: SUSPECT: (MSW) Re: Advice needed for EMC CX500 setup
Richard, This is what I call helpfull information ! It confirms what I read in EMC's engineering white paper Backup-to-Disk Guide with IBM Tivoli Storage Manager, where they recommend using RAID3 for storage pools. Unfortunately there was not any word about TSM DB and logs ... As our Clariion is also equipped with 50TB SATA drives, I'll use them as sequential type volumes with raid3, and will give raid5 a chance on FC drives, for primary disk pool where our nighly backups are landing (hopefully it will not be too slow), for DB and LOGS too ... Thanks. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Rhodes Sent: Wednesday, 08 June, 2005 16:57 To: ADSM-L@VM.MARIST.EDU Subject: SUSPECT: (MSW) Re: Advice needed for EMC CX500 setup At the recent EMC conference at a session about Clariions, they indicated several things about Clariions that I thought I would share. From my notes . . . . 1) Raid 0+1 is better for writes, but doesn't help with reads. It will only/mostly use just one copy for reads. It's not as smart as a dmx/symm, which will perform reads from both copies. Raid 5 random reads are just as good as 0+1 random reads. 2) Raid 3. The way I heard it explained, r3 was recommended for big block sequential processing (like tsm staging pools) for ATA drives. The reasoning was that ATA drives don't currently have command tag queueing. Since they can only do one i/o op at a time, r3 fits real well with this. They recommended this for up to around 10 concurrent data streams to the raidset. The quote went something like this: ATA drives are brain dead, and raid 3 optimizes their brain-deadness. 3) Raid 5 on Fiber Channel drives is very good with large block sequential I/O. Raid 3 is not needed here. 4) Raid5 definitely has the write performance penality, which requires 4 i/o's per random write (not writing a full strip). This is hidden behind the write cache and performed later. They gave a rule of thumb of using raid5 for random I/O up to a write/read ratios of around 25-30%. That is, a random access pattern where there is 70% reads and 25% writes. 5) Leave the raidset strip size at the default (I think it's 64k, or 128 blocks). They have performed all kinds of internal testing and this is the optimum size for Clariion raid 5 raidsets. Period. The internal processing logic of the Clariion is optimized for this strip size - don't mess with it unless you reallly know what you are doing. 6) 15k rpm fc drives give around a 30% increase in small block random iops than 10k drives. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Solaris 10 support
For SPARC, we are currently targetting end of 2Q05 or beginning of 3Q05. Note that this is not a formal announcement or commitment, and is subject to change at the discretion of IBM. If you need a more formal answer, you should consult with your IBM marketing or account representative. There are no plans for x386 support at this time. Thanks very much Andy for the prompt reply! 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-06-08 05:01:53: Hi All, Has anyone heard when TSM will support Solaris 10? Thanks, Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564) Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564)
Server message about password
A user received this from one of her machines. According to the Actlog, the password expired at the exact time, but processing continued and backups worked again last night. I can't find details in the manuals, but my supposition is that the PASSEXP=, and we use the default of 90, does not apply to the generated passwords. What I can't account for is the message itself. This is one of a dozen machines in this department, all of which have had their passwords expire numerous times without such a message. There is nothing on the machine itself that looks for and traps and transmits problems. Anyone have an idea of the source of this? Original Message Date: Tue, 7 Jun 2005 19:51:52 -0500 (CDT) From: Super-User [EMAIL PROTECTED] To: undisclosed-recipients:; Password for TSM server 'SERVER_A' has been changed to (an 8 character string) Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: Solaris 10 support
FYI We have the latest TSM client backup/archive code running on Solaris 10 test machine now so it is running but not yet supported. We also have the latest TDPO code installed for Oracle and is running in our test Solaris 10 machine but not yet supported. Justin Case TSM Administrator/Storage Administrator IT Analyst OIT Infrastructure Support 334 Blackwell Street 2nd floor Suite 2108 Durham,NC 27701 Duke University Andrew Raibeck [EMAIL PROTECTED] OMTo Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: Solaris 10 support 06/08/2005 11:34 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU For SPARC, we are currently targetting end of 2Q05 or beginning of 3Q05. Note that this is not a formal announcement or commitment, and is subject to change at the discretion of IBM. If you need a more formal answer, you should consult with your IBM marketing or account representative. There are no plans for x386 support at this time. 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-06-08 05:01:53: Hi All, Has anyone heard when TSM will support Solaris 10? Thanks, Steve Roder University at Buffalo ([EMAIL PROTECTED] | (716)645-3564)
Re: TSM 5.3 client support
I'm using 5.2.2.9 client to back up win2003 to a 5.2.4 server. Haven't had any issues except with VSS. Those same issues with VSS were also present on my 5.3.0 nodes. Loon, E.J. van - SPLXM [EMAIL PROTECTED] To M.COMADSM-L@vm.marist.edu Sent by: ADSM:cc Dist Stor Manager Subject [EMAIL PROTECTED] [ADSM-L] TSM 5.3 client support .edu 06/08/2005 03:28 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .edu Hi *SM-ers! We are forced to downgrade our server level on our new TSM Server environment because the hardware we are about to use (EMC DL700) is not 5.3 certified. We are already using several 5.3.0 clients, so in the new environment we will backup to a 5.2.4.0 server (on AIX) with 5.3.0.0 clients (AIX and Windows) and start from scratch. I cannot find any information about whether using 5.3 clients to a 5.2 server is supported. I would like to use 5.3 for the client because this level is required for System State backup on Windows 2003. Thank you very much for your reply in advance! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Server message about password
A user received this from one of her machines. According to the Actlog, the password expired at the exact time, but processing continued and backups worked again last night. I can't find details in the manuals, but my supposition is that the PASSEXP=, and we use the default of 90, does not apply to the generated passwords. What I can't account for is the message itself. This is one of a dozen machines in this department, all of which have had their passwords expire numerous times without such a message. There is nothing on the machine itself that looks for and traps and transmits problems. Anyone have an idea of the source of this? The TSM client software will mail out this kind of message if the 'mailprog' option is specified in the system options file. Original Message Date: Tue, 7 Jun 2005 19:51:52 -0500 (CDT) From: Super-User [EMAIL PROTECTED] To: undisclosed-recipients:; Password for TSM server 'SERVER_A' has been changed to (an 8 character string)
Re: TSM 5.3 client support
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David W Litten I'm using 5.2.2.9 client to back up win2003 to a 5.2.4 server. Haven't had any issues except with VSS. Those same issues with VSS were also present on my 5.3.0 nodes. Wandering the Microsoft support site, I found references to a good many of the VSC-related errors we find in dsmerror.log. Microsoft's solution for many of them is to install Win2003 SP1. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Office 262.521.5627
expire file does not find files............
expire files... I do a q backup /home/nysta/tclmgr/nysta-sector7/tollcoll_plz/*/* and get a long list but when I do a tsm exp file /home/nysta/tclmgr/nysta-sector7/tollcoll_plz/*/* I get Expire function invoked. Backup files will be expired. Do you wish to proceed? (Yes (Y)/No (N)) y ANS1302E No objects on server match query This is on AIX and I am invoking dsmc as root...
Re: expire file does not find files............
Your command syntax asks TSM to expire things called file and /home/nysta/tclmgr/nysta-sector7/tollcoll_plz/*/* You probably don't have a file out there called file. Richard Sims On Jun 8, 2005, at 2:52 PM, Lawrence Clark wrote: expire files... I do a q backup /home/nysta/tclmgr/nysta-sector7/tollcoll_plz/*/* and get a long list but when I do a tsm exp file /home/nysta/tclmgr/nysta-sector7/tollcoll_plz/*/* I get Expire function invoked. Backup files will be expired. Do you wish to proceed? (Yes (Y)/No (N)) y ANS1302E No objects on server match query This is on AIX and I am invoking dsmc as root...
Threshold on Copypool relcamation
A couple of weeks ago I was given the opportunity to take on the TSM admin role :-) I was wondering if anyone reclaims copy storage pools. Currently, we execute a schedule to reclaim space from our copy storage pool using the upd stgp copypool recl=80 command, this is scheduled for 15:00. Then we have a schedule to set the threshold back to 100%, using the upd stgp copypool recl=100 command at 18:00, but that doesn't work. We usually cancel it manually after 23:00. I took TSM classes about 4 years ago, and my book recommends leaving the threshold 100%, meaning no reclamation will occur. Once all offsite volumes go into an empty status we can bring them back. Our versions info - versions data exists, versions data deleted, retain extra versions, and retain only version are all set to 7. Wouldn't the tape empty after 7 days? Thanks, Debbie
Re: Threshold on Copypool relcamation
DEFINITION OF BACKUP RULES: VEREXISTS: # of versions to keep while file exists (adjusted by RETEXTRA) VERDELETED: # of versions to keep on TSM when file is deleted from client RETEXTRA: # of DAYS to keep non current versions defined by VEREXISTS RETONLY: # of DAYS to keep file(s) on TSM after deleted on client (adjusted by VEREDELETED) I would think you would set VEREDELETED to 1 After all , you are deleteing all the 'extra' versions after 7 days. Yes, we reclaim copy pools. Threshhold set to 50% setting it at 80% requires a lot of consolidation of a lot of volumes that have only 20% empty. No wonder you have long runs that need to be manually terminated. [EMAIL PROTECTED] 06/08/2005 3:55:58 PM A couple of weeks ago I was given the opportunity to take on the TSM admin role :-) I was wondering if anyone reclaims copy storage pools. Currently, we execute a schedule to reclaim space from our copy storage pool using the upd stgp copypool recl=80 command, this is scheduled for 15:00. Then we have a schedule to set the threshold back to 100%, using the upd stgp copypool recl=100 command at 18:00, but that doesn't work. We usually cancel it manually after 23:00. I took TSM classes about 4 years ago, and my book recommends leaving the threshold 100%, meaning no reclamation will occur. Once all offsite volumes go into an empty status we can bring them back. Our versions info - versions data exists, versions data deleted, retain extra versions, and retain only version are all set to 7. Wouldn't the tape empty after 7 days? Thanks, Debbie
Re: Threshold on Copypool relcamation
Thanks to allI had a brain block...I was thinking our copy storage pool was collocated, as are our primary pools,,boy, it's hard to get back in the saddle (and stay on) :-) Lawrence Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 06/08/2005 04:13 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: [ADSM-L] Threshold on Copypool relcamation DEFINITION OF BACKUP RULES: VEREXISTS: # of versions to keep while file exists (adjusted by RETEXTRA) VERDELETED: # of versions to keep on TSM when file is deleted from client RETEXTRA: # of DAYS to keep non current versions defined by VEREXISTS RETONLY: # of DAYS to keep file(s) on TSM after deleted on client (adjusted by VEREDELETED) I would think you would set VEREDELETED to 1 After all , you are deleteing all the 'extra' versions after 7 days. Yes, we reclaim copy pools. Threshhold set to 50% setting it at 80% requires a lot of consolidation of a lot of volumes that have only 20% empty. No wonder you have long runs that need to be manually terminated. [EMAIL PROTECTED] 06/08/2005 3:55:58 PM A couple of weeks ago I was given the opportunity to take on the TSM admin role :-) I was wondering if anyone reclaims copy storage pools. Currently, we execute a schedule to reclaim space from our copy storage pool using the upd stgp copypool recl=80 command, this is scheduled for 15:00. Then we have a schedule to set the threshold back to 100%, using the upd stgp copypool recl=100 command at 18:00, but that doesn't work. We usually cancel it manually after 23:00. I took TSM classes about 4 years ago, and my book recommends leaving the threshold 100%, meaning no reclamation will occur. Once all offsite volumes go into an empty status we can bring them back. Our versions info - versions data exists, versions data deleted, retain extra versions, and retain only version are all set to 7. Wouldn't the tape empty after 7 days? Thanks, Debbie
Re: Threshold on Copypool relcamation
On Wed, 8 Jun 2005, Debbie Bassler wrote: I was wondering if anyone reclaims copy storage pools. Currently, we execute a schedule to reclaim space from our copy storage pool using the upd stgp copypool recl=80 command, this is scheduled for 15:00. Then we have a schedule to set the threshold back to 100%, using the upd stgp copypool recl=100 command at 18:00, but that doesn't work. We usually cancel it manually after 23:00. I suspect when you say that doesn't work you mean that setting recl=100 doesn't kill any ongoing reclamation process (but that it does set the reclamation threshhold back to 100%)? If so, then that's behaving normally; the reclamation threshhold is only used by the TSM server to determine whether or not it should start a reclamation process. Once that process is running, it will normally run to completion regardless of what the reclamation threshhold is subsequently set to. I took TSM classes about 4 years ago, and my book recommends leaving the threshold 100%, meaning no reclamation will occur. Once all offsite volumes go into an empty status we can bring them back. I think what you do just depends on your needs and resources; if you have plenty of tapes, you can afford to do things this way. It may take quite a while for tapes to empty off, as the data on them expires only after the files become inactive (which could be 'never' for lots of clients). If you don't have an infinite supply of tapes, then reclamation seems reasonable; the higher the reclamation percentage you use, the 'more empty' a tape will be when it becomes eligible for reclamation. That can still mean a lot of mounts of primary pool tapes, though, in order to create a new copy pool tape containing that still-good data; this is the case if the primary pool is collocated and the copy pool is not, which is a pretty common scenario, I think. So you've gotta have a couple of tape drives free for a while in order to do the reclamation. Our versions info - versions data exists, versions data deleted, retain extra versions, and retain only version are all set to 7. Wouldn't the tape empty after 7 days? Only if all the data on the tape has gone inactive (files deleted from the client machine's disk, or newer versions of files backed up). Hope this helps, Bill Bill Kelly Auburn University OIT 334-844-9917
Re: Splitting files across tapes
Hi Wanda, I have some real data which might mean something for your question. I am in the process of moving all the files on one server into collocation groups. I am copying tapes to sequential disk to do this. The sizes of full disk volumes vary a lot which might mean that an aggregate won't go across disk base sequential volumes. The data, see the Est. cap for the full volumes -- tsm: XXXq vol stg=seqdisk2 Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status --- -- - - /seqdisk2/cgseq2_000 SEQDISK2SEQDISK2 2,016.0 100.0 Full /seqdisk2/cgseq2_001 SEQDISK2SEQDISK2 2,037.0 100.0 Full /seqdisk2/cgseq2_002 SEQDISK2SEQDISK2 2,016.9 100.0 Full /seqdisk2/cgseq2_003 SEQDISK2SEQDISK2 2,036.7 100.0 Full /seqdisk2/cgseq2_004 SEQDISK2SEQDISK2 2,043.4 100.0 Full /seqdisk2/cgseq2_005 SEQDISK2SEQDISK2 2,045.1 100.0 Full /seqdisk2/cgseq2_006 SEQDISK2SEQDISK2 2,035.0 100.0 Full /seqdisk2/cgseq2_007 SEQDISK2SEQDISK2 2,042.4 100.0 Full /seqdisk2/cgseq2_008 SEQDISK2SEQDISK2 2,008.0 100.0 Full /seqdisk2/cgseq2_009 SEQDISK2SEQDISK2 2,041.1 100.0 Full /seqdisk2/cgseq2_00A SEQDISK2SEQDISK2 2,034.3 100.0 Full /seqdisk2/cgseq2_00B SEQDISK2SEQDISK2 2,048.0 6.8 Filling /seqdisk2/cgseq2_00C SEQDISK2SEQDISK2 2,048.0 0.0 Empty /seqdisk2/cgseq2_00D SEQDISK2SEQDISK2 2,048.0 0.0 Empty /seqdisk2/cgseq2_01F SEQDISK2SEQDISK2 2,048.0 0.0 Empty /seqdisk2/cgseq2_020 SEQDISK2SEQDISK2 2,024.7 100.0 Full Hope this helps, Bill Colwell -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, June 07, 2005 10:07 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Splitting files across tapes Hi Richard, Thanks for responding; maybe this will give you something to amuse your brain over morning coffee. The reason for the question, mgmt here is considering going to all-disk backup (for onsite). So our sequential volumes will be disk instead of tape. We occasionally have issues with mis-classified data ending up on a tape, and the tape has to be pulled and destroyed. No big deal with a tape. Big deal when the volume is a 1 TB raid array! So the question comes, what is the likelihood that we would contaminate TWO 1 TB raid arrays with a split file? I think for sequential volumes, TSM doesn't know that the volume is full, until it tries to write to it. If there isn't space for the next block, then it mounts a scratch and rewrites the block to a new tape, yes? So can I assume that the file would have to be larger than an aggregate (what is that, MOVESIZETHRESH?) in order to end up split across 2 tapes? Thanks for lending brain power! W -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, June 07, 2005 9:55 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Splitting files across tapes Hi, Wanda - I don't believe there is any rule, per se: it is just the case that the drive finally reaches end-of-volume (EOV - TSM msg ANR8341I). This results in the subsequent data being written in a spanned Segment on a new volume. Richard Sims On Jun 7, 2005, at 9:36 AM, Prather, Wanda wrote: Does anyone happen to know what rules TSM uses to decide when to split a backup file/aggregate across 2 tapes? Or can you point me to a document? (Management wants to know.)
Conflicting slot counts
Why is my AIX TSM server lying about the slot count in my 3583 Library ? When I check the 3583 via the panel, it says there are 3-free slots. TSM refuses to check any more tapes into this library, saying it is full ! Yes, I have done an audit of the library (barcodes)...numerous times !
Keeping files in diskpools
All, First time poster, fairly new to the whole thing, so help much appreciated. We've got a TSM server on which we've just upgraded the disk array, from 1TB to 2TB. It also has a Spectralogic Treefrog unit with two AIT2 drives and a 15-slot robot. We're looking to keep the current generation of files from our main file server in the diskpools, so that we (in the event of a meltdown of the fileserver) won't have to resort to tape. The amount of storage on the file server is roughly 1TB - the other servers are only a small fraction of that. We've kept the old diskpools, and created new ones to catch new data. The file server currently has its storage divided into two partitions. I'm reconfiguring the array on the file server to add space, and I'm going to switch to a single large partition, and change the drive letter so that the TSM server will pick up all of the files on the reconfigured array as new. (I've got a copy of the data on a test machine, done with robocopy, to retain all of the ACL information, and will be copying the data back after the production file server is reconfigured.) Is there some way 1) to fix those files in their diskpools, or 2) get notification if they start to migrate to tape and/or 3) get notification if space in the diskpools is such that files from the file server are likely to migrate to tape? The version for TSM shown at the CLI interface is Version 5, Release 1, Level 5.0. Thanks, Kurt Buff Sr. Network Administrator Zetron, Inc. [EMAIL PROTECTED]
Re: Conflicting slot counts
On Jun 8, 2005, at 6:57 PM, Zoltan Forray/AC/VCU wrote: Why is my AIX TSM server lying about the slot count in my 3583 Library ? When I check the 3583 via the panel, it says there are 3-free slots. TSM refuses to check any more tapes into this library, saying it is full ! Yes, I have done an audit of the library (barcodes)...numerous times ! I'm no 3583 expert, but perhaps this entry in its manual explains it: Though the total number of slots available per storage column is 19, the server can only access 18 slots because the fixed, nonaddressable slot at the top of columns 2, 4, and 5 is reserved for cleaning cartridges and is not available. The librarys bar code reader cannot read the label of a cartridge that is stored in the fixed slot. I believe that the AutoClean dialog will report cleaning tape population of those reserved slots. The manual doesn't make clear if the overall slots count reported by the library includes the reserved slots. If this doesn't agree with your library situation, perhaps you could post more details, as in total slots count, number of columns present, and where the free slots are located: this may help with the analysis. Richard Sims
Re: password
Seeing this post prompted me to run a test. It appears that Windows 2003 cluster ensures the replication of the changed password happens right away, not when the group fails over. Details: I have 3 test clusters a Windows 2000 cluster a Windows 2003 cluster and a Windows 2003 Itanium cluster. I set the password expiration for all the nodes on all clusters to 1 day. The next day the password changed as it should. The registry reflected the new password on all nodes that currently own the group that TSM service is in. On the Windows 2003 clusters the password matched. On the Windows 2000 cluster the node that did not own the group still had the old password. As you suggest a controlled move of the group did update the password however it took that. So I see where a system crash would result in an invalid password on the other side of the cluster. However, it looks like a Windows 2003 cluster does not have this issue. I know that Windows 2000 is still out there but with advanced features like clustering. I've found more and more people migrating to Windows 2003 so if your there you don't have the same fear and thus should be able to use the password expiration. Wheelock, Michael D [EMAIL PROTECTED] wrote: Hi, The answer is that it depends. 1) For the normal backup/archive client and the ms-sql and ms-exchange clients, this is no problem. They will change their passwords without issue. 2) The oracle client cannot change its password on its own. 3) Microsoft clusters (IMHO) should still be set to 0. Here is why (from experience no less). The encrypted password for a B/A client is stored in the registry. The manual states that you need to have the generic service you setup in cluster administrator copy over this reg key when the service moves. This only works in the world where servers don't crash. If the server crashes, the key does not get copied (how can it...the server that had it is down) and the service can fail to start (likely because it has the old password). 4) Unix B/A has no problem with this. Others may be able to speak to the domino clients, etc as I have no experience with them. Michael Wheelock Integris Health -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Brenda Collins Sent: Monday, June 06, 2005 2:07 PM To: ADSM-L@VM.MARIST.EDU Subject: password We use password access generate on all of our configurations. In the past, we have used expiration 0 so that we do not run into issues with expirations. We are now being asked to set up an expiration period and I am wondering if the 'passwordaccess generate' is going to create a new password itself upon expiration or just fail the backup. The manual does not state that it will do that and I do not want backups failing as a result of the passwords expiring. I have heard answers both ways on this configuration. For anyone expiring passwords, are you resetting them manually or does this happen automatically? Thanks, Brenda ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
