Restart TSM Client on Windows 2000
Hi to all I have a question regarding TSM Client. How can i restart the TSM Client on Windows2000? Thanks Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended recipient is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify us immediately. All reasonable precautions have been taken to ensure no viruses are present in this e-mail. As we cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use. The views, opinions, conclusions and other information expressed in this electronic mail are not given or endorsed by Laiki Group unless otherwise indicated by an authorised representative independent of this message.
Re: How to stop tape from being ejected?
Thanks Mark and Ted Increasing the retention setting worked. On 5 Nov 2003 at 6:49, Mark Mooney wrote: > Try increasing the mount retention parameter on your device class. I > don't think it'll affect the behavior after a label operation though. > > Mooney > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Steve Ochani > Sent: Tuesday, November 04, 2003 19:40 > To: [EMAIL PROTECTED] > Subject: How to stop tape from being ejected? > > Hello, > > I'm running tsm 5.1 on sun solaris 8 with a DDS4 tape drive. > > After any tape operation such as labeling a tape or a backup the tape is > ejected, and I have to go back to the server room to put the tape back > in. > > Anyway to configure the software to stop ejecting the tape? > > > Thanks
TSM TDP for Notes Experts?
I wanted to ask something more specific as I'm not very strong in regards to Lotus Notes and their backups/restores. I have old backups of a Notes 5.x server that were supposedly taken with a TDP for Notes v1.1.x.. 1. Is it possible to restore those restores with the latest TDP for Notes (5.1.x)? 2. Is it possible to restore those restores with the latest TDP for Notes (5.1.x) to Notes 6.x? Thanks, Gerald This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm) service. For more information, visit us at www.zantaz.com. IMPORTANT: This electronic mail message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or directly reply to the original message(s) sent. Thank you.
Re: Data Protection Agent for Notes
Gerald, There was an old client called ADSMConnect Agent for Lotus Notes. That worked at the item level, and was only supported on Notes 4. Lotus introduced a backup API starting with Domino 5. Data Protection for Lotus Domino supports Domino 5 and Domino 6. The history of the releases looks like this: 1.1.0 9/1999 1.1.1 4/2000 1.1.210/2001 5.1.510/2002 - version realigned with client and server 5.2.0 7/2003 - This was OS/400 only (There were a few fixtest levels in there as well.) You can restore a backup made with any prior version. So... if you took a backup with 1.1.0, you can restore it with any version at that level or older. Thanks, Del > Does anyone have a good understanding of the Lotus Notes Data Protection > Agents and their history? From what I can gather there are/were 3 versions.. > > 1.1.x > 2.1.x > 5.1.x > > Similarly there are different versions of notes - 4.x, 5.x, 6.x.. > > What is restore-compatible with what in this matrix? If I have backups of a > Notes 5.x server that were originally taken with 1.1, can I restore with 2.1 > or 5.1 as well?
Re: How does "replace=no" work?
Alex, On 05.11.2003 19:04, Alex Paschal wrote: Tobi, To (kind of, but not really) address your question from yesterday, when doing a restore of large disk volumes, it's good to use the command line client and tee your output into a file. You can often avoid these kinds of issues by looking at that output file to see which file the restore last performed. Noted. Thanks! Cunning Plan... :) greets, tobi... :) -- -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] --
Data Protection Agent for Notes
Does anyone have a good understanding of the Lotus Notes Data Protection Agents and their history? From what I can gather there are/were 3 versions.. 1.1.x 2.1.x 5.1.x Similarly there are different versions of notes - 4.x, 5.x, 6.x.. What is restore-compatible with what in this matrix? If I have backups of a Notes 5.x server that were originally taken with 1.1, can I restore with 2.1 or 5.1 as well? Gerald Wichmann This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm) service. For more information, visit us at www.zantaz.com. IMPORTANT: This electronic mail message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or directly reply to the original message(s) sent. Thank you.
Re: TDP for Oracle Errors
I have received a similar error using TDP 2.2.1.0 for Oracle 8 with TSM server at 4.2.1. This setup has been functional for over a year and then out of the blue one night. from the actlog on the server: ANE4994S (Session: 732, Node: XX) TDP Oracle AIX ANU0599 ANU2602E The object /x///backup/y/hbkp__508578213_2322- _1 was not found on the TSM Server The error in the RMAN log was: RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE RMAN-03006: non-retryable error occurred during execution of command: backup RMAN-07004: unhandled exception during command execution on channel w2 RMAN-10035: exception raised in RPC: ORA-27192: skgfcls: sbtclose2 returned error - failed to close file ORA-19511: ANS1301E (RC1)Server detected system error RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE William Wells AIX Systems Administrator Atos Origin -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 16:30 To: [EMAIL PROTECTED] Subject: Re: TDP for Oracle Errors Eric, Oracle 9i introduced the concept of autobackups for the control file. During the autobackup process, Oracle dynamically generates the backuppiece name for the control files that are being saved. During this backup processing, a unique name is generated by Oracle prior to backing it up and the TSM Server is then checked to ensure that this backuppiece name does not exist. When performing this check for any existing objects that might have this name, Oracle will first try to delete this file regardless of whether it exists or not. The return code from the deletion process not finding the object on the TSM Server is the ANU2602E message. During the autobackup processing, Oracle calls the Media Management Layer (Data Protection for Oracle/TSM Server in this case). Oracle issues the command to attempt a deletion prior to autobackup of the control file. Because each MML operation is a unique and distinct session, the MML has to treat each delete the same. In other words, Oracle gives no hints as to the type of deletion being performed therefor Data Protection for Oracle just attempts the delete. >From Data Protection for Oracle's point of view a file not found during a delete could be a potentially serious error. For example: - During the delete the user is actually using a TSM filespace name that is different than what the objects were originally backed up under. - The TSM node does not have the backup delete permissions (backdel=yes|no). - During the deletion a different TDPO_NODE is specified than what was used during backup. The reason that these are potentially dangerous is that when Data Protection for Oracle detects an error during delete that a file is not found or cannot be deleted Oracle specifies that the MML does not return an error to Oracle. This causes a situation where during normal deletion Oracle would remove the backuppiece name from it's catalog but the backup could still exist on the TSM Server there by using up unnecessary storage space. Unfortunately, unless we ignore this error altogether then there is nothing that we (developement) can do. In the mean time the only tips we can give to work around these error messages during autobackups is for the user to do the following: Use the DISABLE EVENTS command on the TSM Server to suppress all ANU0599 ANU2602E messages so there would be no notification when a the file is not being found during DP for Oracle processing. For the tdpoerror.log, a different DSMI_LOG could be specified (in the tdpo.opt file) for the autobackup so that the errorlog would go to a different directory - in this way these logs could be monitored separately. -- Date:Tue, 4 Nov 2003 16:28:55 +0100 From:"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> Subject: TDP for Oracle Errors Hi *SM-ers! Our Oracle guys and girls are currently testing DP for Oracle 5.2 on Oracle 9i. They turned one a new RMAN feature for automated controlfile backup (for those of you interested, the command is 'configure controlfile autobackup on;') Now, whenever a controlfile backup is running it generates the following error in both the tdpoerror.log and the actlog: ANE4994S (Session: 1437562, Node: KL1003VC-ORC) TDP Oracle AIX ANU0599 ANU2602E The object /mount/appl1//c-213141136-20031104-0e was not found on the TSM Server We had to make a trace to see that this error is generated because TSM first checks whether the object exists on the server before allocating it. I created a PMR for this behavior and level 1 now says: works as designed, just suppress ANE4994S from the actlog (impossible since ANE4994S is a generic message) and build something yourself to clear your tdpoerror.log periodically. I find this a VERY disappointing reply from IBM Has anybody encountered this behavior to and maybe
Re: TDP for Oracle Errors
Eric, Oracle 9i introduced the concept of autobackups for the control file. During the autobackup process, Oracle dynamically generates the backuppiece name for the control files that are being saved. During this backup processing, a unique name is generated by Oracle prior to backing it up and the TSM Server is then checked to ensure that this backuppiece name does not exist. When performing this check for any existing objects that might have this name, Oracle will first try to delete this file regardless of whether it exists or not. The return code from the deletion process not finding the object on the TSM Server is the ANU2602E message. During the autobackup processing, Oracle calls the Media Management Layer (Data Protection for Oracle/TSM Server in this case). Oracle issues the command to attempt a deletion prior to autobackup of the control file. Because each MML operation is a unique and distinct session, the MML has to treat each delete the same. In other words, Oracle gives no hints as to the type of deletion being performed therefor Data Protection for Oracle just attempts the delete. >From Data Protection for Oracle's point of view a file not found during a delete could be a potentially serious error. For example: - During the delete the user is actually using a TSM filespace name that is different than what the objects were originally backed up under. - The TSM node does not have the backup delete permissions (backdel=yes|no). - During the deletion a different TDPO_NODE is specified than what was used during backup. The reason that these are potentially dangerous is that when Data Protection for Oracle detects an error during delete that a file is not found or cannot be deleted Oracle specifies that the MML does not return an error to Oracle. This causes a situation where during normal deletion Oracle would remove the backuppiece name from it's catalog but the backup could still exist on the TSM Server there by using up unnecessary storage space. Unfortunately, unless we ignore this error altogether then there is nothing that we (developement) can do. In the mean time the only tips we can give to work around these error messages during autobackups is for the user to do the following: Use the DISABLE EVENTS command on the TSM Server to suppress all ANU0599 ANU2602E messages so there would be no notification when a the file is not being found during DP for Oracle processing. For the tdpoerror.log, a different DSMI_LOG could be specified (in the tdpo.opt file) for the autobackup so that the errorlog would go to a different directory - in this way these logs could be monitored separately. -- Date:Tue, 4 Nov 2003 16:28:55 +0100 From:"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> Subject: TDP for Oracle Errors Hi *SM-ers! Our Oracle guys and girls are currently testing DP for Oracle 5.2 on Oracle 9i. They turned one a new RMAN feature for automated controlfile backup (for those of you interested, the command is 'configure controlfile autobackup on;') Now, whenever a controlfile backup is running it generates the following error in both the tdpoerror.log and the actlog: ANE4994S (Session: 1437562, Node: KL1003VC-ORC) TDP Oracle AIX ANU0599 ANU2602E The object /mount/appl1//c-213141136-20031104-0e was not found on the TSM Server We had to make a trace to see that this error is generated because TSM first checks whether the object exists on the server before allocating it. I created a PMR for this behavior and level 1 now says: works as designed, just suppress ANE4994S from the actlog (impossible since ANE4994S is a generic message) and build something yourself to clear your tdpoerror.log periodically. I find this a VERY disappointing reply from IBM Has anybody encountered this behavior to and maybe found a better way to solve these errors? Maybe someone from development listening on this list has a good suggestion? I'm really stuck here with the Dutch level 1 support... :-(( Kindest regards, Eric van Loon KLM Royal Dutch Airlines Regards, Neil Rasmussen Software Development Data Protection for Oracle [EMAIL PROTECTED]
Re: Cannot restore Database
I ran into this a few weeks ago. I had to format the log and DB volumes before the restore would work. Something like: dsmserv format numberoflogfiles logfilenames numberofdbvolumes dbvolnames ie dsmserv format 1 /adsmlog/log1 1 /adsmdb/db1 You only need to do the prime volumes, not the mirrors. Once it formats, run the restore command again. See this page for reference: http://www.uni-ulm.de/urz/Hard_Software/Dokumentationen/tsm/reference/an rar343.htm Michael French Savvis Communications IDS01 Santa Clara, CA (408)450-7812 -- desk (408)239-9913 -- mobile -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Alan Davenport Sent: Wednesday, November 05, 2003 12:36 PM To: [EMAIL PROTECTED] Subject: Cannot restore Database Hello Group, I'm trying to restore a TSM database to a disaster recovery copy of one of our remote TSM servers without success. I installed TSM onto the DR box, copied the DEVCFG.OUT and VOLHIST.OUT files into the directory where the new server was built. When I try to restore the database I get the following error. Any idea where I am going wrong? ANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.o- pt. ANR7800I DSMSERV generated at 09:58:50 on Jun 13 2003. Tivoli Storage Manager for Windows Version 5, Release 2, Level 0.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990,2003. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR8200I TCP/IP driver ready for connection with clients on port 1500. ANR0200I Recovery log assigned capacity is 1000 megabytes. ANR0201I Database assigned capacity is 2000 megabytes. ANR4621I Database backup device class TAPE2. ANR4622I Volume 1: B4. ANR4632I Starting point-in-time database restore (no commit). ANRD icrest.c(2076): ThreadId<0> Rc=33 reading header record. ANR2032E RESTORE DB: Command failed - internal server error detected. Entering exception handler. Thanks, Al Alan Davenport Senior Storage Administrator Selective Insurance Co. of America [EMAIL PROTECTED] (973) 948-1306
Cannot restore Database
Hello Group, I'm trying to restore a TSM database to a disaster recovery copy of one of our remote TSM servers without success. I installed TSM onto the DR box, copied the DEVCFG.OUT and VOLHIST.OUT files into the directory where the new server was built. When I try to restore the database I get the following error. Any idea where I am going wrong? ANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.o- pt. ANR7800I DSMSERV generated at 09:58:50 on Jun 13 2003. Tivoli Storage Manager for Windows Version 5, Release 2, Level 0.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990,2003. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR8200I TCP/IP driver ready for connection with clients on port 1500. ANR0200I Recovery log assigned capacity is 1000 megabytes. ANR0201I Database assigned capacity is 2000 megabytes. ANR4621I Database backup device class TAPE2. ANR4622I Volume 1: B4. ANR4632I Starting point-in-time database restore (no commit). ANRD icrest.c(2076): ThreadId<0> Rc=33 reading header record. ANR2032E RESTORE DB: Command failed - internal server error detected. Entering exception handler. Thanks, Al Alan Davenport Senior Storage Administrator Selective Insurance Co. of America [EMAIL PROTECTED] (973) 948-1306
Re: Upgrading Netware Client from 4.1.3.0 to 5.1.5.15
No, in fact once I've expanded the client once my upgrade process involves renaming the existing Tivoli folder out of the way and copying the new one in. You will need to manually load and run a backup to reestablish the passwords and ID's, although you can cheat on that as well. Even if you upgrade the nlms no restart is required. Just rename the old ones, copy in the new ones and unload/reload. Marc Levitan wrote: > > Client Info: > Netware 5 sp6 > Client level 4.1.3.0 > > When I upgrade the client to 5.1.5.15, will I have to reboot netware? > > Thanks, > Marc -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Upgrading Netware Client from 4.1.3.0 to 5.1.5.15
Client Info: Netware 5 sp6 Client level 4.1.3.0 When I upgrade the client to 5.1.5.15, will I have to reboot netware? Thanks, Marc
Re: Help with TSM server being hammered by clients
If you have anymore questions about my system layout, contact me: 1. The server is a Sun 4500 with 4 400MHz Sparc III procs and 4GB RAM. Attached to the system is 1 D100 disk array used to hold the OS. All of the TSM volumes are held on A5200 fiber channel arrays (3 of them containing 66 disk drives). 2. tsm: I02SV1000>q dbvol f=d Volume Name Copy Volume Name Copy Volume Name Copy AvailableAllocated (Copy 1)Status(Copy 2)Status(Copy 3) StatusSpaceSpace (MB) (MB)(MB) ---- ---- /adsmdb2/db1a Sync'd/adsmdb2m/db1am Sync'd Undef-8,3528,352 ined /adsmdb3/db1a Sync'd/adsmdb3m/db1am Sync'd Undef-8,5008,352 ined /adsmdb4/db1a Sync'd/adsmdb4m/db1am Sync'd Undef-8,3528,352 ined /adsmdb5/db1a Sync'd/adsmdb5m/db1am Sync'd Undef-8,3528,352 ined /adsmdb10/db1a Sync'd/adsmdb10m/db1amSync'd Undef-8,3528,352 ined /adsmdb9/db1a Sync'd/adsmdb9m/db1am Sync'd Undef-8,3528,352 ined /adsmdb8/db1a Sync'd/adsmdb8m/db1am Sync'd Undef-8,3528,352 ined /adsmdb7/db1a Sync'd/adsmdb7m/db1am Sync'd Undef-8,3528,352 ined /adsmdb6/db1a Sync'd/adsmdb6m/db1am Sync'd Undef-8,3528,352 ined /adsmdb1/db1a Sync'd/adsmdb1m/db1am Sync'd Undef-8,3528,352 ined tsm: I02SV1000>q logvol f=d Volume Name Copy Volume Name Copy Volume Name Copy AvailableAllocated (Copy 1)Status(Copy 2)Status(Copy 3) StatusSpaceSpace (MB) (MB)(MB) ---- ---- /adsmlog2/log4 Sync'd/adsmlog2m/log4mSync'd Undef- 300 300 ined /adsmlog1/log2 Sync'd/adsmlog1m/log2mSync'd Undef- 100 100 ined /adsmlog1/log1 Sync'd/adsmlog1m/log1mSync'd Undef-4,0964,096 ined /adsmlog1/log4 Sync'dUndef- Undef- 200 200 ined ined tsm: I02SV1000>q vol Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status (MB) --- -- - - /dev/vx/rdsk/datadg/ads- BACKUPPOOL DISK36,864.0 64.1 On-Line mdata1 /dev/vx/rdsk/datadg/ads- BACKUPPOOL DISK36,864.0 72.0 On-Line mdata2 /dev/vx/rdsk/datadg/ads- BACKUPPOOL DISK36,864.0 47.3 On-Line mdata3 /dev/vx/rdsk/datadg/ads- BACKUPPOOL DISK36,864.0 56.4 On-Line mdata4 /dev/vx/rdsk/datadg/ads- BACKUPPOOL DISK36,864.0 49.7 On-Line mdata5 /dev/vx/rdsk/datadg/ads- BACKUPPOOL DISK36,864.0 79.0 On-Line 3. File system is UFS and VXFS (for all TSM volumes). 4. RAID is software with Veritas Volume Manager. 5. Each DB and Log volume is on it's own disk group. The unfortunate problem is that they are on mounted file system partitions instead of raw volumes. In doing benchmark testing, this had a dramatic effect on backup performance. The main issue seemed to be the diskpool volumes which were easy to convert to raw, at least compared to doing the DB volumes, so I have already done that several weeks ago. I am planning on doing the DB and log vols soon. I did not see any performance gain with backups of many large files, just on medium and large ones. 6. Yes, the volumes are seperated by type. 7. Most volumes appear to be broken out over two physical disks. I am not sure how many spindles each disk has. They are mostly 9GB and 18GB FC drives. 8. tsm: I02SV1000>q db f=d Available Space (MB): 83,520 Assigned Capacity (MB): 83,520 Maximum Extension (MB): 0 Maximum Reduction (MB): 14,832 Page Size (bytes): 4,096 Total Usable Pages: 21,381,120 Used Pages: 8,748,928 Pct Util: 40.9 Max. Pct Util: 41.2 Physical Volumes: 20 Buffer Pool Pages: 393,216 Total Buffer Requests: 10,118,152 Cache Hit Pct.: 96.81 C
Re: TDP Exchange Copy Group Definitions
Tom, VERExists Specifies the maximum number of backup versions to retain for storage groups/databases that are currently on the Exchange Server. VERDeleted Specifies the maximum number of backup versions to retain for storage groups/databases that have been deleted from the Exchange Server after being backed up using Tivoli Storage Manager. RETExtra Specifies the number of days to retain a backup version after that version becomes inactive. A version becomes inactive when Data Protection for Exchange stores a more recent backup version. The Tivoli Storage Manager server deletes inactive versions based on retention time even if the number of inactive versions does not exceed the number allowed by the VEREXISTS or VERDELETED parameters. RETOnly Specifies the number of days to retain the last backup version of storage groups/databases that has been deleted from the Exchange Server. For more details on the generic definitions, look here: http://publib.boulder.ibm.com/tividd/td/IBMTivoliStorageManagerforWindows5.2.html Also, look at the Data Protection for Exchange User's Guide under section: "Data Protection for Exchange policy settings" Thanks, Del > Now that I understand that, how about commenting on > each of the copy group items in my example, supply a > definition which is easily understandable, an example > would suffice. I have read the redbook and I am still > confused.
Re: TDP Exchange Copy Group Definitions
You can check Redbook sg246147 "Using TDP for MS Exchange Server" Chapter 2.3.1 "Policies and management classes" ; there is really good and in depth explanation of how the backup works. I didn't fully understand it when I read it, but after I setup test environment and tried it everything cleared up. Joe Crnjanski Infinity Network Solutions Inc. Phone: 416-235-0931 x26 Fax: 416-235-0265 Web: www.infinitynetwork.com -Original Message- From: Fought,Tom [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 12:50 PM To: [EMAIL PROTECTED] Subject: Re: TDP Exchange Copy Group Definitions Thanks Del. Now that I understand that, how about commenting on each of the copy group items in my example, supply a definition which is easily understandable, an example would suffice. I have read the redbook and I am still confused. Tom -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 12:43 PM To: [EMAIL PROTECTED] Subject: Re: TDP Exchange Copy Group Definitions Tom, First... I am assuming you are referring to Data Protection for Exchange version 2 or higher. Version 2 and higher use standard TSM policy management. (Version 1 used different policy management.) These settings basically mean that you will be able to restore any full backup for that last 90 days as long as there haven't been more than 90 different backups within that timeframe. These settings are OK... but if the intent is to keep any backup for 90 days... ... the settings should be more like this: Versions Data Exists NOLIMIT Versions Data DeletedNOLIMIT Retain Extra Versions90 Retain Only Version 90 This makes it so that no matter how many backups you take during the timespan... they won't expire earlier than 90 days. Thanks, Del > Could someone with TDP Exchange experience comment on what > the following copy group definition for TDP Exchange clients > would mean for tdp object retention? > > Versions Data Exists 90 > Versions Data Deleted 90 > Retain Extra Versions 90 > Retain Only Version 90
Re: Z/OS and TSM - preferred server level??
I believe, when IBM was working on the zap, I was told that there was a problem moving from the 4.1 version - something about a legacy member table instead of the backup groups table problem. I'm running at the 5.2.1.1 level with the zap. -Original Message- From: Stumpf, Joachim [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:19 AM To: [EMAIL PROTECTED] Subject: Re: Z/OS and TSM - preferred server level?? Jim, I didn't recognize that you are at 4.1. I think theres no problem with the upgrade for you, because the problems we had were with the systemobjects of windows nodes which were included with 4.2. Our migrations: 3.7 --> 4.1.3 --> 4.1.5 --> 5.1.0.0 --> 5.1.1.6 --> 5.1.5.0 --> 5.1.5.3 --> 5.1.6.1 ---> 5.1.6.3 and now we are migrating to 5.2.1.1 I think our problems with the systemobjects occured somewhere during migration from 4.1.5 to 5.1.6.3. -- mit freundlichen Grüßen Joachim Stumpf - Original-Nachricht folgt - Joachim, Thanks, I remember seeing something about this earlier. I wonder if it applies, though, as we are moving from 4.1.x and the problem description specifically references 4.2 and 5.1 >From what release did you jump to 5.1.6? "Stumpf, Joachim" wrote: > > Hi, > > at the moment we are migrating from 5.1.6.3 to 5.2.1.1. > If you are at 4.x you should have a look at: > http://www-1.ibm.com/support/docview.wss?uid=swg1PQ80211 > > We had big problems with the performance during upgradedb (AuditDB run 80h with a 16GB database and used over 65h CPU). > After the ZAP the Upgradedb took nearly 30min and used 3min. CPU. > > So the ZAP mentioned in the ARPAR worked for us. > > Good Luck ;-) > > -- > mit freundlichen Grüßen / regards > Joachim Stumpf > > > - Original-Nachricht folgt - > > We are closing in on bringing up Z/OS 1.4 and with it a new version of > TSM server. It looks like 5.1.7 was delivered with our server pac (FMID > HDN5510). In a meeting earlier this week a Tivoli rep recommended that > we go ahead and pull down the latest server level (5.2.1 w/5.2.2 due in > early Dec.) > > Any recommendations or experiences with this platform and TSM levels out > there worth passing along? We're currently at 4.1.4.2 > > As always, thanks in advance! > > -- > Jim Kirkman > AIS - Systems > UNC-Chapel Hill > 966-5884 -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: How does "replace=no" work?
Tobi, To (kind of, but not really) address your question from yesterday, when doing a restore of large disk volumes, it's good to use the command line client and tee your output into a file. You can often avoid these kinds of issues by looking at that output file to see which file the restore last performed. Alex Paschal Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Tobias Hofmann [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:33 AM To: [EMAIL PROTECTED] Subject: Re: How does "replace=no" work? Andy, On 05.11.2003 17:58, Andrew Raibeck wrote: >>Now I restore this file to the original location, >>with replace=no - what happens? > > Because foo.avi already exists, foo.avi is not restored. Ok, got that. Thanks! :) >>Does TSM not replace the file, since the "existing >>file" (even though with different size, and different >>modification date - are there any other criteria?) is >>there with the same name and in the same location? > > Correct. Because a file already exists with the same name, That was (for me) the crucial point. it is not > restored. > >>Or is it replaced, as it is different from the one in >>the backup? > > The decision is based solely on the file name. Therefore the content and > attributes of the file have no bearing on the decision. Pity. Well... :) Thanks for clarification, greets, tobi... :) > 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. > > > > > Tobias Hofmann <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 11/05/2003 09:37 > Please respond to "ADSM: Dist Stor Manager" > > To: [EMAIL PROTECTED] > cc: > Subject:Re: How does "replace=no" work? > > > Hi Andy, all, > > On 05.11.2003 16:01, Andrew Raibeck wrote: > > >>I would recommend that you consult the client manual, which includes a >>reference chapter for client options. > > > This is from ansbc550.pdf, page 194, obtained from > http://web.urz.uni-heidelberg.de/ADSM/ibmdoc.tsm51/aix/pdf/unixc/ansbc550.pd f > > , which I hope to be the correct document for the linux clients version > 5.1.1.0: > > "The replace option specifies what you want the system to do when it > restores files that already exist on your workstation. This option > applies to the restore, retrieve, and restore backupset commands only. > > [...] > > All > All existing files are overwritten, including read-only files. If access > to a file is denied, you are prompted to skip or overwrite the file. No > action is taken on the file until there is a response to the prompt. > > [This is clear to me. All files will be restored, given they are not > access protected] > > Yes > Any existing files are overwritten, except read-only files. If a file is > read-only, you are prompted to overwrite the file or skip it. No action > is taken on the file until there is a response to the prompt. If access > to a file is denied, the file is skipped. > > [This is clear to me, too] > > No > Existing files are not overwritten. No prompts will display." > > >>If, after reading the information on REPLACE you still don't understand >>it, let me know what is not clear. > > > To me, not clear is the meaning of "existing file". > > Given a file in my backup, foo.avi, with a creation and modification > date, and a size of 1 Gigabyte. > > Given a file foo.avi (same name) on my harddisk in the same location > from which the backup has been created, with the same creation date as > in the backup, but later mod-date, and a filesize of only 500Kb. > > Now I restore this file to the original location, with replace=no - what > happens? > > Does TSM not replace the file, since the "existing file" (even though > with different size, and different modification date - are there any > other criteria?) is there with the same name and in the same location? > > Or is it replaced, as it is different from the one in the backup? > > I am sorry to bother you with this, but from the docs it is not clear to > us. Thanks in advance for your time, it is very much appreciated - > > Kind regards, tobi... > > >>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. >> >> >> >> >>Tobias Hofmann <[EMAIL PROTECTED]> >>Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> >>11/05/2003 07:18 >>Please respond to "ADSM: Dist Stor Manager" >> >>To: [EMAIL PROTECTED] >>cc: >>Subject:How does "replace
Re: TDP Exchange Copy Group Definitions
Thanks Del. Now that I understand that, how about commenting on each of the copy group items in my example, supply a definition which is easily understandable, an example would suffice. I have read the redbook and I am still confused. Tom -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 12:43 PM To: [EMAIL PROTECTED] Subject: Re: TDP Exchange Copy Group Definitions Tom, First... I am assuming you are referring to Data Protection for Exchange version 2 or higher. Version 2 and higher use standard TSM policy management. (Version 1 used different policy management.) These settings basically mean that you will be able to restore any full backup for that last 90 days as long as there haven't been more than 90 different backups within that timeframe. These settings are OK... but if the intent is to keep any backup for 90 days... ... the settings should be more like this: Versions Data Exists NOLIMIT Versions Data DeletedNOLIMIT Retain Extra Versions90 Retain Only Version 90 This makes it so that no matter how many backups you take during the timespan... they won't expire earlier than 90 days. Thanks, Del > Could someone with TDP Exchange experience comment on what > the following copy group definition for TDP Exchange clients > would mean for tdp object retention? > > Versions Data Exists 90 > Versions Data Deleted 90 > Retain Extra Versions 90 > Retain Only Version 90
Re: TDP Exchange Copy Group Definitions
Tom, First... I am assuming you are referring to Data Protection for Exchange version 2 or higher. Version 2 and higher use standard TSM policy management. (Version 1 used different policy management.) These settings basically mean that you will be able to restore any full backup for that last 90 days as long as there haven't been more than 90 different backups within that timeframe. These settings are OK... but if the intent is to keep any backup for 90 days... ... the settings should be more like this: Versions Data Exists NOLIMIT Versions Data DeletedNOLIMIT Retain Extra Versions90 Retain Only Version 90 This makes it so that no matter how many backups you take during the timespan... they won't expire earlier than 90 days. Thanks, Del > Could someone with TDP Exchange experience comment on what > the following copy group definition for TDP Exchange clients > would mean for tdp object retention? > > Versions Data Exists 90 > Versions Data Deleted 90 > Retain Extra Versions 90 > Retain Only Version 90
Re: How does "replace=no" work?
Andy, On 05.11.2003 17:58, Andrew Raibeck wrote: Now I restore this file to the original location, with replace=no - what happens? Because foo.avi already exists, foo.avi is not restored. Ok, got that. Thanks! :) Does TSM not replace the file, since the "existing file" (even though with different size, and different modification date - are there any other criteria?) is there with the same name and in the same location? Correct. Because a file already exists with the same name, That was (for me) the crucial point. it is not restored. Or is it replaced, as it is different from the one in the backup? The decision is based solely on the file name. Therefore the content and attributes of the file have no bearing on the decision. Pity. Well... :) Thanks for clarification, greets, tobi... :) 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. Tobias Hofmann <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/2003 09:37 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: How does "replace=no" work? Hi Andy, all, On 05.11.2003 16:01, Andrew Raibeck wrote: I would recommend that you consult the client manual, which includes a reference chapter for client options. This is from ansbc550.pdf, page 194, obtained from http://web.urz.uni-heidelberg.de/ADSM/ibmdoc.tsm51/aix/pdf/unixc/ansbc550.pdf , which I hope to be the correct document for the linux clients version 5.1.1.0: "The replace option specifies what you want the system to do when it restores files that already exist on your workstation. This option applies to the restore, retrieve, and restore backupset commands only. [...] All All existing files are overwritten, including read-only files. If access to a file is denied, you are prompted to skip or overwrite the file. No action is taken on the file until there is a response to the prompt. [This is clear to me. All files will be restored, given they are not access protected] Yes Any existing files are overwritten, except read-only files. If a file is read-only, you are prompted to overwrite the file or skip it. No action is taken on the file until there is a response to the prompt. If access to a file is denied, the file is skipped. [This is clear to me, too] No Existing files are not overwritten. No prompts will display." If, after reading the information on REPLACE you still don't understand it, let me know what is not clear. To me, not clear is the meaning of "existing file". Given a file in my backup, foo.avi, with a creation and modification date, and a size of 1 Gigabyte. Given a file foo.avi (same name) on my harddisk in the same location from which the backup has been created, with the same creation date as in the backup, but later mod-date, and a filesize of only 500Kb. Now I restore this file to the original location, with replace=no - what happens? Does TSM not replace the file, since the "existing file" (even though with different size, and different modification date - are there any other criteria?) is there with the same name and in the same location? Or is it replaced, as it is different from the one in the backup? I am sorry to bother you with this, but from the docs it is not clear to us. Thanks in advance for your time, it is very much appreciated - Kind regards, tobi... 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. Tobias Hofmann <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/2003 07:18 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:How does "replace=no" work? Ladies, Gentlemen, following up to my (maybe confused) question yesterday, I think my question boils down to this: How does 'restore ... replace=no' work? That is, what does it take for a file to not be replaced? Is name and location already sufficient? Or does the client check for creation/modification date, size, or something like md5-hash? tia for any info on that, kind regards, tobi... :) -- -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701
Re: How does "replace=no" work?
Reading all these messages I think its clear that the client documentation has to be updated to answer all these questions from a users point of few and not to the experience of the user. replace = no story. If you try to save a file with the same name to a directory the OS will not let you, so replace=no will not restore the file; sending files with replace=no. The data is sent to the client and the client will skip the file. Regard, Karel -Oorspronkelijk bericht- Van: Thomas Denier [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 17:57 Aan: [EMAIL PROTECTED] Onderwerp: Re: How does "replace=no" work? There is a separate issue that has never been clear to me. If a file is not written to disk because of the "replace=no" option, does the TSM server refrain from reading the file from tape, or does the TSM server read the file and send it to the client, only to have the client code discard the data?
Re: Node names for TDPO
We are using a diferent tdpo.opt file with a diferent filespace on each one for diferent oracle instances. So always the same node. That is what I can tell you. If you need more details about how to make it, do not hesitate to ask for files details. Juan Manuel López. ING National Nederlanden Madrid. Spain Por favor, responda a "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Enviado por:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Destinatarios:[EMAIL PROTECTED] CC: Asunto:Node names for TDPO We have Tivoli Data Protection for Oracle running on two systems. In each case we have defined a separate node name for TDP as the documentation recommends. We are currently backing up one Oracle instance on each system but are getting ready to extend TDP coverage to additional instances. Our Database Administrators report that they are getting conflicting advice from Tivoli, sometimes being advised to use a separate node name for each instance, sometimes being advised to use a single node name and separate filespace names for the Oracle instances on a particular server, and never being given an explanation of the reasons behind either recommendation. Have other TDPO sites found it necessary or desirable to use a separate node name for each instance?
Re: How does "replace=no" work?
> To me, not clear is the meaning of "existing file". > Given a file in my backup, foo.avi, with a creation > and modification date, and a size of 1 Gigabyte. > Given a file foo.avi (same name) on my harddisk in > the same location from which the backup has been > created, with the same creation date as in the > backup, but later mod-date, and a filesize of only > 500Kb. > Now I restore this file to the original location, > with replace=no - what happens? Because foo.avi already exists, foo.avi is not restored. > Does TSM not replace the file, since the "existing > file" (even though with different size, and different > modification date - are there any other criteria?) is > there with the same name and in the same location? Correct. Because a file already exists with the same name, it is not restored. > Or is it replaced, as it is different from the one in > the backup? The decision is based solely on the file name. Therefore the content and attributes of the file have no bearing on the decision. 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. Tobias Hofmann <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/2003 09:37 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: How does "replace=no" work? Hi Andy, all, On 05.11.2003 16:01, Andrew Raibeck wrote: > I would recommend that you consult the client manual, which includes a > reference chapter for client options. This is from ansbc550.pdf, page 194, obtained from http://web.urz.uni-heidelberg.de/ADSM/ibmdoc.tsm51/aix/pdf/unixc/ansbc550.pdf , which I hope to be the correct document for the linux clients version 5.1.1.0: "The replace option specifies what you want the system to do when it restores files that already exist on your workstation. This option applies to the restore, retrieve, and restore backupset commands only. [...] All All existing files are overwritten, including read-only files. If access to a file is denied, you are prompted to skip or overwrite the file. No action is taken on the file until there is a response to the prompt. [This is clear to me. All files will be restored, given they are not access protected] Yes Any existing files are overwritten, except read-only files. If a file is read-only, you are prompted to overwrite the file or skip it. No action is taken on the file until there is a response to the prompt. If access to a file is denied, the file is skipped. [This is clear to me, too] No Existing files are not overwritten. No prompts will display." > If, after reading the information on REPLACE you still don't understand > it, let me know what is not clear. To me, not clear is the meaning of "existing file". Given a file in my backup, foo.avi, with a creation and modification date, and a size of 1 Gigabyte. Given a file foo.avi (same name) on my harddisk in the same location from which the backup has been created, with the same creation date as in the backup, but later mod-date, and a filesize of only 500Kb. Now I restore this file to the original location, with replace=no - what happens? Does TSM not replace the file, since the "existing file" (even though with different size, and different modification date - are there any other criteria?) is there with the same name and in the same location? Or is it replaced, as it is different from the one in the backup? I am sorry to bother you with this, but from the docs it is not clear to us. Thanks in advance for your time, it is very much appreciated - Kind regards, tobi... > 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. > > > > > Tobias Hofmann <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > 11/05/2003 07:18 > Please respond to "ADSM: Dist Stor Manager" > > To: [EMAIL PROTECTED] > cc: > Subject:How does "replace=no" work? > > > Ladies, Gentlemen, > > following up to my (maybe confused) question yesterday, I think my > question boils down to this: > > How does 'restore ... replace=no' work? > > That is, what does it take for a file to not be replaced? > Is name and location already sufficient? > Or does the client check for creation/modification date, size, or > something like md5-hash? > > tia for any info on that, > > kind regards, tobi... :) > > > -- > -- > Dipl.-Ing.
Re: How does "replace=no" work?
There is a separate issue that has never been clear to me. If a file is not written to disk because of the "replace=no" option, does the TSM server refrain from reading the file from tape, or does the TSM server read the file and send it to the client, only to have the client code discard the data?
Node names for TDPO
We have Tivoli Data Protection for Oracle running on two systems. In each case we have defined a separate node name for TDP as the documentation recommends. We are currently backing up one Oracle instance on each system but are getting ready to extend TDP coverage to additional instances. Our Database Administrators report that they are getting conflicting advice from Tivoli, sometimes being advised to use a separate node name for each instance, sometimes being advised to use a single node name and separate filespace names for the Oracle instances on a particular server, and never being given an explanation of the reasons behind either recommendation. Have other TDPO sites found it necessary or desirable to use a separate node name for each instance?
Re: How does "replace=no" work?
Hi Andy, all, On 05.11.2003 16:01, Andrew Raibeck wrote: I would recommend that you consult the client manual, which includes a reference chapter for client options. This is from ansbc550.pdf, page 194, obtained from http://web.urz.uni-heidelberg.de/ADSM/ibmdoc.tsm51/aix/pdf/unixc/ansbc550.pdf , which I hope to be the correct document for the linux clients version 5.1.1.0: "The replace option specifies what you want the system to do when it restores files that already exist on your workstation. This option applies to the restore, retrieve, and restore backupset commands only. [...] All All existing files are overwritten, including read-only files. If access to a file is denied, you are prompted to skip or overwrite the file. No action is taken on the file until there is a response to the prompt. [This is clear to me. All files will be restored, given they are not access protected] Yes Any existing files are overwritten, except read-only files. If a file is read-only, you are prompted to overwrite the file or skip it. No action is taken on the file until there is a response to the prompt. If access to a file is denied, the file is skipped. [This is clear to me, too] No Existing files are not overwritten. No prompts will display." If, after reading the information on REPLACE you still don't understand it, let me know what is not clear. To me, not clear is the meaning of "existing file". Given a file in my backup, foo.avi, with a creation and modification date, and a size of 1 Gigabyte. Given a file foo.avi (same name) on my harddisk in the same location from which the backup has been created, with the same creation date as in the backup, but later mod-date, and a filesize of only 500Kb. Now I restore this file to the original location, with replace=no - what happens? Does TSM not replace the file, since the "existing file" (even though with different size, and different modification date - are there any other criteria?) is there with the same name and in the same location? Or is it replaced, as it is different from the one in the backup? I am sorry to bother you with this, but from the docs it is not clear to us. Thanks in advance for your time, it is very much appreciated - Kind regards, tobi... 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. Tobias Hofmann <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/2003 07:18 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:How does "replace=no" work? Ladies, Gentlemen, following up to my (maybe confused) question yesterday, I think my question boils down to this: How does 'restore ... replace=no' work? That is, what does it take for a file to not be replaced? Is name and location already sufficient? Or does the client check for creation/modification date, size, or something like md5-hash? tia for any info on that, kind regards, tobi... :) -- -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] -- -- -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] --
Re: Upgraded Tape Drives and Scratch Tapes
Thanks to all who answered these question for me. Very much appreciated All the best Farren Minns - John Wiley & Sons Ltd |+---+| || Bill Fitzgerald || || <[EMAIL PROTECTED]> || || Sent by: "ADSM: Dist Stor | To: [EMAIL PROTECTED] | || Manager"| cc: | || <[EMAIL PROTECTED]> | Subject: Re: Upgraded | || | Tape Drives and Scratch Tapes| || 11/05/2003 04:28 PM || || Please respond to "ADSM:|| || Dist Stor Manager" || || || |+---+| actually I just did a migration from 4 3590B to 6 3590E You do not have to change access on all tapepool tapes to read-only, only the ones with the status of FILLING although doing it to the entire pool will not cause any problems. you will however have to move the data from the filling volumes to new volumes using the move data command as TSM does not reclaim space from tapes in the primary sequential pool in the filling mode. I checked out all the scratch and then checked them back in just to be safe. >>> [EMAIL PROTECTED] 11/05/03 10:14AM >>> Hi again all TSM 5.1.6.2 on Solaris 2.7 Tomorrow we are having our B1A drives upgraded to H1A (housed in a 3494 library). Once this has been done, I understand that I will need to mark all TAPEPOOL volumes as readonly (see prev post), but can I assume that I need to relable all the scratch tapes that are in the lib at present, so that they use the new formatting? Many thanks again All the best Farren Minns - John Wiley & Sons * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. * * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
Re: Upgraded Tape Drives and Scratch Tapes
actually I just did a migration from 4 3590B to 6 3590E You do not have to change access on all tapepool tapes to read-only, only the ones with the status of FILLING although doing it to the entire pool will not cause any problems. you will however have to move the data from the filling volumes to new volumes using the move data command as TSM does not reclaim space from tapes in the primary sequential pool in the filling mode. I checked out all the scratch and then checked them back in just to be safe. >>> [EMAIL PROTECTED] 11/05/03 10:14AM >>> Hi again all TSM 5.1.6.2 on Solaris 2.7 Tomorrow we are having our B1A drives upgraded to H1A (housed in a 3494 library). Once this has been done, I understand that I will need to mark all TAPEPOOL volumes as readonly (see prev post), but can I assume that I need to relable all the scratch tapes that are in the lib at present, so that they use the new formatting? Many thanks again All the best Farren Minns - John Wiley & Sons * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
Re: Query Event for Previous day shows status In Progress
Hi, Be very careful about clients in the event record recorded as "In Progress". In Progress means the back-up is still running. Because you sent your "Q SESS" output, we know that the TSM server hasn't any running back-up sessions, so someone isn't on track. I would recommend that you either take a good look at the schedule log (client side) and/or actlog (server sided) and see if the last back-up of this client was indeed that from yesterday. In the past we saw that new back-ups didn't start for clients which were in the "In Progress" state. One thing we did to minimize the number of "In Progress" clients was making the scheduler service managed by the client acceptor. The other thing was upgrading these failing client to v5.1.5.15 (still do, but there are people out there who will tell you to go to another level). Regard, Karel -Oorspronkelijk bericht- Van: James Choate [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 17:05 Aan: [EMAIL PROTECTED] Onderwerp: Re: Query Event for Previous day shows status In Progress I guess I should rephrase the question. Can someone tell me what the when I query an event what in-progress in the status column means? This isn't making much sense to me. For example, today I queried the events for my nt_backups. I queried my events for the past 3 days. The output seem to indicate that the event is still in progress. I have attached the schedule and the output from the query events, but I still don't understand what in-progress means from 2 days ago?? tsm: TSM>q event * nt_backups begind=today-3 begint=00:00 endd=today Scheduled Start Actual Start Schedule Name Node Name Status - - - 11/02/03 22:30:00 11/02/03 23:14:38 NT_BACKUPSIBS Completed 11/02/03 22:30:00 11/02/03 22:30:17 NT_BACKUPSFS_VSI Completed 11/02/03 22:30:00 11/02/03 22:30:18 NT_BACKUPSPLUS_2000 Completed 11/02/03 22:30:00 11/02/03 22:30:22 NT_BACKUPSID_CARD Completed 11/02/03 22:30:00 11/02/03 22:30:26 NT_BACKUPSFS_DEVII Completed 11/02/03 22:30:00 NT_BACKUPSFIRSTPLACEMissed 11/02/03 22:30:00 11/02/03 22:40:30 NT_BACKUPSPOWERFAIDS Completed 11/02/03 22:30:00 11/02/03 22:30:16 NT_BACKUPSTPG Completed 11/02/03 22:30:00 11/02/03 22:30:14 NT_BACKUPSFS_VSJ Completed 11/02/03 22:30:00 11/02/03 22:30:15 NT_BACKUPSFS-HEAT Completed 11/02/03 22:30:00 11/02/03 22:30:11 NT_BACKUPSFS-LIB Completed 11/02/03 22:30:00 11/02/03 22:30:12 NT_BACKUPSTNVOICE Completed 11/02/03 22:30:00 11/02/03 22:30:08 NT_BACKUPSFS_ACT Completed 11/02/03 22:30:00 11/02/03 23:02:55 NT_BACKUPSMERLIN2 Completed 11/02/03 22:30:00 11/02/03 22:30:07 NT_BACKUPSMERCYWEBSRV Completed 11/02/03 22:30:00 11/02/03 22:43:10 NT_BACKUPSW2KDC Completed 11/02/03 22:30:00 NT_BACKUPSW2K-GC1 Missed 11/02/03 22:30:00 11/02/03 22:30:02 NT_BACKUPSFS-XTD Completed 11/03/03 22:30:00 11/03/03 22:45:00 NT_BACKUPSIBS In Progr- ess 11/03/03 22:30:00 11/04/03 00:18:12 NT_BACKUPSFS_VSI Completed 11/03/03 22:30:00 11/03/03 22:30:41 NT_BACKUPSPLUS_2000 In Progr- ess 11/03/03 22:30:00 11/04/03 00:15:34 NT_BACKUPSID_CARD Completed 11/03/03 22:30:00 11/04/03 00:16:36 NT_BACKUPSFS_DEVII Completed 11/03/03 22:30:00 NT_BACKUPSFIRSTPLACEMissed 11/03/03 22:30:00 11/04/03 00:15:41 NT_BACKUPSPOWERFAIDS Completed 11/03/03 22:30:00 11/04/03 00:15:44 NT_BACKUPSTPG Completed 11/03/03 22:30:00 11/04/03 00:17:13 NT_BACKUPSFS_VSJ Completed 11/03/03 22:30:00 11/04/03 00:16:42 NT_BACKUPSFS-HEAT Completed 11/03/03 22:30:00 11/03/03 22:30:33 NT_BACKUPSFS-LIBIn Progr- ess 11/03/03 22:30:00 11/04/03 00:07:09 NT_BACKUPSTNVOICE Completed 11/03/03 22:30:00 11/04/03 00:16:34 NT_BACKUPSFS_ACT Completed 11/03/03 22:30:00 11/03/03 23:16:54 NT_BACKUPSMERLIN2 In Progr- ess 11/03/03 22:30:00 11/03/03 22:40:38 NT_BACKUPSMERCYWEBSRV In Progr- ess 11/03/03 22:30:00 11/04/03 00:28:27 NT_BACKUPSW2KDC Completed 11/03/03 22:30:00 NT_BACKUPSW2K-GC1 Missed 11/03/03 22:30:00 11/04/03 00:15:36 NT_BACKUPSFS-XTD Completed 11/04/03 22:30:00 NT_BACKUPSIBS Missed 11/04/03 22:30:00 11/04/03 22:30:37 NT_BACKUPSFS_VSI Comple
Re: Query Event for Previous day shows status In Progress
I guess I should rephrase the question. Can someone tell me what the when I query an event what in-progress in the status column means? This isn't making much sense to me. For example, today I queried the events for my nt_backups. I queried my events for the past 3 days. The output seem to indicate that the event is still in progress. I have attached the schedule and the output from the query events, but I still don't understand what in-progress means from 2 days ago?? tsm: TSM>q event * nt_backups begind=today-3 begint=00:00 endd=today Scheduled Start Actual Start Schedule Name Node Name Status - - - 11/02/03 22:30:00 11/02/03 23:14:38 NT_BACKUPSIBS Completed 11/02/03 22:30:00 11/02/03 22:30:17 NT_BACKUPSFS_VSICompleted 11/02/03 22:30:00 11/02/03 22:30:18 NT_BACKUPSPLUS_2000 Completed 11/02/03 22:30:00 11/02/03 22:30:22 NT_BACKUPSID_CARD Completed 11/02/03 22:30:00 11/02/03 22:30:26 NT_BACKUPSFS_DEVII Completed 11/02/03 22:30:00 NT_BACKUPSFIRSTPLACEMissed 11/02/03 22:30:00 11/02/03 22:40:30 NT_BACKUPSPOWERFAIDSCompleted 11/02/03 22:30:00 11/02/03 22:30:16 NT_BACKUPSTPG Completed 11/02/03 22:30:00 11/02/03 22:30:14 NT_BACKUPSFS_VSJCompleted 11/02/03 22:30:00 11/02/03 22:30:15 NT_BACKUPSFS-HEAT Completed 11/02/03 22:30:00 11/02/03 22:30:11 NT_BACKUPSFS-LIBCompleted 11/02/03 22:30:00 11/02/03 22:30:12 NT_BACKUPSTNVOICE Completed 11/02/03 22:30:00 11/02/03 22:30:08 NT_BACKUPSFS_ACTCompleted 11/02/03 22:30:00 11/02/03 23:02:55 NT_BACKUPSMERLIN2 Completed 11/02/03 22:30:00 11/02/03 22:30:07 NT_BACKUPSMERCYWEBSRV Completed 11/02/03 22:30:00 11/02/03 22:43:10 NT_BACKUPSW2KDC Completed 11/02/03 22:30:00 NT_BACKUPSW2K-GC1 Missed 11/02/03 22:30:00 11/02/03 22:30:02 NT_BACKUPSFS-XTDCompleted 11/03/03 22:30:00 11/03/03 22:45:00 NT_BACKUPSIBS In Progr- ess 11/03/03 22:30:00 11/04/03 00:18:12 NT_BACKUPSFS_VSICompleted 11/03/03 22:30:00 11/03/03 22:30:41 NT_BACKUPSPLUS_2000 In Progr- ess 11/03/03 22:30:00 11/04/03 00:15:34 NT_BACKUPSID_CARD Completed 11/03/03 22:30:00 11/04/03 00:16:36 NT_BACKUPSFS_DEVII Completed 11/03/03 22:30:00 NT_BACKUPSFIRSTPLACEMissed 11/03/03 22:30:00 11/04/03 00:15:41 NT_BACKUPSPOWERFAIDSCompleted 11/03/03 22:30:00 11/04/03 00:15:44 NT_BACKUPSTPG Completed 11/03/03 22:30:00 11/04/03 00:17:13 NT_BACKUPSFS_VSJCompleted 11/03/03 22:30:00 11/04/03 00:16:42 NT_BACKUPSFS-HEAT Completed 11/03/03 22:30:00 11/03/03 22:30:33 NT_BACKUPSFS-LIBIn Progr- ess 11/03/03 22:30:00 11/04/03 00:07:09 NT_BACKUPSTNVOICE Completed 11/03/03 22:30:00 11/04/03 00:16:34 NT_BACKUPSFS_ACTCompleted 11/03/03 22:30:00 11/03/03 23:16:54 NT_BACKUPSMERLIN2 In Progr- ess 11/03/03 22:30:00 11/03/03 22:40:38 NT_BACKUPSMERCYWEBSRV In Progr- ess 11/03/03 22:30:00 11/04/03 00:28:27 NT_BACKUPSW2KDC Completed 11/03/03 22:30:00 NT_BACKUPSW2K-GC1 Missed 11/03/03 22:30:00 11/04/03 00:15:36 NT_BACKUPSFS-XTDCompleted 11/04/03 22:30:00 NT_BACKUPSIBS Missed 11/04/03 22:30:00 11/04/03 22:30:37 NT_BACKUPSFS_VSICompleted 11/04/03 22:30:00 NT_BACKUPSPLUS_2000 Missed 11/04/03 22:30:00 11/04/03 22:30:38 NT_BACKUPSID_CARD Completed 11/04/03 22:30:00 11/04/03 22:30:39 NT_BACKUPSFS_DEVII Completed 11/04/03 22:30:00 NT_BACKUPSFIRSTPLACEMissed 11/04/03 22:30:00 11/04/03 22:30:34 NT_BACKUPSPOWERFAIDSCompleted 11/04/03 22:30:00 11/04/03 22:30:32 NT_BACKUPSTPG Completed 11/04/03 22:30:00 11/04/03 22:40:44 NT_BACKUPSFS_VSJCompleted 11/04/03 22:30:00 11/04/03 22:30:30 NT_BACKUPSFS-HEAT Completed 11/04/03 22:30:00 NT_BACKUPSFS-LIBMissed 11/04/03 22:30:00 11/04/03 22:30:34 NT_BACKUPSTNVOICE Completed 11/04/03 22:30:00 11/04/03 22:
Antwort: Re: Antwort: Re: ANR4391I during expiration
Hi *, o.k. when this is normal with the new version I will change also the parameter! >Reclamation once every hour??? Nice that you can, but why? You are right. This is very often and I reduce it to 1 per day. The library on this server has only few volumes, therefore I must often create place. Thanks for your help! Regard, Frank Karel Bos <[EMAIL PROTECTED]An: [EMAIL PROTECTED] OM> Kopie: Gesendet von:Thema:Re: Antwort: Re: ANR4391I during expiration "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 05.11.2003 16:33 Bitte antworten an "ADSM: Dist Stor Manager" Hi, This was some of the things that changes in one of the upgrades, and one of the reasons we turned detailed off... Regard, Karel ps Reclamation once every hour??? Nice that you can, but why? -Oorspronkelijk bericht- Van: Frank Mueller [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 16:08 Aan: [EMAIL PROTECTED] Onderwerp: Antwort: Re: ANR4391I during expiration Hi Karel, thanks for your answer. The problem is not the detailed output, but the number of entries in the log. The option was on both server on detaillet. But I did not see ever so many same entries before. The expiration runs on this server 1 x hour and I get 1 message per expiration in the log. But after the update I get > 30 messages per second. Here for and after the update: tsm: ADSM_OERAG02>q act begind=-2 search=ANR4391I Date/TimeMessage -- 11/03/03 15:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 16:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 17:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . after update: 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . Best regards, Frank Mueller Karel Bos <[EMAIL PROTECTED]An: [EMAIL PROTECTED] OM> Kopie: Gesendet von:Thema:Re: ANR4391I during expiration "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 05.11.2003 15:36 Bitte antworte
Re: Exchange 2003
Hi, TSM supports Exchange 2003 as of TDP Mail for Exchange 5.2.1 which is avaiable electronically (I haven't gotten my cd yet). We have it installed, and have tested everything short of a complete disaster recovery. Michael Wheelock Integris Health of Oklahoma -Original Message- From: Mark Mooney [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 9:58 AM To: [EMAIL PROTECTED] Subject: Re: Exchange 2003 Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 > Does TSM support Exchange 2003 yet? > > Thanks > > > > Mehdi Amini > LAN/WAN Engineer > ValueOptions > 12369 Sunrise Valley Drive > Suite C > Reston, VA 20191 > Phone: 703-390-6855 > Fax: 703-390-2581 > ** 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 sender by email, delete and destroy this message and its attachments. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Exchange 2003
It will, if you use the correct TDP version: Software Requirements - Data Protection for Microsoft Exchange version 5.2.1 requires the following MINIMUM software levels: - Microsoft Windows NT Server SP5 Microsoft Windows 2000 Server SP3 Microsoft Windows Server 2003 - Microsoft Exchange Server 5.5 SP3 Microsoft Exchange 2000 Server SP2 Microsoft Exchange 2003 Server - IBM Tivoli Storage Manager API 5.1.5 - IBM Tivoli Storage Manager Server 5.1 IBM Tivoli Storage Manager Server does not have to be on the same machine as Data Protection for Exchange and may be on any platform supported by IBM Tivoli Storage Manager Server. - IBM Tivoli Storage Manager Backup-Archive Client 5.1 Required only if the central scheduler service of the IBM Tivoli Storage Manager Backup-Archive Client will be used. If so, the Backup-Archive Client must reside on the same machine as Data Protection for Exchange. - Microsoft Internet Explorer V4.01 The Online Information (User's Guide, and links to Web sites) requires this support. For the web links to work in Online Information, Internet Explorer needs to be configured to access the Internet. -Oorspronkelijk bericht- Van: Amini, Mehdi [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 16:33 Aan: [EMAIL PROTECTED] Onderwerp: Exchange 2003 > Does TSM support Exchange 2003 yet? > > Thanks > > > > Mehdi Amini > LAN/WAN Engineer > ValueOptions > 12369 Sunrise Valley Drive > Suite C > Reston, VA 20191 > Phone: 703-390-6855 > Fax: 703-390-2581 > ** 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 sender by email, delete and destroy this message and its attachments. **
Re: Exchange 2003
Not that I'm aware of. We're waiting for this as well because we moved from 2000 to 2003 and the TDP no longer functions. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Amini, Mehdi Sent: Wednesday, November 05, 2003 09:33 To: [EMAIL PROTECTED] Subject: Exchange 2003 > Does TSM support Exchange 2003 yet? > > Thanks > > > > Mehdi Amini > LAN/WAN Engineer > ValueOptions > 12369 Sunrise Valley Drive > Suite C > Reston, VA 20191 > Phone: 703-390-6855 > Fax: 703-390-2581 > ** 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 sender by email, delete and destroy this message and its attachments. **
Exchange 2003
> Does TSM support Exchange 2003 yet? > > Thanks > > > > Mehdi Amini > LAN/WAN Engineer > ValueOptions > 12369 Sunrise Valley Drive > Suite C > Reston, VA 20191 > Phone: 703-390-6855 > Fax: 703-390-2581 > ** 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 sender by email, delete and destroy this message and its attachments. **
TDP Exchange Copy Group Definitions
Could someone with TDP Exchange experience comment on what the following copy group definition for TDP Exchange clients would mean for tdp object retention? Versions Data Exists 90 Versions Data Deleted 90 Retain Extra Versions 90 Retain Only Version 90 Thanks. Tom Thomas L. Fought (E-mail).vcf Description: Binary data
Re: Antwort: Re: ANR4391I during expiration
Hi, This was some of the things that changes in one of the upgrades, and one of the reasons we turned detailed off... Regard, Karel ps Reclamation once every hour??? Nice that you can, but why? -Oorspronkelijk bericht- Van: Frank Mueller [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 16:08 Aan: [EMAIL PROTECTED] Onderwerp: Antwort: Re: ANR4391I during expiration Hi Karel, thanks for your answer. The problem is not the detailed output, but the number of entries in the log. The option was on both server on detaillet. But I did not see ever so many same entries before. The expiration runs on this server 1 x hour and I get 1 message per expiration in the log. But after the update I get > 30 messages per second. Here for and after the update: tsm: ADSM_OERAG02>q act begind=-2 search=ANR4391I Date/TimeMessage -- 11/03/03 15:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 16:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 17:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . after update: 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . Best regards, Frank Mueller Karel Bos <[EMAIL PROTECTED]An: [EMAIL PROTECTED] OM> Kopie: Gesendet von:Thema:Re: ANR4391I during expiration "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 05.11.2003 15:36 Bitte antworten an "ADSM: Dist Stor Manager" Expiration is running without the quiet option. When scheduled update the command by adding quiet=yes, else modify the dsmserv.opt. Regard, Karel -Oorspronkelijk bericht- Van: Frank Mueller [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 15:12 Aan: [EMAIL PROTECTED] Onderwerp: ANR4391I during expiration Hi *, we have 2 TSM-Server runs on 2 x AIX-nodes (AIX 4.3.3). Both server runs with 4.2.2.6 (I know, no support, but I want now migrate to TSM 5.1). So I update the first server to Version TSM 4.2.4.0 Now (after the update) I observe many many entries during a expiration on this server with the same contents: 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and
Re: Include/exclude not working
Lan, In general, DOMAIN is used to specify drives or special objects such as the system objects, system services, etc. Since \\nodename\g$\inetpub is most likely a directory, not a drive or share name, it is not a valid DOMAIN item. As I mentioned before, I would recommend that you read the client manual to gain a better understanding of the TSM client. Check out the chapter that describes the client options, and look up the DOMAIN statement. If you want to back up only the inetpub directory (and its files and subdirectories), you have several options: 1) Use the GUI backup function, navigate to the desired directory, click the checkbox to the left of the directory name, then back it up. 2) From an OS prompt, run: dsmc i g:\inetpub\ -subdir=yes 3) Define a schedule on the server where ACTION=INCREMENTAL, OBJECTS="g:\inetpub\", and OPTIONS="-subdir=yes". 4) I suppose you could define a network share that points to the inetpub directory, perhaps something like the following: net share inetpub=g:\inetpub Then in the options file you could have a DOMAIN statement like this: domain \\nodename\inetpub (where "nodename" is the machine name, i.e. \\nodename\inetpub is the UNC name for the share) Then a regular incremental backup will back up only the files and directories in that share. Note that the account used to back up the share must have access to network resources (LocalSystem typically does not have such access). 5) Another method would be to specify the following in your options file: domain g: exclude *:\...\* include g:\inetpub\...\* This will cause all *directories* in G: to be traversed and backed up, but only the *files* in g:\inetpub and its subdirectories will be backed up. 5) If the method in #4 is inadequate for your needs; for example, if there is a very large number of files and directories on G: making a traversal of the entire file system too time-consuming, then consider methods #1, #2, #3, and/or #4. Also see my post to Eric on 31 October 2003 for additional hints on configuring include, exclude, and exclude.dir. 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. Lan Wu-Cavener <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/04/2003 11:38 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Include/exclude not working Hi, Can you define a domain as DOMAIN: "\\nodename\g$\inetpub\ ,then only backup this domain? Lan At 08:07 AM 10/31/2003 -0700, you wrote: > > This is exactly what I asked about yesterday, > > but it seems that no one yesterday knew what > > I was asking for > >Well, I tried (yesterday)... in fact, what you wrote below looks similar >to what I suggested. :-) > > > Whats better then doing all those lines you > > can have the following in your dsm.opt and it > > will ONLY backup ONE directory > > > domain g: > > exclude *:\...\* > > include g:\inetpub\* > > > This will only backup g:\inetpub\ and all files > > and subdirs. > >Not quite... > >INCLUDE and EXCLUDE operate on files but not directories. So while your >approach above will back up only the *files* under g:\inetpub, as I >mentioned yesterday, it will also traverse and back up (if appropriate) >the other directories on g:. While it technically will work okay, Eric was >looking for a way to have TSM traverse *only* the g:\inetpub directory >structure. > >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. > > > > >"Blodgett, Olin" <[EMAIL PROTECTED]> >Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> >10/31/2003 07:37 >Please respond to "ADSM: Dist Stor Manager" > > To: [EMAIL PROTECTED] > cc: > Subject:Re: Include/exclude not working > > >This is exactly what I asked about yesterday, but it seems that no one >yesterday knew what I was asking for, Whats better then doing all those >lines you can have the following in your dsm.opt and it will ONLY backup >ONE >directory > >domain g: >exclude *:\...\* >include g:\inetpub\* > >This will only backup g:\inetpub\ and all files and subdirs. For me g: is >a >network drive. I have not tested this on local file systems. Side note ALL >other files on the computer WILL NOT be backed up, BUT if you just add >more >include lines then you can have several directories that will get backed >up. > > >Hi *SM-ers! > >I must be doing something wrong.
Re: Upgraded Tape Drives and Scratch Tapes
In the past when I went from B1A to E1A: besides marking all the private tapes READO, I also Deleted all the scratch tapes and put them back into category FF00 and then followed up with a LABEL LIBV. Other people have claimed this isn't neccessary. I figure why guess? Better to know. Regards, Al Barth Farren Minns <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/03 09:14 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Upgraded Tape Drives and Scratch Tapes Hi again all TSM 5.1.6.2 on Solaris 2.7 Tomorrow we are having our B1A drives upgraded to H1A (housed in a 3494 library). Once this has been done, I understand that I will need to mark all TAPEPOOL volumes as readonly (see prev post), but can I assume that I need to relable all the scratch tapes that are in the lib at present, so that they use the new formatting? Many thanks again All the best Farren Minns - John Wiley & Sons * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
Re: How to mark all TAPEPOOL volumes read only
Or.. (if your storage pool name is TAPEPOOL, then) update volume * access=readonly wherestgpool=tapepool goran <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/2003 09:16 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Fax to: Subject:Re: How to mark all TAPEPOOL volumes read only update volume _volume_name acc=reado - Original Message - From: "Farren Minns" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 05, 2003 4:08 PM Subject: How to mark all TAPEPOOL volumes read only > Hi TSMers > > TSM 5.1.6.2 on Solaris 2.7 > > What's the best way to make all tapes in our TAPEPOOL read-only. I don't > want the TAPEPOOL itself read-only, just the volumes it's using at present. > Then it can start using new scratch tapes from now on. > > Thanks > > Farren Minns - John Wiley & Sons Ltd > * > > This email transmission is confidential and intended for the person or > organisation it is addressed to. If you are not the intended recipient, you > must not copy, distribute, or disseminate the information, open any > attachment, or take any action in reliance of it. If you have received this > message in error please notify the sender. > > Any views expressed in this message are those of the individual sender, > except where the sender specifically states otherwise. > > Although this email has been scanned for viruses you should rely on your > own virus check, as the sender takes no responsibility for any damage > arising out of any bug or virus infection. > *
Re: Damaged volume
>The following is the proper (and only) method to restore a damaged volume: > >1. Run UPDATE VOLUME 100ABN ACCESS=DESTROYED. This will enable step #2. >2. Run RESTORE VOLUME 100ABN PREVIEW=YES. Review the results in the activity log to get the >names of the copy pool volumes required to rebuild the volume. >3. Have those copy pool volumes brought onsite and check them into the library as private >volumes. >4. Run RESTORE VOLUME 100ABN. When the restore completes, volume 100ABN will become a >scratch tape. Pitch it. > >You're done. > Well not quite done. Then you need to mark the copy pool volumes for offiste again, eject them, and take them back to the vault. David
Re: Z/OS and TSM - preferred server level??
Jim, I didn't recognize that you are at 4.1. I think theres no problem with the upgrade for you, because the problems we had were with the systemobjects of windows nodes which were included with 4.2. Our migrations: 3.7 --> 4.1.3 --> 4.1.5 --> 5.1.0.0 --> 5.1.1.6 --> 5.1.5.0 --> 5.1.5.3 --> 5.1.6.1 ---> 5.1.6.3 and now we are migrating to 5.2.1.1 I think our problems with the systemobjects occured somewhere during migration from 4.1.5 to 5.1.6.3. -- mit freundlichen Grüßen Joachim Stumpf - Original-Nachricht folgt - Joachim, Thanks, I remember seeing something about this earlier. I wonder if it applies, though, as we are moving from 4.1.x and the problem description specifically references 4.2 and 5.1 >From what release did you jump to 5.1.6? "Stumpf, Joachim" wrote: > > Hi, > > at the moment we are migrating from 5.1.6.3 to 5.2.1.1. > If you are at 4.x you should have a look at: > http://www-1.ibm.com/support/docview.wss?uid=swg1PQ80211 > > We had big problems with the performance during upgradedb (AuditDB run 80h with a > 16GB database and used over 65h CPU). > After the ZAP the Upgradedb took nearly 30min and used 3min. CPU. > > So the ZAP mentioned in the ARPAR worked for us. > > Good Luck ;-) > > -- > mit freundlichen Grüßen / regards > Joachim Stumpf > > > - Original-Nachricht folgt - > > We are closing in on bringing up Z/OS 1.4 and with it a new version of > TSM server. It looks like 5.1.7 was delivered with our server pac (FMID > HDN5510). In a meeting earlier this week a Tivoli rep recommended that > we go ahead and pull down the latest server level (5.2.1 w/5.2.2 due in > early Dec.) > > Any recommendations or experiences with this platform and TSM levels out > there worth passing along? We're currently at 4.1.4.2 > > As always, thanks in advance! > > -- > Jim Kirkman > AIS - Systems > UNC-Chapel Hill > 966-5884 -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: How to mark all TAPEPOOL volumes read only
this will do it: upd vol * wherestg=TAPEPOOL acc=reado Regards, Al Barth t-14 days Farren Minns <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/03 09:08 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:How to mark all TAPEPOOL volumes read only Hi TSMers TSM 5.1.6.2 on Solaris 2.7 What's the best way to make all tapes in our TAPEPOOL read-only. I don't want the TAPEPOOL itself read-only, just the volumes it's using at present. Then it can start using new scratch tapes from now on. Thanks Farren Minns - John Wiley & Sons Ltd * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
Re: Antwort: Re: ANR4391I during expiration
i think that this is the feature of new version ... - Original Message - From: "Frank Mueller" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 05, 2003 4:08 PM Subject: Antwort: Re: ANR4391I during expiration > Hi Karel, > > thanks for your answer. > > > The problem is not the detailed output, but the number of entries in the > log. The option was on both server on detaillet. > But I did not see ever so many same entries before. > The expiration runs on this server 1 x hour and I get 1 message per > expiration in the log. But after the update I get > 30 messages per second. > > Here for and after the update: > > tsm: ADSM_OERAG02>q act begind=-2 search=ANR4391I > > Date/TimeMessage > > -- > 11/03/03 15:00:26 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > 11/03/03 16:00:26 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > 11/03/03 17:00:26 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > . > . > . > . > . > . > after update: > > 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.SERVER, fsId 1, domain TSMSERVER, > and > management class MC_TSMSERVER - for ARCHIVE type > files. > > . > . > . > . > . > . > > > Best regards, > Frank Mueller > > > > > Karel Bos > <[EMAIL PROTECTED]An: [EMAIL PROTECTED] > OM> Kopie: > Gesendet von:Thema:Re: ANR4391I during expiration > "ADSM: Dist Stor > Manager" > <[EMAIL PROTECTED] > .EDU> > > > 05.11.2003 15:36 > Bitte antworten > an "ADSM: Dist > Stor Manager" > > > > > > > Expiration is running without the quiet option. When scheduled update the > command by adding quiet=yes, else modify the dsmserv.opt. > > Regard, > > Karel > > > -Oorspronkelijk bericht- > Van: Frank Mueller [mailto:[EMAIL PROTECTED] > Verzonden: woensdag 5 november 2003 15:12 > Aan: [EMAIL PROTECTED] > Onderwerp: ANR4391I during expiration > > > Hi *, > > we have 2 TSM-Server runs on 2 x AIX-nodes (AIX 4.3.3). Both server runs > with 4.2.2.6 (I know, no support, but I want now migrate to TSM 5.1). > > So I update the first server to Version TSM 4.2.4.0 > > Now (after the update) I observe many many entries during a expiration on > this server with the same contents: > > 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, > filespace ADSM.
Upgraded Tape Drives and Scratch Tapes
Hi again all TSM 5.1.6.2 on Solaris 2.7 Tomorrow we are having our B1A drives upgraded to H1A (housed in a 3494 library). Once this has been done, I understand that I will need to mark all TAPEPOOL volumes as readonly (see prev post), but can I assume that I need to relable all the scratch tapes that are in the lib at present, so that they use the new formatting? Many thanks again All the best Farren Minns - John Wiley & Sons * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
Re: How to mark all TAPEPOOL volumes read only
update volume _volume_name acc=reado - Original Message - From: "Farren Minns" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 05, 2003 4:08 PM Subject: How to mark all TAPEPOOL volumes read only > Hi TSMers > > TSM 5.1.6.2 on Solaris 2.7 > > What's the best way to make all tapes in our TAPEPOOL read-only. I don't > want the TAPEPOOL itself read-only, just the volumes it's using at present. > Then it can start using new scratch tapes from now on. > > Thanks > > Farren Minns - John Wiley & Sons Ltd > * > > This email transmission is confidential and intended for the person or > organisation it is addressed to. If you are not the intended recipient, you > must not copy, distribute, or disseminate the information, open any > attachment, or take any action in reliance of it. If you have received this > message in error please notify the sender. > > Any views expressed in this message are those of the individual sender, > except where the sender specifically states otherwise. > > Although this email has been scanned for viruses you should rely on your > own virus check, as the sender takes no responsibility for any damage > arising out of any bug or virus infection. > *
Antwort: Re: ANR4391I during expiration
Hi Karel, thanks for your answer. The problem is not the detailed output, but the number of entries in the log. The option was on both server on detaillet. But I did not see ever so many same entries before. The expiration runs on this server 1 x hour and I get 1 message per expiration in the log. But after the update I get > 30 messages per second. Here for and after the update: tsm: ADSM_OERAG02>q act begind=-2 search=ANR4391I Date/TimeMessage -- 11/03/03 15:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 16:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/03/03 17:00:26 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . after update: 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:07 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. . . . . . . Best regards, Frank Mueller Karel Bos <[EMAIL PROTECTED]An: [EMAIL PROTECTED] OM> Kopie: Gesendet von:Thema:Re: ANR4391I during expiration "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 05.11.2003 15:36 Bitte antworten an "ADSM: Dist Stor Manager" Expiration is running without the quiet option. When scheduled update the command by adding quiet=yes, else modify the dsmserv.opt. Regard, Karel -Oorspronkelijk bericht- Van: Frank Mueller [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 15:12 Aan: [EMAIL PROTECTED] Onderwerp: ANR4391I during expiration Hi *, we have 2 TSM-Server runs on 2 x AIX-nodes (AIX 4.3.3). Both server runs with 4.2.2.6 (I know, no support, but I want now migrate to TSM 5.1). So I update the first server to Version TSM 4.2.4.0 Now (after the update) I observe many many entries during a expiration on this server with the same contents: 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. What is t
How to mark all TAPEPOOL volumes read only
Hi TSMers TSM 5.1.6.2 on Solaris 2.7 What's the best way to make all tapes in our TAPEPOOL read-only. I don't want the TAPEPOOL itself read-only, just the volumes it's using at present. Then it can start using new scratch tapes from now on. Thanks Farren Minns - John Wiley & Sons Ltd * This email transmission is confidential and intended for the person or organisation it is addressed to. If you are not the intended recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance of it. If you have received this message in error please notify the sender. Any views expressed in this message are those of the individual sender, except where the sender specifically states otherwise. Although this email has been scanned for viruses you should rely on your own virus check, as the sender takes no responsibility for any damage arising out of any bug or virus infection. *
Re: Problem with Expire Inventory.
On Wed, 5 Nov 2003 12:58:36 -0200 Jorge Martins <[EMAIL PROTECTED]> wrote: > Hi, folks. > > I'm having a trouble with TSM Version 5, Release 1, Level 1.0 > > Whem I run Expire inventory, I received the following message: > > 11/04/2003 07:00:10 ANR0106E imarqry.c(4633): Unexpected error 2 > fetching row >in table "Archive.Descriptions". > > 11/04/2003 07:00:10 ANR0104E imarins.c(1503): Error 2 deleting row from > table >"Archive.Descriptions". > > I saw a possible solution that will be run a DB Fix (auditdb fix=yes) and > clean the table entries (clean archdir), but the problem stays over > > How can I repair my database ??? > call tsm support... They have found marvellous solutions to repair my db once, and it didn't even include an audit > Hugs for everybody !!! > > Jorge Martins > > > _ > Quer ajudar o Brasil e nco sabe como? > AjudaBrasil: http://www.ajudabrasil.org/mail.html. -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
Re: How does "replace=no" work?
I would recommend that you consult the client manual, which includes a reference chapter for client options. If, after reading the information on REPLACE you still don't understand it, let me know what is not clear. 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. Tobias Hofmann <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/05/2003 07:18 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:How does "replace=no" work? Ladies, Gentlemen, following up to my (maybe confused) question yesterday, I think my question boils down to this: How does 'restore ... replace=no' work? That is, what does it take for a file to not be replaced? Is name and location already sufficient? Or does the client check for creation/modification date, size, or something like md5-hash? tia for any info on that, kind regards, tobi... :) -- -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] --
Re: How to stop tape from being ejected?
Try increasing the mount retention parameter on your device class. I don't think it'll affect the behavior after a label operation though. Mooney -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ochani Sent: Tuesday, November 04, 2003 19:40 To: [EMAIL PROTECTED] Subject: How to stop tape from being ejected? Hello, I'm running tsm 5.1 on sun solaris 8 with a DDS4 tape drive. After any tape operation such as labeling a tape or a backup the tape is ejected, and I have to go back to the server room to put the tape back in. Anyway to configure the software to stop ejecting the tape? Thanks
Problem with Expire Inventory.
Hi, folks. I'm having a trouble with TSM Version 5, Release 1, Level 1.0 Whem I run Expire inventory, I received the following message: 11/04/2003 07:00:10 ANR0106E imarqry.c(4633): Unexpected error 2 fetching row in table "Archive.Descriptions". 11/04/2003 07:00:10 ANR0104E imarins.c(1503): Error 2 deleting row from table "Archive.Descriptions". I saw a possible solution that will be run a DB Fix (auditdb fix=yes) and clean the table entries (clean archdir), but the problem stays over How can I repair my database ??? Hugs for everybody !!! Jorge Martins _ Quer ajudar o Brasil e nco sabe como? AjudaBrasil: http://www.ajudabrasil.org/mail.html.
Re: Z/OS and TSM - preferred server level??
Joachim, Thanks, I remember seeing something about this earlier. I wonder if it applies, though, as we are moving from 4.1.x and the problem description specifically references 4.2 and 5.1 >From what release did you jump to 5.1.6? "Stumpf, Joachim" wrote: > > Hi, > > at the moment we are migrating from 5.1.6.3 to 5.2.1.1. > If you are at 4.x you should have a look at: > http://www-1.ibm.com/support/docview.wss?uid=swg1PQ80211 > > We had big problems with the performance during upgradedb (AuditDB run 80h with a > 16GB database and used over 65h CPU). > After the ZAP the Upgradedb took nearly 30min and used 3min. CPU. > > So the ZAP mentioned in the ARPAR worked for us. > > Good Luck ;-) > > -- > mit freundlichen Grüßen / regards > Joachim Stumpf > > > - Original-Nachricht folgt - > > We are closing in on bringing up Z/OS 1.4 and with it a new version of > TSM server. It looks like 5.1.7 was delivered with our server pac (FMID > HDN5510). In a meeting earlier this week a Tivoli rep recommended that > we go ahead and pull down the latest server level (5.2.1 w/5.2.2 due in > early Dec.) > > Any recommendations or experiences with this platform and TSM levels out > there worth passing along? We're currently at 4.1.4.2 > > As always, thanks in advance! > > -- > Jim Kirkman > AIS - Systems > UNC-Chapel Hill > 966-5884 -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: ANR4391I during expiration
Expiration is running without the quiet option. When scheduled update the command by adding quiet=yes, else modify the dsmserv.opt. Regard, Karel -Oorspronkelijk bericht- Van: Frank Mueller [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 15:12 Aan: [EMAIL PROTECTED] Onderwerp: ANR4391I during expiration Hi *, we have 2 TSM-Server runs on 2 x AIX-nodes (AIX 4.3.3). Both server runs with 4.2.2.6 (I know, no support, but I want now migrate to TSM 5.1). So I update the first server to Version TSM 4.2.4.0 Now (after the update) I observe many many entries during a expiration on this server with the same contents: 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. What is the reason for this? What can I do now? Best regards, Frank Mueller
Re: Z/OS and TSM - preferred server level??
Hi, at the moment we are migrating from 5.1.6.3 to 5.2.1.1. If you are at 4.x you should have a look at: http://www-1.ibm.com/support/docview.wss?uid=swg1PQ80211 We had big problems with the performance during upgradedb (AuditDB run 80h with a 16GB database and used over 65h CPU). After the ZAP the Upgradedb took nearly 30min and used 3min. CPU. So the ZAP mentioned in the ARPAR worked for us. Good Luck ;-) -- mit freundlichen Grüßen / regards Joachim Stumpf - Original-Nachricht folgt - We are closing in on bringing up Z/OS 1.4 and with it a new version of TSM server. It looks like 5.1.7 was delivered with our server pac (FMID HDN5510). In a meeting earlier this week a Tivoli rep recommended that we go ahead and pull down the latest server level (5.2.1 w/5.2.2 due in early Dec.) Any recommendations or experiences with this platform and TSM levels out there worth passing along? We're currently at 4.1.4.2 As always, thanks in advance! -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
ANR4391I during expiration
Hi *, we have 2 TSM-Server runs on 2 x AIX-nodes (AIX 4.3.3). Both server runs with 4.2.2.6 (I know, no support, but I want now migrate to TSM 5.1). So I update the first server to Version TSM 4.2.4.0 Now (after the update) I observe many many entries during a expiration on this server with the same contents: 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. 11/04/03 17:00:05 ANR4391I Expiration processing node ADSM_OERAG01, filespace ADSM.SERVER, fsId 1, domain TSMSERVER, and management class MC_TSMSERVER - for ARCHIVE type files. What is the reason for this? What can I do now? Best regards, Frank Mueller
How does "replace=no" work?
Ladies, Gentlemen, following up to my (maybe confused) question yesterday, I think my question boils down to this: How does 'restore ... replace=no' work? That is, what does it take for a file to not be replaced? Is name and location already sufficient? Or does the client check for creation/modification date, size, or something like md5-hash? tia for any info on that, kind regards, tobi... :) -- -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] --
Re: Query Event for Previous day shows status In Progress
Am I off base in suggesting that query events is not a reliable way to check backup status? We've found that you can have: --events that say Missed, but you DO have a good backup (it started late, or was run manually, etc, but it WAS done) --events that say Completed, but you DON'T have a good backup (it Completed the kickoff of a TDP agent; the agent failed an hour later) --NO events at all for some nodes (your DBA may want to control the timing with crontab, rather than the TSM scheduler do it) --skipped files, and events doesn't help you there. (outlook.pst, for example, usually stays open/locked, so TSM misses it. The event status is Completed, because it's "only" one file...!!) This is old news to some people, but maybe useful for others. - Mr. Lindsay Morris Lead Architect www.servergraph.com 512-482-6138 ext 105 > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of > James Choate > Sent: Wednesday, November 05, 2003 8:23 AM > To: [EMAIL PROTECTED] > Subject: Query Event for Previous day shows status In Progress > > > Can someone tell me what is going on with a client(s) that has a > status of In Progress when I query the event? When I query the > event for the previous day, the status indicates that the event > is in progress. When I query the event for the current day, the > event status shows future. When I query the session and the > process on the tsm server, I do not see anything going on with > respect to this event. I have attached the output. Any > help/guidance is appreciated. > > > tsm: TSM>q event nt_servers nt_backups begint=00:00 begind=11/03/2003 > > Scheduled Start Actual Start Schedule Name > Node Name Status > - > - - > 11/03/03 22:30:00 11/03/03 22:45:00 NT_BACKUPS > IBS In Progr- > > ess > 11/03/03 22:30:00 11/04/03 00:18:12 NT_BACKUPS > FS_VSICompleted > 11/03/03 22:30:00 11/03/03 22:30:41 NT_BACKUPS > PLUS_2000 In Progr- > > ess > 11/03/03 22:30:00 11/04/03 00:15:34 NT_BACKUPS > ID_CARD Completed > 11/03/03 22:30:00 11/04/03 00:16:36 NT_BACKUPS > FS_DEVII Completed > 11/03/03 22:30:00 11/04/03 00:15:41 NT_BACKUPS > POWERFAIDSCompleted > 11/03/03 22:30:00 11/04/03 00:15:44 NT_BACKUPS > TPG Completed > 11/03/03 22:30:00 11/04/03 00:17:13 NT_BACKUPS > FS_VSJCompleted > 11/03/03 22:30:00 11/04/03 00:16:42 NT_BACKUPS > FS-HEAT Completed > 11/03/03 22:30:00 11/03/03 22:30:33 NT_BACKUPS > FS-LIBIn Progr- > > ess > 11/03/03 22:30:00 11/04/03 00:07:09 NT_BACKUPS > TNVOICE Completed > 11/03/03 22:30:00 11/04/03 00:16:34 NT_BACKUPS > FS_ACTCompleted > 11/03/03 22:30:00 11/03/03 23:16:54 NT_BACKUPS > MERLIN2 In Progr- > > ess > 11/03/03 22:30:00 11/03/03 22:40:38 NT_BACKUPS > MERCYWEBSRV In Progr- > > ess > 11/03/03 22:30:00 11/04/03 00:28:27 NT_BACKUPS > W2KDC Completed > 11/03/03 22:30:00 11/04/03 00:15:36 NT_BACKUPS > FS-XTDCompleted > tsm: TSM>q sess > Sess Comm. Sess Wait Bytes Bytes > Sess Platform Client Name > Number Method StateTimeSent Recvd > Type > -- -- -- -- --- --- > - > 1 ShMem Run 0 S 112.8 K 139 > Admin AIX ADMIN > 17,411 ShMem Run 0 S 45.9 M 139 > Admin AIX ADMIN > 19,029 ShMem Run 0 S1.0 M 1,018 > Admin AIX UHO > > > tsm: TSM>q pr > > Process Process Description Status > > Number > >
Z/OS and TSM - preferred server level??
We are closing in on bringing up Z/OS 1.4 and with it a new version of TSM server. It looks like 5.1.7 was delivered with our server pac (FMID HDN5510). In a meeting earlier this week a Tivoli rep recommended that we go ahead and pull down the latest server level (5.2.1 w/5.2.2 due in early Dec.) Any recommendations or experiences with this platform and TSM levels out there worth passing along? We're currently at 4.1.4.2 As always, thanks in advance! -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: Query Event for Previous day shows status In Progress
Your schedule window for yesterday has not expired, hence in progress your enquiry for today is looking at start time this evening hence future. cheers, John ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Query Event for Previous day shows status In Progress
Can someone tell me what is going on with a client(s) that has a status of In Progress when I query the event? When I query the event for the previous day, the status indicates that the event is in progress. When I query the event for the current day, the event status shows future. When I query the session and the process on the tsm server, I do not see anything going on with respect to this event. I have attached the output. Any help/guidance is appreciated. tsm: TSM>q event nt_servers nt_backups begint=00:00 begind=11/03/2003 Scheduled Start Actual Start Schedule Name Node Name Status - - - 11/03/03 22:30:00 11/03/03 22:45:00 NT_BACKUPSIBS In Progr- ess 11/03/03 22:30:00 11/04/03 00:18:12 NT_BACKUPSFS_VSI Completed 11/03/03 22:30:00 11/03/03 22:30:41 NT_BACKUPSPLUS_2000 In Progr- ess 11/03/03 22:30:00 11/04/03 00:15:34 NT_BACKUPSID_CARD Completed 11/03/03 22:30:00 11/04/03 00:16:36 NT_BACKUPSFS_DEVII Completed 11/03/03 22:30:00 11/04/03 00:15:41 NT_BACKUPSPOWERFAIDS Completed 11/03/03 22:30:00 11/04/03 00:15:44 NT_BACKUPSTPG Completed 11/03/03 22:30:00 11/04/03 00:17:13 NT_BACKUPSFS_VSJ Completed 11/03/03 22:30:00 11/04/03 00:16:42 NT_BACKUPSFS-HEAT Completed 11/03/03 22:30:00 11/03/03 22:30:33 NT_BACKUPSFS-LIB In Progr- ess 11/03/03 22:30:00 11/04/03 00:07:09 NT_BACKUPSTNVOICE Completed 11/03/03 22:30:00 11/04/03 00:16:34 NT_BACKUPSFS_ACT Completed 11/03/03 22:30:00 11/03/03 23:16:54 NT_BACKUPSMERLIN2 In Progr- ess 11/03/03 22:30:00 11/03/03 22:40:38 NT_BACKUPSMERCYWEBSRV In Progr- ess 11/03/03 22:30:00 11/04/03 00:28:27 NT_BACKUPSW2KDC Completed 11/03/03 22:30:00 11/04/03 00:15:36 NT_BACKUPSFS-XTD Completed tsm: TSM>q sess Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 1 ShMem Run 0 S 112.8 K 139 Admin AIX ADMIN 17,411 ShMem Run 0 S 45.9 M 139 Admin AIX ADMIN 19,029 ShMem Run 0 S1.0 M 1,018 Admin AIX UHO tsm: TSM>q pr Process Process Description Status Number - 2,917 Space ReclamationOffsite Volume(s) (storage pool AIX_OFFSITE_1), Moved Files: 52400, Moved Bytes: 21,509,772,447, Unreadable Files: 3476, Unreadable Bytes: 0. Current Physical File (bytes): 20,597,841 Current input volume: OP0303. Current output volume: OP0287. tsm: TSM>q event nt_servers nt_backups begint=00:00 begind=11/04/2003 Scheduled Start Actual Start Schedule Name Node Name Status - - - 11/04/03 22:30:00 NT_BACKUPSIBS Future 11/04/03 22:30:00 NT_BACKUPSFS_VSI Future 11/04/03 22:30:00 NT_BACKUPSPLUS_2000 Future 11/04/03 22:30:00 NT_BACKUPSID_CARD Future 11/04/03 22:30:00 NT_BACKUPSFS_DEVII
AW: Two virtual libraries in one physical (IBM3583)
Hi, it's well described in redbook SG24-6502-01. best regards, Kirsten Glöer -Ursprüngliche Nachricht- Von: Karel Bos [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 5. November 2003 13:59 An: [EMAIL PROTECTED] Betreff: Re: Two virtual libraries in one physical (IBM3583) Hi, >From the IBM website: Exclusive multi-path architecture increases configuration flexibility with logical library partitioning. So, you can define 2 logical libraries with each a set of drive (2 if you want) and its own set of tapeslots. Yes, it will work. Regard, Karel -Oorspronkelijk bericht- Van: Tomáš Hrouda Ing. [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 13:56 Aan: [EMAIL PROTECTED] Onderwerp: Two virtual libraries in one physical (IBM3583) Hi all, Env: TSM 4.2 on W2K, IBM-3583 library, 2x LTO-1 drives. Now I am planning migration of all data from one set of LTO-1 media to another (due to intensive media errors). I will have two new LTO-1 drives available and new set of media. In TSM v5.2 is possible to define multiple logical libraries in one physical, if multiple device types and media are supported in this library. My idea is to do this migration by defining two logical libraries in one 3583, old drives as first library, new drives as second library. Our request is don4t use old media in new drives and new media in old drives. Question1: Is it possible to use multiple libraries in IBM-3583? Question2: Will it works if all drives and media are the same type? Thanks for any suggestion Tom
Re: Two virtual libraries in one physical (IBM3583)
Hi, >From the IBM website: Exclusive multi-path architecture increases configuration flexibility with logical library partitioning. So, you can define 2 logical libraries with each a set of drive (2 if you want) and its own set of tapeslots. Yes, it will work. Regard, Karel -Oorspronkelijk bericht- Van: Tomáš Hrouda Ing. [mailto:[EMAIL PROTECTED] Verzonden: woensdag 5 november 2003 13:56 Aan: [EMAIL PROTECTED] Onderwerp: Two virtual libraries in one physical (IBM3583) Hi all, Env: TSM 4.2 on W2K, IBM-3583 library, 2x LTO-1 drives. Now I am planning migration of all data from one set of LTO-1 media to another (due to intensive media errors). I will have two new LTO-1 drives available and new set of media. In TSM v5.2 is possible to define multiple logical libraries in one physical, if multiple device types and media are supported in this library. My idea is to do this migration by defining two logical libraries in one 3583, old drives as first library, new drives as second library. Our request is don4t use old media in new drives and new media in old drives. Question1: Is it possible to use multiple libraries in IBM-3583? Question2: Will it works if all drives and media are the same type? Thanks for any suggestion Tom
Two virtual libraries in one physical (IBM3583)
Hi all, Env: TSM 4.2 on W2K, IBM-3583 library, 2x LTO-1 drives. Now I am planning migration of all data from one set of LTO-1 media to another (due to intensive media errors). I will have two new LTO-1 drives available and new set of media. In TSM v5.2 is possible to define multiple logical libraries in one physical, if multiple device types and media are supported in this library. My idea is to do this migration by defining two logical libraries in one 3583, old drives as first library, new drives as second library. Our request is don4t use old media in new drives and new media in old drives. Question1: Is it possible to use multiple libraries in IBM-3583? Question2: Will it works if all drives and media are the same type? Thanks for any suggestion Tom
Re: TDP for Domino problem (need help urgently!!!)
Ameerul, Try looking for a possible solution on www.ibm.com. 1. Go to "www.ibm.com" 2. In the upper right part of the screen, there is a "Search" field. Enter the following in that field ACD5130E You will find some articles written that address this symptom. Thanks, Del > I have a linux redhat client running Domino 6. The TSM > 5.1.5 is installed. It is attached to a AIX running > TSM server 5.2. > > The backups through domdsmc was running fine until > recently got the error > "ACD5130E Could not initialize the connection to Lotus > Domino properly. error=417" > > I thought it was the Domino problem. Check with Admin, > there was no changes. I tried to run the dominstall > again but still the same error persist.
Re: ANR0480W
Hi, Do you know, from where i can download IC34566 fix Thanks Zlatko Krastev <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: Dist cc: Stor Manager" bcc: <[EMAIL PROTECTED]>Subject: Re: ANR0480W 31/10/2003 04:42 μμ Please respond to "ADSM: Dist Stor Manager" Looking through Message manual: "ANR0480W Session session number for node node name (client platform) terminated - connection with client severed. Explanation: The specified client session is ended because the communications link has been closed by a network error or by the client program. System Action: Server operation continues. User Response: If a user breaks out of a client program, this message will be displayed on the server as the connection is suddenly closed by the client. A network failure can also cause this message to be displayed. If a large number of these messages occur simultaneously, check the network for failure and correct any problems. " So the questions are: - did someone killed the client's process - did someone powered the node's system - are there any network problems Zlatko Krastev IT Consultant [EMAIL PROTECTED] 31.10.2003 12:02 To: "Zlatko Krastev" <[EMAIL PROTECTED]> cc: Subject:ANR0480W Hi, I have the following problem while i am taking a backup: ANR0480W: Session session number for node node name (client platform) terminated -connection with client severed. I will appreciate for any help Thanks N.Savva Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended recipient is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify us immediately. All reasonable precautions have been taken to ensure no viruses are present in this e-mail. As we cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use. The views, opinions, conclusions and other information expressed in this electronic mail are not given or endorsed by Laiki Group unless otherwise indicated by an authorised representative independent of this message. Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended recipient is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify us immediately. All reasonable precau
