Migration process unable to locate cluster element ....
Hi list, Using a TSM server v 5.1.6.2 on AIX 4.3.3, I'm sometimes getting following entry in activity log : 30.05.2003 22:36:02 ANRD dfmigr.c(3224): ThreadId56 Migration process 3464 unable to locate cluster element srvId=0, ck1=603 Should this error be considered as dangerous, and needing to open a PMR by IBM, or will TSM server survive it ? I also got that one : 29.05.2003 01:49:17 ANR0538I A resource waiter has been aborted. 29.05.2003 01:49:17 ANR0918E Inventory Query Backup for node XXX terminated - Concerning this error, it looks like every time I get the message, the scheduled backup job for involved node finishes with status Failed. What shall I do to avoid this kind of lock ? Thanks in advance ! Regards. Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
RMAN issue
Hi there, I have TSM 4.2 running on AIX 4.3.3 and I do a backup for ORACLE 8.1.7 in the same TSM server using RMAN TSM everyday. Sometimes the rman backup failed. Every time the backup failed, a tape drive error will be generated in the error log in the operating system. Could anyone tell me what is the problem and how can I solve it? This is the RMAN log: RMAN-08504: input archivelog thread=1 sequence=17603 recid=22515 stamp=495480018 RMAN-08504: input archivelog thread=1 sequence=17604 recid=22516 stamp=495480752 RMAN-08504: input archivelog thread=1 sequence=17605 recid=22518 stamp=495481650 RMAN-08504: input archivelog thread=1 sequence=17606 recid=22519 stamp=495482801 RMAN-08504: input archivelog thread=1 sequence=17607 recid=22520 stamp=495484635 RMAN-08504: input archivelog thread=1 sequence=17608 recid=22522 stamp=495486622 RMAN-08504: input archivelog thread=1 sequence=17609 recid=22523 stamp=495489370 RMAN-03026: error recovery releasing channel resources RMAN-08031: released channel: t1 RMAN-08031: released channel: t2 RMAN-08031: released channel: t3 RMAN-08031: released channel: t4 RMAN-00571: === RMAN-00569: === ERROR MESSAGE STACK FOLLOWS === RMAN-00571: === RMAN-10035: exception raised in RPC: O RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE ATE RMAN-10035: exception raised in RPC: O RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE ATE RMAN-10035: exception raised in RPC: O RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE ATE RMAN-03015: error occurred in stored script prod_archivebackup RMAN-03007: retryable error occurred during execution of command: backup RMAN-07004: unhandled exception during command execution on channel t1 RMAN-10035: exception raised in RPC: ORA-19506: failed to create sequential file , name=hgeojmjv_1_1, parms= ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: ANS1474E (RC-451) An error occurred using the Shared Memory protocol RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE ATE Recovery Manager complete. This is the AIX error log: IDENTIFIER: D1A1AE6F Date/Time: Sun Jun 1 19:24:16 Sequence Number: 29671 Machine Id: 0050675A4C00 Node Id: hnab Class: H Type: INFO Resource Name: rmt3 Resource Class: tape Resource Type: 3590 Location: 40-58-01 VPD: ManufacturerIBM Machine Type and Model..03590E1A Serial Number...000C5897 Device Specific.(FW)E32E Loadable Microcode LevelA0B00E26 Description AAA0 Probable Causes TAPE DRIVE Failure Causes TAPE DRIVE Recommended Actions REFER TO PRODUCT DOCUMENTATION FOR ADDITIONAL INFORMATION Detail Data DIAGNOSTIC EXPLANATION 3100 0044 6140 0130 3030 3030 3030 3233 3245 3537 3030 3941 3030 3030 3030 4646 4335 3539 4335 3539 3830 3030 4942 4D31 332D 3030 3030 3030 3043 3538 3937 3033 3539 3045 3141 Regards, Abdulaziz Almaummar
Re: MOVE NODEDATA on a copypool doesn't process anything
On Mon, Jun 02, 2003 at 01:36:12PM +0100, Wilcox, Andy wrote: I found that you can't do a move nodedata against a copypool. You can, but you can't move files out of one copypool into another. This is documented. You have to move the data from the onsite pool to another onsite pool and copy this to a different copypool. The data in the old copypool is then inconveniently left around (although existing copy group expiration value will apply). You are describing a different phenomenon, but it would be nice if there were a way to address this. Even a DELETE NODEDATA would be handy. :-) Although... what would happen in the following scenario: - NODE_A is backed up to primary pool PRIM01. - PRIM01 gets backed up to COPY01. - The TSM admin does a MOVE NODEDATA NODE_A FROM=PRIM01 TO=PRIM02 - After that, PRIM02 gets backed up to COPY02. - All copypool-volumes are taken offsite - A disaster strikes and the DR procedure is started. - In a new TSM server, NODE_A is being restored directly from copypool-volumes. Which volumes will the server choose? This could be relevant, since COPY01 might be noncollocated while COPY02 is collocated. This can make a large difference during DR. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: ACN5304E when I use the CLI to backup Exchange
Niklas, It is looking at the Information Store service. Sometimes this occurs when you are running under a Windows userid that does not have Administrator authority to view the registry. For example, this may occur when you are running from a scheduler service that is being run under a different userid. If you are still having problems, please call IBM support and a trace can be examined to find out what the problem is. Thanks, Del When I use the GUI I can backup my Exchange storage groups without problem, but when I run the CLI, tdpexcc.exe, I get ACN5304E, Unable to open service to determine if running or not Have anyone seen this??? Which service does it want to open???
Re: Virtual Volumes on same server (Was Create more then one backu pset to one tape)
Well I found out that this is not supported. APAR IC35654 - Virtual Volumes with source and target servers residing on same server is not supported. -Original Message- From: Rushforth, Tim [mailto:[EMAIL PROTECTED] Sent: May 29, 2003 1:19 PM To: [EMAIL PROTECTED] Subject: Re: Create more then one backupset to one tape Cool! Thanks for this post Steven - I didn't realize that this could be done with one server. I want to use backupsets but never considered because of the 1 volume per backupset limit. For my purposes I wish backupsets could use storage pools as a destination - this method gives me that. I'm curious if anyone is using this method - ie one TSM server setup to send Virtual Volumes to itself. Is there anything to watch out for in this configuration? Now if only the client GUI could be used to restore individual files from a backupset Tim Rushforth City of Winnipeg -Original Message- From: Steven Pemberton [mailto:[EMAIL PROTECTED] Sent: May 15, 2003 5:45 PM To: [EMAIL PROTECTED] Subject: Re: Create more then one backupset to one tape On Friday 16 May 2003 00:46, Christian Svensson wrote: Hi Everyone! Do anyone know if is possible to create more then one backupset to one tape. Becuse each backupset is only 5 GB large and I only have AIT-3 tapes to send the backupset data to. And I going to use this backupset to send offsite. Actually TSM uses a new *volume* per backupset. Normally this is equal to a new tape, but by using server-to-server virtual volumes you can effectively consolidate multiple backupsets onto a single physical volume. This is best done between two TSM servers, where the on-site TSM server sends the backupset (virtual volume) to the off-site TSM server electronically via the server-to-server communucations. Of course this requires that you have a sufficiently fast WAN... Alternatively you could define a loopback TSM server-to-server definition. The TSM server then sends the backupset (virtual volume) to itself via the server-to-server definition. The TSM server can then consolidate the backupset (virtual volume) onto a single physical volume. Finally, if you want to send this data off-site, you would need to either create a copypool of the storage pool containing the backupset volumes, or simply checkout the primary storage pool volumes and send them offsite. One problem with this approach is that the backupsets are no longer external to TSM, and are actually stored in the normal storage pools. Whether this is useful to you depends on why you need to create backupsets in the first place. If you are just creating backupsets for monthly archival purposes, then it's probably acceptable. But, if you want the ability to restore the backupsets via a locally attached tape drive on a client, then you should not use this method. Regards, Steven P. -- Steven Pemberton Mobile: +61 4 1833 5136 Innovative Business Knowledge Office: +61 3 9820 5811 Senior Enterprise Management ConsultantFax: +61 3 9820 9907
Re: MOVE NODEDATA on a copypool doesn't process anything
From: Jurjen Oskam [mailto:[EMAIL PROTECTED] You are describing a different phenomenon, but it would be nice if there were a way to address this. Even a DELETE NODEDATA would be handy. :-) There is. It's called DELETE FILESPACE. :o) -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: MOVE NODEDATA on a copypool doesn't process anything
On Mon, Jun 02, 2003 at 11:16:44AM -0500, Stapleton, Mark wrote: You are describing a different phenomenon, but it would be nice if there were a way to address this. Even a DELETE NODEDATA would be handy. :-) There is. It's called DELETE FILESPACE. :o) Well, yes, but DELETE FILESPACE isn't able to delete things from only a certain storagepool, which would be the point of that fictional DELETE NODEDATA command. Although, granted, an option such as FROMSTG=storagepool to DELETE FILESPACE would work too. :-) -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
virtual volumes on target server - when do they go away?
I've been testing a remote Copypool setup, and now want to clean up ... As the last thing on the (temporary) source server, I deleted all virtual volumes, and checked via RECONCILE VOLUMES that they were all (logically) gone. On the target server though, I still have the non-empty archive filespace ADSM.SERVER belonging to the source node (TYPE=SERVER), which can't be deleted via DELETE FILESPACE. So far, a few expirations have been run on the target server without changing things. Will the contents of the ADSM.SERVER filespace eventually go away, and if so, when? Wolfgang J. Moeller, Tel. +49 551 201-1516/-1510, [EMAIL PROTECTED] GWDG, D-37077 Goettingen, F.R.Germany |Disclaimer: No claim intended! http://www.gwdg.de/~moeller/ [EMAIL PROTECTED] [EMAIL PROTECTED]
Going from 5.1.0 to 5.1.5
I'm going from TSM 5.1.0 to 5.1.5 on OS/390 2.10, do I need to use the DBUPGRADE parameter when starting it with 5.1.5 initially? thanks Gene
Re: Windows 2000 scheduled backup problem
Here is a schedule I use. This is defined on a 5.1.5 TSM server on AIX O/S going to 5.1.5 W2k Client. I also have incorporated an exclude file to specify the exclusion of certain files. I wondered if the options portion of the schedule might help? I just ran a test to a directory on the C: drive, I entered the schedule with the options=-subdir=yes and objects=c:\testdir\* - please note, the - on the sudir is important. The job ran perfectly, but I am running archive versus backup. Maybe there is some help info in the schedule definition below: Define schedule: nt_dom nt_weekly type=client description=W2K weekly backup C: and E: drives action=archive options=-subdir=yes objects=C:\* E:\* startdate=today starttime=10:00 duration=1 durunits=Hours period=1 perunits=Days dayofweek=Sunday -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 7:14 AM To: [EMAIL PROTECTED] Subject: Re: Windows 2000 scheduled backup problem As directed from the ref guide, I changed my objects to 'C:\Research Folder\*' Now the schedlog shows every file on the machine backing up, so I am back to where I started. Are you certain that this is the only client schedule associated with the client...that there is no other server-defined schedule with a null Objects spec such that the Incremental Backup is following the dictates of your dsm.opt file (i.e., Domain specs, or absence thereof)? Do 'Query ASSOCiation' to verify what schedules are associated with the client. Do a full 'Query SCHedule Format=Detailed' to check for other schedules. The client's Backup log should indicate exactly what it was dispatched to do, so if you don't see C:\Research Folder\* reflected in it, something else is likely going on. Assure that there is no non-TSM time initiated backup execution occurring. Indirectly related: do 'dsmc query inclexcl' to verify that any client- or server-based Include-Exclude lists are as they should be. If you made any client options changes, assure that you restarted the client scheduler to absorb them. If necessary, post the output of 'Query SCHedule ... Format=Detailed' on the suspect client schedule, and the top 20 or so lines from the client log so that we may evaluate that data. Richard Sims, BU
Re: virtual volumes on target server - when do they go away?
delete filespace nodename ADSM.SERVER type=server That should get rid of the filespace. Jim Sporer At 07:15 PM 6/2/2003 +0200, you wrote: I've been testing a remote Copypool setup, and now want to clean up ... As the last thing on the (temporary) source server, I deleted all virtual volumes, and checked via RECONCILE VOLUMES that they were all (logically) gone. On the target server though, I still have the non-empty archive filespace ADSM.SERVER belonging to the source node (TYPE=SERVER), which can't be deleted via DELETE FILESPACE. So far, a few expirations have been run on the target server without changing things. Will the contents of the ADSM.SERVER filespace eventually go away, and if so, when? Wolfgang J. Moeller, Tel. +49 551 201-1516/-1510, [EMAIL PROTECTED] GWDG, D-37077 Goettingen, F.R.Germany |Disclaimer: No claim intended! http://www.gwdg.de/~moeller/ [EMAIL PROTECTED] [EMAIL PROTECTED]
OS/390 server and USS
We run a 5.1.6.2 server under OS/390. We have a separate test server running in a logical partition used for system programmer testing. The test TSM server stopped working when we installed a new release of Top Secret, our security product, on the system programmer test partition. The server fails during initialization with messages and symptom dump contents indicating that the user running the server is not authorized to use OMVS, which is part of Unix System Services. The server is normally run as a started task with no associated user and no security checking. The server will initialize if it is run as a batch job submitted from a TSO user with authorization for Unix System Services. My coworkers are still skeptical about the idea that the TSM server uses Unix System Services. Does anyone know for sure whether it does or not?
Database Cleanup
I noticed that after awhile, my database gets quite large. Assuming that it's consistent, unloaddb/loaddb seems to compress out all of the junk and makes it much smaller. Is there a way to check the database for how much space might be recovered by doing an unloaddb/loaddb? Currently, I'm at about 100GB.
EXPORT NODE to SERVER question/issue....
I am now on my fourth attempt to do an EXPORT NODE to SERVER, from my zOS TSM server (5.1.6.4) to our AIX TSM server (5.1.6.2). The reason I am on my fourth attempt is that it seems to quit/drop-dead/whatever for no apparent reason I can fathom. The last attempt, while the final status said SUCCESSFULL, further digging for an error message found one that said INCOMPLETE (not sure why a previous failure still registers as successfull but I am not concerned about this, right now). Eventhough each attempt seems to move some data, nothing seems to appear on the receiving end. My question(s): 1. Where is the stuff being imported/exported going if it doesn't seem to appear on the other end ? 2. If it actually does send some files across and I run the EXPORT again, does it just skip the files previously sent ? 3. What if an *EXACT* copy of the file(s) I am export/importing already exists on the receiving end ? Does it ignore it ?
Re: MOVE NODEDATA on a copypool doesn't process anything
Over two years ago I asked for the following enhancements: add the node= parameter to move data command add the stgpool= parameter to delete filespace command I still believe these would provide a great enhancement to storage management. Al Jurjen Oskam [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/02/03 12:01 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: MOVE NODEDATA on a copypool doesn't process anything On Mon, Jun 02, 2003 at 11:16:44AM -0500, Stapleton, Mark wrote: You are describing a different phenomenon, but it would be nice if there were a way to address this. Even a DELETE NODEDATA would be handy. :-) There is. It's called DELETE FILESPACE. :o) Well, yes, but DELETE FILESPACE isn't able to delete things from only a certain storagepool, which would be the point of that fictional DELETE NODEDATA command. Although, granted, an option such as FROMSTG=storagepool to DELETE FILESPACE would work too. :-) -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Web submission of OS/390 server problem
I am attempting to use the new and improved IBM support pages to open an incident relating to our OS/390 TSM server. At the beginning of the process I am presented with a list of 161 products and asked to pick one. There are entries for TSM server code under Unix, AS/400, Windows NT, and even OS/2. There is no entry immediately recognizable as being for TSM server code under OS/390. Which of the 161 products am I supposed to choose?
Re: Database Cleanup
I noticed that after awhile, my database gets quite large. Assuming that it's consistent, unloaddb/loaddb seems to compress out all of the junk and makes it much smaller. Is there a way to check the database for how much space might be recovered by doing an unloaddb/loaddb? Currently, I'm at about 100GB. A frequently asked question. There is no junk in the database. What you are achieving, at the expense of downtime and some jeopardy, is a short-lived compaction of the data in the database. Reasonable Policy definitions, expiration, and disposal of obsolete filespaces is the ultimate salvation for a TSM database. Don't get into the habit of doing unloaddb/loaddb. As the expression goes, It's a database Richard Sims, BU
Re: OS/390 server and USS
We run a 5.1.6.2 server under OS/390. ... The release level of the OS/390 may be a factor... ... My coworkers are still skeptical about the idea that the TSM server uses Unix System Services. Does anyone know for sure whether it does or not? Page 65 of the 5.2 Getting Started manual talks about TSM using USS at OS/390 release 5 or higher, for sockets in TCP/IP communication. Richard Sims, BU
Re: TSM WinNT Restore Procedures
I really enjoyed the replies to this question. I have W2k machines I am backing up / restoring. I choose to use Archive for the backup method. I tried to backup the system state with TSM, I did not consistently get a good backup of the system state, meaning, the backup reported success. When I did a test recovery it would fail. I opted not to use TSM systemstate backup, I have a prescript that runs a cmd script, that runs the W2K O/S utility to backup the system state info, I save the file in a directory on the C: drive this same script runs the msinfo exe and I save the config information in the same directory. I will always know the O/S level and Service Pack levels before I begin the restore. I do an Archive of the C: drive and pickup the system state backup this way. My recovery process is this: Install base O/S from Microsoft CD. Apply service packs Install driver to get a network adaptor working. Install TSM client. Retrieve the Data via the GUI. Do not reboot when Retrieve is done. Run the W2k O/S utility to restore the systemstate saved to the C: drive. Reboot. -Original Message- From: Christian Bagard [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 12:02 PM To: [EMAIL PROTECTED] Subject: Re: TSM WinNT Restore Procedures Hello, We use the following process : 1.. Install system NT with Microsoft CDRom on another disk than C: Then install the service pack. 2.. Copy boot.ini , which is on C:, in boot.bck . 3.. Install on the same disk TSM client. Customize TSM client with the same name than the one to restore. 4.. Launch GUI of TSM client and select all C: and restore. 5.. With Edit (wordpad, etc.) open the file boot.ini restored. 6.. Copy at the end of this file the content of boot.bck. boot.ini contains now two adresses of boot : the one of the restored system (which doesn't work yet) and the one of the installed system (which is working). 7.. Then copy two other files from the installed system to the restored system : WINNT/SYSTEM32/HAL.DLL WINNT/SYSTEM32/NTOSKRNL 8.. Reboot the server on the restored NT system. 9.. Relaunch GUI of client TSM and ask for a restoration of the registry base with selecting system object. 10.. Reboot the server on the restored NT system. 11.. Verify that it works fine. 12.. When restore of C: is OK, it's possible to delete NT system on the other disk. Then modify boot.ini to delete the boot address of the installed NT system. 13.. Restore the other disks with the GUI TSM client. It works and you are less dependant of the hardware. I hope it will help ! Ask if you need more Christian Bagard SOS-Restore (France) [EMAIL PROTECTED] - Original Message - From: Ruth Peters [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 5:37 PM Subject: TSM WinNT Restore Procedures Hi TSM-ers, My TSM server is AIX 5.2.1 with TSM 5.1.6.3 My NT Client is 4.0 with Service Pack 56 with TSM 5.1.5.0 I know this issue has come across the board before, however I need to revisit it. We are in the process of testing our NT 4.0, and 2000 clients in preparation for our July 2 disaster recovery test. The problem we are having is that we are trying to restore to a machine with different hardware. We have just implemented NT and 2000 into our TSM backup and recovery process, and this is the first time that we are attempting a restore. We have successfully restored the 2000 machine but we are struggling with the NT recovery. We have reviewed the recommended redbooks and the Summary BMR Procedures for Windows NT, however we are still having problems. I know that TSM only supports Bare Metal restores using Identical hardware, however I also know that some of you wizards out there have done this. Does anyone have documentation of these procedures that they don't mind sharing?? Ruth Peters, Dasd Storage Administrator Watkins Motor Lines, Inc. --IT/HDQ [EMAIL PROTECTED] 800-284-4544 Ext. 5452 (863) 688-6662 x5452
Re: TSM Backup of open files
I experience the same condition when I backup my w2k servers (files failed to be backed up due to in use), I run 5.1.5 TSM client and 5.1.5 on AIX TSM server. While the backup says its successful (to address Eric van Loon's reply) there is always the concern, it this an important file to the success of my recovery? I have abandoned using TSM to backup the system state files for this very reason. I'm looking forward to trying 5.2 if it will indeed address the open file issue. Jackie -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:27 AM To: [EMAIL PROTECTED] Subject: Re: TSM Backup of open files Well, to be more specific, the current TSM version IS able to backup open files. Indeed, 5.2 will offer a built-in locked file manager which will allow you to backup LOCKED files. Shawn Price stated: I have 9 Win2K servers running various versions of the TSM Client that will have a status of 'Failed' because of two or three log files. Is there something I'm missing or is this normal. Which files is TSM skipping? A skipped file should not result in a backup state of failed. This is a known bug in older 4.2 level clients. Which level are you running? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Kamp, Bruce [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2003 20:59 To: [EMAIL PROTECTED] Subject: Re: TSM Backup of open files It is my understanding that version 5.2 will have support for backing up open files --- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E-mail: [EMAIL PROTECTED] Phone: (954) 987-2020 x4597 Fax: (954) 985-1404 --- -Original Message- From: Shawn Price [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2003 2:31 PM To: [EMAIL PROTECTED] Hello all, I was wondering if Tivoli can actually backup an open file (such as a system log file)? I have 9 Win2K servers running various versions of the TSM Client that will have a status of 'Failed' because of two or three log files. Is there something I'm missing or is this normal. BTW, the server is AIX 4.3.3 running TSM 4.2 and the clients again are Win2k servers with either 4.x or 5.x versions of the client. Thanks Shawn Price ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: EXPORT NODE to SERVER question/issue....
When you do a server to server export the data ends up in your archive storage pool as a single file. If for some reason the export fails before completion you lose everything. We had some rather large nodes that we exported that took upwards of 10 to 15 hours. We would occasionally have network problems that would require us to start from scratch. To get around the problem we started doing the exports by filespace. Jim Sporer At 04:07 PM 6/2/2003 -0400, you wrote: I am now on my fourth attempt to do an EXPORT NODE to SERVER, from my zOS TSM server (5.1.6.4) to our AIX TSM server (5.1.6.2). The reason I am on my fourth attempt is that it seems to quit/drop-dead/whatever for no apparent reason I can fathom. The last attempt, while the final status said SUCCESSFULL, further digging for an error message found one that said INCOMPLETE (not sure why a previous failure still registers as successfull but I am not concerned about this, right now). Eventhough each attempt seems to move some data, nothing seems to appear on the receiving end. My question(s): 1. Where is the stuff being imported/exported going if it doesn't seem to appear on the other end ? 2. If it actually does send some files across and I run the EXPORT again, does it just skip the files previously sent ? 3. What if an *EXACT* copy of the file(s) I am export/importing already exists on the receiving end ? Does it ignore it ?
Re: TDP 4 MSSQL restore
Thanks for everybody, perfect timing when I got this email coz we have a problem restoring large database. The restore was successful after we modified the value of this option from 300 to 18000 in TSM server. Regards, -Original Message- From: Vladimir Zykov [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 2:04 PM To: [EMAIL PROTECTED] Subject: Re: TDP 4 MSSQL restore Thanks, Del I've increased COMMTIMEOUT up to 5 hrs. Restore went OK. - Original Message - From: Del Hoobler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 30, 2003 10:24 PM Subject: Re: TDP 4 MSSQL restore Vladimir, Yes. I know what the problem is. There is a known situation that you must handle when restoring very large SQL databases. Basically, this is what happens: 1. The database is started to be restored. A small amount of data is restored from the TSM Server. 2. The SQL server looks at that data and sets up the database according to the information that it finds in first part of the backup data. The SQL Server preformats the files. If the database is large... the preformatting and initialization of the files could take a long time. The SQL Server is spending most of the time preformatting the files. 3. After the SQL Server is done preformatting the files, it continues restoring the rest of the data. The SQL Server is still working to preformat the files when the COMMTIMEOUT on the server times out and cancels the operation. The way to get around this issue is to increase the COMMTIMEOUT value to something very large. It needs to be large enough to allow the SQL Server to finish preformatting the files. Increase the COMMTIMEOUT to something very large (like 5 hours which is 18000 seconds) then... retry the restore. This is known issue and there is a requirement opened against the TSM Server to allow COMMTIMEOUT to be set on a NODENAME basis... since you don't normally want to set COMMTIMEOUT that large for all nodes. By the way, it is also documented in the IBM Support Solutions Database under reference # 1079494. Thanks, Del -- This message was sent with an unlicensed evaluation version of Novell NetMail. Please see http://www.netmail.com/ for details. This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.
Re: OS/390 server and USS
Thomas, My coworkers are still skeptical about the idea that the TSM server uses Unix System Services. Does anyone know for sure whether it does or not? We are at os390 2.10 TSM definitely uses unix system services. I had a pmr at TSM 4.2.2 concerning inability to restore backupsets made under daylight saving time during GMT and vice versa. It turned out that because we not setting the TZ (time zone) environment variable in the TSM started task, TSM was picking up the the default value from unix system services eg. the specification in your USS environment /etc/profile ((see Unix System Services User's Guide, section 4.9) In our case this default value was not allowing for the clock change. Hope this helps 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. **
Re: ACN5304E when I use the CLI to backup Exchange RESOLVED
Hello I was logged in as a local admin, when I logged in as a domain admin it worked fine Regards Niklas Lundström -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED] Sent: den 2 juni 2003 15:42 To: [EMAIL PROTECTED] Subject: Re: ACN5304E when I use the CLI to backup Exchange Niklas, It is looking at the Information Store service. Sometimes this occurs when you are running under a Windows userid that does not have Administrator authority to view the registry. For example, this may occur when you are running from a scheduler service that is being run under a different userid. If you are still having problems, please call IBM support and a trace can be examined to find out what the problem is. Thanks, Del When I use the GUI I can backup my Exchange storage groups without problem, but when I run the CLI, tdpexcc.exe, I get ACN5304E, Unable to open service to determine if running or not Have anyone seen this??? Which service does it want to open???
Re: ACN5304E when I use the CLI to backup Exchange RESOLVED
As is said in the monthly TSM FAQ (which I haven't posted this month! sorry, folks) it states: 04-19. My scheduled backups fail (or are incomplete), but my manual ones work fine. Why? This almost always occurs in Windows servers, and it's always a Windows permissions problem. By default, the TSM scheduler runs as a service with System account privileges. By default all Windows files are read/writeable by System; however, there are a few Windows admins (and applications) out there who remove System privileges from files. (For what reasons, I cannot imagine.) When a manual backup is run, it uses the permissions of the account of the person who is logged on, not the System account. (You can't log on as System, as it's a non-interactive account.) The real solution is reset all files to have System read/write privileges. If that's not possible, you need to alter the scheduler service so as to use a logon ID with privileges that have access to all files that you want backed up. Remember that if that logon ID changes passwords, you're going to have to update the service properties to reflect the new password. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 -Original Message- From: Niklas Lundstrom [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2003 4:37 AM To: [EMAIL PROTECTED] Subject: Re: ACN5304E when I use the CLI to backup Exchange RESOLVED Hello I was logged in as a local admin, when I logged in as a domain admin it worked fine Regards Niklas Lundström -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED] Sent: den 2 juni 2003 15:42 To: [EMAIL PROTECTED] Subject: Re: ACN5304E when I use the CLI to backup Exchange Niklas, It is looking at the Information Store service. Sometimes this occurs when you are running under a Windows userid that does not have Administrator authority to view the registry. For example, this may occur when you are running from a scheduler service that is being run under a different userid. If you are still having problems, please call IBM support and a trace can be examined to find out what the problem is. Thanks, Del When I use the GUI I can backup my Exchange storage groups without problem, but when I run the CLI, tdpexcc.exe, I get ACN5304E, Unable to open service to determine if running or not Have anyone seen this??? Which service does it want to open???
Monthly TSM FAQ 06/2003
This Frequently Asked Question list for the ADSM-L mailing list is
posted on the first day of each month. It was created to cut down on the
number of questions that are repeated regularly in the ADSM-L mailing
list from vm.marist.edu. I would be grateful for any requests to include
additional material. (Please send them directly to me, rather than to
the list.)
updated 05/09/2003
* Questions marked with * are new or improved since the last posting.
QUESTIONS
01. About the list itself
01-01. How do I subscribe to ADSM-L?
01-02. How do I unsubscribe to ADSM-L?
01-03. Why don't I see the questions I post to ADSM-L?
01-04. How can I see the questions I post to ADSM-L?
01-05. Who decides what questions go on ADSM-L?
01-06. Is there a digest or archive of ADSM-L?
01-07. How do I get more information about ADSM-L?
01-08. Does IBM/Tivoli participate in ADSM-L?
01-09 *How can I get just a digest of ADSM-L, instead of all the
postings?
02. Types of questions asked
02-01. What subjects are covered in this list?
02-02. What kinds of questions can be asked?
02-03. What kinds of questions can I expect answers to?
02-04. What levels of netiquette are expected?
02-05. What's the first thing to do when I have a question about TSM?
02-06. What's the second thing to do when I have a question about TSM?
02-07. What's the third thing to do when I still have a question about
TSM?
02-08. What's the fourth thing to do when I STILL have a question about
TSM?
02-09. What's the fifth thing to do when I *STILL* have a question
about
TSM?
02-10. What's the last thing to do when I *STILL* have a question about
TSM?
02-11. What are those out of office messages I keep seeing in the
list?
02-12. What's the single best thing I can do to improve the list?
02-13. Why don't I get answers to my I need comparisons between TSM
and
brandX backup software questions?
02-14. What kinds of things shouldn't I post on ADSM-L?
02-15. Is there some sort of acronym list?
02-16. Whatever happened to Richard Sims?
03. Available TSM resources
03-01. What FAQs are already out there?
03-02. What other sources of help can I find?
03-03. How do I get official TSM support?
04. Frequently-asked questions on ADSM-L
04-01. Is it called ADSM, or TSM, or ITSM? What's the deal here?
04-02. What are backupsets? How can I use them?
04-03. How does TSM do full/incremental/differential backups, just like
my old backup software fillintheblank used to?
04-04. How do I unsubscribe to ADSM-L?
04-05. How do I do mailbox-level restores of Exchange using the Tivoli
Data
Protection Agent for Exchange?
04-06. How do I force TSM to do a full backup of a client?
04-07. Where can I download the latest version of TSM/TDP?
04-08. What's the very first thing I do after TSM is delivered to me?
04-09. I'm getting message ANRX from the TSM server. What does it
mean?
04-10. I'm getting message ANSX from the TSM client. What does it
mean?
04-11. My large-scale restores are slow. How can I speed them up?
04-12. How do I back up normally open files, like database files?
04-13. What's all this about TSM and SQL select statements?
04-14. My boss wants disaster recovery procedures. What's the best way
to do it?
04-15. How do I get TSM to report problems to me?
04-16. Why does version X of TSM have this bad bug in it?
04-17. How come my copy pool tape reclamation runs so slowly?
04-18. I keep getting these server out of license compliance
messages.
Why?
04-19. My scheduled backups fail (or are incomplete), but my manual
ones
work fine. Why?
04-20. While backleveling my TSM client from 4.2.1 to 4.1.3, I get a
downlevel message. Why?
04-21. Why do I get an ANR1440I All drives in use. Process being
preempted by higher priority operation message when my
storage pool backup fails?
04-22. I've deleted all data from a tape volume, but it hasn't come
back
as a scratch tape. Why?
04-23. What is this ANRD error message. I don't understand it.
04-24. I'm upgrading my TSM server/client from version X.X to version
Y.Y.
Any pitfalls?
04-25. How do I restore one client's data onto another client?
04-26. Will my new tape library work with TSM?
04-27. My Windows client backs up the same 3,000 files or so everyday.
Why?
04-28. I'm moving TSM to a new physical server. What's the best way
to do that?
04-29. How do I back up my NetWare NDS license files?
04-30. What's all this fuss about cleanup backupgroups?
04-31. I'm trying to include some files for backups, but it's not
working. Why?
04-32. Can I put TSM db and log volumes on raw devices?
04-33. Why is my client backup {taking so long|running so
slowly|sluggish}?
04-34. I have a tape volume that Q
SANERGY vs File Drives - Lan free to disk
HI TSMers, On a LAN free setup (pure AIX, SAN), is there a big difference between using FILE device class drives vs using SANergy? What does SANergy really do? I have tested FILE drives and it sits on NFS. I also know that it is Sequential just like the tapes and needs more Drives to support multiple node concurrently backing up. I guess what I'm looking for is something like Disk device class. Can SANergy support the Disk Device class or is it also Sequential File Devices. What's the difference? Any opinion would be greatly appreciated. Thanks in advance. inotzki TSM System Administrator - Do you Yahoo!? Free online calendar with sync to Outlook(TM).
Re: EXPORT NODE to SERVER question/issue....
H.. Thanks for the details. One question, you specifically said the data ends up in your archive storage pool as a single file. Is this true about the ARCHIVE pool ? Why the ARCHIVE pool ?Which ARCHIVE pool ?Can I control this ? If this really is true, this is probably the cause of my problem since I have a very SMALL archive pool on the receiving server since I don't do much if any archiving there ! Jim Sporer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/02/2003 05:16 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: EXPORT NODE to SERVER question/issue When you do a server to server export the data ends up in your archive storage pool as a single file. If for some reason the export fails before completion you lose everything. We had some rather large nodes that we exported that took upwards of 10 to 15 hours. We would occasionally have network problems that would require us to start from scratch. To get around the problem we started doing the exports by filespace. Jim Sporer At 04:07 PM 6/2/2003 -0400, you wrote: I am now on my fourth attempt to do an EXPORT NODE to SERVER, from my zOS TSM server (5.1.6.4) to our AIX TSM server (5.1.6.2). The reason I am on my fourth attempt is that it seems to quit/drop-dead/whatever for no apparent reason I can fathom. The last attempt, while the final status said SUCCESSFULL, further digging for an error message found one that said INCOMPLETE (not sure why a previous failure still registers as successfull but I am not concerned about this, right now). Eventhough each attempt seems to move some data, nothing seems to appear on the receiving end. My question(s): 1. Where is the stuff being imported/exported going if it doesn't seem to appear on the other end ? 2. If it actually does send some files across and I run the EXPORT again, does it just skip the files previously sent ? 3. What if an *EXACT* copy of the file(s) I am export/importing already exists on the receiving end ? Does it ignore it ?
