Automatically generated emails from TSM OR
I just wanted to canvas opinions from anyone who uses Operational Reporting to generate emails to client owners regarding the failure of their schedules. Currently the only exceptions that are trapped are 'Missed' and 'Failed'. However Failed in this sense does not include schedules whose entries in the events table have a status of, for example, 'Severed'. I was wondering how many people were, like myself, under the misapprehension that their users are being emailed about all failures. I logged a PMR with IBM about this, but it looks like this may turn out to be a design change request. At the moment I'd settle for generating emails on any events meeting the same criteria as the EXCEPTIONSONLY=YES option on QUERY EVENTS. As a client owner, it's the exceptions I'd be interested in and not missed/failed schedules. Regards Neil Schofield Yorkshire Water Services Ltd. - Ever wondered how your water works? - now you can see for yourself with a tour of our water or waste water treatment works across Yorkshire - click here http://www.yorkshirewater.com/see-how-your-water-works.aspx to book now. The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
Re: VTL Tape Size
Andy, Regarding the point made below about writing 100GB exchange files on smaller VTL volumes, you are probably aware of this but you could make use of the maximum size threshold parameter on the VTL storage pool. Any data whose size matches or exceeds the threshold will be sent straight to the next storage pool in your architecture preferably the physical tape pool thus alleviating the load on the VTL and avoiding large data spanning across multiple VTL volumes. In our environment, each of our TSM servers is configured as its own VTL Library (We allocated a certain number of expandable VTL volumes per server in the VE for Tape Console and checked them in TSM); the VTL pool sits between the disk and tape pools; we defined maximum size thresholds on our disk and VTL storage pools. The only tape contention issues we encounter on rare occasions are concurrent migrations and storage pool backups needing the same volume; they are quickly resolved either by letting the server negotiate the priority between the processes or by canceling one of the processes and initiating at a later time. I hope you work out your issues with the VTL Andy. BERTAUT TCHUISE Storage Support Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Tuesday, July 07, 2009 3:21 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL Tape Size The top problems we are trying to solve are tape contention and utilization. Contention is a little troublesome from time to time. Utilization is why we did some testing to the extreme of 10GB volumes. There are some very interesting points: I think your volume size should be something fitting the data type going into the storage pool. Putting 100GB exchange db files on 10gb volumes or 1kb files on 100GB volumes doesn't seem efficient. Object size is a little hard to define. We have big DBs to millions of tiny files. Some considerations: - This varies with the different VTL vendor's, but some had a maximum number of Virtual Tapes that was allowed in the system, which would argue for larger volumes. - On the other hand, smaller volumes reduce the amount of reclamation you have to do (depending on your data) - If you ever want to export to physical tapes, you might want to just use the same size that you are emulating. I.E. 400GB for LTO3 I had not considered the number of slots in the emulated library. There is no chance of the VTL moving data to physical tape, our libraries are not supported. If you try to provide virtual sequential access mount points for each client session you may need during client processing, you will likely need much more system resources to complete nightly backups. We are currently using the VTL's, so the overall design of the storage pools and what goes where and when it goes there is running smoothly. We go to disk first except for the large objects. Another thing to think about is, have you sized the virtual library to have enough capacity for all your primary storage pool needs, or will the primary pool have to migrate to real tape? We have already seen the spanning tape problem with backup storage pool and have a procedure to handle that. That is annoying. The VTLs are large enough to hold the primary copy, but they are approaching their maximum capacity. We make use of expandable virtual volumes with an initial size of 5G and a max size of 60G and it works well in my opinion. We tried expandable or capacity on demand, but found that we generally fill the tapes so all we gained was an ambiguous scratch tape count. We do have compression on; we average nearly 2:1. The leaning here seems to be in the 50GB range. Thank you for the responses so far. Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information
Installation error on MS SQL2008.
I try to install TDPSQL 5.5.2.0 on a Windows2008 X64 server with MS SQL2008, but I get the error: The installation of Microsoft SQL Server Native Client (X64) appears to have failed. I have installed Microsoft SQL Server 2008 Management Objects Collection Package and Microsoft SQL Server Native Client Package. Any hint is appreciated . aOaThanks Bo Nielsen * +45 4386 4671 Coop IT * (Internt postcenter): 6244 Data Storage Center * mailto:bo.niel...@coop.dk Remember, a dead fish can float downstream, But it takes a live one to svim upstream. - W.C. Fields.
Re: Installation error on MS SQL2008.
When I had this error before I extracted Native Client msi from SQL 2008 Sp1 setup files and ran it which went well Thanks, Sanju -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nielsen, Bo Sent: Wednesday, July 08, 2009 6:37 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Installation error on MS SQL2008. I try to install TDPSQL 5.5.2.0 on a Windows2008 X64 server with MS SQL2008, but I get the error: The installation of Microsoft SQL Server Native Client (X64) appears to have failed. I have installed Microsoft SQL Server 2008 Management Objects Collection Package and Microsoft SQL Server Native Client Package. Any hint is appreciated . aOaThanks Bo Nielsen * +45 4386 4671 Coop IT * (Internt postcenter): 6244 Data Storage Center * mailto:bo.niel...@coop.dk Remember, a dead fish can float downstream, But it takes a live one to svim upstream. - W.C. Fields.
Re: VTL Tape Size
We are setup with the primary pools in the data center and the copies off-site. All of our primary data ends up in the VTL expect the NAS and DPM (Exchange) which go straight to physical tape. I am less concerned about the spanning issue because we have experience with it and most of the DBs that will span even with 100GB tapes are completed early enough not to be a problem. We have 4 VTLs, 1 TSM server is using a pair. The goal is to move to a 1:1 setup. With that change we are looking at changing the volume size and we are checking to see what others are doing and why to see if we missed any pluses or minuses of using smaller or larger volumes. It seems that 50GB is popular with some 100's and 200's, but no clear winner on why. It is nice to see that most at least have a reason why. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Tchuise, Bertaut Sent: Wednesday, July 08, 2009 8:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL Tape Size Andy, Regarding the point made below about writing 100GB exchange files on smaller VTL volumes, you are probably aware of this but you could make use of the maximum size threshold parameter on the VTL storage pool. Any data whose size matches or exceeds the threshold will be sent straight to the next storage pool in your architecture preferably the physical tape pool thus alleviating the load on the VTL and avoiding large data spanning across multiple VTL volumes. In our environment, each of our TSM servers is configured as its own VTL Library (We allocated a certain number of expandable VTL volumes per server in the VE for Tape Console and checked them in TSM); the VTL pool sits between the disk and tape pools; we defined maximum size thresholds on our disk and VTL storage pools. The only tape contention issues we encounter on rare occasions are concurrent migrations and storage pool backups needing the same volume; they are quickly resolved either by letting the server negotiate the priority between the processes or by canceling one of the processes and initiating at a later time. I hope you work out your issues with the VTL Andy. BERTAUT TCHUISE Storage Support Administrator Legg Mason Technology Services *410-580-7032 btchu...@leggmason.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Tuesday, July 07, 2009 3:21 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL Tape Size The top problems we are trying to solve are tape contention and utilization. Contention is a little troublesome from time to time. Utilization is why we did some testing to the extreme of 10GB volumes. There are some very interesting points: I think your volume size should be something fitting the data type going into the storage pool. Putting 100GB exchange db files on 10gb volumes or 1kb files on 100GB volumes doesn't seem efficient. Object size is a little hard to define. We have big DBs to millions of tiny files. Some considerations: - This varies with the different VTL vendor's, but some had a maximum number of Virtual Tapes that was allowed in the system, which would argue for larger volumes. - On the other hand, smaller volumes reduce the amount of reclamation you have to do (depending on your data) - If you ever want to export to physical tapes, you might want to just use the same size that you are emulating. I.E. 400GB for LTO3 I had not considered the number of slots in the emulated library. There is no chance of the VTL moving data to physical tape, our libraries are not supported. If you try to provide virtual sequential access mount points for each client session you may need during client processing, you will likely need much more system resources to complete nightly backups. We are currently using the VTL's, so the overall design of the storage pools and what goes where and when it goes there is running smoothly. We go to disk first except for the large objects. Another thing to think about is, have you sized the virtual library to have enough capacity for all your primary storage pool needs, or will the primary pool have to migrate to real tape? We have already seen the spanning tape problem with backup storage pool and have a procedure to handle that. That is annoying. The VTLs are large enough to hold the primary copy, but they are approaching their maximum capacity. We make use of expandable virtual volumes with an initial size of 5G and a max size of 60G and it works well in my opinion. We tried expandable or capacity on demand, but found that we generally fill the tapes so all we gained was an ambiguous scratch tape count. We do have compression on; we average nearly 2:1. The leaning here seems to be in the 50GB range. Thank you for the responses so far. Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If
Re: TSM6.1 on Linux
We did the same. Installed RedHat 5.3 on a fresh server with 2-mirrored 400GB SAS drives for the OS/DB/Logs and 8-1TB drives for the LZ. While the install went without incident, the numerous problems with 6.1 have totally deterred us from making this a production system. We are eagerly waiting for 6.1.2 (and of course, the latest DB2) to see if we can make this system usable. The biggest headache we stumbled upon was the issue with the transaction-archive logs (see my previous post about the requirements for 3-FULL DB backups). This totally blew-away the space on the 400GB filesystem. Never had these problem with V5.x This box is connected to the SAN to use the 6-TS1120 and 6-TS1130 drives in our 3494, as a library client. So far we have not seen any incidents related to interaction with our 5-TSM 5.5.2.1 servers. From: Gill, Geoffrey L. geoffrey.l.g...@saic.com To: ADSM-L@VM.MARIST.EDU Date: 07/07/2009 02:27 PM Subject: [ADSM-L] TSM6.1 on Linux Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU For those that tested 6.1 in a Linux environment I'm looking for any problems you had. During my testing on AIX and Windows I had failures during the installation which were always DB2 related. I'm getting ready to bring up TSM on a Linux box and am looking for your experience. This is a new installation not an upgrade. This is a test but I really want to get a working environment up as quickly and easily as possible. In the end I will blow this away and bring it up on an IBM p series box running Linux which will hopefully be just as easy but for now this is just a test on a blade I was given till the other hardware arrives. I will direct 2 LTO2 drives to this box from the 3584 along with a VTL that is coming in this week. Learning Linux from scratch so I really have no idea how these devices are even found. I have SAN disk displayed for DB and I need to figure out how to get all that set up too, unfortunately it's not something I've figured out. I can tap some other Linux resources here for help with that I hope. I'm taking notes on what I've done with specific commands since I certainly won't remember it tomorrow. I really hate asking for documents others have put together but in this case, since I'm being pressured to get this going, I certainly would appreciate anything others have put together if anyone may have something already. Thanks for any info you can provide. Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-B1P (858)826-4062 (office) (858)412-9883 (blackberry) Email: geoffrey.l.g...@saic.com
Stop HSM clients migration jobs
CANCEL SESSION +-- |This was sent by dem...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Replacing tape drives (or there has to be a better way)
I need thoughts/suggestions/help on how to deal with SAN attached tape drive replacements when a library is shared amongst 5-servers. We just has a drive replaced, therefore giving us a new serial number (3494ATL - TS1130). All servers that use these drives/libraries are RedHat Linux and use very current lin_tape drivers. Currently, the method we use is to bounce each server so the system rescans the SAN and gets the new serial number. In the past, just stopping the TSM server and then restarting the lin_tape driver would often be enough. Now with the latest lin_tape drivers, I don't see the lin_taped daemon running any more. Yes, I have tried updating the paths on the library manager server and telling it to autodetect but that didn't help. There has to be a better way! If you have a similar configuration, how do you handle this scenario?
Automatically generated emails from TSM OR
try commercial applications - tsmexplorer http://www.s-iberia.com - tsmmanager http://www.tsmmanager.us +-- |This was sent by dem...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Automatically generated emails from TSM OR
could you please be so kind as to provide some context to your postings? I know that backupcentral hides this from you, but there are 1700+ people reading this from a real mailing list. On 8 jul 2009, at 17:37, Demetrio wrote: try commercial applications - tsmexplorer http://www.s-iberia.com - tsmmanager http://www.tsmmanager.us + -- |This was sent by dem...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. + -- -- Met vriendelijke groeten/Kind regards, Remco Post
Re: Replacing tape drives (or there has to be a better way)
Zoltan, The majority of our TSM servers are AIX and we do have a setup where we share multiple library clients with one library. When we have IBM CEs come out and replace drives, they just change the serial number on the new drive to match the old drive they are replacing. Apparently there is a way to do that on the drive itself. Thanks, Sean Zoltan Forray/AC/VCU zfor...@vcu.edu Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/08/2009 11:30 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Replacing tape drives (or there has to be a better way) I need thoughts/suggestions/help on how to deal with SAN attached tape drive replacements when a library is shared amongst 5-servers. We just has a drive replaced, therefore giving us a new serial number (3494ATL - TS1130). All servers that use these drives/libraries are RedHat Linux and use very current lin_tape drivers. Currently, the method we use is to bounce each server so the system rescans the SAN and gets the new serial number. In the past, just stopping the TSM server and then restarting the lin_tape driver would often be enough. Now with the latest lin_tape drivers, I don't see the lin_taped daemon running any more. Yes, I have tried updating the paths on the library manager server and telling it to autodetect but that didn't help. There has to be a better way! If you have a similar configuration, how do you handle this scenario?
Change IP
Dear ALL, Am moving the Windows TSM server to a new network environment, what is the procedure to change a TSM Server's IP address with a new IP? Thanks madunix
Re: Replacing tape drives (or there has to be a better way)
Thanks for the duh suggestion. I know how to get into the CE mode to change the serial number and it would make life simpler. For this drive, since it was an upgrade, this will work. However, for new drives with maintenance, I think they would frown on changing the serial #. I still would like to know how other folks handle it if they can't change the serial #. From: Sean English sean.engl...@wachovia.com To: ADSM-L@VM.MARIST.EDU Date: 07/08/2009 11:48 AM Subject: Re: [ADSM-L] Replacing tape drives (or there has to be a better way) Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Zoltan, The majority of our TSM servers are AIX and we do have a setup where we share multiple library clients with one library. When we have IBM CEs come out and replace drives, they just change the serial number on the new drive to match the old drive they are replacing. Apparently there is a way to do that on the drive itself. Thanks, Sean Zoltan Forray/AC/VCU zfor...@vcu.edu Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/08/2009 11:30 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Replacing tape drives (or there has to be a better way) I need thoughts/suggestions/help on how to deal with SAN attached tape drive replacements when a library is shared amongst 5-servers. We just has a drive replaced, therefore giving us a new serial number (3494ATL - TS1130). All servers that use these drives/libraries are RedHat Linux and use very current lin_tape drivers. Currently, the method we use is to bounce each server so the system rescans the SAN and gets the new serial number. In the past, just stopping the TSM server and then restarting the lin_tape driver would often be enough. Now with the latest lin_tape drivers, I don't see the lin_taped daemon running any more. Yes, I have tried updating the paths on the library manager server and telling it to autodetect but that didn't help. There has to be a better way! If you have a similar configuration, how do you handle this scenario?
Re: Replacing tape drives (or there has to be a better way)
Well, to speak on that as well, we just had 8 new drives put into one of the libraries managed by this library manager. We were told by TSM that you are not able to just define new drives and paths to TSM because TSM is not going to recognize the element numbers. We had to recycle the library manager so that TSM would run an IOCTL and rescan the library and pick up the new drives. Thanks, Sean English Data Protection Services - Production Control Wachovia Bank, A Wells Fargo Company Office: 704.590.7146 Cell: 704.281.0318 sean.engl...@wachovia.com TSM Sharepoint Teamsite Wells Fargo Confidential: The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Zoltan Forray/AC/VCU zfor...@vcu.edu Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/08/2009 12:03 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Replacing tape drives (or there has to be a better way) Thanks for the duh suggestion. I know how to get into the CE mode to change the serial number and it would make life simpler. For this drive, since it was an upgrade, this will work. However, for new drives with maintenance, I think they would frown on changing the serial #. I still would like to know how other folks handle it if they can't change the serial #. From: Sean English sean.engl...@wachovia.com To: ADSM-L@VM.MARIST.EDU Date: 07/08/2009 11:48 AM Subject: Re: [ADSM-L] Replacing tape drives (or there has to be a better way) Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Zoltan, The majority of our TSM servers are AIX and we do have a setup where we share multiple library clients with one library. When we have IBM CEs come out and replace drives, they just change the serial number on the new drive to match the old drive they are replacing. Apparently there is a way to do that on the drive itself. Thanks, Sean Zoltan Forray/AC/VCU zfor...@vcu.edu Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/08/2009 11:30 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Replacing tape drives (or there has to be a better way) I need thoughts/suggestions/help on how to deal with SAN attached tape drive replacements when a library is shared amongst 5-servers. We just has a drive replaced, therefore giving us a new serial number (3494ATL - TS1130). All servers that use these drives/libraries are RedHat Linux and use very current lin_tape drivers. Currently, the method we use is to bounce each server so the system rescans the SAN and gets the new serial number. In the past, just stopping the TSM server and then restarting the lin_tape driver would often be enough. Now with the latest lin_tape drivers, I don't see the lin_taped daemon running any more. Yes, I have tried updating the paths on the library manager server and telling it to autodetect but that didn't help. There has to be a better way! If you have a similar configuration, how do you handle this scenario? image/gif
Re: Replacing tape drives (or there has to be a better way)
When IBM replace my drives on maintenance (3592-J1A and LTO4), they unloaded the VPD from the old drive and downloaded the VPD to the new drive. They also place a sticky label indicating the original serial number. IBM also has to keep their records correct for field maintenance. Our maintenance contracts specifies the SN of all the drives and what a nightmare it would be if the drives SN changes every time IBM replaces one. We just can't change the contracts every time a SN changes on a drive. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Wednesday, July 08, 2009 8:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Replacing tape drives (or there has to be a better way) I need thoughts/suggestions/help on how to deal with SAN attached tape drive replacements when a library is shared amongst 5-servers. We just has a drive replaced, therefore giving us a new serial number (3494ATL - TS1130). All servers that use these drives/libraries are RedHat Linux and use very current lin_tape drivers. Currently, the method we use is to bounce each server so the system rescans the SAN and gets the new serial number. In the past, just stopping the TSM server and then restarting the lin_tape driver would often be enough. Now with the latest lin_tape drivers, I don't see the lin_taped daemon running any more. Yes, I have tried updating the paths on the library manager server and telling it to autodetect but that didn't help. There has to be a better way! If you have a similar configuration, how do you handle this scenario?
Re: Replacing tape drives (or there has to be a better way)
In fact we found out that for lto-3 and lto-4 tape drives in an IBM 3584 library, it is required that they change the serial number to match the old tape drive. Because IBM tracks the drives by serial number for maint contracts. This we found when the serial numbers that we send in for a maint contract renewal were kicked out as field engineering had not been updating the serial numbers. But not for lto-2 tape drives. len -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sean English Sent: Wednesday, July 08, 2009 11:47 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Replacing tape drives (or there has to be a better way) Zoltan, The majority of our TSM servers are AIX and we do have a setup where we share multiple library clients with one library. When we have IBM CEs come out and replace drives, they just change the serial number on the new drive to match the old drive they are replacing. Apparently there is a way to do that on the drive itself. Thanks, Sean Zoltan Forray/AC/VCU zfor...@vcu.edu Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/08/2009 11:30 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Replacing tape drives (or there has to be a better way) I need thoughts/suggestions/help on how to deal with SAN attached tape drive replacements when a library is shared amongst 5-servers. We just has a drive replaced, therefore giving us a new serial number (3494ATL - TS1130). All servers that use these drives/libraries are RedHat Linux and use very current lin_tape drivers. Currently, the method we use is to bounce each server so the system rescans the SAN and gets the new serial number. In the past, just stopping the TSM server and then restarting the lin_tape driver would often be enough. Now with the latest lin_tape drivers, I don't see the lin_taped daemon running any more. Yes, I have tried updating the paths on the library manager server and telling it to autodetect but that didn't help. There has to be a better way! If you have a similar configuration, how do you handle this scenario?
SV: Change IP
Are you using Server-2-Server communication between multiple TSM Servers? If not. Then just change the IP in Windows and restart the TSM Server Service then are you up and running. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r madunix [madu...@gmail.com] Skickat: den 8 juli 2009 17:49 Till: ADSM-L@VM.MARIST.EDU Ämne: Change IP Dear ALL, Am moving the Windows TSM server to a new network environment, what is the procedure to change a TSM Server's IP address with a new IP? Thanks madunix
TSM development survey: TSM server on 32-bit Windows
Hello TSMers, The TSM development team is discussing the possibility of removing support for the TSM server on 32-bit Windows in a future release. This will not affect the storage agent or client, for which 32-bit versions will continue. The concerns revolve around TSM server performance as it relates to available and application-accessible memory on 32-bit Windows. If you currently run (or if you plan to run) the TSM 6.1 server on 32-bit Windows, then we are interested in your feedback on this subject. Please address your responses directly to me at stor...@us.ibm.com. All responses will remain confidential. The following questions assume that you are running, or you intend to run, the TSM 6.1 server on 32-bit Windows. 1. What is the status of your TSM 6.1 server implementation on 32-bit Windows (currently running or intend to run) 2. Do you use (or intend to use) TSM 6.1 on 32-bit Windows for production? Or will such usage be limited to testing or demonstration? 3. How much physical memory is installed (or will be installed) on the systems? (Note: for production use, a minimum of 4 GB is required, see http://www-01.ibm.com/support/docview.wss?uid=swg21064234) 4. Are you using (or do you plan to use) Windows Physical Address Extension (PAE) to access more than 4 GB of memory? 5. If you are currently running TSM 6.1 on 32-bit Windows, is the performance acceptable? 6. What would be the impact to your TSM installation if a future TSM release no longer supported 32-bit Windows? That is, if the TSM server on Microsoft Windows only supported x64 Windows? (This would not affect storage agents or the client, for which 32-bit versions will continue.) 7. Other related comments? Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence.
Dirmc and cloptset questions
Just ran into the dreaded invisible files in point-in-time restore with tsm gui. Looks like some of the directories of some clients didn't get bound to my dirsonly management class with retonly of 180 days. I would like to force all directories to rebind to this class. I propose adding the dirmc option to any cloptsets and then define as apppropriate for all clients. I have such a set defined for solaris clients to exclude /etc/mnttab, and one for win2k clients with specific excludes. Anything wrong with this idea; and how best to implement. Suggestions and criticisms welcome. Tsm server 5.4.4 clients rangeing from 3.7 through 6.1. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: SV: Change IP
You also need to change the IP address on dsm.sys and dsm.opt files on the linux clients and on windows clients just change dsm.opt to the new ip address of the TSM server. Hope this help! Desalegne Guangul Regional Occupational Health 1800 Harrison St. 21st Floor 510-625-3038 or tieline 8/428-3038 NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Christian Svensson christian.svens...@cristie.se Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/08/09 11:02 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject SV: Change IP Are you using Server-2-Server communication between multiple TSM Servers? If not. Then just change the IP in Windows and restart the TSM Server Service then are you up and running. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r madunix [madu...@gmail.com] Skickat: den 8 juli 2009 17:49 Till: ADSM-L@VM.MARIST.EDU Ämne: Change IP Dear ALL, Am moving the Windows TSM server to a new network environment, what is the procedure to change a TSM Server's IP address with a new IP? Thanks madunix
Re: SV: Change IP
Also if your TOR or ISC connections were set up using the IP address instead of the hostname, you'll have to change them. I always recommend that my customers set up a DNS alias for the TSM server, and point the clients to the DNS alias instead of using hard-coded IP addresses. Eliminates this problem altogether. On Wed, Jul 8, 2009 at 2:57 PM, Desalegne Guangul desalegne.t.guan...@kp.org wrote: You also need to change the IP address on dsm.sys and dsm.opt files on the linux clients and on windows clients just change dsm.opt to the new ip address of the TSM server. Hope this help! Desalegne Guangul Regional Occupational Health 1800 Harrison St. 21st Floor 510-625-3038 or tieline 8/428-3038 NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Christian Svensson christian.svens...@cristie.se Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 07/08/09 11:02 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject SV: Change IP Are you using Server-2-Server communication between multiple TSM Servers? If not. Then just change the IP in Windows and restart the TSM Server Service then are you up and running. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r madunix [madu...@gmail.com] Skickat: den 8 juli 2009 17:49 Till: ADSM-L@VM.MARIST.EDU Ämne: Change IP Dear ALL, Am moving the Windows TSM server to a new network environment, what is the procedure to change a TSM Server's IP address with a new IP? Thanks madunix
Re: Internal compression?
THANK YOU Richard! You are a national treasure Wanda On Thu, Jun 11, 2009 at 7:49 PM, Richard Sims r...@bu.edu wrote: On Jun 11, 2009, at 4:15 PM, Wanda Prather wrote: The accounting log has multiple fields for the session: backup transactions backup KB total transmitted On a backup, you'll find the total transmitted is significantly higher than the total backed up. That's the difference in the metadata. Now what I can't remember, is whether the backup KB includes the retries or not Richard? W Hi, Wanda - From what I've seen, the dsmaccnt backup KB records the actual amount of data going into server storage pools, which excludes retries. Note that the Total number of bytes transferred summary statistic reflects traffic which flows from the client to the server, in Data verbs. The flow of Active files inventory information from the server to the client at the start of an Incremental backup is thus not included in that number. Dsmaccnt records a Session KB number, which does account for the flow in both directions. Also, with backup of ordinary directories and empty files in Unix, such objects do not participate in Data verbs because they only constitute attributes for database storage, not storage pool data. Richard Sims, at Boston University
Re: Internal compression?
On Jul 8, 2009, at 3:38 PM, Wanda Prather wrote: THANK YOU Richard! You are a national treasure Wanda W - I'll send you that $10 we agreed on for the posting. ;-) R.
Re: Change IP
-madunix wrote: - Am moving the Windows TSM server to a new network environment, what is the procedure to change a TSM Server's IP address with a new IP? Do you have backups that pass through firewalls, and will continue to do so after the server move? If so, you will probably have to arrange for changes in firewall rules. Will any of your backups start passing through firewalls as a result of the server move? If so, you will probably need new firewall rules, and may need to change client options for the affected nodes (for example, firewall policies at some sites are compatible with polling mode scheduling but not with prompted mode scheduling). Will any of your backups stop passing through firewalls as a result of the server move? If so, you should probably arrange to have any obsolete firewall rules removed after the server move, and may want to change client options for the affected nodes (for example, changing from polling to prompted scheduling).
Re: Dirmc and cloptset questions
Should work! This is what TSM refers to as rebinding. Be sure to mark the override client settings in the cloptset option. Regards, Nicholas ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/08/2009 01:46:01 PM: [image removed] [ADSM-L] Dirmc and cloptset questions Lee, Gary D. to: ADSM-L 07/08/2009 01:47 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager Just ran into the dreaded invisible files in point-in-time restore with tsm gui. Looks like some of the directories of some clients didn't get bound to my dirsonly management class with retonly of 180 days. I would like to force all directories to rebind to this class. I propose adding the dirmc option to any cloptsets and then define as apppropriate for all clients. I have such a set defined for solaris clients to exclude /etc/ mnttab, and one for win2k clients with specific excludes. Anything wrong with this idea; and how best to implement. Suggestions and criticisms welcome. Tsm server 5.4.4 clients rangeing from 3.7 through 6.1. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
EMC DL3D 3000
If there is anyone using this VTL, if you don't mind would you please contact me off the list? I've got some questions for anyone with some experience with it. Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-B1P (858)826-4062 (office) (858)412-9883 (blackberry) Email: geoffrey.l.g...@saic.com
Changing Library Client to Manager server...
Hi, I have setup of two TSM server sharing a library with one as Library Manager server and one as Library client. Is it possible to make The client TSM server instance as Library manager server and a new TSM instance as Library Client? I want to discard the existing TSM instance which is library server right now? Regards, Kiran. Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address
SV: Dirmc and cloptset questions
Hi, Remember to have the same Ver Exist. Ver Deleted, Retention Exist and Retention Only as the highest MGMT Class you have. I have see some installations where DIRMC only have VerE = 2 VerD=1 RetO=30 RetE=60. When you do a point-in-time restore via GUI then has the directory been expired and you can not browse your files because of that. You can only restore via command line. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r Nicholas Rodolfich [nrodolf...@cmaontheweb.com] Skickat: den 8 juli 2009 23:19 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: Dirmc and cloptset questions Should work! This is what TSM refers to as rebinding. Be sure to mark the override client settings in the cloptset option. Regards, Nicholas ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/08/2009 01:46:01 PM: [image removed] [ADSM-L] Dirmc and cloptset questions Lee, Gary D. to: ADSM-L 07/08/2009 01:47 PM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager Just ran into the dreaded invisible files in point-in-time restore with tsm gui. Looks like some of the directories of some clients didn't get bound to my dirsonly management class with retonly of 180 days. I would like to force all directories to rebind to this class. I propose adding the dirmc option to any cloptsets and then define as apppropriate for all clients. I have such a set defined for solaris clients to exclude /etc/ mnttab, and one for win2k clients with specific excludes. Anything wrong with this idea; and how best to implement. Suggestions and criticisms welcome. Tsm server 5.4.4 clients rangeing from 3.7 through 6.1. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
