Re: DB backup on a DDS drive
Hi Michal, one more way would be backing up the TSM-database to a second TSM-Server using virtual volumes. Setting up a TSM-Server on a workstation is a quick task, and setting up the vv is rather straightforward. If you take a machine that is backed up anyway, it will even be free of cost, as the cpu is charged, regardless if you run a TSM-client or a TSM server. One more benefit: if you use the same OS, you could even recover the whole TSM-server to this alternative hardware if you lose the primary machine. Have a go, it´s really worth it! Regards, Markus -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. __ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.
Re: SQL2062N: Reason code =406
I have changed the permission for the errorlog. Still I still have the error. On another database server , when I execute dsmapipw in /usr/opt/db2_08_01/adsm64/dsmapipw, I received Segmentation Fault (coredump) and my offline fullbackup failed with error : SQL2079N Return code 30. Did I execute the correct dsmapipw? There 2 folders, adsm and adsm64 and I execute the dsmapipw in adsm64. Appreciate if anyone could give me any suggestions to troubleshoot this 2 errors. Thanks, Regards, Zareyna Salim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jacques Van Den Berg Sent: Monday, July 10, 2006 10:05 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SQL2062N: Reason code =406 Check file permissions for your errorlog file... Jacques van den Berg TSM / SAP Storage Administrator Pick 'n Pay IT Email : [EMAIL PROTECTED] Tel : 021 - 658 1711 Fax : 021 - 658 1699 Mobile : 082 - 653 8164 Dis altyd lente in die hart van die mens wat God en sy medemens liefhet (John Vianney). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of zareyna Sent: Monday, July 10, 2006 11:14 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SQL2062N: Reason code =406 Hi all, Has anyone has ever countered this problem: SQL2062N An error occurred while accessing media /home/db2admin/sqllib/adsm/libtsm.a. Reason code: 406. Below are the steps that I have done: 1. Setup the environment variables as below DSMI_DIR=/usr/tivoli/tsm/client/api/bin64 DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin64/dsm.opt DSMI_LOG=/usr/tivoli/tsm/client/api/bin64 export DSMI_DIR DSMI_CONFIG DSMI_LOG 2. Copy the dsm.opt and dsm.sys in the /usr/tivoli/tsm/client/api/bin64 /usr/tivoli/tsm/client/api/bin64 # ls -l total 12168 -r 1 root system 108626 Jul 05 12:33 db2uext2.c -rwxrwxrwx 1 root system 763 Jul 10 16:27 dsm.opt -rw-r--r-- 1 root system 782 Sep 17 2005 dsm.opt.smp -rw--- 1 root system 1077 Jul 10 14:08 dsm.sys DSM.OPT SErvername TSM_Server1 DSM.SYS SErvername TSM_SERVER1 COMMMethod TCPip tcpport1500 TCPServeraddress 10.211.214.18 tcpclientaddress 10.211.214.11 passwordaccess generate schedmodeprompted NODENAME PRDDBLA1_DB2 3. Set db2 Userexit=YES, LOGRETAIN= YES 4. Backup database : Offline = SUCCESS 5. Backup database : Online= FAILED (receive the above error prompt: SQL2062N) Our database is DB 8.2.4 running on AIX 5.1 Is there any step that I have missed out? Thanks, Regards, Zareyna Salim Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED] Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.10/384 - Release Date: 7/10/2006
Retry # 1 in dsmc ouput meaning
Hello the list when archiving files in /etc/ dsmc outputs lots of Retry # 1 file_type whereas : - all my copygroups are set dynamic - the retried files are said to be already Sent From the Log pattern, it looks like a rollback/commit behaviour. For exemple, we have : Directory-- 4,096 /etc/foo [Sent] Directory-- 4,096 /etc/bar [Sent] Normal File-- 42 /etc/bar/pipo [Sent] Normal File-- 1 /etc/bar/notreadablefile ** Unsuccessful ** Retry # 1 Directory-- 4,096 /etc/foo [Sent] Retry # 1 Directory-- 4,096 /etc/bar [Sent] Retry # 1 Normal File--42 /etc/bar/pipo [Sent] ANS1228E Sending of object '/etc/bar/notreadablefile' failed ANS4007E Error processing '/etc/bar/notreadablefile' : access to the object is denied 1/ Does someone know the underlaying actions done by TSM ? 2/ For large file written directly to tape, isn't this behaviour inefficient? is it possible to commit after each file ? Regards, mrs
Checkout Archive tapes
All, Will the following sql command move my archive tapes to be offsite, ie: into the vault where drm will present them back as vault retrieve once the archive data expires. move media TAPE_NAME stg=ARCHIVETAPEPOOL wherest=mountableinlib wherestatus=filling,full ovflocation=VAULT remove=bulk Regards, Jim
Re: SQL2062N: Reason code =406
On Jul 11, 2006, at 3:09 AM, zareyna wrote: I have changed the permission for the errorlog. Still I still have the error. On another database server , when I execute dsmapipw in /usr/opt/db2_08_01/adsm64/dsmapipw, I received Segmentation Fault (coredump) and my offline fullbackup failed with error : SQL2079N Return code 30. Did I execute the correct dsmapipw? There 2 folders, adsm and adsm64 and I execute the dsmapipw in adsm64. Appreciate if anyone could give me any suggestions to troubleshoot this 2 errors. Some considerations... IBM Technote 1212707 talks about the error condition. Don't be shy about searching the IBM site for helpful info. ADSM-L can provide some informal assistance, but the definitive info is on the IBM site. You haven't revealed what bitmode is in play. As IBM advises: The TSM API bit level needs to match the DB2 bit level; the bit level of the OS does not affect this. For example, if a 32bit DB2 instance is installed on a 64bit AIX OS, then the 32bit TSM API should be installed to match the bit level of the DB2 instance. Make sure that the errorlog is the dsmierror.log, and that DSMI_LOG allows its use in a directory which is writable. You can use the AIX 'touch' command like 'touch $DSMI_LOG/whatever' to verify writability in the directory. If your executions have created that error log, then by all means inspect it for supplementary info on the problem. The environment variables should be in effect within the process running the DB2 instance, not the process running the 'db2 backup' command. Be sure to follow the instructions in redbook Backing Up DB2 Using IBM Tivoli Storage Manager. You haven't told us what level of the TSM API you are using. Segfaults may occur because of the use of incorrect values; but they are software defects, and applying the latest maintenance level may correct them. If not, TSM Support should be contacted. Richard Sims
Re: DB backup on a DDS drive
Markus Engelhard píše v út 11. 07. 2006 v 07:59 +0100: Hi Michal, one more way would be backing up the TSM-database to a second TSM-Server using virtual volumes. Setting up a TSM-Server on a workstation is a quick task, and setting up the vv is rather straightforward. If you take a machine that is backed up anyway, it will even be free of cost, as the cpu is charged, regardless if you run a TSM-client or a TSM server. One more benefit: if you use the same OS, you could even recover the whole TSM-server to this alternative hardware if you lose the primary machine. Have a go, it´s really worth it! Thank you, this is probably more work and time then I am allowed to spend on it but is definitely also useful idea. Michal Regards, Markus
Re: Retry # 1 in dsmc ouput meaning
On Jul 11, 2006, at 4:50 AM, Marc REYNES wrote: Hello the list when archiving files in /etc/ dsmc outputs lots of Retry # 1 file_type whereas : - all my copygroups are set dynamic - the retried files are said to be already Sent From the Log pattern, it looks like a rollback/commit behaviour. For exemple, we have : Directory-- 4,096 /etc/foo [Sent] Directory-- 4,096 /etc/bar [Sent] Normal File-- 42 /etc/bar/pipo [Sent] Normal File-- 1 /etc/bar/notreadablefile ** Unsuccessful ** Retry # 1 Directory-- 4,096 /etc/foo [Sent] Retry # 1 Directory-- 4,096 /etc/bar [Sent] Retry # 1 Normal File--42 /etc/bar/pipo [Sent] ANS1228E Sending of object '/etc/bar/notreadablefile' failed ANS4007E Error processing '/etc/bar/notreadablefile' : access to the object is denied 1/ Does someone know the underlaying actions done by TSM ? 2/ For large file written directly to tape, isn't this behaviour inefficient? is it possible to commit after each file ? Marc - A Retry occurs because something interrupted the action, where it can be: - Media not ready; have to await a mount. - File changed during the TSM operation. - A file system object accessibility issue. The Sent notation is misleading... Rather than meaning that the object was sent from the client to TSM server storage, it really means that the object was successfully written to the client buffer, and will be sent once the buffer is full. Simply stated, the client- server interaction occurs by Transactions, where the transaction buffer size is governed by the agreed Aggregate size. Large files are bigger than the Aggregate size, and are stored by themselves (Query CONTent F=D on a volume will have a No value for Aggregated?). A transaction interruption is painful, in that it has to be initiated all over again. TSM transaction processing is best described in the Admin Guide, and in the Technical Guide redbook for each version-release. Richard Sims
Re: Intel Mac support date?
5.2 appears to work, but there are problems with the scheduler. We are recommending that our users schedule a dsmc incr via cron in this environment. At 03:35 PM 7/7/2006, Alexander Lazarevich wrote: Does anyone know when they plan to support Intel based macs officially? And is 5.2 client with rosetta the prevailing way to backup Intel based macs until they do? Thanks, Alex -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Novell schedule failures that actually complete
Have a Novell server that is actually finishing the backups and the totals are coming through on the operational reports. In the schedule log, it spits out a generic ANS1512E error message. Any insights would be appreciated. Thanks. 07/10/2006 23:01:53 Successful incremental backup of 'NDS:' 07/10/2006 23:01:53 --- SCHEDULEREC STATUS BEGIN 07/10/2006 23:01:53 Total number of objects inspected: 591,911 07/10/2006 23:01:53 Total number of objects backed up:8,780 07/10/2006 23:01:53 Total number of objects updated: 0 07/10/2006 23:01:53 Total number of objects rebound: 0 07/10/2006 23:01:53 Total number of objects deleted: 0 07/10/2006 23:01:53 Total number of objects expired: 8,492 07/10/2006 23:01:53 Total number of objects failed: 7 07/10/2006 23:01:53 Total number of bytes transferred: 1.43 GB 07/10/2006 23:01:53 Data transfer time: 124.42 sec 07/10/2006 23:01:53 Network data transfer rate:12,120.32 KB/sec 07/10/2006 23:01:53 Aggregate data transfer rate: 4,057.37 KB/sec 07/10/2006 23:01:53 Objects compressed by:0% 07/10/2006 23:01:53 Elapsed processing time: 00:06:11 07/10/2006 23:01:53 --- SCHEDULEREC STATUS END 07/10/2006 23:01:53 --- SCHEDULEREC OBJECT END NOVELL 07/10/2006 23:00:00 07/10/2006 23:01:53 ANS1512E Scheduled event 'NOVELL' failed. Return code = 12. 07/10/2006 23:01:53 Sending results for scheduled event 'NOVELL'. 07/10/2006 23:01:53 Results sent to server for scheduled event 'NOVELL'. 07/10/2006 23:01:53 ANS1483I Schedule log pruning started. 07/10/2006 23:01:53 ANS1484I Schedule log pruning finished successfully. 07/10/2006 23:01:53 Querying server for next scheduled event. 07/10/2006 23:01:53 Node Name: IJS 07/10/2006 23:01:57 Session established with server TSMSERVER: Windows 07/10/2006 23:01:57 Server Version 5, Release 2, Level 4.5 07/10/2006 23:01:57 Server date/time: 07/10/2006 23:06:31 Last access: 07/10/2006 23:00:21 07/10/2006 23:01:57 --- SCHEDULEREC QUERY BEGIN 07/10/2006 23:02:02 --- SCHEDULEREC QUERY END 07/10/2006 23:02:02 Next operation scheduled: 07/10/2006 23:02:02 07/10/2006 23:02:02 Schedule Name: NOVELL 07/10/2006 23:02:02 Action:Incremental 07/10/2006 23:02:02 Objects: 07/10/2006 23:02:02 Options: 07/10/2006 23:02:02 Server Window Start: 23:00:00 on 07/11/2006 07/10/2006 23:02:02 07/10/2006 23:02:02 Scheduler has been stopped. Bob Martoncik Lucas County Information Services 419-213-4633
redirecting output question ...
hi all ... a quick one : how to get rid of ... IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 2, Level 3.0 (c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights Reserved. Session established with server TSM01: AIX-RS/6000 Server Version 5, Release 3, Level 3.1 Server date/time: 07/11/06 16:35:06 Last access: 07/11/06 16:34:14 in output files ? stripheaders ? sumtin' like that ? thanks in advance goran
Re: Novell schedule failures that actually complete
07/10/2006 23:01:53 Total number of objects failed: 7 Bob, depending on the way these files failed (not found, in use..), these failed objects could well produce your Failed event. That's what it looks like to me. Check the dsmerror.log to find out why they failed and either exclude them or bind them to a Dynamic/SharedDynamic management class. Does that resolve it? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Martoncik Sent: 11 July 2006 15:00 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Novell schedule failures that actually complete Have a Novell server that is actually finishing the backups and the totals are coming through on the operational reports. In the schedule log, it spits out a generic ANS1512E error message. Any insights would be appreciated. Thanks. 07/10/2006 23:01:53 Successful incremental backup of 'NDS:' 07/10/2006 23:01:53 --- SCHEDULEREC STATUS BEGIN 07/10/2006 23:01:53 Total number of objects inspected: 591,911 07/10/2006 23:01:53 Total number of objects backed up:8,780 07/10/2006 23:01:53 Total number of objects updated: 0 07/10/2006 23:01:53 Total number of objects rebound: 0 07/10/2006 23:01:53 Total number of objects deleted: 0 07/10/2006 23:01:53 Total number of objects expired: 8,492 07/10/2006 23:01:53 Total number of objects failed: 7 07/10/2006 23:01:53 Total number of bytes transferred: 1.43 GB 07/10/2006 23:01:53 Data transfer time: 124.42 sec 07/10/2006 23:01:53 Network data transfer rate:12,120.32 KB/sec 07/10/2006 23:01:53 Aggregate data transfer rate: 4,057.37 KB/sec 07/10/2006 23:01:53 Objects compressed by:0% 07/10/2006 23:01:53 Elapsed processing time: 00:06:11 07/10/2006 23:01:53 --- SCHEDULEREC STATUS END 07/10/2006 23:01:53 --- SCHEDULEREC OBJECT END NOVELL 07/10/2006 23:00:00 07/10/2006 23:01:53 ANS1512E Scheduled event 'NOVELL' failed. Return code = 12. 07/10/2006 23:01:53 Sending results for scheduled event 'NOVELL'. 07/10/2006 23:01:53 Results sent to server for scheduled event 'NOVELL'. 07/10/2006 23:01:53 ANS1483I Schedule log pruning started. 07/10/2006 23:01:53 ANS1484I Schedule log pruning finished successfully. 07/10/2006 23:01:53 Querying server for next scheduled event. 07/10/2006 23:01:53 Node Name: IJS 07/10/2006 23:01:57 Session established with server TSMSERVER: Windows 07/10/2006 23:01:57 Server Version 5, Release 2, Level 4.5 07/10/2006 23:01:57 Server date/time: 07/10/2006 23:06:31 Last access: 07/10/2006 23:00:21 07/10/2006 23:01:57 --- SCHEDULEREC QUERY BEGIN 07/10/2006 23:02:02 --- SCHEDULEREC QUERY END 07/10/2006 23:02:02 Next operation scheduled: 07/10/2006 23:02:02 07/10/2006 23:02:02 Schedule Name: NOVELL 07/10/2006 23:02:02 Action:Incremental 07/10/2006 23:02:02 Objects: 07/10/2006 23:02:02 Options: 07/10/2006 23:02:02 Server Window Start: 23:00:00 on 07/11/2006 07/10/2006 23:02:02 07/10/2006 23:02:02 Scheduler has been stopped. Bob Martoncik Lucas County Information Services 419-213-4633 _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: Novell schedule failures that actually complete
As a first effort, I would recommend going to the TSM support site (see my sig) and doing a search on: ANS1512E and see what you come up with. Make sure you put the search term in the box labeled Search Support (this product) in the middle of the page. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/11/2006 06:59:58: Have a Novell server that is actually finishing the backups and the totals are coming through on the operational reports. In the schedule log, it spits out a generic ANS1512E error message. Any insights would be appreciated. Thanks. 07/10/2006 23:01:53 Successful incremental backup of 'NDS:' 07/10/2006 23:01:53 --- SCHEDULEREC STATUS BEGIN 07/10/2006 23:01:53 Total number of objects inspected: 591,911 07/10/2006 23:01:53 Total number of objects backed up:8,780 07/10/2006 23:01:53 Total number of objects updated: 0 07/10/2006 23:01:53 Total number of objects rebound: 0 07/10/2006 23:01:53 Total number of objects deleted: 0 07/10/2006 23:01:53 Total number of objects expired: 8,492 07/10/2006 23:01:53 Total number of objects failed: 7 07/10/2006 23:01:53 Total number of bytes transferred: 1.43 GB 07/10/2006 23:01:53 Data transfer time: 124.42 sec 07/10/2006 23:01:53 Network data transfer rate:12,120.32 KB/sec 07/10/2006 23:01:53 Aggregate data transfer rate: 4,057.37 KB/sec 07/10/2006 23:01:53 Objects compressed by:0% 07/10/2006 23:01:53 Elapsed processing time: 00:06:11 07/10/2006 23:01:53 --- SCHEDULEREC STATUS END 07/10/2006 23:01:53 --- SCHEDULEREC OBJECT END NOVELL 07/10/2006 23:00:00 07/10/2006 23:01:53 ANS1512E Scheduled event 'NOVELL' failed. Return code = 12. 07/10/2006 23:01:53 Sending results for scheduled event 'NOVELL'. 07/10/2006 23:01:53 Results sent to server for scheduled event 'NOVELL'. 07/10/2006 23:01:53 ANS1483I Schedule log pruning started. 07/10/2006 23:01:53 ANS1484I Schedule log pruning finished successfully. 07/10/2006 23:01:53 Querying server for next scheduled event. 07/10/2006 23:01:53 Node Name: IJS 07/10/2006 23:01:57 Session established with server TSMSERVER: Windows 07/10/2006 23:01:57 Server Version 5, Release 2, Level 4.5 07/10/2006 23:01:57 Server date/time: 07/10/2006 23:06:31 Last access: 07/10/2006 23:00:21 07/10/2006 23:01:57 --- SCHEDULEREC QUERY BEGIN 07/10/2006 23:02:02 --- SCHEDULEREC QUERY END 07/10/2006 23:02:02 Next operation scheduled: 07/10/2006 23:02:02 07/10/2006 23:02:02 Schedule Name: NOVELL 07/10/2006 23:02:02 Action:Incremental 07/10/2006 23:02:02 Objects: 07/10/2006 23:02:02 Options: 07/10/2006 23:02:02 Server Window Start: 23:00:00 on 07/11/2006 07/10/2006 23:02:02 07/10/2006 23:02:02 Scheduler has been stopped. Bob Martoncik Lucas County Information Services 419-213-4633
Re: admin interface / Integrated Solutions Console
Lawrence, As of 5.3.0.0 a new web admin interface was made available. To install the TSM Administration Center: 1) Download and install ISC. ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/isc/v5r3/5.3.2.0 2) Download and install the Administration Center (think of it as a plug-in to ISC). ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v5r3/5.3.3.0 3) See the README for more detailed install instructions. ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v5r3/5.3.3.0/README Note: Additionally the old web admin is still available for a transition period while migrating to the new interface. This is available as-is. http://www-1.ibm.com/support/docview.wss?uid=swg24009569 Nick Kovacs IBM Tivoli Storage Manager Development Nicholas Kovacs/Tucson/IBM [EMAIL PROTECTED] -- Date:Mon, 10 Jul 2006 10:57:17 -0400 From:Lawrence Clark [EMAIL PROTECTED] Subject: admin interface / Integrated Solutions Console admin interface.. went to access it under 5.3.2 and got message: ANR4747W The web administrative interface is no longer supported. Begin using the Integrated Solutions Console instead. Is that installed on aIX when the server is installed and how do you access it?
dsmsched.log Inspected equals Failed????
Hi All, I wanted to see if any of you have experienced the following reporting issue in the dsmsched.log. Our TSM Server is a RS6000, running TSM Server 5.3.2.3 and the client in question is a Windows 2003 Server running the TSM Client 5.03.0200. On this particular client when the backup completes, the summary of the dsmsched.log reports the following: 07/11/2006 02:28:49 Total number of objects inspected: 24,440 07/11/2006 02:28:49 Total number of objects backed up: 0 07/11/2006 02:28:49 Total number of objects updated: 0 07/11/2006 02:28:49 Total number of objects rebound: 0 07/11/2006 02:28:49 Total number of objects deleted: 0 07/11/2006 02:28:49 Total number of objects expired: 48 07/11/2006 02:28:49 Total number of objects failed: 24,440 07/11/2006 02:28:49 Total number of subfile objects: 0 07/11/2006 02:28:49 Total number of bytes transferred: 411.82 MB 07/11/2006 02:28:49 Data transfer time: 57.52 sec 07/11/2006 02:28:49 Network data transfer rate: 7,331.34 KB/sec 07/11/2006 02:28:49 Aggregate data transfer rate: 1,314.17 KB/sec 07/11/2006 02:28:49 Objects compressed by: 51% 07/11/2006 02:28:49 Subfile objects reduced by: 0% 07/11/2006 02:28:49 Elapsed processing time: 00:05:20 However, when the dsmsched.log is reviewed we only see 18 files that truly failed. According to the above summary, total number of items insepcted is equal to the total number of objects failed. I looked on the TSM server and it also reporting that 24,440 files failed. Anyone have any ideas of what is going on here? Thanks in advance for your help. Shawn Malone
Re: dsmsched.log Inspected equals Failed????
Try going to the web site in my sig and using the Search Support (this product) search facility. Check the Solve a problem checkbox and try some search criteria like: windows objects inspected failed and see what you can see. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/11/2006 10:31:38: Hi All, I wanted to see if any of you have experienced the following reporting issue in the dsmsched.log. Our TSM Server is a RS6000, running TSM Server 5.3.2.3 and the client in question is a Windows 2003 Server running the TSM Client 5.03.0200. On this particular client when the backup completes, the summary of the dsmsched.log reports the following: 07/11/2006 02:28:49 Total number of objects inspected: 24,440 07/11/2006 02:28:49 Total number of objects backed up: 0 07/11/2006 02:28:49 Total number of objects updated: 0 07/11/2006 02:28:49 Total number of objects rebound: 0 07/11/2006 02:28:49 Total number of objects deleted: 0 07/11/2006 02:28:49 Total number of objects expired: 48 07/11/2006 02:28:49 Total number of objects failed: 24,440 07/11/2006 02:28:49 Total number of subfile objects: 0 07/11/2006 02:28:49 Total number of bytes transferred: 411.82 MB 07/11/2006 02:28:49 Data transfer time: 57.52 sec 07/11/2006 02:28:49 Network data transfer rate: 7,331.34 KB/sec 07/11/2006 02:28:49 Aggregate data transfer rate: 1,314.17 KB/sec 07/11/2006 02:28:49 Objects compressed by: 51% 07/11/2006 02:28:49 Subfile objects reduced by: 0% 07/11/2006 02:28:49 Elapsed processing time: 00:05:20 However, when the dsmsched.log is reviewed we only see 18 files that truly failed. According to the above summary, total number of items insepcted is equal to the total number of objects failed. I looked on the TSM server and it also reporting that 24,440 files failed. Anyone have any ideas of what is going on here? Thanks in advance for your help. Shawn Malone
Re: dsmsched.log Inspected equals Failed????
Try a client upgrade, I had a lot of things going on with a couple 2003 servers, I think the latest and greatest fixed this for me. [EMAIL PROTECTED] 07/11/06 01:31PM Hi All, I wanted to see if any of you have experienced the following reporting issue in the dsmsched.log. Our TSM Server is a RS6000, running TSM Server 5.3.2.3 and the client in question is a Windows 2003 Server running the TSM Client 5.03.0200. On this particular client when the backup completes, the summary of the dsmsched.log reports the following: 07/11/2006 02:28:49 Total number of objects inspected: 24,440 07/11/2006 02:28:49 Total number of objects backed up: 0 07/11/2006 02:28:49 Total number of objects updated: 0 07/11/2006 02:28:49 Total number of objects rebound: 0 07/11/2006 02:28:49 Total number of objects deleted: 0 07/11/2006 02:28:49 Total number of objects expired: 48 07/11/2006 02:28:49 Total number of objects failed: 24,440 07/11/2006 02:28:49 Total number of subfile objects: 0 07/11/2006 02:28:49 Total number of bytes transferred: 411.82 MB 07/11/2006 02:28:49 Data transfer time: 57.52 sec 07/11/2006 02:28:49 Network data transfer rate: 7,331.34 KB/sec 07/11/2006 02:28:49 Aggregate data transfer rate: 1,314.17 KB/sec 07/11/2006 02:28:49 Objects compressed by: 51% 07/11/2006 02:28:49 Subfile objects reduced by: 0% 07/11/2006 02:28:49 Elapsed processing time: 00:05:20 However, when the dsmsched.log is reviewed we only see 18 files that truly failed. According to the above summary, total number of items insepcted is equal to the total number of objects failed. I looked on the TSM server and it also reporting that 24,440 files failed. Anyone have any ideas of what is going on here? Thanks in advance for your help. Shawn Malone - CONFIDENTIALITY NOTICE: This message is confidential, intended only for the named recipient(s) and may contain information that is privileged, or exempt from disclosure under applicable law. If you are not the intended recipient(s), you are notified that the dissemination, distribution or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender by reply e-mail, delete this e-mail from your computer, and destroy any copies in any form immediately. Receipt by anyone other than the named recipient(s) is not a waiver of any attorney-client, work product, or other applicable privilege. This message and all contents may be reviewed by authorized parties of the Catholic Health System other than those named in the message header. The contents of this message do not bind the Catholic Health System to any contract, position, or course of action unless the sender is specifically authorized to enter into contracts on behalf of the Catholic Health System. The contents of this message do not necessarily constitute an official representation of the Catholic Health System.
Communications Protocol Error
Hi All, I am running TSM 5.2.7 on AIX 5.3 and a remote client running 5.3.4 on W2K. I have two problems that are probably related. Perhaps someone has seen this and could help clue me in. My nightly incremental backup always fails with the following message: dsmsched.log --- SCHEDULEREC OBJECT BEGIN DAILY_BACKUP_1900 07/10/2006 19:00:00 ANS1026E The session is rejected: There was a communications protocol error. dsmerror.log cuGetPSQryResp: Out of sequence verb received; VB_PSQryResp or EndTxn wanted ANS1026E The session is rejected: There was a communications protocol error. When I start the backup gui on the client, the first start tries to establish a session but after 10 minutes times out with a gui message: Communications Protocol Error. HOWEVER, while the session initialization is in the 10 minute wait, I can initiate another gui session from the same console without any issue and run a backup via the gui successfully. Also, if I have a gui session active at the time the nightly incremental wants to start, it does establish a session and the scheduled backup runs to a successful completion. I have tried every backup client from 5.1 to 5.3.4 . This has been going on for months so I can't rightfully say what if anything has changed. It used to run successfully all the time but over time TSM and network upgrades have certainly occurred. The problem is recreateable every run. Anyone's insight would be greatly appreciated. Thanks, Ralph Levi
oddevaix:/home/archivedb2 backup db archive online use tsm SQL2062N An error occurred while accessing media, Reason Code: 137
TSM Server 5.3.2.2 TSM DB2 Client 5.3.0.0 DB2 8.2.0 Trying to help our DB2 Admins get a backup. I know very little about DB2, so any help is appreciated. What we have tried/verified: We can run db2adutl from the client - it was successful I see in the 'Backing Up DB2 Using TSM' book, under troubleshooting suggested for 137' error, is the incorrect password We compared the .profile with another successful db2 client - that looks correct, DSM_DIR DSMI_LOG, DSMI_DIR, and DSMI_CONFIG too. Passwordgenerate set in the options file Updated the node nodename password on the TSM Server, then regenerated the password file with db2 command dsmapipw again. ERROR: DB2Node :/home/archivedb2 backup db archive online use tsm SQL2062N An error occurred while accessing media /home/archive/sqllib/adsm/libtsm.a. Reason code: 137. Nancy Backhaus Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: dsmsched.log Inspected equals Failed????
Andy and Aaron, Thanks, I was able to find the answer, by going to the site Andy pointed out. Shawn Try going to the web site in my sig and using the Search Support (this product) search facility. Check the Solve a problem checkbox and try some search criteria like: windows objects inspected failed and see what you can see. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/11/2006 10:31:38: Hi All, I wanted to see if any of you have experienced the following reporting issue in the dsmsched.log. Our TSM Server is a RS6000, running TSM Server 5.3.2.3 and the client in question is a Windows 2003 Server running the TSM Client 5.03.0200. On this particular client when the backup completes, the summary of the dsmsched.log reports the following: 07/11/2006 02:28:49 Total number of objects inspected: 24,440 07/11/2006 02:28:49 Total number of objects backed up: 0 07/11/2006 02:28:49 Total number of objects updated: 0 07/11/2006 02:28:49 Total number of objects rebound: 0 07/11/2006 02:28:49 Total number of objects deleted: 0 07/11/2006 02:28:49 Total number of objects expired: 48 07/11/2006 02:28:49 Total number of objects failed: 24,440 07/11/2006 02:28:49 Total number of subfile objects: 0 07/11/2006 02:28:49 Total number of bytes transferred: 411.82 MB 07/11/2006 02:28:49 Data transfer time: 57.52 sec 07/11/2006 02:28:49 Network data transfer rate: 7,331.34 KB/sec 07/11/2006 02:28:49 Aggregate data transfer rate: 1,314.17 KB/sec 07/11/2006 02:28:49 Objects compressed by: 51% 07/11/2006 02:28:49 Subfile objects reduced by: 0% 07/11/2006 02:28:49 Elapsed processing time: 00:05:20 However, when the dsmsched.log is reviewed we only see 18 files that truly failed. According to the above summary, total number of items insepcted is equal to the total number of objects failed. I looked on the TSM server and it also reporting that 24,440 files failed. Anyone have any ideas of what is going on here? Thanks in advance for your help. Shawn Malone
Re: Communications Protocol Error
Hi Ralph, When we've had protocol errors, it has been when a client tried to use a feature that the server did not support. In other words, a client at a higher rev than the server, and, using a feature of that client that the lower rev tsm server doesn't support. Rick Levi, Ralph [EMAIL PROTECTED] Sent by: ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager cc [EMAIL PROTECTED] .EDU Subject Communications Protocol Error 07/11/2006 02:11 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hi All, I am running TSM 5.2.7 on AIX 5.3 and a remote client running 5.3.4 on W2K. I have two problems that are probably related. Perhaps someone has seen this and could help clue me in. My nightly incremental backup always fails with the following message: dsmsched.log --- SCHEDULEREC OBJECT BEGIN DAILY_BACKUP_1900 07/10/2006 19:00:00 ANS1026E The session is rejected: There was a communications protocol error. dsmerror.log cuGetPSQryResp: Out of sequence verb received; VB_PSQryResp or EndTxn wanted ANS1026E The session is rejected: There was a communications protocol error. When I start the backup gui on the client, the first start tries to establish a session but after 10 minutes times out with a gui message: Communications Protocol Error. HOWEVER, while the session initialization is in the 10 minute wait, I can initiate another gui session from the same console without any issue and run a backup via the gui successfully. Also, if I have a gui session active at the time the nightly incremental wants to start, it does establish a session and the scheduled backup runs to a successful completion. I have tried every backup client from 5.1 to 5.3.4 . This has been going on for months so I can't rightfully say what if anything has changed. It used to run successfully all the time but over time TSM and network upgrades have certainly occurred. The problem is recreateable every run. Anyone's insight would be greatly appreciated. Thanks, Ralph Levi - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Dsmc memory leak
I'm sure this has been discussed in past...the dsmc sch process slowly has a memory leak over time and the only way to free it up is to kill the process and let it respawn. We are at version 5.2.2.9 on AIX 5.3.3 Does anybody know if this has been fixed on any later versions of the ba client...thanks Rod
Re: Deleting database snapshot
Well, you should only have 1 tape tied up - the last one, right? First the std disclaimer that you should NEVER do this with your real DB backup tapes; but if you want to free up that last, unused DBSNAPSHOT tape: 1) create a file device class 2) run a Dbsnapshot to the file device class 3) run a DELETE VOLHIST to free up the tape that is now the next-to-last DBSNAPSHOT 4) delete the file from (2) using OS-level tools, to get your disk space back. The name of the last Dbsnapshot will still be in volhist. But nobody will care. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bell, Charles (Chip) Sent: Tuesday, July 11, 2006 3:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Deleting database snapshot I recently asked about this and received good answers. But what I would like to know is if TSM development is ever going to consider making it to where you can rid yourself of ALL unwanted database backups/snapshots. The docs says The latest snapshot database backup will not be deleted when you attempt a 'delete volhist' on them. So is it still correct that I cannot delete these through any method, and if not, is that ever going to change? I have some tapes I could sure use as scratches... :-) If you're curious we went from full database backups to snapshots back to fulls again. God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional (ITSM 5.2) Baptist Health System Birmingham, AL - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Admin Center with z/OS server
Is the Admin Center aware if your TSM server is z/OS? I finally installed and started Admin Center but my server is now starting to contain messages about unknown commands and unknown SQL table names. ANR2939E The reference 'DRIVES' is an unknown SQL table name. ANR2000E Unknown command - QUERY DR Is there a place in Admin Center to tell is the server is z/OS?
DB Backup Trigger
As far as I know, once the db backup completes, the log utilization should be clean to zero. But in the activity log, I did find it was not true. Can anybody tell me why? Thanks in advance. 07/11/06 05:07:00 ANR0984I Process 391 for DATABASE BACKUP started in the BACKGROUND at 05:07:00. (PROCESS: 391) 07/11/06 05:07:00 ANR4552I Full database backup triggered; started as process 391. (PROCESS: 391) 07/11/06 05:15:55 ANR4550I Full database backup (process 391) complete, 4216422 pages copied. (PROCESS: 391) 07/11/06 05:15:55 ANR0985I Process 391 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 05:15:55. (PROCESS: 391) 07/11/06 05:15:55 ANR4556W Attention: the database backup operation did not free sufficient recovery log space to lower utilization below the database backup trigger. The recovery log size may need to be increased or the database backup trigger parameters may need to be adjusted. 07/11/06 05:16:06 ANR2997W The server log is 80 percent full. The server will delay transactions by 3 milliseconds. (SESSION: 12862) *The first trigger, after db backup completed, the log was still 80% FULL.* ... The second trigger, after db backup completed, the log was still 25% FULL 07/11/06 06:28:13 ANR0984I Process 394 for DATABASE BACKUP started in the BACKGROUND at 06:28:13. (PROCESS: 394) 07/11/06 06:28:13 ANR4552I Full database backup triggered; started as process 394. (PROCESS: 394) 07/11/06 06:39:27 ANR4550I Full database backup (process 394) complete, 4338380 pages copied. (PROCESS: 394) 07/11/06 06:39:27 ANR0985I Process 394 for DATABASE BACKUP running in the BACKGROUND completed with completion state SUCCESS at 06:39:27. (PROCESS: 394) 07/11/06 06:39:27 ANR2996I The server log is 25 percent full. The server is no longer delaying transactions. (SESSION: 12957)
tsm_barcode missed in new firmware
My 3584 library missed the tsm_barcode parameter after upgraded to new firmware on AIX 5.2. Did anybody come across it? Thanks in advance. Old firmware 5360: *lscfg -vpl smc0 * smc0 U7311.D20.10B16FA-P1-C02-T1-W500507630054FD01-L1 IBM 3584 Library Medium Changer (FCP) ManufacturerIBM Machine Type and Model..03584L32 Serial Number...078151170401 Device Specific.(FW)*5360* *lsattr -El smc0* alt_pathing no Enable Alternate Pathing Support True debug_trace no Debug Trace Logging Enabled True dev_status N/A False devtype 03584L32 Device Type False location Location True lun_id 0x1Logical Unit Number True new_name New Logical Name True node_name 0x500507630014fd01 World Wide Node Name False primary_device smc0 Primary Logical Device False reserve_support yesUse Reserve/Release on Open and CloseTrue retain_reserve no Retain Reservation False scsi_id 0x6b0dcc SCSI Target ID True trace_logging no Trace Logging EnabledTrue *tsm_barcode_len 8 TSM Barcode Length for Ultrium 1/Ultrium 2 Media True *ww_name 0x500507630054fd01 World Wide Port Name False new firmware 5790: *lscfg* [EMAIL PROTECTED]:/home/ddeng%3E#lscfg* -vpl smc0* smc0 U0.1-P2-I2/Q2-W500507630054B401-L1 IBM 3584 Library Medium Changer (FCP) ManufacturerIBM Machine Type and Model..03584L32 Serial Number...078150440401 Device Specific.(FW)*5790* *lsattr* [EMAIL PROTECTED]:/home/ddeng%3E#lsattr* -El smc0* alt_pathing no Enable Alternate Pathing Support True devtype 03584L32 Device Type False location Location True lun_id 0x1Logical Unit Number True new_name New Logical Name True node_name 0x500507630014b401 N/A False primary_device smc0 Primary Logical Device False reserve_support yesUse Reserve/Release on Open and Close True retain_reserve no Retain Reservation False scsi_id 0x6105cc SCSI Target ID True ww_name 0x500507630054b401 World Wide Name False
Re: Dsmc memory leak
Instead of using the dsm sched process, you should use the dsmcad process to start either the webclient or the schedule daemon or both. It keeps any memory leaks from showing up and is a pretty reliable mechanism. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Tuesday, July 11, 2006 12:55 PM To: ADSM-L@VM.MARIST.EDU Subject: Dsmc memory leak I'm sure this has been discussed in past...the dsmc sch process slowly has a memory leak over time and the only way to free it up is to kill the process and let it respawn. We are at version 5.2.2.9 on AIX 5.3.3 Does anybody know if this has been fixed on any later versions of the ba client...thanks Rod
Deleting database snapshot
I recently asked about this and received good answers. But what I would like to know is if TSM development is ever going to consider making it to where you can rid yourself of ALL unwanted database backups/snapshots. The docs says The latest snapshot database backup will not be deleted when you attempt a 'delete volhist' on them. So is it still correct that I cannot delete these through any method, and if not, is that ever going to change? I have some tapes I could sure use as scratches... :-) If you're curious we went from full database backups to snapshots back to fulls again. God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional (ITSM 5.2) Baptist Health System Birmingham, AL - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Re: Communications Protocol Error
* Do any other clients have this problem? If so, what are the commonalities? Do any other clients NOT have this problem? If so, what are the differences? What I mean by this is, can you find any pattern or something unique that might help localize the problem (for example, options file settings)? * Check the TSM server activity log to see what's going on there at the time the client tries to start the backup. * In a vein similar to earlier posts I've made, I'd suggest going to the TSM support site (see my sig) and use the Search Support (this product) facility to see if you get any hits for your symptoms. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/11/2006 11:11:43: Hi All, I am running TSM 5.2.7 on AIX 5.3 and a remote client running 5.3.4 on W2K. I have two problems that are probably related. Perhaps someone has seen this and could help clue me in. My nightly incremental backup always fails with the following message: dsmsched.log --- SCHEDULEREC OBJECT BEGIN DAILY_BACKUP_1900 07/10/2006 19:00:00 ANS1026E The session is rejected: There was a communications protocol error. dsmerror.log cuGetPSQryResp: Out of sequence verb received; VB_PSQryResp or EndTxn wanted ANS1026E The session is rejected: There was a communications protocol error. When I start the backup gui on the client, the first start tries to establish a session but after 10 minutes times out with a gui message: Communications Protocol Error. HOWEVER, while the session initialization is in the 10 minute wait, I can initiate another gui session from the same console without any issue and run a backup via the gui successfully. Also, if I have a gui session active at the time the nightly incremental wants to start, it does establish a session and the scheduled backup runs to a successful completion. I have tried every backup client from 5.1 to 5.3.4 . This has been going on for months so I can't rightfully say what if anything has changed. It used to run successfully all the time but over time TSM and network upgrades have certainly occurred. The problem is recreateable every run. Anyone's insight would be greatly appreciated. Thanks, Ralph Levi
Fw: redirecting output question ...
You're looking for: -dataonly=yes to be added to the end of the dsmadmc command you're running. Nick Cassimatis email: [EMAIL PROTECTED] - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 07/11/2006 10:30 PM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/11/2006 10:33:02 AM: hi all ... a quick one : how to get rid of ... IBM Tivoli Storage Manager Command Line Administrative Interface - Version 5, Release 2, Level 3.0 (c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights Reserved. Session established with server TSM01: AIX-RS/6000 Server Version 5, Release 3, Level 3.1 Server date/time: 07/11/06 16:35:06 Last access: 07/11/06 16:34:14 in output files ? stripheaders ? sumtin' like that ? thanks in advance goran
Multiple nodes on linux with dsmcad ?
Hi! How do I run multiple nodes/schedulers on linux, if I want to use DSMCAD ? In my batch file, I've tried to use: export DSM_CONFIG=/test/dsm1.opt dsmcad sleep 2 export DSM_CONFIG=/test/dsm2.opt dsmcad But for some wierd reason this doesn't seem to work ? Regards /Brian
Re: Multiple nodes on linux with dsmcad ?
Brian Did you try dsmcad -optfile=/test/dsm1.opt and another one dsmcad -optfile=/test/dsm2.opt Regards Robert Ouzen -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ipsen Sent: Wednesday, July 12, 2006 8:19 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Multiple nodes on linux with dsmcad ? Hi! How do I run multiple nodes/schedulers on linux, if I want to use DSMCAD ? In my batch file, I've tried to use: export DSM_CONFIG=/test/dsm1.opt dsmcad sleep 2 export DSM_CONFIG=/test/dsm2.opt dsmcad But for some wierd reason this doesn't seem to work ? Regards /Brian
