Re: Anyone know of issues running older clients against 5.4.3 server?
Thanks for everyone's feedback on this. John, thanks especially for the notes on older AIX clients. We do have a couple of those left. Remco, we do plan to send out a notice to these users, but I also wanted to find out if they were likely to stop working or not. We have over a thousand clients running 5.1.5, so there's no way we can get all of them to upgrade in a short timeframe (we don't manage desktop machines centrally here). No one mentioned Mac clients. That's the one platform where we've had a problem in the past when we upgraded our server software. I also noticed the following item in IBM's "end-of-life" announcement for 5.3: Select support for three operating systems will be added to TSM 5.4 in April 2008. Special 5.3.6 backup-archive clients and 5.3.6.3 storage agents will be supported on only these operating systems, for use with TSM 5.4 and 5.5 servers. However (as was noted some time ago on this list), these 5.3.6 clients are not yet available. It would be nice to know if there are code changes for 5.3.6, or if this is just a repackaging of some sort. It's a bit annoying that these will only be made available "in the nick of time" before 5.3 server support ends. ..Paul At 03:06 PM 4/10/2008, Schneider, John wrote: Paul, We just upgraded our AIX 5.3.5.1 server at one location to 5.4.2, and when we did, we found some unreliability problems show up on some AIX clients running TSM 5.2.0.0 and TSM 5.1.5. These were neglected clients anyway, and should have been upgraded long ago. So we upgraded one of them to TSM 5.4.2 yesterday, and the problem seems to have gone away. We will be doing this to the rest of them soon. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-486-2359 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Zarnowski Sent: Thursday, April 10, 2008 1:21 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Anyone know of issues running older clients against 5.4.3 server? We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED] -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
How do I get TDPO to send controlfiles to SBT_TAPE instead of DISK?
My DBAs and I are completely baffled. How do I get TDPO to send
controlfiles to SBT_TAPE instead of DISK?
My setup:
TSM server (Enterprise) 5.5 on AIX 5.2.
TDPO 5.4.1 on Solaris 10/SPARC and Oracle 10gR2.
RMAN settings:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; #
default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 3 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS '';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO
'/opt/oracle10/product/10.2.0/db_1/dbs/snapcf_mydb.f'; # default
How we backup -- RMAN commands:
allocate channel t1 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t2 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocate channel t3 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
sql 'alter system archive log current';
backup incremental level = ${LEVEL}
filesperset 5
format "df_%d_%s_%p_%t.lv${LEVEL}"
(database include current controlfile);
backup
filesperset 20
format "ar_%d_%s_%p_%t.lv${LEVEL}"
(archivelog all delete all input);
release channel t1;
release channel t2;
release channel t3;
tdpo.conf for the restore on a test box:
DSMI_ORC_CONFIG /opt/tivoli/tsm/client/oracle/bin64/dsm.opt
DSMI_LOG/var/log/tsm
TDPO_FS prod-oracle
TDPO_MGMT_CLASS_2 tsmoracle-mgmt2
TDPO_MGMT_CLASS_3 tsmoracle-mgmt3
TDPO_MGMT_CLASS_4 tsmoracle-mgmt4
Not a fancy setup; pretty much 'stock' (standard). Thoughts/ideas?
-Dan
Re: Anyone know of issues running older clients against 5.4.3 server?
Paul, We just upgraded our AIX 5.3.5.1 server at one location to 5.4.2, and when we did, we found some unreliability problems show up on some AIX clients running TSM 5.2.0.0 and TSM 5.1.5. These were neglected clients anyway, and should have been upgraded long ago. So we upgraded one of them to TSM 5.4.2 yesterday, and the problem seems to have gone away. We will be doing this to the rest of them soon. Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-486-2359 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Zarnowski Sent: Thursday, April 10, 2008 1:21 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Anyone know of issues running older clients against 5.4.3 server? We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: Anyone know of issues running older clients against 5.4.3 server?
Maybe in a perfect world But when you have vendor maintained applications/servers that run things like Windows 2000 or the Linux 2.4 kernel or Solaris 8 or SGI, you don't have a choice but to use the old clients! Remco Post <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 04/10/2008 02:38 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Anyone know of issues running older clients against 5.4.3 server? Paul Zarnowski wrote: > We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know > if anyone knows of any problems running older clients with a 5.4.x > server. While I know IBM only supports 1 version back, it's usually the > case that older clients continue to work (with some exceptions). Thanks > for any feedback. We still have a bunch of 5.1.5 clients out there that > we've been unsuccessful in prodding our users to upgrade from, so that's > the level I'm most concerned about. > Hi Paul, if you know who the users are, I'd say you can give m sort of final notice... 'your client will be unsupported as of our next upgrade due $data, if you haven't upgraded to at least version 5.4, we will be unable to help you with any problems or guarantee service'. It's sort of BOFH-style CYA, but nobody would be able to claim that you haven't given them proper notice. > ..Paul > > > -- > Paul ZarnowskiPh: 607-255-4757 > Manager, Storage Services Fx: 607-255-8521 > 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED] -- Met vriendelijke groeten, Remco Post
Re: Anyone know of issues running older clients against 5.4.3 server?
We are using 5.4.1 server and have twenty-five clients at the 5.1.5 level or worse that are doing just fine. - Margaret Clark, San Diego Data Processing Corporation -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Zarnowski Sent: Thursday, April 10, 2008 11:21 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Anyone know of issues running older clients against 5.4.3 server? We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: Anyone know of issues running older clients against 5.4.3 server?
And I've got customers running 5.1 Windows clients against 5.4.x servers. No issues. On 4/10/08, Richard Rhodes <[EMAIL PROTECTED]> wrote: > > We run TSM server 5.4.1 and have some old 5.1.6 clients running just fine. > These are old AIX 4.3.3 servers still hanging around. > > rick > > > > > > Paul Zarnowski > <[EMAIL PROTECTED] > > To > Sent by: "ADSM: ADSM-L@VM.MARIST.EDU > Dist Stor cc > Manager" > <[EMAIL PROTECTED] Subject > .EDU> Anyone know of issues running older > clients against 5.4.3 server? > > 04/10/2008 02:20 > PM > > > Please respond to > "ADSM: Dist Stor > Manager" > <[EMAIL PROTECTED] > .EDU> > > > > > > > We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know > if anyone knows of any problems running older clients with a 5.4.x > server. While I know IBM only supports 1 version back, it's usually the > case that older clients continue to work (with some exceptions). Thanks > for any feedback. We still have a bunch of 5.1.5 clients out there that > we've been unsuccessful in prodding our users to upgrade from, so that's > the level I'm most concerned about. > > ..Paul > > > -- > Paul ZarnowskiPh: 607-255-4757 > Manager, Storage Services Fx: 607-255-8521 > 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED] > > > > - > 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: Anyone know of issues running older clients against 5.4.3 server?
If you check the archives for ADSM-L, you would see that I and others have already answered this question. I am running clients ranging from 3.1.0.6 (OpenVMS) up to the lates (5.5.0.6) t, to my 5.5 servers! I made sure to experiment with the 3.1 client before I implemented the 5.5 server. Paul Zarnowski <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 04/10/2008 02:24 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Anyone know of issues running older clients against 5.4.3 server? We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: Anyone know of issues running older clients against 5.4.3 server?
We run TSM server 5.4.1 and have some old 5.1.6 clients running just fine. These are old AIX 4.3.3 servers still hanging around. rick Paul Zarnowski <[EMAIL PROTECTED] > To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Anyone know of issues running older clients against 5.4.3 server? 04/10/2008 02:20 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED] - 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: Anyone know of issues running older clients against 5.4.3 server?
Paul Zarnowski wrote: We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. Hi Paul, if you know who the users are, I'd say you can give m sort of final notice... 'your client will be unsupported as of our next upgrade due $data, if you haven't upgraded to at least version 5.4, we will be unable to help you with any problems or guarantee service'. It's sort of BOFH-style CYA, but nobody would be able to claim that you haven't given them proper notice. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED] -- Met vriendelijke groeten, Remco Post
Anyone know of issues running older clients against 5.4.3 server?
We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: 5.5 server in larger environments?
Running 5.5.0.0 AIX Server since about New Years. Had one sequence of two crashes in a row, but other than that very stable over 3 months of very heavy production use. We have a 283GB database, backing up about 2TB/night. New features in 5.5 proved their value in our January disaster recovery situation. So I see mostly upside, and no downside, to 5.5. Version 5.5.0.0 AIX Server is very clean and stable. (I only wish the 5.5 clients were as good ...but that's another story.) Only problem was that when migrating from 5.3 to 5.5, the automatic install procedure failed to do the required UPGRADEDB. But this was obvious to detect, and it was easy to run the UPGRADEDB manually, so I consider it to be no big deal. Just beware it could happen to you and be ready to do it manually if necessary. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] Academic Computing & Communications Center On Wed, 9 Apr 2008, Remco Post wrote: > >usually, after new TSM server is released you hear many complaints from >early adopters about lots of problems. With 5.5 I've heard very little, >so I was wondering, how many people are actually using the 5.5 server in >a production environment, and how big are these? Is anyone with a db >over 100 GB in size running 5.5 server? Or over 200 GB? How much data do >you backup on an average day? During the last dutch TSM UG meeting, >there was only one site using 5.5 server out of about 30 attendees. > >-- > >Met vriendelijke groeten, > >Remco Post, PLCS >
Re: ACN5798SE error Restoring Exchange
Well, we changed nothing about how we were doing the restores, except for that option, and all of our backups are legacy. We do a full on weekends via a cmd file, and incrs. Each day. Now, if the TDP is doing a vss backup when we do the full on Sunday, it's doing so of its own accord. Here's the Sunday command that kicks off the full backup: start /B tdpexcc backup * full /tsmoptfile=dsm.exch.opt /logfile=excsch.log /excserver=svrname >> excfull.log Here's the daily command that kicks off the incremental backup: start /B tdpexcc backup * incr /tsmoptfile=dsm.exch.opt /logfile=excsch.log /excserver=svrname >> excincr.log See Ya' Howard > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Del Hoobler > Sent: Thursday, April 10, 2008 10:09 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] ACN5798SE error Restoring Exchange > > Howard, > > If you are performing legacy restores the "Disable VSS Instant Restore" > will have no effect on what you are doing. > And so... I think it must have been your run recovery settings > or the way in which you were performing the restores. > > As far as applying legacy incremental restore on top of VSS full > restores, > that is not supported by Microsoft for Exchange. > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on 04/10/2008 > 10:55:47 AM: > > > Right after I sent this message I asked the Exchange guy to disable > "vss > > instant restore" and see if that worked, and viola, its working. > > > > Not sure what the vss instant does, but it obviously doesn't like > > incrementals from a legacy backup, :-D. > > > > No, I don't think I'm running 5.3.3.0.1 I have never downloaded it. > > > > The backup was legacy, which I believe had something to do with it, > > actually. > > > > See Ya' > > Howard
Re: 5.5 server in larger environments?
Skylar Thompson wrote: Out of curiosity, what hardware and OS are you running? We've had a couple segfaults in 5.5 when there were a bunch of transactions running during a database backup, but none since I upped the LOGPOOLSIZE to 2048. And out of fairness, I should say that we run on 64-bit Red Hat Enterprise 4. -- -- Skylar Thompson ([EMAIL PROTECTED]) -- Genome Sciences Department, System Administrator -- Foege Building S048, (206)-685-7354 -- University of Washington School of Medicine
Re: ACN5798SE error Restoring Exchange
Howard, If you are performing legacy restores the "Disable VSS Instant Restore" will have no effect on what you are doing. And so... I think it must have been your run recovery settings or the way in which you were performing the restores. As far as applying legacy incremental restore on top of VSS full restores, that is not supported by Microsoft for Exchange. Thanks, Del "ADSM: Dist Stor Manager" wrote on 04/10/2008 10:55:47 AM: > Right after I sent this message I asked the Exchange guy to disable "vss > instant restore" and see if that worked, and viola, its working. > > Not sure what the vss instant does, but it obviously doesn't like > incrementals from a legacy backup, :-D. > > No, I don't think I'm running 5.3.3.0.1 I have never downloaded it. > > The backup was legacy, which I believe had something to do with it, > actually. > > See Ya' > Howard
Re: Improving TSM performance - memory related setting
We have experienced this phenomenon as well at 5.3.5.2 on a Solaris TSM Server. The system has 32GB memory, 6 CPU. We used 20GB for bufferpool and verified that there was no paging going on. Performance was terrible! As a measure, expiration took about a week. All other processes, sessions, queries were similarly bad. Reduced buffpool to about 1/2 GB and performance is now great. Expiration now runs in about 3 hours. Other measures improved dramatically as well. Current DB stats: Available Space (MB): 204,800 Assigned Capacity (MB): 202,860 Maximum Extension (MB): 1,940 Maximum Reduction (MB): 75,212 Page Size (bytes): 4,096 Total Usable Pages: 51,932,160 Used Pages: 32,695,965 Pct Util: 63.0 Max. Pct Util: 63.0 Physical Volumes: 16 Buffer Pool Pages: 131,072 Total Buffer Requests: 306,981,255 Cache Hit Pct.: 99.72 Cache Wait Pct.: 0.00 Robert R. Price TSM Administrator Computer Sciences Corporation Phone: 412-374-3247 Fax: 412-374-6371 [EMAIL PROTECTED] Computer Sciences Corporation Registered Office: 3170 Fairview Park Drive, Falls Church, Virginia 22042, USA Registered in Nevada, USA No: C-489-59 - This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - Matthew Glanville To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: Improving TSM performance - memory related setting 04/07/2008 09:43 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Just a warning, don't necessarily go to 1/2 or 1/8th of your total physical memory.. If your server has 64 GB of memory, 8 GB (1/8th) for BUFPOOLSIZE is probably too high. I would keep it below 1 GB unless you prove to yourself with some testing that it is helping speed up the backups or restores. Just don't look at database cache hit rate. I think there's some inefficiency in how TSM database cache works, as it may have to search through that cached memory to find a hit. When you are caching 8 GB, that takes some time to search through all that. You'll see this as the dsmserv processes CPU use will increase the larger the BUFPOOLSIZE is. If it takes longer to search through that memory than it does to read the page from disk, you are hurting performance not helping it by caching in memory. Maybe DB2 TSM in version 6 will help this issue. I tried to put a problem in for it a few years back, but couldn't get beyond level 2 since no one understood what I was talking about, they kept thinking the server was slow due to the operating system using it's own page file to make up for the large memory setting, even though the 64 bit server had 32 GB of physical memory... Ahh well. I can use that other 30 GB for something else. or is it fixed now? Matt G. "ADSM: Dist Stor Manager" wrote on 04/04/2008 03:40:56 AM: > Bufpoolsize should be set between 1/2 and 1/8 of the among of the > total physical memory, if I remember well, that is, what best > practices recommend. > Also if you modify this parameter you will have to take a look at > the percentage hit cache (q db f=d) that can be increase (modifying > the bufpolsize), or perhaps decrease if the setting is incorrect. > Percentage hit cache must be above 99 %. > > I will also recommend to take a look at the performance tuning > guide, that will let you know more about many settings that can > increase the performance of your TSM server. > > Regards, > Bernaldo. > > > > - Mensaje original > De: Paul Dudley <[EMAIL PROTECTED]> > Para: ADSM-L@VM.MARIST.EDU > Enviado: viernes, 4 de abril, 2008 5:44:02 > Asunto: Re: [ADSM-L] Improving TSM performance - memory related setting
Re: 5.5 server in larger environments?
Zoltan Forray/AC/VCU wrote: We are running 4-servers. [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] The 5.5 servers have given us grief. We have at least 4-known (apars) problems we are waiting on patches for. 1-requires occasional restarts of the server (this is the IBM workaround). The other one has crashed frequently. In fact, we currently have an open problem on this server. IBM had to create us a "diagnostic kernel" version of dsmserv to try to reproduce the problem and get additional information. The biggest has a 160GB DB, which is showing us the most problems. Expires are running 48-hours+. We only backup 1-2TB daily on this server but have an occupancy of 177TB with 289M files which I think is where our drag on the expires, is. I will not upgrade the non-5.5 servers until IBM gets these problems resolved. 5.4.2 is the highest I recommend! Out of curiosity, what hardware and OS are you running? We've had a couple segfaults in 5.5 when there were a bunch of transactions running during a database backup, but none since I upped the LOGPOOLSIZE to 2048. Even with the segfaults, I don't think we'd be able to go back from 5.5 because 5.5 solved a long-standing bug with SET EVENTs on archives. Whenever we tried to activate retention on an archive with more than a few hundred thousand files (read: all of our archives) we'd get an aborted transaction on the client. -- -- Skylar Thompson ([EMAIL PROTECTED]) -- Genome Sciences Department, System Administrator -- Foege Building S048, (206)-685-7354 -- University of Washington School of Medicine
Re: ACN5798SE error Restoring Exchange
Right after I sent this message I asked the Exchange guy to disable "vss instant restore" and see if that worked, and viola, its working. Not sure what the vss instant does, but it obviously doesn't like incrementals from a legacy backup, :-D. No, I don't think I'm running 5.3.3.0.1 I have never downloaded it. The backup was legacy, which I believe had something to do with it, actually. See Ya' Howard > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Del Hoobler > Sent: Thursday, April 10, 2008 9:44 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] ACN5798SE error Restoring Exchange > > Could this be APAR IC50413? Do you have DP/Exchange 5.3.3.01 installed? > If not, please install and use it. > > ftp://ftp.software.ibm.com/storage/tivoli-storage- > management/patches/tivoli-data-protection/ntexch/v533/ > > If you do have DP/Exchange 5.3.3.0.1 installed... > Are you using the GUI or CLI? > Are you restoring the FULL and INCREMENTAL in a single operation? > If you are using separate operations, are you specifying > the option to NOT run recovery on the FULL and then > specifying the option to run recovery on the INCREMENTAL? > Is this Exchange 2003 or Exchange 2007? > Is this Legacy or VSS? > > Thanks, > > Del > > > > "ADSM: Dist Stor Manager" wrote on 04/10/2008 > 10:13:42 AM: > > > I need some assistance. > > > > > > > > We're trying to restore some mail for a user, and we're getting a > > strange set of errors. > > > > > > > > When we do a restore from the full from 03/30/2008 the restore goes > > fine. > > > > When we restore from 1 incremental we get something like the > following: > > > > > > > > SG1INCR 03/31/2008 19:00:27 Restore failed, ACN5798E MS > Exchange > > API HRESERESTOREREOPEN() failed with HRESULT: 0xc7ff0bc3 -Restore > > environment information corrupted. > > > > SG1FULL 03/30/2008 18:00:10 Restore failed, ACN5798E MS > Exchange > > API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1142 - > Database > > not found. > > > > > > > > TSM Server version 5.2.9 (hopefully getting upgraded in the very near > > future). > > > > TSM Client version: 5.3.4 > > > > TSM Exchange TDP version: 5.3.3.0 > > > > > > > > I have verified with the Exchange Admin that the Exchange DB is set > to > > accept restores, and the Database to the Recovery Storage Group was > > added before the restore. I have also verified that its set to be > > overwritten by a restore. > > > > > > > > I found no errors in any of the backups from the 30th on for this > node, > > so it appears the backups worked.
SystemExcludeCache files question
I have exactly the same problem with TSM client 5.5.0.0. I found a workaround* to clean up the files of the C:\ADSM.SYS\VSS_STAGING directory, but nothing for the C:\ADSM.SYS\SystemExcludeCache__*.TsmCacheDB files... so I don't know whether it is safe to delete them using a post-schedule command. ( * http://www.ibm.com/support/docview.wss?rs=663&context=SSGSG7&dc=DB550&uid=swg1IC55612&loc=en_US&cs=UTF-8&lang=en&rss=ct663tivoli ) +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--
Re: ACN5798SE error Restoring Exchange
Could this be APAR IC50413? Do you have DP/Exchange 5.3.3.01 installed? If not, please install and use it. ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/tivoli-data-protection/ntexch/v533/ If you do have DP/Exchange 5.3.3.0.1 installed... Are you using the GUI or CLI? Are you restoring the FULL and INCREMENTAL in a single operation? If you are using separate operations, are you specifying the option to NOT run recovery on the FULL and then specifying the option to run recovery on the INCREMENTAL? Is this Exchange 2003 or Exchange 2007? Is this Legacy or VSS? Thanks, Del "ADSM: Dist Stor Manager" wrote on 04/10/2008 10:13:42 AM: > I need some assistance. > > > > We're trying to restore some mail for a user, and we're getting a > strange set of errors. > > > > When we do a restore from the full from 03/30/2008 the restore goes > fine. > > When we restore from 1 incremental we get something like the following: > > > > SG1INCR 03/31/2008 19:00:27 Restore failed, ACN5798E MS Exchange > API HRESERESTOREREOPEN() failed with HRESULT: 0xc7ff0bc3 -Restore > environment information corrupted. > > SG1FULL 03/30/2008 18:00:10 Restore failed, ACN5798E MS Exchange > API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1142 -Database > not found. > > > > TSM Server version 5.2.9 (hopefully getting upgraded in the very near > future). > > TSM Client version: 5.3.4 > > TSM Exchange TDP version: 5.3.3.0 > > > > I have verified with the Exchange Admin that the Exchange DB is set to > accept restores, and the Database to the Recovery Storage Group was > added before the restore. I have also verified that its set to be > overwritten by a restore. > > > > I found no errors in any of the backups from the 30th on for this node, > so it appears the backups worked.
ACN5798SE error Restoring Exchange
I need some assistance. We're trying to restore some mail for a user, and we're getting a strange set of errors. When we do a restore from the full from 03/30/2008 the restore goes fine. When we restore from 1 incremental we get something like the following: SG1INCR 03/31/2008 19:00:27 Restore failed, ACN5798E MS Exchange API HRESERESTOREREOPEN() failed with HRESULT: 0xc7ff0bc3 -Restore environment information corrupted. SG1FULL 03/30/2008 18:00:10 Restore failed, ACN5798E MS Exchange API HRESERESTOREADDDATABASE() failed with HRESULT: 0xc7fe1142 -Database not found. TSM Server version 5.2.9 (hopefully getting upgraded in the very near future). TSM Client version: 5.3.4 TSM Exchange TDP version: 5.3.3.0 I have verified with the Exchange Admin that the Exchange DB is set to accept restores, and the Database to the Recovery Storage Group was added before the restore. I have also verified that its set to be overwritten by a restore. I found no errors in any of the backups from the 30th on for this node, so it appears the backups worked. See Ya' Howard Coles Jr. Sr. Systems Engineer Ardent Health Services John 3:16!
Re: 5.5 server in larger environments?
We are running 4-servers. [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] The 5.5 servers have given us grief. We have at least 4-known (apars) problems we are waiting on patches for. 1-requires occasional restarts of the server (this is the IBM workaround). The other one has crashed frequently. In fact, we currently have an open problem on this server. IBM had to create us a "diagnostic kernel" version of dsmserv to try to reproduce the problem and get additional information. The biggest has a 160GB DB, which is showing us the most problems. Expires are running 48-hours+. We only backup 1-2TB daily on this server but have an occupancy of 177TB with 289M files which I think is where our drag on the expires, is. I will not upgrade the non-5.5 servers until IBM gets these problems resolved. 5.4.2 is the highest I recommend! Remco Post <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 04/09/2008 03:55 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] 5.5 server in larger environments? Hi All, usually, after new TSM server is released you hear many complaints from early adopters about lots of problems. With 5.5 I've heard very little, so I was wondering, how many people are actually using the 5.5 server in a production environment, and how big are these? Is anyone with a db over 100 GB in size running 5.5 server? Or over 200 GB? How much data do you backup on an average day? During the last dutch TSM UG meeting, there was only one site using 5.5 server out of about 30 attendees. -- Met vriendelijke groeten, Remco Post, PLCS
