AW: 5.2.3.5 Upgrade and Slow Expiration
Wats about your logpoolsize and logutil at this moment? regards joachim -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Auftrag von Hart, Charles Gesendet: Mittwoch, 15. Dezember 2004 21:10 An: [EMAIL PROTECTED] Betreff: 5.2.3.5 Upgrade and Slow Expiration We have two identical TSM Server (AIX 5.2 / p630 / TSM 5.2.3.5) They were both @ TSM 5.2.3.4 then we upgraded to 5.2.3.5 on the same day. One of the servers has been running just fine (TSM Server1). When the other TSM server (TSM Server2) runs Expiration it grinds to a halt with in an hour regardless of doing a cancel expiration or just trying to cancel the process. This TSMServer2 Backups / Archives our Oracle Env so when Expiration runs it brings the TSM Server instance to its knees to the point it won't take client data. Server Info: TSM Server 1 ver 5.2.3.5 DB = 141GB Cache Hit 98.89% Expiration Runs Fine (thousands obj per min) Backup Clients are primarily Windows (4-500 Clients) TSM Server 2 ver 5.2.3.5 DB = 149GB DB Cache Hit 98.26% Expiration Runs So Slow (a few obj per min) Backup Clients are primarily Unix (2-300 Clients) Does dsmc Archives and Incremental Has anyone run into strange issues when going to 5.2.3.5? I have a PMR open... but not getting much out of them... (Which usually isn't the case) I have searched the list and any APARS... No luck yet. Appreciate any info!
Re: Best practice for backing up same data different schedule?
On Dec 15, 2004, at 3:54 PM, Robert Knutsen wrote: What is the best way to automatically backup the same data at different intervals? I want weekly, monthly and yearly backups of the same data on a schedule I setup, with expiring old data automatically. ... Robert - "Full-Incremental Rotations Using IBM Tivoli Storage Manager": http://www.ibm.com/support/docview.wss?uid=swg27005212 Richard Sims
5.2.4.0 Servers available for download
Hi *SM-ers! For those of you who haven't noticed it yet: IBM has quietly put the 5.2.4.0 server codes on their FTP server. 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: 5.2.4.0 Servers available for download
A new client code 5.2.3.11 is posted with yesterdays date. [BINARY] TSM523C_11_WIN32.exe . . . . . . . . . .[Dec 15 16:37] 18M Regards, Samiran Das -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Thursday, December 16, 2004 7:52 AM To: [EMAIL PROTECTED] Subject: Re: 5.2.4.0 Servers available for download Could you please send a link to where you found this code? I just went out to try to get the 5.2.4.0 code for a Windows 2000 client and I couldn't find it. Thank you in advance! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED] To M.COM>[EMAIL PROTECTED] Sent by: "ADSM: cc Dist Stor Manager" Subject <[EMAIL PROTECTED] 5.2.4.0 Servers available for .EDU> download 12/16/2004 07:04 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hi *SM-ers! For those of you who haven't noticed it yet: IBM has quietly put the 5.2.4.0 server codes on their FTP server. 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. ** If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: license costs
>You can't. To be short, you need 1 license / cpu for the servers. OS doesn't >matter. The license count on the server is based on the number of active >nodes. So the number of license you have to buy have nothing to do with the >numer reported by the TSM server. Here is an example of how TSM nodes may not match licensing. We are implementing VMWare - consolidating on average 8 windows servers onto one blade/vmware server. When we checked with IBM, we were told that TSM pricing is per cpu - the number of Win instances doesn't come into it at all. Our TSM server still sees all the individual Windows nodes, but for licensing we only have to count a fraction of them. The interesting result of this is having lots of extra licenses right now. Rick. Stef Coene <[EMAIL PROTECTED]To: [EMAIL PROTECTED] .ORG>cc: Sent by: "ADSM: Subject: Re: license costs Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 12/14/2004 02:56 PM Please respond to "ADSM: Dist Stor Manager" On Tuesday 14 December 2004 19:37, Muthyam Reddy wrote: > ** High Priority ** > > Hi , > present we are taking AIX/DB2 backups to tsm and whenever I add new AIX > client I update server license . > Soon we re planning to take NOVEL,NT client backups tsm. > Do I need to buy extra license for other client backups, NOVEL and NT? > How to check existing License term on TSM server? You can't. To be short, you need 1 license / cpu for the servers. OS doesn't matter. The license count on the server is based on the number of active nodes. So the number of license you have to buy have nothing to do with the numer reported by the TSM server. Stef -- [EMAIL PROTECTED]"Using Linux as bandwidth manager" http://www.docum.org/ - 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: 5.2.4.0 Servers available for download
Eric informed about 5.2.4.0 server code, not client code. Regards, Samiran Das -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Thursday, December 16, 2004 7:52 AM To: [EMAIL PROTECTED] Subject: Re: 5.2.4.0 Servers available for download Could you please send a link to where you found this code? I just went out to try to get the 5.2.4.0 code for a Windows 2000 client and I couldn't find it. Thank you in advance! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED] To M.COM>[EMAIL PROTECTED] Sent by: "ADSM: cc Dist Stor Manager" Subject <[EMAIL PROTECTED] 5.2.4.0 Servers available for .EDU> download 12/16/2004 07:04 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hi *SM-ers! For those of you who haven't noticed it yet: IBM has quietly put the 5.2.4.0 server codes on their FTP server. 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. ** If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: 5.2.4.0 Servers available for download
On Dec 16, 2004, at 7:04 AM, Loon, E.J. van - SPLXM wrote: For those of you who haven't noticed it yet: IBM has quietly put the 5.2.4.0 server codes on their FTP server. Thanks, Eric. IBM: The TSM support page, http://www.ibm.com/software/sysmgmt/products/support/ IBMTivoliStorageManager.html is the ideal venue for communicating the availability of significant new software levels. Could this practice be instituted? thanks, Richard Sims
Re: Tdp for Microsoft Exchange server question
Robert, You need to make sure that you have enough space on your volumes that contain the transaction logs for each Exchange storage group. With Exchange differentials, the transaction logs are not truncated until the next full backup. And so, you will need to make sure there is enough space to hold all transaction logs that are created between each full backup. Alternatively, you could use incremental backups, so that the logs are truncated at each incremental, but depending on the setup of your storage pools, you may pay a small penalty at restore time if the incremental backups are spread among different tapes. (If you have enough disk storage pool space and the incremental backups can remain on disk storage pool, that is the best because from the TSM perspective, restoring a series of incremental backups will be very similar to restoring the latest differential... but you will get the added benefit on the Exchange server transaction log volume because the logs will be truncated more frequently. It boils down to where you want to put your disk storage, I suppose.) And so, there are different ways to approach this depending on your TSM Server storage pool setup. The main thing to remember, though, is do not let you Exchange server transaction log volumes fill up. One other bit of information when moving to less frequent full backups... Keep in mind that come restore time, you will have the additional Exchange transaction log replay for the differential or incremental backups. The log replay will add clock time to your recovery. Thanks, Del "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 12/16/2004 02:37:05 AM: > Hi to all > > I run a backup with a TDP for Microsoft Exchange server 2003 > version 5.2.1.0 on a Tsm server 5.2.3.0 , still now I backup every > night full and during the day I made 3 incremental backup , but my > database is growing a lot ... I am thinking of changing the backup > to once or two full backup during the week and between 2 or 3 > differentials backup each day . > > Did I need to be aware of something special as my space on my > Exchange server because the log's will not be erase till the full > backup or something else ? > > T.I.A Regards > Robert Ouzen > E-mail: [EMAIL PROTECTED]
Re: how to move an NT client to a new backup server
This is under one of the menu Options in the normal Backup/Restore GUI on the client. Cheers, James. James Park. Infrastructure Specialist. EDS Production Engineering Service Delivery Systems Management Team -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weinstein, Stephen Sent: 16 December 2004 14:54 To: [EMAIL PROTECTED] Subject: Re: how to move an NT client to a new backup server Should this GUI utility be on the client somewhere, or do I need the CD. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim Sent: Wednesday, December 15, 2004 3:17 PM To: [EMAIL PROTECTED] Subject:Re: how to move an NT client to a new backup server Usually you will have to update the password entries in the registry for the schedule service when you point to another server. Run the GUI - Utilities - Setup Wizard - Help Me configure the Client Scheduler - Update a previously installed scheduler and go through the steps and enter the password, ensure the services are started after this process (you can check the event log for the next scheduled event if you log events to then nt event log.) -Original Message- From: Weinstein, Stephen [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 1:30 PM To: [EMAIL PROTECTED] Subject: how to move an NT client to a new backup server I have several Windows NT4 servers being backed up on my old Tivoli backup server. I have a new backup server I would like to move these servers to. What I have done So far is set up the clients on the new server and on each client modified to DSM.OPT File pointing it to the new server. I then stopped and restarted the service. The servers however Do not backup. Anyone know what else needs to be done. Thanx steve ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. **
Re: license costs
Well said, Rick. And a downside to this (new in 2004 i think) TSM way of licensing, where you actually end up having to pay MORE: If you have an 8-processor Windows server for each of 50 different applications in your business (sort of the opposite of consolidation) . From: ADSM: Dist Stor Manager on behalf of Richard Rhodes Sent: Thu 12/16/2004 8:13 AM To: [EMAIL PROTECTED] Subject: Re: license costs >You can't. To be short, you need 1 license / cpu for the servers. OS doesn't >matter. The license count on the server is based on the number of active >nodes. So the number of license you have to buy have nothing to do with the >numer reported by the TSM server. Here is an example of how TSM nodes may not match licensing. We are implementing VMWare - consolidating on average 8 windows servers onto one blade/vmware server. When we checked with IBM, we were told that TSM pricing is per cpu - the number of Win instances doesn't come into it at all. Our TSM server still sees all the individual Windows nodes, but for licensing we only have to count a fraction of them. The interesting result of this is having lots of extra licenses right now. Rick. Stef Coene <[EMAIL PROTECTED]To: [EMAIL PROTECTED] .ORG>cc: Sent by: "ADSM: Subject: Re: license costs Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 12/14/2004 02:56 PM Please respond to "ADSM: Dist Stor Manager" On Tuesday 14 December 2004 19:37, Muthyam Reddy wrote: > ** High Priority ** > > Hi , > present we are taking AIX/DB2 backups to tsm and whenever I add new AIX > client I update server license . > Soon we re planning to take NOVEL,NT client backups tsm. > Do I need to buy extra license for other client backups, NOVEL and NT? > How to check existing License term on TSM server? You can't. To be short, you need 1 license / cpu for the servers. OS doesn't matter. The license count on the server is based on the number of active nodes. So the number of license you have to buy have nothing to do with the numer reported by the TSM server. Stef -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ - 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: license costs
On Thursday 16 December 2004 14:13, Richard Rhodes wrote: > >You can't. To be short, you need 1 license / cpu for the servers. OS > > doesn't > > >matter. The license count on the server is based on the number of active > >nodes. So the number of license you have to buy have nothing to do with > > the > > >numer reported by the TSM server. > > Here is an example of how TSM nodes may not match licensing. An other example is how we backup AIX cluster. We use different TSM client node names for the AIX and the application data so we can take a backup or restore when there is a failover. So we can have 10 different TSM clients to backup 2 x 1 CPU, AIX servers. Stef -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/
Re: TSM 5.2.3 journal service crashes?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joe Howell >I'm having problems with the journal service on one of my >clients and need some idea if the problem is with me or with >the service. This particular system is a large Windows 2000 >file server, with around 175GB of stuff on one drive. Because >of processing constraints I am restricted to a 5-hour backup >window. To deal with the root of your problem, have you multithreaded your backup with the use of multiple nodenames? Have you considered the use of weekly image backups in combination with daily regular backups? -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Special Technique for Recovering lost Backups
See my response to a similar question in the adsm-l archives at http://msgs.adsm.org/cgi-bin/get/adsm0001/264.html. 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" <[EMAIL PROTECTED]> wrote on 12/16/2004 09:59:34: > Hi all. > > I want to know if there is a special technique that can be performed > to recover backups on tapes from a server that lost the DB completely. > > Apparently one of our branches was still doing backups using a 3.7 > ADSM server. They lost their DB, no backups but they have the library > :D > > Does Tivoli have a procedure that could actually recover that data? > > Long shot? :D
Re: how to move an NT client to a new backup server
Should this GUI utility be on the client somewhere, or do I need the CD. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim Sent: Wednesday, December 15, 2004 3:17 PM To: [EMAIL PROTECTED] Subject:Re: how to move an NT client to a new backup server Usually you will have to update the password entries in the registry for the schedule service when you point to another server. Run the GUI - Utilities - Setup Wizard - Help Me configure the Client Scheduler - Update a previously installed scheduler and go through the steps and enter the password, ensure the services are started after this process (you can check the event log for the next scheduled event if you log events to then nt event log.) -Original Message- From: Weinstein, Stephen [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 1:30 PM To: [EMAIL PROTECTED] Subject: how to move an NT client to a new backup server I have several Windows NT4 servers being backed up on my old Tivoli backup server. I have a new backup server I would like to move these servers to. What I have done So far is set up the clients on the new server and on each client modified to DSM.OPT File pointing it to the new server. I then stopped and restarted the service. The servers however Do not backup. Anyone know what else needs to be done. Thanx steve ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. **
Re: license costs
FWIW, You may know this already, but make sure you are only paying for REAL processors. A lot of 4-processor servers that have HYPERTHREADING capability APPEAR to have 8 processors, but really only have 4. So you only have to license 4. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Heineman, Joyce Sent: Thursday, December 16, 2004 10:01 AM To: [EMAIL PROTECTED] Subject: Re: license costs Well said, Rick. And a downside to this (new in 2004 i think) TSM way of licensing, where you actually end up having to pay MORE: If you have an 8-processor Windows server for each of 50 different applications in your business (sort of the opposite of consolidation) . From: ADSM: Dist Stor Manager on behalf of Richard Rhodes Sent: Thu 12/16/2004 8:13 AM To: [EMAIL PROTECTED] Subject: Re: license costs >You can't. To be short, you need 1 license / cpu for the servers. OS doesn't >matter. The license count on the server is based on the number of active >nodes. So the number of license you have to buy have nothing to do with the >numer reported by the TSM server. Here is an example of how TSM nodes may not match licensing. We are implementing VMWare - consolidating on average 8 windows servers onto one blade/vmware server. When we checked with IBM, we were told that TSM pricing is per cpu - the number of Win instances doesn't come into it at all. Our TSM server still sees all the individual Windows nodes, but for licensing we only have to count a fraction of them. The interesting result of this is having lots of extra licenses right now. Rick. Stef Coene <[EMAIL PROTECTED]To: [EMAIL PROTECTED] .ORG>cc: Sent by: "ADSM: Subject: Re: license costs Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 12/14/2004 02:56 PM Please respond to "ADSM: Dist Stor Manager" On Tuesday 14 December 2004 19:37, Muthyam Reddy wrote: > ** High Priority ** > > Hi , > present we are taking AIX/DB2 backups to tsm and whenever I add new AIX > client I update server license . > Soon we re planning to take NOVEL,NT client backups tsm. > Do I need to buy extra license for other client backups, NOVEL and NT? > How to check existing License term on TSM server? You can't. To be short, you need 1 license / cpu for the servers. OS doesn't matter. The license count on the server is based on the number of active nodes. So the number of license you have to buy have nothing to do with the numer reported by the TSM server. Stef -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ - 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: Passwordaccess Generate
The dsmcutil.exe utility has a "showpw" command that displays the password for the node: dsmcutil showpw /node:yournodename This has to be run on the machine where the password is encrypted (password is encrypted in the registry). There is no email facility for sending the new password. In general, there is no need for someone to know the password once its been encrypted (this is what "passwordaccess generate" is for!). In cases where the password needs to be known (such as if you are restoring to a different machine), ask the TSM administrator to update the node with a known password, then use the -virtualnodename option when starting the client. In such a case, you will also need to re-encrypt the password on the machine that normally uses the node name, since the current encrypted password will, of course, be invalid. To re-encrypt the password on the node's machine, launch the TSM client, which will prompt you for the new password. The "showpw" command has been removed from dsmcutil.exe as of version 5.3. 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" <[EMAIL PROTECTED]> wrote on 12/16/2004 09:27:27: > Dear All, > > I am using Tivoli Storage Manager v5.2.10 on a Windows Server 2003 > machine with the PASSWORDACCESS GENERATE option in my dsm.opt file. Is > there a way to be notified of the new password when the TSM client > changes it (e.g. in the same manner as the MAILPROG option to the unix > client) or to read the new password from the disk? > > Many thanks, > > Chris.
Re: Passwordaccess Generate
On Windows it's not on disk, it's in the registry, but it's encrypted. You shouldn't ever need to know it, there are other ways to do everything I can think of. What problem are you having that you need it for? Maybe I can tell you how to get around it -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris Rodgers Sent: Thursday, December 16, 2004 11:27 AM To: [EMAIL PROTECTED] Subject: Passwordaccess Generate Dear All, I am using Tivoli Storage Manager v5.2.10 on a Windows Server 2003 machine with the PASSWORDACCESS GENERATE option in my dsm.opt file. Is there a way to be notified of the new password when the TSM client changes it (e.g. in the same manner as the MAILPROG option to the unix client) or to read the new password from the disk? Many thanks, Chris.
Re: POLICY SET Question
You are exactly correct! Changes to the management classes/copy groups do not take effect immediately, they take effecty when you Activate the policy set. That will make the Changed policy set and Active the same. Changing RETEXTRA and RETONLY to 180 will do what you want. The only time you should have to stop/restart your TSM server are to apply server maintenance, to restore the data base (hopefully something you nEVER have to do!) or (sometimes) to clear a hardware problem. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Eric J Sent: Wednesday, December 15, 2004 1:05 PM To: [EMAIL PROTECTED] Subject: POLICY SET Question Good Afternoon. I'm new to the policy sets and someone else set them up for the server. I need to make a change to a Policy Set and was wondering if I needed to stop and start the server for the change to take affect. I need to change the Retain Extra Versions and Retain Only Version from 30 days to 180 days(6 months). If I go into the POLICY SET and drill down to "STANDARD Backup Copy Group" for the policy and do a "Update Copy Group" and change from 30 to 180 will it take affect immediately or do I need to be at the Policy Sets, Select "Validate Policy Set", then "Activate Policy Set". Also when I "Activate Policy Set" does this move it to the "ACTIVE" so both are the same. I need to keep all copies of the file for 180 days. I'm running TSM 5.2.2 server on AIX 5.2. = Backup Copy Groups : UNIX6MONTH UNIX6_MONTH_POLICY UNIX6_MONTH_MGMT STANDARD Policy Domain Name UNIX6MONTH Policy Set Name UNIX6_MONTH_POLICY Mgmt Class Name UNIX6_MONTH_MGMT Copy Group Name STANDARD Versions Data ExistsNOLIMIT Versions Data Deleted NOLIMIT Retain Extra Versions 30 Retain Only Version 30 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationDISKPOOL3 Table of Contents (TOC) Destination - Last Update Date/Time 2004-08-24 07:31:25.00 Last Update by (administrator) JONES Managing profile- Have a Great Day, Eric Jones > * [EMAIL PROTECTED] > *: 607-751-4133 Cell : 607-972-7621
scripts.smp missing on Windows server
A question for the development folks: I have been upgrading my Windows-based TSM server and for the last 5.2.3.x releases as well as 5.2.4.0 scripts.smp was not reinstalled into the server directory. I found the sample scripts extremely useful - it would be nice if they were re-packaged into the server package. Joerg Pohlmann 604-535-0452
Re: Passwordaccess Generate
You shouldn't ever need to know it, there are other ways to do everything I can think of. What problem are you having that you need it for? Maybe I can tell you how to get around it My computer is backed up via TSM to my university's central ADSM server. If I want to do anything which needs more than my own node password (which I know), I have to raise a support request with them. For password resets, these are set to something random which is then sent out on paper arriving a day or two later! Therefore, if I want to be able to recover files in the event of my machine dying (as I did this afternoon), it's invaluable to have the node password so that I can use the -virtualnodename option on another machine to get back my files more quickly and get back to work. Similarly, if a machine dies completely, one also has to wait for the paper password to arrive before being able to get on with doing a bare metal restore because of course the encrypted password dies with the machine. Hmm... Why has this facility (or the MAILPROG equivalent) been removed from v5.3 and upwards? This seems a useful sort of thing to me. Thanks, Chris.
Re: 5.2.4.0 Servers available for download
Richard, good suggestion. Consider it noted. 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" <[EMAIL PROTECTED]> wrote on 12/16/2004 06:31:35: > On Dec 16, 2004, at 7:04 AM, Loon, E.J. van - SPLXM wrote: > > > For those of you who haven't noticed it yet: IBM has quietly put the > > 5.2.4.0 > > server codes on their FTP server. > > Thanks, Eric. > > IBM: The TSM support page, > > http://www.ibm.com/software/sysmgmt/products/support/ > IBMTivoliStorageManager.html > is the ideal venue for communicating the availability of significant > new software levels. Could this practice be instituted? > > thanks, Richard Sims
Re: Passwordaccess Generate
If you have a TSM administrator's id, you can use that with virtualnodename option, instead of needing the individual client password, but from your email I assume you do not have an administrator's id. But you probably DO know the TSM name of the machine you are likely to use to recover if your machine is unavailable. On YOUR machine, start the TSM client, pull down UTILITIES -> NODE ACCESS LIST. OR alternatively, you can use the TSM command line command: SET ACCESS. Read about this in the book, or the HELP. You can grant access to the recovery machine to restore your machine's files. No password required after the SET ACCESS is done. (Of course, you have to plan ahead and do this BEFORE your machine dies.) Also under UTILITIES, you can change your own password, instead of letting the TSM server do it. If your TSM admin has set up to force password change every 30 days, and you change it on day 29, the TSM server won't change it again. So you WILL know what it is. Hope that helps. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris Rodgers Sent: Thursday, December 16, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Re: Passwordaccess Generate > You shouldn't ever need to know it, there are other ways to do > everything I can think of. > > What problem are you having that you need it for? > Maybe I can tell you how to get around it My computer is backed up via TSM to my university's central ADSM server. If I want to do anything which needs more than my own node password (which I know), I have to raise a support request with them. For password resets, these are set to something random which is then sent out on paper arriving a day or two later! Therefore, if I want to be able to recover files in the event of my machine dying (as I did this afternoon), it's invaluable to have the node password so that I can use the -virtualnodename option on another machine to get back my files more quickly and get back to work. Similarly, if a machine dies completely, one also has to wait for the paper password to arrive before being able to get on with doing a bare metal restore because of course the encrypted password dies with the machine. Hmm... Why has this facility (or the MAILPROG equivalent) been removed from v5.3 and upwards? This seems a useful sort of thing to me. Thanks, Chris.
Re: Passwordaccess Generate
OR alternatively, you can use the TSM command line command: SET ACCESS. Read about this in the book, or the HELP. OK, I see that this provides a work around. Also under UTILITIES, you can change your own password, instead of letting the TSM server do it. If your TSM admin has set up to force password change every 30 days, and you change it on day 29, the TSM server won't change it again. So you WILL know what it is. Except that you need to know the (potentially random by now) autogenerated password first. Is it true that scheduled backups need to have an autogenerated password enabled? It strikes me that there should be some facility to tell the user what the new password is when it's changed (e.g., as I say, the MAILPROG option under unix). Would you trust your login password to your SSH client for example... having it randomly change the thing once a month or so, and never let you know what it is? Of course, you can just reset the login password when you finally need it again, but still. It seems strange to me to take a password completely out of the user's control like this. Chris.
Re: scripts.smp missing on Windows server
On Dec 16, 2004, at 1:24 PM, Joerg Pohlmann wrote: A question for the development folks: I have been upgrading my Windows-based TSM server and for the last 5.2.3.x releases as well as 5.2.4.0 scripts.smp was not reinstalled into the server directory. I found the sample scripts extremely useful - it would be nice if they were re-packaged into the server package. You may be giving up too easily. :-) Look around...it may be in the webimages directory (where I found it on AIX). Don't ask me why. Richard Sims "It could be that the purpose of your life is only to serve as a warning to others." -- despair.com
Re: Passwordaccess Generate
Chris,
If this function is important to you, I recommend that you work with your
IBM representative or IBM support to draft a formal requirement, to which
you will get a response.
Scheduled backups do not require a TSM-generated password, but they do
require the use of PASSWORDACCESS GENERATE. If you want, you can automate
the backup yourself and use PASSWORDACCESS PROMPT, passing in the password
via a script.
The PASSWORDACCESS GENERATE and automatic password expiration on the
server are not tied together 100%. You can disable automatic password
expiration at the server level, or at the individual node level (see the
SET PASSEXP and UPDATE NODE server commands). Your TSM administrator could
arrange to query all nodes whose passwords haven't been reset within the
past 'x' number of days ('x' is the number of days after which your site
requires you to change your password) and email anyone who needs to change
their password to do so. Thus you can still use PASSWORDACCESS GENERATE to
aid in automation, but the password change is left up to you.
I realize that this is not the ideal solution that you are looking for,
but the best I can offer for now is the above suggestions.
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" <[EMAIL PROTECTED]> wrote on 12/16/2004
12:40:06:
> > OR alternatively, you can use the TSM command line command: SET
ACCESS.
> > Read about this in the book, or the HELP.
> OK, I see that this provides a work around.
>
> > Also under UTILITIES, you can change your own password, instead of
> > letting the TSM server do it.
> > If your TSM admin has set up to force password change every 30 days,
and
> > you change it on day 29, the TSM server won't change it again. So you
> > WILL know what it is.
> Except that you need to know the (potentially random by now)
> autogenerated password first. Is it true that scheduled backups need to
> have an autogenerated password enabled?
>
> It strikes me that there should be some facility to tell the user what
> the new password is when it's changed (e.g., as I say, the MAILPROG
> option under unix). Would you trust your login password to your SSH
> client for example... having it randomly change the thing once a month
> or so, and never let you know what it is? Of course, you can just reset
> the login password when you finally need it again, but still. It seems
> strange to me to take a password completely out of the user's control
> like this.
>
> Chris.
Re: Passwordaccess Generate
Can't remember if you have to restart the scheduler, I don't think so. (And yes, that's a hassle for you, too. You may want to stick with SET ACCESS as a solution, if your admins require frequent changes.) OK, I'll try it like that. Do you think that perhaps future versions might see the password storing and password changing features split into two options? It's no problem not to be able to recover the password iff the system doesn't change it automatically i.e. only the storing option enabled. Similarly, at many sites, it's no problem to have no-one know the password and just reset it if it's ever needed so both options would be enabled. Finally, some people may feel their machine very insecure and not want to store the password at all, i.e. neither option enabled. This should satisfy both your security and my usability concerns. Chris.
Re: Passwordaccess Generate
> Also under UTILITIES, you can change your own password, instead of > letting the TSM server do it. > If your TSM admin has set up to force password change every 30 days, and > you change it on day 29, the TSM server won't change it again. So you > WILL know what it is. ***Except that you need to know the (potentially random by now) autogenerated password first. Well, you can't find it. But you can have the TSM admins reset it to something you DO know. (And yes, I understand that's a hassle for you). ** Is it true that scheduled backups need to have an autogenerated password enabled? Yes and no, depending on what you mean. The PASSWORDACCESS GENERATE parm causes 2 things: 1) it causes the password to be stored in the registry. THIS IS REQUIRED in order for the scheduler to run without waiting with a prompt for you to enter the password. 2) it causes the password to change automatically IFF the server parms specify that passwords expire after n days. This is not required. And, the scheduler doesn't require a password that was AUTOGENERATED by the server. The password in the registry just has to match the password as it is set on the TSM server, at the time the scheduler tries to run. BUT, If you are using the scheduler, you will need to change the password in the SCHEDULER as well as the GUI, if you do it manually. Pull down Utilities/SETUP WIZARD Click HELP ME CONFIGURE THE SCHEDULER Highlight the current scheduler Take all the defaults, except put in the new password. Can't remember if you have to restart the scheduler, I don't think so. (And yes, that's a hassle for you, too. You may want to stick with SET ACCESS as a solution, if your admins require frequent changes.)
Re: Passwordaccess Generate
> Do you think that perhaps future versions might see the password storing > and password changing features split into two options? It's no problem > not to be able to recover the password iff the system doesn't change it > automatically i.e. only the storing option enabled. Similarly, at many > sites, it's no problem to have no-one know the password and just reset > it if it's ever needed so both options would be enabled. Finally, some > people may feel their machine very insecure and not want to store the > password at all, i.e. neither option enabled. This should satisfy both > your security and my usability concerns. See my last post on this subject. 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.
Re: Passwordaccess Generate
Andrew Raibeck wrote:
Chris,
If this function is important to you, I recommend that you work with your
IBM representative or IBM support to draft a formal requirement, to which
you will get a response.
Scheduled backups do not require a TSM-generated password, but they do
require the use of PASSWORDACCESS GENERATE. If you want, you can automate
the backup yourself and use PASSWORDACCESS PROMPT, passing in the password
via a script.
The PASSWORDACCESS GENERATE and automatic password expiration on the
server are not tied together 100%. You can disable automatic password
expiration at the server level, or at the individual node level (see the
SET PASSEXP and UPDATE NODE server commands). Your TSM administrator could
arrange to query all nodes whose passwords haven't been reset within the
past 'x' number of days ('x' is the number of days after which your site
requires you to change your password) and email anyone who needs to change
their password to do so. Thus you can still use PASSWORDACCESS GENERATE to
aid in automation, but the password change is left up to you.
I realize that this is not the ideal solution that you are looking for,
but the best I can offer for now is the above suggestions.
OK, thanks for these - a homebrew script will probably do what I want
most easily. I appreciate your quick responses, too.
Good night (here, at least)
Chris.
Re: Passwordaccess Generate
I still think TSM provides the necessary facilities to deal with the problem, WITHOUT having to know/compromise/reset/muck with the password. When your client node was registered with TSM, YOU SHOULD HAVE HAD a TSM admin id created for it. Ask your TSM support group to give you the password for that admin id. Or ask them to create the admin id for you; it only has CLIENT OWNER privilege, so you can't do any harm to anyone else's stuff with it. Then you can go to your recovery machine, start dsm with -virtualnodename. When the prompt pops up for the password, OVERRIDE the node name with your admin id, and use your admin id password. YOU DON"T NEED the client password. And when the admin id password expires, you get prompted to change it, that one doesn't get generated automatically. It isn't involved in the use of the scheduler. If your TSM admin group doesn't want you to have the admin id with CLIENT OWNER privilege, well, that's a policy question, not a technical one -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chris Rodgers Sent: Thursday, December 16, 2004 3:09 PM To: [EMAIL PROTECTED] Subject: Re: Passwordaccess Generate > Can't remember if you have to restart the scheduler, I don't think so. > (And yes, that's a hassle for you, too. You may want to stick with SET > ACCESS as a solution, if your admins require frequent changes.) OK, I'll try it like that. Do you think that perhaps future versions might see the password storing and password changing features split into two options? It's no problem not to be able to recover the password iff the system doesn't change it automatically i.e. only the storing option enabled. Similarly, at many sites, it's no problem to have no-one know the password and just reset it if it's ever needed so both options would be enabled. Finally, some people may feel their machine very insecure and not want to store the password at all, i.e. neither option enabled. This should satisfy both your security and my usability concerns. Chris.
Re: AW: 5.2.3.5 Upgrade and Slow Expiration
I would be interested to see the output from a server instrumentation trace. Could you please run one and then forward it to my IBM address? I can take a look at it and see if I can find anything. To run the trace, do the following (from the TSM administrator) when inventory expiration is running: 1. Enter the command: instr begin 2. Let the command run for about 5 minutes. 3. End the command with: instr end file=server.trace.txt Send the file server.trace.txt to my IBM userid in my signature below. At 09:47 AM 12/16/2004 +0100, you wrote: Wats about your logpoolsize and logutil at this moment? regards joachim -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Auftrag von Hart, Charles Gesendet: Mittwoch, 15. Dezember 2004 21:10 An: [EMAIL PROTECTED] Betreff: 5.2.3.5 Upgrade and Slow Expiration We have two identical TSM Server (AIX 5.2 / p630 / TSM 5.2.3.5) They were both @ TSM 5.2.3.4 then we upgraded to 5.2.3.5 on the same day. One of the servers has been running just fine (TSM Server1). When the other TSM server (TSM Server2) runs Expiration it grinds to a halt with in an hour regardless of doing a cancel expiration or just trying to cancel the process. This TSMServer2 Backups / Archives our Oracle Env so when Expiration runs it brings the TSM Server instance to its knees to the point it won't take client data. Server Info: TSM Server 1 ver 5.2.3.5 DB = 141GB Cache Hit 98.89% Expiration Runs Fine (thousands obj per min) Backup Clients are primarily Windows (4-500 Clients) TSM Server 2 ver 5.2.3.5 DB = 149GB DB Cache Hit 98.26% Expiration Runs So Slow (a few obj per min) Backup Clients are primarily Unix (2-300 Clients) Does dsmc Archives and Incremental Has anyone run into strange issues when going to 5.2.3.5? I have a PMR open... but not getting much out of them... (Which usually isn't the case) I have searched the list and any APARS... No luck yet. Appreciate any info! Dave Canan TSM Performance IBM Advanced Technical Support [EMAIL PROTECTED]
Re: POLICY SET Question
Thanks. Just wanted to double check since I've never done this before. Thanks again, Eric -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED] Sent: Thursday, December 16, 2004 1:14 PM To: ADSM: Dist Stor Manager Cc: Jones, Eric J Subject: RE: POLICY SET Question You are exactly correct! Changes to the management classes/copy groups do not take effect immediately, they take effecty when you Activate the policy set. That will make the Changed policy set and Active the same. Changing RETEXTRA and RETONLY to 180 will do what you want. The only time you should have to stop/restart your TSM server are to apply server maintenance, to restore the data base (hopefully something you nEVER have to do!) or (sometimes) to clear a hardware problem. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Eric J Sent: Wednesday, December 15, 2004 1:05 PM To: [EMAIL PROTECTED] Subject: POLICY SET Question Good Afternoon. I'm new to the policy sets and someone else set them up for the server. I need to make a change to a Policy Set and was wondering if I needed to stop and start the server for the change to take affect. I need to change the Retain Extra Versions and Retain Only Version from 30 days to 180 days(6 months). If I go into the POLICY SET and drill down to "STANDARD Backup Copy Group" for the policy and do a "Update Copy Group" and change from 30 to 180 will it take affect immediately or do I need to be at the Policy Sets, Select "Validate Policy Set", then "Activate Policy Set". Also when I "Activate Policy Set" does this move it to the "ACTIVE" so both are the same. I need to keep all copies of the file for 180 days. I'm running TSM 5.2.2 server on AIX 5.2. = Backup Copy Groups : UNIX6MONTH UNIX6_MONTH_POLICY UNIX6_MONTH_MGMT STANDARD Policy Domain Name UNIX6MONTH Policy Set Name UNIX6_MONTH_POLICY Mgmt Class Name UNIX6_MONTH_MGMT Copy Group Name STANDARD Versions Data ExistsNOLIMIT Versions Data Deleted NOLIMIT Retain Extra Versions 30 Retain Only Version 30 Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy DestinationDISKPOOL3 Table of Contents (TOC) Destination - Last Update Date/Time 2004-08-24 07:31:25.00 Last Update by (administrator) JONES Managing profile- Have a Great Day, Eric Jones > * [EMAIL PROTECTED] > *: 607-751-4133 Cell : 607-972-7621
Drives become unavailable
Hi, We have two drives define in TSM 5.1 Level 6.5, it has been happening now from few days that every drives become unavailable quite often, and I update them as online=yes they become available againI am not sure why it is happening and what should i do, to get stable drives, any help Regards Mohsin
Re: Drives become unavailable
Hi there, More info is needed. * What are the messages in your activity log? * What OS is it attached too? If AIX, check the errpt. If Windows check your event viewer. * How long do they work for after you make them available again? Do they break right away as soon as they use a tape, or it is specific tape(s) causing the issue. Bad Tapes can cause weird things to happen. * What kind of drives are they, and what kind of library are they in? Lots of things can cause a drive to go off-line. - David N. Reiss[EMAIL PROTECTED] Home: (309)/243-1504 Cell: (407)/325-7623 A paranoid is someone who has all the facts at his disposal. - William Burroughs -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Mohsin Saleem Khan Sent: Thursday, December 16, 2004 9:58 PM To: [EMAIL PROTECTED] Subject: Drives become unavailable Hi, We have two drives define in TSM 5.1 Level 6.5, it has been happening now from few days that every drives become unavailable quite often, and I update them as online=yes they become available againI am not sure why it is happening and what should i do, to get stable drives, any help Regards Mohsin
Re: scripts.smp missing on Windows server
The omission is not intentional. A defect has been opened to address this missing file in the install package. Best 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" <[EMAIL PROTECTED]> wrote on 12/16/2004 11:24:40: > A question for the development folks: I have been upgrading my > Windows-based TSM server and for the last 5.2.3.x releases as well as > 5.2.4.0 scripts.smp was not reinstalled into the server directory. I > found the sample scripts extremely useful - it would be nice if they were > re-packaged into the server package. > > Joerg Pohlmann > 604-535-0452
Re: POLICY SET Question
I strongly encourage you to read the TSM Administrator's Guide from cover to cover, as it provides a pretty thorough overview of what TSM can do, and how to do it, including information how TSM policy management works. Yes, it's a pretty big book, but should be considered essential reading for TSM administrators. My two cents. :-) 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" <[EMAIL PROTECTED]> wrote on 12/16/2004 19:08:12: > Thanks. Just wanted to double check since I've never done this before. > > Thanks again, > Eric > > -Original Message- > From: Prather, Wanda [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 16, 2004 1:14 PM > To: ADSM: Dist Stor Manager > Cc: Jones, Eric J > Subject: RE: POLICY SET Question > > > You are exactly correct! > > Changes to the management classes/copy groups do not take effect > immediately, they take effecty when you Activate the policy set. > That will make the Changed policy set and Active the same. > > Changing RETEXTRA and RETONLY to 180 will do what you want. > > The only time you should have to stop/restart your TSM server are to > apply server maintenance, to restore the data base (hopefully something > you nEVER have to do!) or (sometimes) to clear a hardware problem. > > Wanda Prather > "I/O, I/O, It's all about I/O" -(me) > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Jones, Eric J > Sent: Wednesday, December 15, 2004 1:05 PM > To: [EMAIL PROTECTED] > Subject: POLICY SET Question > > > Good Afternoon. > I'm new to the policy sets and someone else set them up for the server. > I need to make a change to a Policy Set and was wondering if I needed to > stop and start the server for the change to take affect. > I need to change the Retain Extra Versions and Retain Only Version from > 30 days to 180 days(6 months). > If I go into the POLICY SET and drill down to "STANDARD Backup Copy > Group" for the policy and do a "Update Copy Group" and change from 30 to > 180 will it take affect immediately or do I need to be at the Policy > Sets, Select "Validate Policy Set", then "Activate Policy Set". Also > when I "Activate Policy Set" does this move it to the "ACTIVE" so both > are the same. > I need to keep all copies of the file for 180 days. > I'm running TSM 5.2.2 server on AIX 5.2. > > > = > Backup Copy Groups : UNIX6MONTH UNIX6_MONTH_POLICY UNIX6_MONTH_MGMT > STANDARD > Policy Domain Name UNIX6MONTH > Policy Set Name UNIX6_MONTH_POLICY > Mgmt Class Name UNIX6_MONTH_MGMT > Copy Group Name STANDARD > Versions Data ExistsNOLIMIT > Versions Data Deleted NOLIMIT > Retain Extra Versions 30 > Retain Only Version 30 > Copy Mode MODIFIED > Copy Serialization SHRSTATIC > Copy Frequency 0 > Copy DestinationDISKPOOL3 > Table of Contents (TOC) Destination - > Last Update Date/Time 2004-08-24 07:31:25.00 > Last Update by (administrator) JONES > Managing profile- > > Have a Great Day, > Eric Jones > > * [EMAIL PROTECTED] > > *: 607-751-4133 > Cell : 607-972-7621
legato cluster and handling of filespaces
hello, we have two cluster nodes, server1 and server2. one cluster ressource (partition f) is backed up under the filespacename \\server1\f$ in case of failover of our legato cluster ressource, the filespace now appears under the second node name, \\server2\f$ ibm support tells us, to use the parameters clusternode=yes and /clustername, which is only supported by ms-cluster; we tested it without success. has anyone an idea, how this problem of two filespaces (and double data) could be solved? is there any new support for legato clusters in tsm 5.3? with best regards and thanks stefan savoric
Re: 5.2.3.5 Upgrade and Slow Expiration
On Dec 15, 2004, at 3:09 PM, Hart, Charles wrote: We have two identical TSM Server (AIX 5.2 / p630 / TSM 5.2.3.5) They were both @ TSM 5.2.3.4 then we upgraded to 5.2.3.5 on the same day. One of the servers has been running just fine (TSM Server1). When the other TSM server (TSM Server2) runs Expiration it grinds to a halt with in an hour regardless of doing a cancel expiration or just trying to cancel the process. This TSMServer2 Backups / Archives our Oracle Env so when Expiration runs it brings the TSM Server instance to its knees to the point it won't take client data. ... I would again caution customers to never believe that any two systems are identical. Such a thing is physically impossible, and if believed, will inhibit productive analysis of system performance issues. Differences are healthy, and afford the opportunity to compare the effects of differing ingredients. You're saying that you're running Expiration at the same time that client backup/archive activity is occurring. That's bad. As the TSM Performance Tuning Guide says: "Expiration processing is very CPU and I/O intensive. If possible, it should be run when other TSM processes are not occurring." Realize that Expiration makes heavy use of the Recovery Log where rollforward mode is in effect. And you can run into log pinning (see swg21054574 on the IBM site). Exhaustion of Recovery Log space can cause a configured dbbackup trigger to activate, which further mires processing. In the daily life of a TSM server, loads have to be spread out and apportioned by type to achieve realistic performance. I would encourage review of your TSM processing load on the subject system, to rearrange when things are happening. Then go back and do analysis of remaining problem areas, using the multiple performance guides which IBM has provided us. Richard Sims
Re: 5.2.4.0 Servers available for download
Could you please send a link to where you found this code? I just went out to try to get the 5.2.4.0 code for a Windows 2000 client and I couldn't find it. Thank you in advance! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED] To M.COM>[EMAIL PROTECTED] Sent by: "ADSM:cc Dist Stor Manager" Subject <[EMAIL PROTECTED] 5.2.4.0 Servers available for .EDU> download 12/16/2004 07:04 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hi *SM-ers! For those of you who haven't noticed it yet: IBM has quietly put the 5.2.4.0 server codes on their FTP server. 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. **
Passwordaccess Generate
Dear All, I am using Tivoli Storage Manager v5.2.10 on a Windows Server 2003 machine with the PASSWORDACCESS GENERATE option in my dsm.opt file. Is there a way to be notified of the new password when the TSM client changes it (e.g. in the same manner as the MAILPROG option to the unix client) or to read the new password from the disk? Many thanks, Chris.
TSM 5.2.3 journal service crashes?
I'm having problems with the journal service on one of my clients and need some idea if the problem is with me or with the service. This particular system is a large Windows 2000 file server, with around 175GB of stuff on one drive. Because of processing constraints I am restricted to a 5-hour backup window. I kick off my backups at around 1700 and if they're not done by 2200 the session is cancelled so that migration and vault copies can start. The journal service is critical to this particular server because it speeds things up so much. The problem I'm having is that on some nights the backup runs long and the session gets cancelled. At that point the journal service crashes and then, since the journal gets invalidated, I get into a vicious cycle of having to do a non-journal-based incremental backup that can't finish because it takes so long to scan the filesystem, etc., etc. 1) Is anyone else having problems with a 5.2.3 journal service crashing when a client session is cancelled? I don't see much in the archives and even less in IBM's knowledge base. 2) Does the cancellation of a backup session necessarily invalidate a journal? I don't see why it would, but I didn't write the code. 3) Am I living on the edge here? Should I reasonably expect to be able to do what I'm trying to do? ### Joe Howell Shelter Insurance Companies (573)-214-6534 [EMAIL PROTECTED] === This e-mail is intended only for its addressee and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you have received this communication in error, please notify us immediately by e-mail: [EMAIL PROTECTED], and delete the original message. ===
Special Technique for Recovering lost Backups
Hi all. I want to know if there is a special technique that can be performed to recover backups on tapes from a server that lost the DB completely. Apparently one of our branches was still doing backups using a 3.7 ADSM server. They lost their DB, no backups but they have the library :D Does Tivoli have a procedure that could actually recover that data? Long shot? :D
Re: Special Technique for Recovering lost Backups
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jorge Salinas >I want to know if there is a special technique that can be >performed to recover backups on tapes from a server that lost >the DB completely. > >Apparently one of our branches was still doing backups using a >3.7 ADSM server. They lost their DB, no backups but they have >the library :D > >Does Tivoli have a procedure that could actually recover that data? No database, no restore. Sorry. (Please fix your reply-to address.) -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Node User ID Question
As part of our SOX compliance work, we are currently reviewing all user accounts, password policies, etc Historically, when TSM nodes were created here, everybody just went ahead and created a userID as well. These don't appear to get used. I assume it's so a user can log into TSM with access to a specific node data from another client, or the web client for that matter. What are the pros and cons of leaving v.s. deleting these administrative accounts associated with the TSM nodes? If there's no compelling reason to keep them, then I'll just remove them and make my SOX stuff that much easier. Thanks in advance. Curtis
Re: TSM 5.2.3 journal service crashes?
I am having the same problem and currently have a ticket open with Tivoli. On the server with this issue, 2 of the 8 journal databases remained valid -- all remained active -Original Message- From: Joe Howell [mailto:[EMAIL PROTECTED] Sent: Thursday, December 16, 2004 11:32 AM To: [EMAIL PROTECTED] Subject: TSM 5.2.3 journal service crashes? I'm having problems with the journal service on one of my clients and need some idea if the problem is with me or with the service. This particular system is a large Windows 2000 file server, with around 175GB of stuff on one drive. Because of processing constraints I am restricted to a 5-hour backup window. I kick off my backups at around 1700 and if they're not done by 2200 the session is cancelled so that migration and vault copies can start. The journal service is critical to this particular server because it speeds things up so much. The problem I'm having is that on some nights the backup runs long and the session gets cancelled. At that point the journal service crashes and then, since the journal gets invalidated, I get into a vicious cycle of having to do a non-journal-based incremental backup that can't finish because it takes so long to scan the filesystem, etc., etc. 1) Is anyone else having problems with a 5.2.3 journal service crashing when a client session is cancelled? I don't see much in the archives and even less in IBM's knowledge base. 2) Does the cancellation of a backup session necessarily invalidate a journal? I don't see why it would, but I didn't write the code. 3) Am I living on the edge here? Should I reasonably expect to be able to do what I'm trying to do? ### Joe Howell Shelter Insurance Companies (573)-214-6534 [EMAIL PROTECTED] The enclosed information is STRICTLY CONFIDENTIAL and is intended for the use of the addressee only. University Hospitals Health System and its affiliates disclaim any responsibility for unauthorized disclosure of this information to anyone other than the addressee. Federal and Ohio law protect patient medical information disclosed in this email, including psychiatric disorders, (HIV) test results, AIDs-related conditions, alcohol, and/or drug dependence or abuse. Federal regulation (42 CFR Part 2) and Ohio Revised Code section 5122.31 and 3701.243 prohibit disclosure of this information without the specific written consent of the person to whom it pertains, or as otherwise permitted by law.
Re: Node User ID Question
Yes, you are correct. Those default ids all have "client owner" privilege to the machine of the same name, and are only needed if you want to run the web client instead of the usual Windows GUI to do restores. We delete them (in cases where we forget NOT to create them in the first place). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Stewart Sent: Thursday, December 16, 2004 12:09 PM To: [EMAIL PROTECTED] Subject: Node User ID Question As part of our SOX compliance work, we are currently reviewing all user accounts, password policies, etc Historically, when TSM nodes were created here, everybody just went ahead and created a userID as well. These don't appear to get used. I assume it's so a user can log into TSM with access to a specific node data from another client, or the web client for that matter. What are the pros and cons of leaving v.s. deleting these administrative accounts associated with the TSM nodes? If there's no compelling reason to keep them, then I'll just remove them and make my SOX stuff that much easier. Thanks in advance. Curtis
Re: Passwordaccess Generate
> Why has this facility (or the MAILPROG equivalent) been removed from > v5.3 and upwards? This seems a useful sort of thing to me. While its usefulness under certain circumstances cannot be denied, we felt that this change was an improvement in security, which we weighted with a higher priority. For example, if someone hacked your NT account, they could easily get your TSM password. For what it is worth, this functionality was unique to the TSM client for Windows; it was never available for other TSM clients. 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" <[EMAIL PROTECTED]> wrote on 12/16/2004 11:31:08: > > You shouldn't ever need to know it, there are other ways to do > > everything I can think of. > > > > What problem are you having that you need it for? > > Maybe I can tell you how to get around it > > My computer is backed up via TSM to my university's central ADSM server. > If I want to do anything which needs more than my own node password > (which I know), I have to raise a support request with them. For > password resets, these are set to something random which is then sent > out on paper arriving a day or two later! Therefore, if I want to be > able to recover files in the event of my machine dying (as I did this > afternoon), it's invaluable to have the node password so that I can use > the -virtualnodename option on another machine to get back my files more > quickly and get back to work. > > Similarly, if a machine dies completely, one also has to wait for the > paper password to arrive before being able to get on with doing a bare > metal restore because of course the encrypted password dies with the > machine. Hmm... > > Why has this facility (or the MAILPROG equivalent) been removed from > v5.3 and upwards? This seems a useful sort of thing to me. > > Thanks, > > Chris.
Re: TSM 5.2.3 journal service crashes?
Hmmm. I'd already set RESOURCEUTILIZATION up, but I hadn't thought of actually setting up a separate node. What are the licensing implications of this? Have you noticed any throughput problems from running multiple backups through the same NIC? Not to mention CPU or disk activity. ### Joe Howell Shelter Insurance Companies (573)-214-6534 [EMAIL PROTECTED] "Stapleton, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 12/16/2004 11:06 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: TSM 5.2.3 journal service crashes? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joe Howell >I'm having problems with the journal service on one of my >clients and need some idea if the problem is with me or with >the service. This particular system is a large Windows 2000 >file server, with around 175GB of stuff on one drive. Because >of processing constraints I am restricted to a 5-hour backup >window. To deal with the root of your problem, have you multithreaded your backup with the use of multiple nodenames? Have you considered the use of weekly image backups in combination with daily regular backups? -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 === This e-mail is intended only for its addressee and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you have received this communication in error, please notify us immediately by e-mail: [EMAIL PROTECTED], and delete the original message. ===
Re: Passwordaccess Generate
Prather, Wanda wrote: I still think TSM provides the necessary facilities to deal with the problem, WITHOUT having to know/compromise/reset/muck with the password. When your client node was registered with TSM, YOU SHOULD HAVE HAD a TSM admin id created for it. Ask your TSM support group to give you the password for that admin id. Or ask them to create the admin id for you; it only has CLIENT OWNER privilege, so you can't do any harm to anyone else's stuff with it. Then you can go to your recovery machine, start dsm with -virtualnodename. When the prompt pops up for the password, OVERRIDE the node name with your admin id, and use your admin id password. YOU DON"T NEED the client password. And when the admin id password expires, you get prompted to change it, that one doesn't get generated automatically. It isn't involved in the use of the scheduler. If your TSM admin group doesn't want you to have the admin id with CLIENT OWNER privilege, well, that's a policy question, not a technical one I will ask about this and see what they say. That does sound sufficient to meet my concerns. Thanks, Chris. P.S. Andrew, I think our last couple of e-mails overlapped in cyberspace.
Re: TSM 5.2.3 journal service crashes?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joe Howell >Hmmm. I'd already set RESOURCEUTILIZATION up, but I hadn't >thought of actually setting up a separate node. What are the >licensing implications of this? Have you noticed any >throughput problems from running multiple backups through the >same NIC? Not to mention CPU or disk activity. TSM is licensed by the number of physical processors used by the server and clients; additional nodenames associated with a physical box do not affect license numbers. I've seen little in the way of network bottlenecks when multi-streaming backups. If it's an issue, throw in another NIC (they're cheap) and put the NIC into the same or different network segment. The only serious resource bottleneck I've ever seen on a properly tricked-out TSM server is CPU, and that only during expiration on machines using seriously fast disk systems used by the TSM database volumes. The basic steps are: 1. Register the new nodename(s) on the TSM server. 2. Create multiple client option files (dsm.opt for Windows and NetWare clients or dsm.sys on UNIX clients), one for each nodename. 3. Create a scheduler service for each nodename. 4. Associate a client schedule to each nodename. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
