Re: Using Scratch Volumes
You have to checkin the scratch volumes beforehand, *SM won't ask for them. Kind regards, Jörg -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Doug McLauchlan Sent: Mittwoch, 18. Juli 2001 03:34 To: [EMAIL PROTECTED] Subject: Using Scratch Volumes Hi all, up till now I have been defining tapes in storage pools, but occasionally I run out of storage in a pool, so the backup fails. I want to have a pool of scratch tapes available for use by any storage pool, so gave the max scratch volumes a value of 10 in every storage pool, then labelled a tape but didn't add it to any storage pool. Ran a backup (which would fail as there was no storage available) and in the actlog received the message ANR1405W Scratch volume mount request denied - no scratch volume available and the backup failed. The scratch volume had not been checked into the library at this point. I tried again with the scratch volume checked into the library and this time it added the scratch volume to the storage pool and the backup worked ok. If you are using scratch volumes do they have to be checked into the library for them to work or will TSM call for a scratch to be checked in, or do I need to define all the scratch volumes to a scratch pool, and if so how do I do that. We are running TSM Server 3.7.1 on AIX 4.3.3.0 with a magstar 3570b12 automated library. Thanks Doug McLauchlan DISCLAIMER: The information in this email and in any attachments is confidential and intended solely for the attention and use of the addressee(s). If this email is not intended for you, you must not use, read, distribute or copy it. If you have received this email by mistake please call the sender immediately on 64-9-2620772 and erase the email and any attachments, and any copies of the same. Internet communications are not secure and therefore Woolworths (NZ) Ltd does not accept legal responsibility for the contents of this message. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Woolworths (NZ) Ltd unless specifically stated.
Preemption not working
Hi *SM-ers! Today, again all my client backups were hanging. Again I encountered a 100% full diskpool, but this time it was caused by a very long running backup stgpool. Migration was running, but waiting for mountpoints. According to the Admin Guide, migration processing has a higher priority than a backup stgpool, so the backup should be canceled due to mountpoint preemption, but it didn't So again I'm in deep s***! Should I report this as a bug to Tivoli? I'm running 3.7.4.0 on AIX 4.3.3. Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
offsite copy
How to implement offsite backup copy ... I have two primary tape storage pools for backup and archive. I need to send offsite the backup copy of my primary tape storage for archive. I created one copy storage pool and backup my primary tape storage pool. Then, how do i send this backup copy offsite? Your help is really appreciated regards,
Re: Tivoli for Domino
Hi together, hi Del i´m running version 1.1.1 of TDP for Domino. Plattform is Windows 2000. Transaction logging is set to archival an the command domdsmc archivelog is working from the console also. But when i´m running my scheduler which is the same scheduler i´m using for my other clustered notes server it´s not working. I´m running on each server the same domarc.cmd you see attached to this email.This scheduler is running every 30 minutes. What i´m not understanding is, when i´m removing the cluster server from member list all is working automatically fine ... Thanks you for your help Andre Andre Schwier Information Technology ELSA AG Networking Technology Services Sonnenweg 11 Phone:+49-(0)241-606-3426 52070 Aachen http://www.elsa.de Germany EMail:[EMAIL PROTECTED] |+--- || Del Hoobler | || [EMAIL PROTECTED]| || BM.COM | || | || 17.07.2001 | || 17:16| || Please | || respond to | || ADSM: Dist | || Stor Manager| || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Andre Schwier/ELSA/DE) | | Subject: Re: Tivoli for Domino | | Andre, Are you running version 1.1.1 of TDP for Domino? What platform is your Domino server on? As long as transaction logging is set to archival type on your Domino Server you should be able to run the domdsmc archivelog command and back up the logs. The fact that it is a member of a cluster is not supposed to have any effect on this. Make sure you are running version 1.1.1 and make sure transaction logging is set to archival. Then, retry the domdsmc archivelog command. If it still does not work, please call IBM support. A trace may help determine what is going on. Lotus will also need to get involved since it is the Lotus API that determines when logs are ready for archive. And as of Domino 5.04, the archivelog command (without the threshhold option) will always back up the active log whether it is full or not. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] It's a beautiful day. Don't let it get away. -- Bono Andre Schwier Andre.Schwier To: [EMAIL PROTECTED] @ELSA.DEcc: Sent by: Subject: Re: Tivoli for Domino ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 07/17/2001 10:56 AM Please respond to ADSM: Dist Stor Manager Hi together, i have a problem with a domino cluster member and TSM. When the cluster-domino server is configured as a cluster member the transaction log files will not be archived. ( but no error mesages in the log files ) When removing the cluster-domino server from the member list all is normal. I´m using TSM 3.7.4 on RS/6000 AIX4.1 Domino Server 5.07 Thank you for your help Andre Schwier Andre Schwier Information Technology ELSA AG Networking Technology Services Sonnenweg 11 Phone:+49-(0)241-606-3426 52070 Aachen http://www.elsa.de Germany EMail:[EMAIL PROTECTED]
Antwort: Preemption not working
Eric, it really is a deep s***, and you could report it, but the answer would be: Works as designed When you read the Preemption section of the Admin Guide, you'll see, that only the following actions would cause TSM to cancel another process when needing mount-points = Backup database, Restore, Retrieve, HSM recall, Export and Import So, TSM would never cancel another process, because your migration process needs a Mount Point. The following list (from the manual) only describes the Priority-sequence, which process TSM would cancel, when e.g. a Restore Process needs a mount point = 1. Move data 2. Migration from disk to sequential media 3. Backup, archive, or HSM migration 4. Migration from sequential media to sequential media 5. Reclamation So TSM would first cancel Reclamation. If Reclamation doesn't exist, he would try to cancel the Migration Seq to Seq Media, and so on, and at last he would cancel a Move Data Process. If none of them is running, the Process would hang with waiting for mount point . bla bla Gerhard Wolkerstorfer [EMAIL PROTECTED] (Loon. E.J. van - SPLXM) am 18.07.2001 09:20:07 Bitte antworten an [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT) Thema:Preemption not working Hi *SM-ers! Today, again all my client backups were hanging. Again I encountered a 100% full diskpool, but this time it was caused by a very long running backup stgpool. Migration was running, but waiting for mountpoints. According to the Admin Guide, migration processing has a higher priority than a backup stgpool, so the backup should be canceled due to mountpoint preemption, but it didn't So again I'm in deep s***! Should I report this as a bug to Tivoli? I'm running 3.7.4.0 on AIX 4.3.3. Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Backupsets question
None specifically about backupsets, but the admin guide and reference manual have plenty. Do you have a problem? -Original Message- From: Anderson, Michael - HMIS [mailto:[EMAIL PROTECTED]] Sent: 17 July 2001 21:31 To: [EMAIL PROTECTED] Subject: Backupsets question Is there any kind of documentation or redbooks on backupsets available? CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. http://www.phoenixitgroup.com **Internet Email Confidentiality Footer*** Phoenix IT Group Limited is registered in England and Wales under company number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. No contracts may be concluded on behalf of our firm by means of email communications. Confidentiality: Confidential information may be contained in this message. If you are not the recipient indicated (or responsible for delivery of the message to such person), you may not take any action based on it, nor should you copy or show this to anyone; please reply to this email and highlight the error to the sender, then delete the message from your system. Monitoring of Messages: Please note that we reserve the right to monitor and intercept emails sent and received on our network. Warning: Internet email is not 100% secure. We ask you to understand and observe this lack of security when emailing us. We do not accept responsibility for changes made to this message after it was sent Viruses: Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
Output query
Could someone explain to me the log file output from a backup below? ie. what is meant by 'Full: 0' and the 'Read' and 'Written' columns? Being a bit new to this I'm not sure why I see this on some of the files we backup and not others. Thanks. Backing up database \CDM\CDMOPER.NSF, 1 of 2. Full: 3 Read: 2161152 Written: 0 Rate: 0.00 Kb/Sec Full: 0 Read: 2161152 Written: 2161152 Rate: 1,050.00 Kb/Sec Full: 0 Read: 2161152 Written: 2161152 Rate: 701.16 Kb/Sec Full: 0 Read: 2161152 Written: 2161152 Rate: 526.31 Kb/Sec Full: 0 Read: 2161152 Written: 2161152 Rate: 421.26 Kb/Sec Full: 0 Read: 2161152 Written: 2161152 Rate: 351.16 Kb/Sec Full: 0 Read: 2161152 Written: 2161152 Rate: 324.19 Kb/Sec Backup of team\CIS\CDM\CDMOPER.NSF completed successfully. Sun E5500 running solaris 2.6, TSM SERVER 4.1, Notes clients are Domino R5.05, TDP for DominoNT v1.1
Re: offsite copy
Zosimo, 1) backup stg_pool copy_pool 2) q vol * stg=copy_pool acc=readwr shows a list of volumes for each volume ( a_vol ) in this list do 3) upd vol a_vol acc=offsite 4) checkout libv yourlibrary a_vol 5) take all checked out volumes and ship them offsite :-) herfried Zosimo Noriega (ADNOC IST) [EMAIL PROTECTED]@VM.MARIST.EDU on 18.07.2001 09:41:46 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: offsite copy How to implement offsite backup copy ... I have two primary tape storage pools for backup and archive. I need to send offsite the backup copy of my primary tape storage for archive. I created one copy storage pool and backup my primary tape storage pool. Then, how do i send this backup copy offsite? Your help is really appreciated regards, The information contained in this transmission, which may be confidential and proprietary, is only for the intended recipients. Unauthorized use is strictly prohibited. If you receive this transmission in error, please notify me immediately by telephone or electronic mail and confirm that you deleted this transmission and the reply from your electronic mail system.
selective backup?
I use the selective backup function to do a daily backup of 2 directories in one of my servers. It is run via crontab, this is how the script file looks like dsmc selective /documentum/ /oracle7/ However, I realise when I do it, it doesn't quite seem to back up the directories below that of these 2 directories? I have read through the selective help under dsmc, and it says when you put a slash after the directory, it would back up the file system for that directory. When I run the script manually, this is what I get. From what I understand, directories below the /documentum and /oracle7 are not backed up? How is it possible for me to backup the entire directory then, i.e to do a recursive directory backup of these 2 directories? Many Thanks in Advance. Node Name: SAP_DOC Session established with server SA_DEVT: AIX-RS/6000 Server Version 4, Release 1, Level 3.0 Server date/time: 07/18/01 16:02:50 Last access: 07/18/01 01:36:00 Directory-- 1,024 /documentum/ [Sent] Directory-- 1,024 /documentum/dctm [Sent] Directory-- 1,024 /documentum/dmadmin [Sent] Directory-- 96 /documentum/doclink [Sent] Directory-- 96 /documentum/lost+found [Sent] Directory-- 96 /documentum/orcle734NT [Sent] Directory-- 1,024 /documentum/sapshare_home [Sent] Directory-- 96 /documentum/system_mail_files [Sent] Directory-- 96 /documentum/users [Sent] Directory-- 96 /documentum/work_temp [Sent] Normal File-- 814 /documentum/.cshrc [Sent] Normal File-- 347 /documentum/.exrc [Sent] Normal File-- 341 /documentum/.login [Sent] Normal File-- 446 /documentum/.profile [Sent] Normal File-- 254 /documentum/.sh_history [Sent] Normal File--37 /documentum/test.txt [Sent] Normal File-- 357 /documentum/dsmerror.log [Sent] ANS1114I Waiting for mount of offline media. Retry # 1 Directory-- 1,024 /documentum/ [Sent] Retry # 1 Directory-- 1,024 /documentum/dctm [Sent] Retry # 1 Directory-- 1,024 /documentum/dmadmin [Sent] Retry # 1 Directory-- 96 /documentum/doclink [Sent] Retry # 1 Directory-- 96 /documentum/lost+found [Sent] Retry # 1 Directory-- 96 /documentum/orcle734NT [Sent] Retry # 1 Directory-- 1,024 /documentum/sapshare_home [Sent] Retry # 1 Directory-- 96 /documentum/system_mail_files [Sent] Retry # 1 Directory-- 96 /documentum/users [Sent] Retry # 1 Directory-- 96 /documentum/work_temp [Sent] Retry # 1 Normal File-- 814 /documentum/.cshrc [Sent] Retry # 1 Normal File-- 347 /documentum/.exrc [Sent] Retry # 1 Normal File-- 341 /documentum/.login [Sent] Retry # 1 Normal File-- 446 /documentum/.profile [Sent] Retry # 1 Normal File-- 254 /documentum/.sh_history [Sent] Retry # 1 Normal File--37 /documentum/test.txt [Sent] Retry # 1 Normal File-- 357 /documentum/dsmerror.log [Sent] Selective Backup processing of '/documentum/*' finished without failure. Directory-- 1,024 /oracle7/ [Sent] Directory-- 1,024 /oracle7/EOFFICE [Sent] Directory-- 96 /oracle7/admin [Sent] Directory-- 2,048 /oracle7/bin [Sent] Directory-- 96 /oracle7/cronjobs_dir [Sent] Directory-- 1,024 /oracle7/dbs [Sent] Directory-- 96 /oracle7/guicommon2 [Sent] Directory-- 96 /oracle7/jdbc [Sent] Directory-- 2,048 /oracle7/lib [Sent] Directory-- 96 /oracle7/local [Sent] Directory-- 96 /oracle7/lost+found [Sent] Directory-- 1,024 /oracle7/md [Sent] Directory-- 1,024 /oracle7/network [Sent] Directory-- 96 /oracle7/nlsrtl3 [Sent] Directory-- 96 /oracle7/ocommon [Sent] Directory-- 96 /oracle7/oracore3 [Sent] Directory-- 5,120 /oracle7/orainst [Sent] Directory-- 1,024 /oracle7/otrace [Sent] Directory-- 96 /oracle7/plsql [Sent] Directory-- 1,024 /oracle7/precomp [Sent] Directory-- 1,024 /oracle7/rdbms [Sent] Directory-- 96 /oracle7/slax [Sent] Directory-- 1,024 /oracle7/sqlplus [Sent] Directory-- 1,024 /oracle7/src [Sent] Directory-- 96 /oracle7/svrmgr [Sent] Directory-- 96 /oracle7/tmp [Sent] Directory-- 6,144 /oracle7/work [Sent] Normal File-- 2,376 /oracle7/.sh_history [Sent] Normal File-- 1,071 /oracle7/.profile [Sent] Normal File-- 8,228 /oracle7/unix.prd [Sent] Normal File--
Re: selective backup?
Eugene Awyong - Singapore [EMAIL PROTECTED] schrieb: I use the selective backup function to do a daily backup of 2 directories in one of my servers. It is run via crontab, this is how the script file looks like dsmc selective /documentum/ /oracle7/ However, I realise when I do it, it doesn't quite seem to back up the directories below that of these 2 directories? Try dsmc selective -subdir=yes /documentum/ /oracle7/ or include the following line into your dsm.opt, to make it the default: SUBDIR YES -- Reinhard MerschWestfaelische Wilhelms-Universitaet Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583 E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
Re: selective backup?
Eugene, just add -subdir=yes option from your script. like this: dsmc selective /documentum/ /oracle7/ -subdir=yes regards, -Original Message- From: Eugene Awyong - Singapore [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 12:15 PM To: [EMAIL PROTECTED] Subject: selective backup? I use the selective backup function to do a daily backup of 2 directories in one of my servers. It is run via crontab, this is how the script file looks like dsmc selective /documentum/ /oracle7/ However, I realise when I do it, it doesn't quite seem to back up the directories below that of these 2 directories? I have read through the selective help under dsmc, and it says when you put a slash after the directory, it would back up the file system for that directory. When I run the script manually, this is what I get. From what I understand, directories below the /documentum and /oracle7 are not backed up? How is it possible for me to backup the entire directory then, i.e to do a recursive directory backup of these 2 directories? Many Thanks in Advance. Node Name: SAP_DOC Session established with server SA_DEVT: AIX-RS/6000 Server Version 4, Release 1, Level 3.0 Server date/time: 07/18/01 16:02:50 Last access: 07/18/01 01:36:00 Directory-- 1,024 /documentum/ [Sent] Directory-- 1,024 /documentum/dctm [Sent] Directory-- 1,024 /documentum/dmadmin [Sent] Directory-- 96 /documentum/doclink [Sent] Directory-- 96 /documentum/lost+found [Sent] Directory-- 96 /documentum/orcle734NT [Sent] Directory-- 1,024 /documentum/sapshare_home [Sent] Directory-- 96 /documentum/system_mail_files [Sent] Directory-- 96 /documentum/users [Sent] Directory-- 96 /documentum/work_temp [Sent] Normal File-- 814 /documentum/.cshrc [Sent] Normal File-- 347 /documentum/.exrc [Sent] Normal File-- 341 /documentum/.login [Sent] Normal File-- 446 /documentum/.profile [Sent] Normal File-- 254 /documentum/.sh_history [Sent] Normal File--37 /documentum/test.txt [Sent] Normal File-- 357 /documentum/dsmerror.log [Sent] ANS1114I Waiting for mount of offline media. Retry # 1 Directory-- 1,024 /documentum/ [Sent] Retry # 1 Directory-- 1,024 /documentum/dctm [Sent] Retry # 1 Directory-- 1,024 /documentum/dmadmin [Sent] Retry # 1 Directory-- 96 /documentum/doclink [Sent] Retry # 1 Directory-- 96 /documentum/lost+found [Sent] Retry # 1 Directory-- 96 /documentum/orcle734NT [Sent] Retry # 1 Directory-- 1,024 /documentum/sapshare_home [Sent] Retry # 1 Directory-- 96 /documentum/system_mail_files [Sent] Retry # 1 Directory-- 96 /documentum/users [Sent] Retry # 1 Directory-- 96 /documentum/work_temp [Sent] Retry # 1 Normal File-- 814 /documentum/.cshrc [Sent] Retry # 1 Normal File-- 347 /documentum/.exrc [Sent] Retry # 1 Normal File-- 341 /documentum/.login [Sent] Retry # 1 Normal File-- 446 /documentum/.profile [Sent] Retry # 1 Normal File-- 254 /documentum/.sh_history [Sent] Retry # 1 Normal File--37 /documentum/test.txt [Sent] Retry # 1 Normal File-- 357 /documentum/dsmerror.log [Sent] Selective Backup processing of '/documentum/*' finished without failure. Directory-- 1,024 /oracle7/ [Sent] Directory-- 1,024 /oracle7/EOFFICE [Sent] Directory-- 96 /oracle7/admin [Sent] Directory-- 2,048 /oracle7/bin [Sent] Directory-- 96 /oracle7/cronjobs_dir [Sent] Directory-- 1,024 /oracle7/dbs [Sent] Directory-- 96 /oracle7/guicommon2 [Sent] Directory-- 96 /oracle7/jdbc [Sent] Directory-- 2,048 /oracle7/lib [Sent] Directory-- 96 /oracle7/local [Sent] Directory-- 96 /oracle7/lost+found [Sent] Directory-- 1,024 /oracle7/md [Sent] Directory-- 1,024 /oracle7/network [Sent] Directory-- 96 /oracle7/nlsrtl3 [Sent] Directory-- 96 /oracle7/ocommon [Sent] Directory-- 96 /oracle7/oracore3 [Sent] Directory-- 5,120 /oracle7/orainst [Sent] Directory-- 1,024 /oracle7/otrace [Sent] Directory-- 96 /oracle7/plsql [Sent] Directory-- 1,024 /oracle7/precomp [Sent] Directory-- 1,024 /oracle7/rdbms [Sent] Directory-- 96 /oracle7/slax [Sent] Directory-- 1,024 /oracle7/sqlplus [Sent] Directory-- 1,024 /oracle7/src [Sent] Directory-- 96 /oracle7/svrmgr
Re: Preemption not working
Loon, E.J. van - SPLXM wrote: Hi *SM-ers! Today, again all my client backups were hanging. Again I encountered a 100% full diskpool, but this time it was caused by a very long running backup stgpool. Migration was running, but waiting for mountpoints. According to the Admin Guide, migration processing has a higher priority than a backup stgpool, so the backup should be canceled due to mountpoint preemption, but it didn't So again I'm in deep s***! Should I report this as a bug to Tivoli? I'm running 3.7.4.0 on AIX 4.3.3. Kindest regards, Eric van Loon KLM Royal Dutch Airlines Check your server options for NOPREEMPT. KR, -- Horst SCHERZER e-Mail: [EMAIL PROTECTED] Vienna University Computer Center Phone: (+43 1) 4277 x14053 Universitaetsstr.7 Cellular: (+43) 0664/60 277 14053 A-1010 Wien/Vienna Fax: (+43 1) 4277 x9140 Oesterreich/Austria URL: http://mailbox.univie.ac.at/~sc begin:vcard n:Scherzer;Horst tel;cell:( +43) 0664/60 277 14053 tel;fax:4277-9140 tel;work:4277-14053 x-mozilla-html:FALSE url:http://mailbox.univie.ac.at/~sc org:Zentraler Informatikdienst Uni-Wien adr:;;Universitaetsstr.7;A-1010 Wien/Vienna;Oesterreich/Austria;; version:2.1 email;internet:[EMAIL PROTECTED] title:Systems Programmer fn:Horst Scherzer end:vcard
General PREEMPTION Question
Hi to all, The long story: We are running a rather old ADSM server version : 3.1.2.20 and we will upgrade to 4.? in august. With the version we are running now, I have problems related to the default preemption strategy. In gernal I think it is a good thing, but we have one special application where the Preemption priority is wrong. This is running an SAP Archive ( Archive of scanned documents and generated lists ) via the CommonStore-Content Manager for R3 SW. Here - in real life - the process af bringing a document into the Archive ( adsm operation: archive ) HAS AN HIGHER priority then viewing those archived documents ( adsm operation: retrieve ). As the data is stored on opticals ( permanent worms ) and never expires - it happens that a read-the-data process preempts a write-new-data process. (there are a lot of stg pools - with only 1 writeable volume in it - reason : be able to check the opticals out of the library based on an document-type time-based strategy ). So its not possible for me to define more than one volume for writing within one stg pools - otherwise I would run out of slots within the library. The problem: As far as I know in V 3.1.2.20 Preemption can only be disabled with server-wide scope. The short question: Can in TSM V4.? preemption be defined on an TSM object with smaler scope ( mgmt class, stg pool, ) ? Thanks for you patience herfried The information contained in this transmission, which may be confidential and proprietary, is only for the intended recipients. Unauthorized use is strictly prohibited. If you receive this transmission in error, please notify me immediately by telephone or electronic mail and confirm that you deleted this transmission and the reply from your electronic mail system.
TDP for Domino - Brick level backup?
Hi Does TDP for Domino can do a brick level backup?
TSM modules for Perl
Hi all, because of the large interest in the TSM for PERL Module, I've created a homepage which will be used for updates and news for the time being (don't blame me on the design ;-)). Have a look at: http://home.wtal.de/the_swordsman In regards to the name space: I discussed this issue (seperating methods from the object) and we came to the conclusion, that it doesn't make much sense, since it will make the usage of the module much more complecated. However, the design allows anybody to inherit the object and methods for other modules. After collecting and incorporating the feedback, and after the modules passed the tests, I'll register the TSM namespace at CPAN. As the next steps, I can imagine to collect scripts or code fragments based on this module on my homepage. Volunteers are welcome. Best regards, Jörg Nouvertné http://home.wtal.de/the_swordsman
Re: Antwort: Preemption not working
Hi Gerhard! You are right, the backup stgpool command is not on the priority list. If this means that a backup stgpool will never be canceled, I think this is a really serious problem. What if a client, or several (new) clients are generation a lot of backup data. In this case your backups stgpool processes will run a lot longer than normally. If you haven't got a very large diskpool you will probably run in a full diskpool before the backup stgpool is finished. Some backups (like TDP backups) can't handle this and will hang. Could someone from development confirm that the backup stgpool will never be preempted? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Gerhard Wolkerstorfer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 10:15 To: [EMAIL PROTECTED] Subject: Antwort: Preemption not working Eric, it really is a deep s***, and you could report it, but the answer would be: Works as designed When you read the Preemption section of the Admin Guide, you'll see, that only the following actions would cause TSM to cancel another process when needing mount-points = Backup database, Restore, Retrieve, HSM recall, Export and Import So, TSM would never cancel another process, because your migration process needs a Mount Point. The following list (from the manual) only describes the Priority-sequence, which process TSM would cancel, when e.g. a Restore Process needs a mount point = 1. Move data 2. Migration from disk to sequential media 3. Backup, archive, or HSM migration 4. Migration from sequential media to sequential media 5. Reclamation So TSM would first cancel Reclamation. If Reclamation doesn't exist, he would try to cancel the Migration Seq to Seq Media, and so on, and at last he would cancel a Move Data Process. If none of them is running, the Process would hang with waiting for mount point . bla bla Gerhard Wolkerstorfer [EMAIL PROTECTED] (Loon. E.J. van - SPLXM) am 18.07.2001 09:20:07 Bitte antworten an [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT) Thema:Preemption not working Hi *SM-ers! Today, again all my client backups were hanging. Again I encountered a 100% full diskpool, but this time it was caused by a very long running backup stgpool. Migration was running, but waiting for mountpoints. According to the Admin Guide, migration processing has a higher priority than a backup stgpool, so the backup should be canceled due to mountpoint preemption, but it didn't So again I'm in deep s***! Should I report this as a bug to Tivoli? I'm running 3.7.4.0 on AIX 4.3.3. Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: TDP for Domino - Brick level backup?
What do you mean by Brick Level Backup? If the question is Does TDP for Domino can do a document level backup? the answer is No. The behaviour has changed from Notes Version 4.x to 5. The TDP for Domino is using the Domino transaction functionality to perform incremental backups, which means that you have to restore the DB to a temporary location, apply the transactions and copy the documents to the original database. Kind regards, Joerg Nouvertne http://home.wtal.de/the_swordsman -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ofer vaknin Sent: Mittwoch, 18. Juli 2001 12:29 To: [EMAIL PROTECTED] Subject: TDP for Domino - Brick level backup? Importance: High Hi Does TDP for Domino can do a brick level backup?
Re: TDP for Domino - Brick level backup?
Tivoli Data Protection for Lotus Domino provides two types of database backupincremental and selectiveand a log archive function. Incremental backup provides a conditional backup function that creates a full on-line backup of Domino databases, when necessary. The specific conditions that determine when a new backup is necessary vary depending on whether the database is logged or not. Selective backup unconditionally backs up the specified databases, unless they are excluded from backup through exclude statements. When archival logging is in effect, changes to logged databases can be captured in between full backups, by archiving the transaction log. let me change my Q ,Does selective backup is brick level (brick level backup - most common with MS Exchange ,backup/restore of one inbox and not all the DB) -Original Message- From: J?rg Nouvertn? [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 12:05 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Domino - Brick level backup? What do you mean by Brick Level Backup? If the question is Does TDP for Domino can do a document level backup? the answer is No. The behaviour has changed from Notes Version 4.x to 5. The TDP for Domino is using the Domino transaction functionality to perform incremental backups, which means that you have to restore the DB to a temporary location, apply the transactions and copy the documents to the original database. Kind regards, Joerg Nouvertne http://home.wtal.de/the_swordsman -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ofer vaknin Sent: Mittwoch, 18. Juli 2001 12:29 To: [EMAIL PROTECTED] Subject: TDP for Domino - Brick level backup? Importance: High Hi Does TDP for Domino can do a brick level backup?
Re: TDP for Domino - Brick level backup?
Hi, the answer is yes and no, since brick level does not apply to the Domino infrastructure. No, you cannot restore just a single document, you have to restore the DB and copy the document over. Yes, if you are talking about a user's mail box. In Domino, every user has his own database, you don't have to restore the whole stuff to get the mail file of one user back. Regards, Joerg Nouvertne http://home.wtal.de/the_swordsman -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ofer vaknin Sent: Mittwoch, 18. Juli 2001 13:11 To: [EMAIL PROTECTED] Subject: Re: TDP for Domino - Brick level backup? Importance: High Tivoli Data Protection for Lotus Domino provides two types of database backupincremental and selectiveand a log archive function. Incremental backup provides a conditional backup function that creates a full on-line backup of Domino databases, when necessary. The specific conditions that determine when a new backup is necessary vary depending on whether the database is logged or not. Selective backup unconditionally backs up the specified databases, unless they are excluded from backup through exclude statements. When archival logging is in effect, changes to logged databases can be captured in between full backups, by archiving the transaction log. let me change my Q ,Does selective backup is brick level (brick level backup - most common with MS Exchange ,backup/restore of one inbox and not all the DB) -Original Message- From: J?rg Nouvertn? [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 12:05 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Domino - Brick level backup? What do you mean by Brick Level Backup? If the question is Does TDP for Domino can do a document level backup? the answer is No. The behaviour has changed from Notes Version 4.x to 5. The TDP for Domino is using the Domino transaction functionality to perform incremental backups, which means that you have to restore the DB to a temporary location, apply the transactions and copy the documents to the original database. Kind regards, Joerg Nouvertne http://home.wtal.de/the_swordsman -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ofer vaknin Sent: Mittwoch, 18. Juli 2001 12:29 To: [EMAIL PROTECTED] Subject: TDP for Domino - Brick level backup? Importance: High Hi Does TDP for Domino can do a brick level backup?
Re: selective backup?
I use the selective backup function to do a daily backup of 2 directories in one of my servers... ... However, I realise when I do it, it doesn't quite seem to back up the directories below that of these 2 directories? ... Two things... 1. You don't want to back up directories every time you do a backup: you want the directories backed up the first time, and thereafter have only files backed up. Unix directories are just structural definitions, like empty files. Repeatedly storing them on your server is only going to waste space. 2. Unless you have a compelling reason to cause everything in those directories to be backed up every time, I should think you would want to use Incremental backup against the directories, to back up only changed files, and avoid a lot of server overhead. Richard Sims, BU
Re: offsite copy
1) backup stg_pool copy_pool 2) q vol * stg=copy_pool acc=readwr shows a list of volumes for each volume ( a_vol ) in this list do 3) upd vol a_vol acc=offsite 4) checkout libv yourlibrary a_vol Tip: Consider using the often-overlooked Query MEDia command to generate command lists that you can subsequently run via the Macro command, to save yourself a lot of tedium. Powerful and convenient. Richard Sims, BU
OS error reports
Perhaps you can help me.. I need to know what facilities each of the TSM supported OS's has to report problems.. ie NT = Event Log, AIX = errpt What is there for: Solaris HP OS390 AS400 MVS VM ? Any responses greatly appreaciated! Many Thanks Regards, Matthew Matthew Large TSM Consultant Tel: 44 (0) 775 38 31 358 Phoenix IT Group Limited http://www.phoenixitgroup.com **Internet Email Confidentiality Footer*** Phoenix IT Group Limited is registered in England and Wales under company number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. No contracts may be concluded on behalf of our firm by means of email communications. Confidentiality: Confidential information may be contained in this message. If you are not the recipient indicated (or responsible for delivery of the message to such person), you may not take any action based on it, nor should you copy or show this to anyone; please reply to this email and highlight the error to the sender, then delete the message from your system. Monitoring of Messages: Please note that we reserve the right to monitor and intercept emails sent and received on our network. Warning: Internet email is not 100% secure. We ask you to understand and observe this lack of security when emailing us. We do not accept responsibility for changes made to this message after it was sent Viruses: Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
Antwort: Re: Antwort: Preemption not working
Eric, it is a problem, I guess we all know that. And the same happens, when you have only 2 mount points and Reclamation is running, or something else and the Migration cannot clean up the Diskpool by migrating to tape, because of the missing mount point. We solved the problem by 1) defining 3 mountpoints. When Reclamation, Backup Stg and so on is using 2 mount points, we have one left 2) Because our diskpool has 20 Gb Storage and our clients are used to backup about 80 Gb per night, we are running Backup Diskpool-Copypool each hour and after 1 pm, we are running Backup Primarypool-Copypool to backup the missing data (which was migrated between the hourly Diskpool Backup) Regards Gerhard Wolkerstorfer [EMAIL PROTECTED] (Loon. E.J. van - SPLXM) am 18.07.2001 11:42:53 Bitte antworten an [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT) Thema:Re: Antwort: Preemption not working Hi Gerhard! You are right, the backup stgpool command is not on the priority list. If this means that a backup stgpool will never be canceled, I think this is a really serious problem. What if a client, or several (new) clients are generation a lot of backup data. In this case your backups stgpool processes will run a lot longer than normally. If you haven't got a very large diskpool you will probably run in a full diskpool before the backup stgpool is finished. Some backups (like TDP backups) can't handle this and will hang. Could someone from development confirm that the backup stgpool will never be preempted? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Gerhard Wolkerstorfer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 10:15 To: [EMAIL PROTECTED] Subject: Antwort: Preemption not working Eric, it really is a deep s***, and you could report it, but the answer would be: Works as designed When you read the Preemption section of the Admin Guide, you'll see, that only the following actions would cause TSM to cancel another process when needing mount-points = Backup database, Restore, Retrieve, HSM recall, Export and Import So, TSM would never cancel another process, because your migration process needs a Mount Point. The following list (from the manual) only describes the Priority-sequence, which process TSM would cancel, when e.g. a Restore Process needs a mount point = 1. Move data 2. Migration from disk to sequential media 3. Backup, archive, or HSM migration 4. Migration from sequential media to sequential media 5. Reclamation So TSM would first cancel Reclamation. If Reclamation doesn't exist, he would try to cancel the Migration Seq to Seq Media, and so on, and at last he would cancel a Move Data Process. If none of them is running, the Process would hang with waiting for mount point . bla bla Gerhard Wolkerstorfer [EMAIL PROTECTED] (Loon. E.J. van - SPLXM) am 18.07.2001 09:20:07 Bitte antworten an [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT) Thema:Preemption not working Hi *SM-ers! Today, again all my client backups were hanging. Again I encountered a 100% full diskpool, but this time it was caused by a very long running backup stgpool. Migration was running, but waiting for mountpoints. According to the Admin Guide, migration processing has a higher priority than a backup stgpool, so the backup should be canceled due to mountpoint preemption, but it didn't So again I'm in deep s***! Should I report this as a bug to Tivoli? I'm running 3.7.4.0 on AIX 4.3.3. Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Output query
Marc, Full: tells you how many data transfer buffers are fill at a current instance in time. The number of buffers can be changed by using the BUFFERS option/preference setting. Read: tells you how many bytes of data have been read from the database file at a current instance in time. Written: tells you how many bytes of data (before compression) have been sent to the TSM API (TSM Server) at a current instance in time. That is for backup. For restore, as you might guess, the numbers reflect data movement in the other direction. Keep in mind these stats are only a snapshot of a current instance in time. The snapshot is taken at 1 second intervals. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] It's a beautiful day. Don't let it get away. -- Bono Marc Lowers Marc_R_Lowers@S To: [EMAIL PROTECTED] BPHRD.COM cc: Sent by: ADSM:Subject: Output query Dist Stor Manager [EMAIL PROTECTED] T.EDU 07/18/2001 04:22 AM Please respond to ADSM: Dist Stor Manager Could someone explain to me the log file output from a backup below? ie. what is meant by 'Full: 0' and the 'Read' and 'Written' columns? Being a bit new to this I'm not sure why I see this on some of the files we backup and not others.
ACL Notes Database
With ADSM Connect for Lotus Notes , when j launch a dsmnotes restore ,is it important l'id file used? After the restore i verify the user activity on the database properties, and result the id server that had modified the documents... Is This Important??? Thank Maurizio COnti
Re: What would you think would happen..........
Thanks for the info. Yes, we are doing a point in time restore. Churchfield, Glen [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/17/2001 05:06 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: What would you think would happen.. Zoltan, If you start a restore to another box from the gui, you'd have a restartable restore on the server. That blocks that filespace from backing up until the restore is finished. If you started from the cmd line, the same would happen unless you used the -pittime or some other option that kept it from being a restartable restore. In that case, the backup would go ahead during the restore. I think in that case, that the backup marking files inactive wouldn't interfere because you'd already be restoring only inactive files. The problem with doing that is that it takes maybe three times longer because of the additional processing. -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 17, 2001 2:59 PM To: [EMAIL PROTECTED] Subject: Re: What would you think would happen.. What I mean is that the machine performing the restore (AIX) does not perform backups. It simply connects as NODENAME XYZ. It is not *THE* XYZ node that did the backup. How would you lockout the source node since this machine is signing in using the NODENAME of the source node ? === Zoltan Forray Virginia Commonwealth University University Computing Center e-mail: [EMAIL PROTECTED] voice: 804-828-4807 Martin, Jon R. [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/17/2001 03:00 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: What would you think would happen.. Zoltan, Interesting subject I was just talking about this possibility the other day. My question refers to part 1. When you say the node is not a TSM-client I am assuming that they have the TSM client installed they are just not registered with the server as a node? Otherwise how would they access the utilities to open the connection in the first place? Besides taking the safety precaution of locking the source node out has anyone experienced this situation before? Jon -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 17, 2001 2:24 PM To: [EMAIL PROTECTED] Subject: What would you think would happen.. if the following occured: 1. Client (lets call it ABC for this arguement since it is not a TSM client) signs into TSM using nodename XYZ to restore XYZ's files to another system 2. Restore is progressing. Large compress files take many hours to restore. 3. Node XYZ signs into TSM and does a BACKUP while ABC is still signed on as XYZ and is still restoring XYZ's files to another machine. === Zoltan Forray Virginia Commonwealth University University Computing Center e-mail: [EMAIL PROTECTED] voice: 804-828-4807
Re: Tivoli for Domino
Andre, We have not seen this problem yet. It should not matter whether the server is a member of a Domino server cluster or not. Please call IBM support. A trace may help determine what is going on. Lotus will also need to get involved since it is the Lotus API that determines when logs are ready for archive. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] It's a beautiful day. Don't let it get away. -- Bono Andre Schwier Andre.Schwier To: [EMAIL PROTECTED] @ELSA.DEcc: Sent by: Subject: Re: Tivoli for Domino ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 07/18/2001 03:45 AM Please respond to ADSM: Dist Stor Manager Hi together, hi Del i´m running version 1.1.1 of TDP for Domino. Plattform is Windows 2000. Transaction logging is set to archival an the command domdsmc archivelog is working from the console also. But when i´m running my scheduler which is the same scheduler i´m using for my other clustered notes server it´s not working. I´m running on each server the same domarc.cmd you see attached to this email.This scheduler is running every 30 minutes. What i´m not understanding is, when i´m removing the cluster server from member list all is working automatically fine ... Thanks you for your help Andre
Maxsize problem?
We have recently installed an NSM C01 with an IBM 3584 LTO library. TSM level is V4.1 We use a DISKPOOL and a TAPEPOOL. We defined a MAXSIZE=1G for the DISKPOOL. TAPEPOOL is the nextpool of the DISKPOOL. When we are backing up files we notice that all files smaller than 1 GB are not being backed up at all. If we remove the MAXSIZE parameter, all files are backed up. Any explanation for this? or is this a bug? Ton de Wekker ESSCON Services BV Don't forget to visit our website http://www.esscon.nl Tel. +31 348 449 599 Mob. +31 651 211 080 Email [EMAIL PROTECTED]
Multiple IBM3570 libraries on a single TSM Server.
My Current TSM server has ONE IBM3570 B12 tape library attached and defined. I do not use DISK storage pools, but write backup/archive data direct to tape storage pools. I would like to add another IBM3570 B12 tape libary to the same TSM server ? Can this be done ? What are the implications for my existing storage pools, as only ONE library can be associated with a device-class. Can a storage pool be associated with multiple device-classes ? Thanks Michael Benton _ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service.
Re: Archive Question
Thanks for all the help. Now I can understand why there is a fluctuation in the amount archived when looking through the activity log. -Original Message- From: Alex Paschal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 17, 2001 5:51 PM To: [EMAIL PROTECTED] Subject: Re: Archive Question Hi, Bill. The Total Bytes Transfered statistic isn't actually incorrect; it's just a different statistic than what you're looking for. It just tells how much data was sent over the network. For example, if a 500MB file is half transfered, 250MB, then the file is updated, it starts over, resulting in 750MB of network data transfered for a 500MB object. You can find the information you're looking for in the Accounting log. You can find information on the accounting log in the TSM Admin Guide. Thanks, Alex -Original Message- From: Bill Wheeler [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 17, 2001 10:09 AM To: [EMAIL PROTECTED] Subject: Re: Archive Question snip 07/17/01 06:49:45 ANE4961I (Session: 832, Node: F50_CLIENT) Total number of bytes transferred:70.15 GB snip 07/17/01 06:49:45 ANE4964I (Session: 832, Node: F50_CLIENT) Elapsed processing time:08:12:49 The number that I look at on a daily basis is Total Number of Bytes transferred and Elapsed processing time. It is the total number of bytes transferred that fluctuates. So you are saying that the number it shows for the Total bytes transferred can be incorrect. Is there a better place to look to get the exact amount transferred? Thanks in advance, Bill Wheeler AIX Administrator La-Z-Boy Incorporated mailto:[EMAIL PROTECTED] WorldSecure Freightliner.com made the following annotations on 07/17/01 14:41:35 -- [INFO] -- Content Manager: The information contained in this communication is confidential and intended solely for the use of the individual to whom it is addressed and others authorized to receive it. If you are not the intended recipient, any disclosure, copying, distribution or taking of any action in reliance on the contents of this information is prohibited. If you have received this communication in error, please immediately notify the sender by phone if possible or via email message. ==
Re: selective backup?
The option subdirectory=yes needs to be included in the statement. your backup script would read: dsmc selective -subdir=yes /documentum/ /oracle7/ Try this. if it doesn't work (which it should) let us know.. Regards, -Original Message- From: Eugene Awyong - Singapore [mailto:[EMAIL PROTECTED]] Sent: 18 July 2001 09:15 To: [EMAIL PROTECTED] Subject: selective backup? I use the selective backup function to do a daily backup of 2 directories in one of my servers. It is run via crontab, this is how the script file looks like dsmc selective /documentum/ /oracle7/ However, I realise when I do it, it doesn't quite seem to back up the directories below that of these 2 directories? I have read through the selective help under dsmc, and it says when you put a slash after the directory, it would back up the file system for that directory. When I run the script manually, this is what I get. From what I understand, directories below the /documentum and /oracle7 are not backed up? How is it possible for me to backup the entire directory then, i.e to do a recursive directory backup of these 2 directories? Many Thanks in Advance. Node Name: SAP_DOC Session established with server SA_DEVT: AIX-RS/6000 Server Version 4, Release 1, Level 3.0 Server date/time: 07/18/01 16:02:50 Last access: 07/18/01 01:36:00 Directory-- 1,024 /documentum/ [Sent] Directory-- 1,024 /documentum/dctm [Sent] Directory-- 1,024 /documentum/dmadmin [Sent] Directory-- 96 /documentum/doclink [Sent] Directory-- 96 /documentum/lost+found [Sent] Directory-- 96 /documentum/orcle734NT [Sent] Directory-- 1,024 /documentum/sapshare_home [Sent] Directory-- 96 /documentum/system_mail_files [Sent] Directory-- 96 /documentum/users [Sent] Directory-- 96 /documentum/work_temp [Sent] Normal File-- 814 /documentum/.cshrc [Sent] Normal File-- 347 /documentum/.exrc [Sent] Normal File-- 341 /documentum/.login [Sent] Normal File-- 446 /documentum/.profile [Sent] Normal File-- 254 /documentum/.sh_history [Sent] Normal File--37 /documentum/test.txt [Sent] Normal File-- 357 /documentum/dsmerror.log [Sent] ANS1114I Waiting for mount of offline media. Retry # 1 Directory-- 1,024 /documentum/ [Sent] Retry # 1 Directory-- 1,024 /documentum/dctm [Sent] Retry # 1 Directory-- 1,024 /documentum/dmadmin [Sent] Retry # 1 Directory-- 96 /documentum/doclink [Sent] Retry # 1 Directory-- 96 /documentum/lost+found [Sent] Retry # 1 Directory-- 96 /documentum/orcle734NT [Sent] Retry # 1 Directory-- 1,024 /documentum/sapshare_home [Sent] Retry # 1 Directory-- 96 /documentum/system_mail_files [Sent] Retry # 1 Directory-- 96 /documentum/users [Sent] Retry # 1 Directory-- 96 /documentum/work_temp [Sent] Retry # 1 Normal File-- 814 /documentum/.cshrc [Sent] Retry # 1 Normal File-- 347 /documentum/.exrc [Sent] Retry # 1 Normal File-- 341 /documentum/.login [Sent] Retry # 1 Normal File-- 446 /documentum/.profile [Sent] Retry # 1 Normal File-- 254 /documentum/.sh_history [Sent] Retry # 1 Normal File--37 /documentum/test.txt [Sent] Retry # 1 Normal File-- 357 /documentum/dsmerror.log [Sent] Selective Backup processing of '/documentum/*' finished without failure. Directory-- 1,024 /oracle7/ [Sent] Directory-- 1,024 /oracle7/EOFFICE [Sent] Directory-- 96 /oracle7/admin [Sent] Directory-- 2,048 /oracle7/bin [Sent] Directory-- 96 /oracle7/cronjobs_dir [Sent] Directory-- 1,024 /oracle7/dbs [Sent] Directory-- 96 /oracle7/guicommon2 [Sent] Directory-- 96 /oracle7/jdbc [Sent] Directory-- 2,048 /oracle7/lib [Sent] Directory-- 96 /oracle7/local [Sent] Directory-- 96 /oracle7/lost+found [Sent] Directory-- 1,024 /oracle7/md [Sent] Directory-- 1,024 /oracle7/network [Sent] Directory-- 96 /oracle7/nlsrtl3 [Sent] Directory-- 96 /oracle7/ocommon [Sent] Directory-- 96 /oracle7/oracore3 [Sent] Directory-- 5,120 /oracle7/orainst [Sent] Directory-- 1,024 /oracle7/otrace [Sent] Directory-- 96 /oracle7/plsql [Sent] Directory-- 1,024 /oracle7/precomp [Sent] Directory-- 1,024 /oracle7/rdbms [Sent] Directory-- 96 /oracle7/slax [Sent] Directory-- 1,024 /oracle7/sqlplus [Sent] Directory--
Session lost after upgrade to TSM 3.7.2.17
We upgrade a TSM client from ADSM 3.016 to TSM v. 3.7.2.17. Ever since the upgrade, the client has been experiencing session lost: This is from the dsmsched.log: 07/18/2001 08:18:50 TcpRead(): recv(): errno = 10058 07/18/2001 08:18:50 sessRecvVerb: Error -50 from call to 'readRtn'. 07/18/2001 08:18:50 ANS1809E Session is lost; initializing session reopen procedure. It seems that the sessions will lose when files larger than 79MB was being backed up. This did not happen when we used ADSM 3.1.06. We modified the dsm.opt during our upgrade to use all-local, instead of specifying the domains. The current include-exclude file acutally exclude few files. The network throughput was also different before and after the upgrate: Before upgrade: 07/01/2001 06:44:34 Network data transfer rate: 48.04 KB/sec 07/01/2001 06:44:34 Aggregate data transfer rate: 154.44 KB/sec After upgrade: 07/13/2001 14:10:02 Network data transfer rate: 28.74 KB/sec 07/13/2001 14:10:02 Aggregate data transfer rate130.99 KB/sec Any suggestions ?
Windows Client Tcp Read Errors
Is anyone out seeing this on their Windows NT clients (TSM Version 4.1.2). 07/18/2001 10:29:41 TcpRead(): recv(): errno = 10058 07/18/2001 10:29:41 sessRecvVerb: Error -50 from call to 'readRtn'. Some receive this and some don't even on the same same subnet. Bruce E. Lowrie Sr. Systems Analyst Information Technology Services Storage, Output, Legacy *E-Mail: [EMAIL PROTECTED] *Voice: ?(517) 496-6404 *Post:Mail: CO2111, (DC2 1st Floor) This e-mail transmission and any files that accompany it may contain sensitive information belonging to the sender. The information is intended only for the use of the individual or entity named. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information is strictly prohibited. Dow Corning's practice statement for digitally signed messages may be found at http://www.dowcorning.com/dcps. If you have received this e-mail transmission in error, please immediately notify the Security Administrator at mailto:[EMAIL PROTECTED] _ This message has been checked for all known viruses by the MessageLabs Virus Scanning Service. For further information visit http://www.messagelabs.com/stats.asp
Shared Memory driver on Server startup
Hi all! Today I installed a TSM 4.1x Server from scratch on a Solaris 8 machine. I started with installation of release 4.1.0.0 form the CD (server and client). I made a minimum Configuration in the server and client config files. Then I started the server once, only to test if it could run with this configuration. All was working well. To bring the Server an an actual level I removed all TSM packages except the license package an then installed server release 4.1.4.0 and the client release 4.1.3.0. I used the same configuration files as before and start the server. Now during the server startup I get following Error message ANR8289W Shared Memory driver is terminating due to error in creating a new thread Anybody any Idea what's wrong with my configuration. I checked the suggestions I found in the IBM Message file. There is a lot of free shared memory an the MAXConnections is set to 25. I'm really thankful for any tip Regards Clemens
Re: Shared Memory driver on Server startup
I do not think that Shared Memory is supported for TSM 4.1 under Solaris. I believe TSM 4.2 will provide this. - Original Message - From: Block, Clemens [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 18, 2001 1:50 PM Subject: Shared Memory driver on Server startup Hi all! Today I installed a TSM 4.1x Server from scratch on a Solaris 8 machine. I started with installation of release 4.1.0.0 form the CD (server and client). I made a minimum Configuration in the server and client config files. Then I started the server once, only to test if it could run with this configuration. All was working well. To bring the Server an an actual level I removed all TSM packages except the license package an then installed server release 4.1.4.0 and the client release 4.1.3.0. I used the same configuration files as before and start the server. Now during the server startup I get following Error message ANR8289W Shared Memory driver is terminating due to error in creating a new thread Anybody any Idea what's wrong with my configuration. I checked the suggestions I found in the IBM Message file. There is a lot of free shared memory an the MAXConnections is set to 25. I'm really thankful for any tip Regards Clemens
Re: Offsite volume in strange state
Quoting Prather, Wanda [EMAIL PROTECTED]: Bring the volume back (it's empty, anyway). Check it in, run AUDIT VOL FIX=YES. That usually fixes this problem. I had the volume retrieved from the vault and inserted into the tape library. TSM under OS/390 does not have a check-in procedure of its own. I changed the access to read/write and ran the 'audit volume' command. The command reported that it had created or corrected information for the volume. The status of the volume was EMPTY, as I had hoped. I changed the access back to offsite and attempted to execute a 'move drmedia' command to change the DR media status from vaultretrieve to onsiteretrieve. The command failed with the following message: ANRD ASVOL(2751): Volume 600206 cannot be deleted to SCRATCH - it still has SEGMENT references. Attempts to run the 'audit volume' command again fail because the access is offsite. Attempts to change the access to read/write or read-only fail with messages reporting internal server errors. Does anyone have any suggestions for clearing up the new inconsistency?
TransWin32RC(): Win32 RC 1 from FileRead(): ReadFile
Has anyone seen the following error on a WinNT system? This happened on a system running client v3.7.2.17, but I have not been able to reproduce it on a test box here. The error is preventing the partition from getting backed up. Thanks in advance. 07/10/2001 04:02:38 ANS4018E Error processing '\\ntschool1\d$\long path abbreviated\My Summer Experience Writing Seminar 119.doc': file name too long 07/10/2001 04:03:23 TransWin32RC(): Win32 RC 1 from FileRead(): ReadFile 07/10/2001 04:03:26 ANS1028S Internal program error. Please see your service representative.
Re: Offsite volume in strange state
The command failed with the following message: ANRD ASVOL(2751): Volume 600206 cannot be deleted to SCRATCH - it still has SEGMENT references. Attempts to run the 'audit volume' command again fail because the access is offsite. Attempts to change the access to read/write or read-only fail with messages reporting internal server errors. Does anyone have any suggestions for clearing up the new inconsistency? This sounds like APAR PQ45067 - applies to TSM 3.7.3 and up, fixed in 4.?. or in 3.7 run DSMSERV AUDITDB ARCHSTORAGE FIX=YES Tim Rushforth City of Winnipeg
AIX 4.3.3 and ML8
Has anyone successfully applied ML 8 to 4.3.3 and NOT have SCSI adapters and 3590 drives disappear? We just updated to ML8 and upon IPL lost one of the SCSI adapters and four of our 3590 drives, and running cfgmgr doesn't get them back. We are at 4.1.3.0 TSM server level, and the latest for Atape and atldd. Any ideas? Call support or reject the ML?? thanks lisa
Re: AIX 4.3.3 and ML8
I applied it a few weeks ago with no problems. Possibly the microcode level on the scsi adapters was too backlevel? Christopher Leven Senior Programmer/Analyst IBM Certified Specialist AIX Administration IBM Certified Specialist AIX Support IBM Certified Specialist RS6000/SP - PSSP 3.1 Garlock Sealing Technologies Division of Goodrich (Formerly BF Goodrich) 1666 Division Street Palmyra, New York 14522 *Voice: 315.597.3034 *Fax: 315.597.7250 *Email: [EMAIL PROTECTED] Please note new email address -Original Message- From: Lisa Cabanas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 3:57 PM To: [EMAIL PROTECTED] Subject: AIX 4.3.3 and ML8 Has anyone successfully applied ML 8 to 4.3.3 and NOT have SCSI adapters and 3590 drives disappear? We just updated to ML8 and upon IPL lost one of the SCSI adapters and four of our 3590 drives, and running cfgmgr doesn't get them back. We are at 4.1.3.0 TSM server level, and the latest for Atape and atldd. Any ideas? Call support or reject the ML?? thanks lisa
Re: AIX 4.3.3 and ML8
The CE just installed these less than a month ago-- we are sharing the drives between two TSM servers. I tried to find the microcode level, but couldn't (I am the TSM admin, and am (always) learning AIX. Would you please tell me what command to use, and what microcode level is current. The weird thing is that the other 5 SCSI adapters are found, as are two of the 3590 drives. thank you!! lisa Leven, Chris [EMAIL PROTECTED] 07/18/2001 03:03 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: (bcc: Lisa Cabanas/SC/MODOT) Subject:Re: AIX 4.3.3 and ML8 I applied it a few weeks ago with no problems. Possibly the microcode level on the scsi adapters was too backlevel? Christopher Leven Senior Programmer/Analyst IBM Certified Specialist AIX Administration IBM Certified Specialist AIX Support IBM Certified Specialist RS6000/SP - PSSP 3.1 Garlock Sealing Technologies Division of Goodrich (Formerly BF Goodrich) 1666 Division Street Palmyra, New York 14522 *Voice: 315.597.3034 *Fax: 315.597.7250 *Email: [EMAIL PROTECTED] Please note new email address -Original Message- From: Lisa Cabanas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 3:57 PM To: [EMAIL PROTECTED] Subject: AIX 4.3.3 and ML8 Has anyone successfully applied ML 8 to 4.3.3 and NOT have SCSI adapters and 3590 drives disappear? We just updated to ML8 and upon IPL lost one of the SCSI adapters and four of our 3590 drives, and running cfgmgr doesn't get them back. We are at 4.1.3.0 TSM server level, and the latest for Atape and atldd. Any ideas? Call support or reject the ML?? thanks lisa
Mismatch between bytes transferred and data in storage pool
I have a mismatch between the quantity of data being backed up overnight (according to the accounting log) and the amount of data within my disk storage pool in the morning. My accounting log says I've backed up 360 GB. The activity log confirms this (adding up entries like this one). 07/19/01 07:14:19 ANE4961I (Session: 6469, Node: NSYDMN10) Total number of bytes transferred:61.32 GB The entries all add up to 370 GB of data apparently transferred. The storage pool was empty before the backups started, did not migrate during the night, has a maximum size threshold of 'no limit', and indeed there were no tape mounts over night. There are no copygroups with a tape pool destination. However, the storage pool is only 215 GB in total, and was only 75% full once the backups had finished. The clients do not compress their data, not that that should make any difference. I'd appreciate any ideas to help explain what's going on. (Software levels: TSM Server 3.7.4, clients at 3.1 and 4.1) Thanks for any suggestions. Regards, Eric Winters
