HELP!! . Return code is: 127
hi all,
my problem is the code: 127
after running my postschedule the code error 127 is registered in my
dsmsched.log
look below:
TSM SERVER V4.2.2.0 (Win2k)
TSM Client V4.2.1.0 (Red Hat Linux release 6.2)
- file DSMSCHED.LOG
--
10/21/03 04:43:08 --- SCHEDULEREC STATUS BEGIN
10/21/03 04:43:08 Total number of objects inspected: 118,610
10/21/03 04:43:08 Total number of objects backed up:1,750
10/21/03 04:43:08 Total number of objects updated: 0
10/21/03 04:43:08 Total number of objects rebound: 0
10/21/03 04:43:08 Total number of objects deleted: 0
10/21/03 04:43:08 Total number of objects expired: 1
10/21/03 04:43:08 Total number of objects failed: 0
10/21/03 04:43:08 Total number of bytes transferred:38.86 GB
10/21/03 04:43:08 Data transfer time:3,684.83 sec
10/21/03 04:43:08 Network data transfer rate:11,060.34 KB/sec
10/21/03 04:43:08 Aggregate data transfer rate: 9,530.66 KB/sec
10/21/03 04:43:08 Objects compressed by:0%
10/21/03 04:43:08 Elapsed processing time: 01:11:16
10/21/03 04:43:08 --- SCHEDULEREC STATUS END
10/21/03 04:43:08 --- SCHEDULEREC OBJECT END BKP_SERVER1 10/21/03
03:30:00
10/21/03 04:43:08
Executing Operating System command or script:
remove_files.sh
10/21/03 04:43:08 Finished command. Return code is:
127
10/21/03 04:43:08 Scheduled event 'BKP_SERVER1' completed
successfully.
10/21/03 04:43:08 Sending results for scheduled event 'BKP_SERVER1'.
10/21/03 04:43:08 Results sent to server for scheduled event
'BKP_SERVER1'.
CONFIG
DSM.SYS
* Sample Client System Options file for UNIX (dsm.sys.smp) *
* This file contains the minimum options required to get started
* using TSM. Copy dsm.sys.smp to dsm.sys. In the dsm.sys file,
* enter the appropriate values for each option listed below and
* remove the leading asterisk (*) for each one.
* If your client node communicates with multiple TSM servers, be
* sure to add a stanza, beginning with the SERVERNAME option, for
* each additional server.
SERVERNAME SERVER_A
PASSWORDACCESS generate
COMMmethod TCPip
TCPPort1500
TCPServeraddress 100.100.100.1
NODENAME server1
ERRORLOGRETENTION3
SCHEDLOGRETENTION3
ERRORLOGNAME /opt/tivoli/tsm/client/ba/bin/dsmerror.log
SCHEDLOGNAME /opt/tivoli/tsm/client/ba/bin/dsmsched.log
DOMain ALL-LOCAL
INCLUDE /
INCLUDE /backup
INCLUDE /boot
INCLUDE /home
INCLUDE /usr
INCLUDE /var
POSTSCHEDULECMD remove_files.sh
PRESCHEDULECMD
the file "remove_files.sh" it is the same directory of dsm.exe
description of remove_files.sh
cd /backup/oracle/server1/redo_logs/
find . -mtime +2 -type f -exec rm {} \; | tee >
/opt/tivoli/tsm/client/ba/bin/remove_files_success
Best Regards,
Elenara
Elenara Geraldo
Senior TSM Administrator
Phone : 55 41 381 7588
Cellular: 55 41 91035796
Compatible TAPE.
Hi all, The tape: DLT - model: Powervault 112T 40/80 - Manufactures: DELL -> is compatible with TSM?? TSM Server Version 4.2 Unix/AIX Version 4.3 Thanks. Regards, Elenara Elenara Geraldo Senior TSM Administrator Phone : 55 41 381 7588 Cellular: 55 41 91035796
RES: TDP for SQL v2.2 backup errors..
BUG: The SQL Server VDI Backup and Restore Operations Are Not Successful
and
the CoCreateInstance Error Occurs
The information in this article applies to:
Microsoft SQL Server 2000 (all editions)
Microsoft SQL Server 7.0
This article was previously published under Q323602
IMPORTANT: This article contains information about modifying the
registry. Before you modify the registry, make sure to back it up and
make sure that you understand how to restore the registry if a problem
occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the
Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
BUG #: 357231 (SHILOH_BUGS)
SYMPTOMS
Backup or restore operations that use the SQL Server Virtual Device
Interface (VDI) may not succeed and SQL Server logs one of the following
errors in the SQL Server error log:
BackupVirtualDeviceSet::Initialize: CoCreateInstance failure on backup
device 'TDPSQL-0798-'. Operating system error -2147467262 (No
such interface supported).
-or-
BackupVirtualDeviceSet::Initialize: CoCreateInstance failure on backup
device 'TDPSQL-0036-'. Operating system error -2147221163
(Interface not registered).
CAUSE
This problem occurs because a worker thread in SQL Server that was
previously initialized in the Component Object Model (COM) has remained
in a single-threaded apartment (STA). This worker thread then tries to
load the SQL Server VDI. Because the SQL Server VDI is free threaded, it
cannot be loaded to an STA, and one of error messages that is listed in
the "Symptoms" section occur.
WORKAROUND
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft cannot guarantee that you can solve problems that result from
using Registry Editor incorrectly. Use Registry Editor at your own risk.
To change the registered threading model for the SQL Server VDI:
Start Registry Editor (Regedt32.exe).
Locate, and then click the following key in the registry:
HKEY_CLASSES_ROOT\CLSID\{40700425-0080-11d2-851f-00c04fc21759}\InprocSer
ver32
Edit the ThreadingModel value from Free to Both.
Locate, and then click the following key in the registry:
HKEY_CLASSES_ROOT\CLSID\{b5e7a132-a7bd-11d1-84c2-00c04fc21759}\InprocSer
ver32
Edit the ThreadingModel value from Free to Both.
Quit Registry Editor.
You may have to stop, and then restart SQL Server for the workaround to
take affect.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article.
MORE INFORMATION
For more information about how to use the SQL Server VDI, see the
"Virtual Backup Device Samples" topic in SQL Server Books Online.
Last Reviewed: 7/17/2002
Keywords: kbbug KB323602
Best Regards,
Elenara
-Mensagem original-
De: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED]
Enviada em: quarta-feira, 3 de setembro de 2003 11:02
Para: [EMAIL PROTECTED]
Assunto: TDP for SQL v2.2 backup errors..
B/A client 4.1.2.12
TDP for SQL v2.2
SQL 2000 SP3
TSM server 5.1.6.2
AIX 5.1.5
We are having trouble backing up on particular DB. Anyone seen this
before?
>From tdpsql.log
09/03/2003 08:27:26 ACO0302E A failure occured on stripe number (0), rc
=
418
09/03/2003 08:27:26 ANS1245E (RC122) Format unknown
09/03/2003 08:27:26 ACO5452E Unable to delete temporary object:
(USHERNC132SQL\data\0001) (\gns) (\full.200309030826390CF4)
09/03/2003 08:27:26 ANS1026E (RC136) Session rejected: Communications
protocol error
09/03/2003 08:27:26 Backup of gns failed.
09/03/2003 08:27:26 ANS1245E (RC122) Format unknown
>From W2K event logs...
18210 :
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on
backup device 'TDPSQL-0CF4-'. Operating system error 995(The I/O
operation has been aborted because of either a thread exit or an
application
request.).
3041 :
BACKUP failed to complete the command USE master BACKUP DATABASE
[gns] TO VIRTUAL_DEVICE=N'TDPSQL-0CF4-' WITH BLOCKSIZE=512,
MAXTRANSFERSIZE=1048576, NAME=N'full',
DESCRIPTION=N'TDPSQL-0CF4-
(TDP MS SQL V2)'
Any thoughts??
Regards,
Matt
This message (including any attachments) contains confidential
information
intended for a specific individual and purpose, and is protected by law.
If
you are not the intended recipient, you should delete this message. Any
disclosure, copying, or distribution of this message, or the taking of
any
action based on it, is strictly prohibited.
RES: INACTIVE -> ACTIVE FILE VERSION
Thank you Alex, My problem was solved yesterday by our friend Andrew Raibeck. Att, Elenara -Mensagem original- De: Alex Paschal [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 16 de julho de 2003 15:46 Para: [EMAIL PROTECTED] Assunto: Re: INACTIVE -> ACTIVE FILE VERSION Elenara, It actually looks like you're selecting from the backups table here. When you do your restore, try displaying active and inactive versions (green diamond button, or view menu). That should show the file. If not, please describe more closely exactly what you do when you attempt the restore, because from your description I'm not certain exactly what you might be experiencing. Alex Paschal Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: T_MML [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 12:00 PM To: [EMAIL PROTECTED] Subject: INACTIVE -> ACTIVE FILE VERSION Importance: High Hi all, The TSM modified the state of the archive that necessary for restoration, "state: inactive_version" and does not show to the archives in client TSM. Existe a form to bring these data in return? The data continue in ribbons. NODE_NAME: SERVER1 FILESPACE_NAME: \\SERVER1\c$ FILESPACE_ID: 8 STATE: INACTIVE_VERSION TYPE: FILE HL_NAME: \FOLDER1\MY DOCUMENTS\DOCS\ LL_NAME: TRAINEE (VERSION 1).XLS OBJECT_ID: 39898187 BACKUP_DATE: 2002-11-13 11:07:02.00 DEACTIVATE_DATE: 2003-05-20 08:37:48.00 OWNER: CLASS_NAME: DEFAULT VOLUME_NAME: AA0004L1 NODE_NAME: SERVER1 TYPE: Bkup FILESPACE_NAME: \\SERVER1\c$ FILE_NAME: \FOLDER1\MY DOCUMENTS\DOCS\TRAINEE (VERSION 1).XLS AGGREGATED: 12/16 FILE_SIZE: 1137850 SEGMENT: 1/1 CACHED: No FILESPACE_ID: 7 FILESPACE_HEXNAME: 5c5c67616c62655c7824 FILE_HEXNAME: 5c424b5058505c5445434e4f53554c5c4d415243454c4f205f20434f4e5- 3554c544f525c4d5920444f43554d454e54535c475241564152204e4f2- 04344204f53204152515549564f532044455354412050415354415c434- 420315c20545245494e414d454e544f202856455253494f4e2031292e5- 84c53 King Regards, Elenara Geraldo Senior TSM Administrator MML Systems Phone : 55 41 342 7864 Cellular: 55 41 91035796
RES: lan-free tape dismount retention
Hi Joni, You it restarted the TSM Server after modifying the Mount Retention (min): 9,999? Att, Elenara -Mensagem original- De: Joni Moyer [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 16 de julho de 2003 10:08 Para: [EMAIL PROTECTED] Assunto: lan-free tape dismount retention Hello! I'm working on the TPOC right now and I have the mount retention set to minutes, but as you can see below the volumes is being dismounted seconds after the archive session to the tape drive has completed for the storage agent. Is there a parameter that must be set on the storage agent? Or do I need to change something under the TSM server configuration. Thanks! 07/16/03 08:45:02 ANR0403I Session 421 ended for node PGSU017 (SUN SOLARIS). 07/16/03 08:46:00 ANR8325I (Session: 249, Origin: STORAGENT) Dismounting volume 331ABJ - 1 minute mount retention expired. 07/16/03 08:46:05 ANR8336I (Session: 249, Origin: STORAGENT) Verifying label of LTO volume 331ABJ in drive LTO2_DRIVE-1 (/dev/rmt/2st). 07/16/03 08:47:17 ANR0408I Session 427 started for server STORAGENT (Solaris 2.6/7/8 ) (Tcp/Ip) for library sharing. 07/16/03 08:47:17 ANR8336I Verifying label of LTO volume 331ABJ in drive LTO2_DRIVE-1 (/dev/rmt/3st). 07/16/03 08:47:17 ANR8468I (Session: 249, Origin: STORAGENT) LTO volume 331ABJ dismounted from drive LTO2_DRIVE-1 (/dev/rmt/2st) in library 3584_LTO2. Here is the device class that the data was going to: Device Class Name: DEVCLASS_LTO2 Device Access Strategy: Sequential Storage Pool Count: 1 Device Type: LTO Format: ULTRIUM2 Est/Max Capacity (MB): 409,600.0 Mount Limit: 2 Mount Wait (min): 60 Mount Retention (min): 9,999 Label Prefix: ADSM Library: 3584_LTO2 Directory: Server Name: Retry Period: Retry Interval: Shared: Joni Moyer Systems Programmer [EMAIL PROTECTED] (717)975-8338
INACTIVE -> ACTIVE FILE VERSION
Hi all, The TSM modified the state of the archive that necessary for restoration, "state: inactive_version" and does not show to the archives in client TSM. Existe a form to bring these data in return? The data continue in ribbons. NODE_NAME: SERVER1 FILESPACE_NAME: \\SERVER1\c$ FILESPACE_ID: 8 STATE: INACTIVE_VERSION TYPE: FILE HL_NAME: \FOLDER1\MY DOCUMENTS\DOCS\ LL_NAME: TRAINEE (VERSION 1).XLS OBJECT_ID: 39898187 BACKUP_DATE: 2002-11-13 11:07:02.00 DEACTIVATE_DATE: 2003-05-20 08:37:48.00 OWNER: CLASS_NAME: DEFAULT VOLUME_NAME: AA0004L1 NODE_NAME: SERVER1 TYPE: Bkup FILESPACE_NAME: \\SERVER1\c$ FILE_NAME: \FOLDER1\MY DOCUMENTS\DOCS\TRAINEE (VERSION 1).XLS AGGREGATED: 12/16 FILE_SIZE: 1137850 SEGMENT: 1/1 CACHED: No FILESPACE_ID: 7 FILESPACE_HEXNAME: 5c5c67616c62655c7824 FILE_HEXNAME: 5c424b5058505c5445434e4f53554c5c4d415243454c4f205f20434f4e5- 3554c544f525c4d5920444f43554d454e54535c475241564152204e4f2- 04344204f53204152515549564f532044455354412050415354415c434- 420315c20545245494e414d454e544f202856455253494f4e2031292e5- 84c53 King Regards, Elenara Geraldo Senior TSM Administrator MML Systems Phone : 55 41 342 7864 Cellular: 55 41 91035796
RES: DATABASE HELP!!!
Yes, I could change the status of the inactive archives for asset Thanks! Att, Elenara -Mensagem original- De: Remco Post [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 11 de julho de 2003 10:25 Para: [EMAIL PROTECTED] Assunto: Re: DATABASE HELP!!! On donderdag, jul 10, 2003, at 20:58 Europe/Amsterdam, T_MML wrote: > Hi all, > > > > exists a form of edtar, manually modifying the database of the TSM? > > > > Hi, no, there is no way to manually edit the contents of the TSM databse. And I have a feeling you really don't want to do that anyway. Is there a reason you are asking? > > King Regards, > > > > Elenara Geraldo > > TSM Administrator > > MML Systems > > Phone : 55 41 342 7864 > > Cellular: 55 41 91035796 > > > -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdamhttp://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
DATABASE HELP!!!
Hi all, exists a form of edtar, manually modifying the database of the TSM? King Regards, Elenara Geraldo TSM Administrator MML Systems Phone : 55 41 342 7864 Cellular: 55 41 91035796
RES: Weekday
Yes... select day in the "DAYofweek" parameter when to define your schedule. For more information, write " help define schedule" in the TSM Server. .-DAYofweek--=--ANY---. >--+-+--> '-DAYofweek--=--+-ANY---+-' +-WEEKDay---+ +-WEEKEnd---+ +-SUnday+ +-Monday+ +-TUesday---+ +-Wednesday-+ +-THursday--+ +-Friday+ '-SAturday--' (r) Elenara Geraldo TSM Administrator MML Systems Phone : 55 41 342 7864 Cellular: 55 41 91035796 -Mensagem original- De: Zosimo Noriega [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 28 de maio de 2003 05:10 Para: [EMAIL PROTECTED] Assunto: Weekday Hi, In TSM, is it possible to change the weekdays to start Saturday to Wednesday instead of Monday to Friday in order to avoid schedule running on Thursday and Friday. Any help from you would be appreciated. Zosi Noriega
RES: SQL TDP fails to run with scheduler
Philip, Attention for the parameter "OPTIONS" The configuration file " progra~1\tivoli\tsm\tdpsql\sqlfull.cmd " it must be placed in OBJECTS ... OK! 02/18/2003 02:37:35 Schedule Name: ENTERPRISE_SQL_BACKUP 02/18/2003 02:37:35 Action:Command 02/18/2003 02:37:35 Objects: 02/18/2003 02:37:35 Options: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd <--- 02/18/2003 02:37:35 Server Window Start: 02:30:00 on 02/19/2003 02/18/2003 02:37:35 < CORRECT FORM> Policy Domain Name: Schedule Name: ENTERPRISE_SQL_BACKUP Description: Action: Command Options: Objects: c:\tsmboticario\optfiles\diario\sqlfull.cmd Priority: -- Start Date/Time: -- Duration: -- Period: -- Day of Week: -- Expiration: Last Update by (administrator): ADMIN Last Update Date/Time: -- Managing profile: King regards, Elenara ® Elenara Geraldo TSM Administrator Phone : 55 41 381 7849 Cellular: 55 44 91077262 -Mensagem original- De: Hamlin, Philip [mailto:[EMAIL PROTECTED]] Enviada em: terça-feira, 18 de fevereiro de 2003 14:03 Para: [EMAIL PROTECTED] Assunto: SQL TDP fails to run with scheduler I am having trouble getting the SQL TDP v2.2.1 to run with the scheduler. Here is the system description: Both the TSM server and the SQL server are running Windows 2000 with SP3. The SQL server is running SQL 2000 patched to SP3. TSM server version 4.2.1.12 TSM BAClient version 4.2.2.8 TSM Tivoli Data Protection of Microsoft SQL Server v2.2.1.0 I installed the TDP following the install instructions and the Redbook. The directories are default. I installed a separate scheduler service using default names. The scheduler kicks off and (as you can see) quits with three error lines in the excerpt from the tdpsched.log. I can run the "sqlfull.cmd" manually and it runs fine each and every time. I have included the tdpsched.log, sqlfull.cmd, and dsm.opt files below. I set this TSM install as close as I could to an another, existing server where the TDP works great. I have tried to remark out items in the dsm.opt file (which I think is where the complains are coming from). I have recreated the dsm.opt and sqlfull.cmd files in case they were somehow corrupted. When I redid the dsm.opt file, I used a copy of the sample file to start with and modified to what you see. I looked at ADSM.org for help as well as the IBM Tivoli sites. I cannot find anything that is relevant. I first installed the v2.2.0 with the 4.2.28 baclient. Then I "upgraded" to version 2.2.1.0. Same outcome with both versions. Any ideas would be most appreciated. Here are the log and file excerpts: TDPSCHED.LOG 02/18/2003 02:37:35 Executing scheduled command now. 02/18/2003 02:37:35 ANS1038S Invalid option specified 02/18/2003 02:37:35 ANS1820E Command line options must be preceded by a '-' 02/18/2003 02:37:35 ANS1512E Scheduled event 'ENTERPRISE_SQL_BACKUP' failed. Return code = 4. 02/18/2003 02:37:35 Sending results for scheduled event 'ENTERPRISE_SQL_BACKUP'. 02/18/2003 02:37:35 Node Name: CIONISQL001_SQL 02/18/2003 02:37:35 Session established with server CIONITSM001: Windows NT 02/18/2003 02:37:35 Server Version 4, Release 2, Level 1.12 02/18/2003 02:37:35 Server date/time: 02/18/2003 02:37:35 Last access: 02/17/2003 20:42:35 02/18/2003 02:37:35 Results sent to server for scheduled event 'ENTERPRISE_SQL_BACKUP'. 02/18/2003 02:37:35 ANS1483I Schedule log pruning started. 02/18/2003 02:37:35 Schedule Log Prune: 684 lines processed. 104 lines pruned. 02/18/2003 02:37:35 ANS1484I Schedule log pruning finished successfully. 02/18/2003 02:37:35 Querying server for next scheduled event. 02/18/2003 02:37:35 Node Name: CIONISQL001_SQL 02/18/2003 02:37:35 Session established with server CIONITSM001: Windows NT 02/18/2003 02:37:35 Server Version 4, Release 2, Level 1.12 02/18/2003 02:37:35 Server date/time: 02/18/2003 02:37:35 Last access: 02/18/2003 02:37:35 02/18/2003 02:37:35 --- SCHEDULEREC QUERY BEGIN 02/18/2003 02:37:35 --- SCHEDULEREC QUERY END 02/18/2003 02:37:35 Next operation scheduled: 02/18/2003 02:37:35 02/18/2003 02:37:35 Schedule Name: ENTERPRISE_SQL_BACKUP 02/18/2003 02:37:35 Action:Command 02/18/2003 02:37:35 Objects: 02/18/2003 02:37:35 Options: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd 02/18/2003 02:37:35 Server Window Start: 02:30:00 on 02/19/2003 02/18/2003 02:37:35 02/18/2003 02:37:35 Schedule will be refre
ENC: SQL TDP fails to run with scheduler
Philip, Attention for the parameter "OPTIONS" The configuration file " progra~1\tivoli\tsm\tdpsql\sqlfull.cmd " it must be placed in OBJECTS ... OK! 02/18/2003 02:37:35 Schedule Name: ENTERPRISE_SQL_BACKUP 02/18/2003 02:37:35 Action:Command 02/18/2003 02:37:35 Objects: 02/18/2003 02:37:35 Options: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd <--- 02/18/2003 02:37:35 Server Window Start: 02:30:00 on 02/19/2003 02/18/2003 02:37:35 < CORRECT FORM> Policy Domain Name: Schedule Name: ENTERPRISE_SQL_BACKUP Description: Action: Command Options: Objects: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd <- Priority: -- Start Date/Time: -- Duration: -- Period: -- Day of Week: -- Expiration: Last Update by (administrator): ADMIN Last Update Date/Time: -- Managing profile: King regards, Elenara ® Elenara Geraldo TSM Administrator Phone : 55 41 381 7849 Cellular: 55 44 91077262 -Mensagem original- De: Hamlin, Philip [mailto:[EMAIL PROTECTED]] Enviada em: terça-feira, 18 de fevereiro de 2003 14:03 Para: [EMAIL PROTECTED] Assunto: SQL TDP fails to run with scheduler I am having trouble getting the SQL TDP v2.2.1 to run with the scheduler. Here is the system description: Both the TSM server and the SQL server are running Windows 2000 with SP3. The SQL server is running SQL 2000 patched to SP3. TSM server version 4.2.1.12 TSM BAClient version 4.2.2.8 TSM Tivoli Data Protection of Microsoft SQL Server v2.2.1.0 I installed the TDP following the install instructions and the Redbook. The directories are default. I installed a separate scheduler service using default names. The scheduler kicks off and (as you can see) quits with three error lines in the excerpt from the tdpsched.log. I can run the "sqlfull.cmd" manually and it runs fine each and every time. I have included the tdpsched.log, sqlfull.cmd, and dsm.opt files below. I set this TSM install as close as I could to an another, existing server where the TDP works great. I have tried to remark out items in the dsm.opt file (which I think is where the complains are coming from). I have recreated the dsm.opt and sqlfull.cmd files in case they were somehow corrupted. When I redid the dsm.opt file, I used a copy of the sample file to start with and modified to what you see. I looked at ADSM.org for help as well as the IBM Tivoli sites. I cannot find anything that is relevant. I first installed the v2.2.0 with the 4.2.28 baclient. Then I "upgraded" to version 2.2.1.0. Same outcome with both versions. Any ideas would be most appreciated. Here are the log and file excerpts: TDPSCHED.LOG 02/18/2003 02:37:35 Executing scheduled command now. 02/18/2003 02:37:35 ANS1038S Invalid option specified 02/18/2003 02:37:35 ANS1820E Command line options must be preceded by a '-' 02/18/2003 02:37:35 ANS1512E Scheduled event 'ENTERPRISE_SQL_BACKUP' failed. Return code = 4. 02/18/2003 02:37:35 Sending results for scheduled event 'ENTERPRISE_SQL_BACKUP'. 02/18/2003 02:37:35 Node Name: CIONISQL001_SQL 02/18/2003 02:37:35 Session established with server CIONITSM001: Windows NT 02/18/2003 02:37:35 Server Version 4, Release 2, Level 1.12 02/18/2003 02:37:35 Server date/time: 02/18/2003 02:37:35 Last access: 02/17/2003 20:42:35 02/18/2003 02:37:35 Results sent to server for scheduled event 'ENTERPRISE_SQL_BACKUP'. 02/18/2003 02:37:35 ANS1483I Schedule log pruning started. 02/18/2003 02:37:35 Schedule Log Prune: 684 lines processed. 104 lines pruned. 02/18/2003 02:37:35 ANS1484I Schedule log pruning finished successfully. 02/18/2003 02:37:35 Querying server for next scheduled event. 02/18/2003 02:37:35 Node Name: CIONISQL001_SQL 02/18/2003 02:37:35 Session established with server CIONITSM001: Windows NT 02/18/2003 02:37:35 Server Version 4, Release 2, Level 1.12 02/18/2003 02:37:35 Server date/time: 02/18/2003 02:37:35 Last access: 02/18/2003 02:37:35 02/18/2003 02:37:35 --- SCHEDULEREC QUERY BEGIN 02/18/2003 02:37:35 --- SCHEDULEREC QUERY END 02/18/2003 02:37:35 Next operation scheduled: 02/18/2003 02:37:35 02/18/2003 02:37:35 Schedule Name: ENTERPRISE_SQL_BACKUP 02/18/2003 02:37:35 Action:Command 02/18/2003 02:37:35 Objects: 02/18/2003 02:37:35 Options: c:\progra~1\tivoli\tsm\tdpsql\sqlfull.cmd 02/18/2003 02:37:35 Server Window Start: 02:30:00 on 02/19/2003 02/18/2003 02:37:35 02/18/2003 02:37:35 Schedule will be refr
RES: ???????????? in TSM status
Hi, the description of the status follows below: Status of Schedule with command "Query--EVEN--domain_name--schedule_name-->" Specifies whether the startup of the event has been completed. Possible values are: "Completed" Specifies that the scheduled event has been completed. "Missed" Specifies that the scheduled startup window for this event has passed and the schedule has not begun. "Failed" Specifies that the client reports a failure in executing the scheduled operation and successive retries have not succeeded. "Started" Specifies that the event has begun processing. "Restarted" Specifies that the client has retried processing the scheduled operation. "Severed" Specifies that the communications with the client is severed before the event can complete. "Future" Specifies that the beginning of the startup window for the event is in the future. "Pending" Specifies that the QUERY EVENT command was issued during the startup window for the event, but processing the scheduled operation has not yet begun. "Uncertain" Specifies that the state of the event cannot be determined. The server specifies Uncertain if the QUERY EVENT command does not find an event record. An event record will not be found if the record was deleted or if the server was unavailable during the scheduled startup window (the schedule was never started). Records with Uncertain status do not reside in the database. If you do not want these records to be displayed, either specify EXCEPTIONSONLY=YES or delete the schedule if it is no longer needed. Note: When a scheduled operation is processing without having been restarted, within its specified duration, the Status field shows Started. If the operation continues beyond the specified duration, no event record is created. If a query is issued after the specified duration has passed, the Status shows as Failed even if the operation is still running. After the operation completes, an event record is created, and a subsequent query shows the result in the Status field. (r) Elenara Geraldo TSM System Administrator Curitiba - Parana - Brazil Number phone: 55 41 381 7849 Cellular phone: 55 44 91077262 -Mensagem original- De: shekhar Dhotre [mailto:[EMAIL PROTECTED]] Enviada em: segunda-feira, 3 de fevereiro de 2003 20:01 Para: [EMAIL PROTECTED] Assunto: in TSM status Hi All , what does ?? means in TSM status , I am searching in help q eve but don't see anything pointing to ? tsm: LLNBUPASP>q eve * * begind=-1 Scheduled Start Actual Start Schedule Name Node Name Status - - - 02/03/03 18:50:00 02/04/03 08:19:28 MON_NOTES_INC LLNOTESP Restarted 02/03/03 20:31:01 02/03/03 20:31:19 MON_INC PLAZMN11 Completed 02/03/03 20:31:01 02/03/03 20:38:43 MON_INC PLAZML03 Completed 02/03/03 20:31:01 02/03/03 20:31:16 MON_INC PLAZMN30 Completed 02/03/03 20:31:01 02/03/03 20:31:15 MON_INC PLAZMN12 Completed 02/03/03 20:31:01 02/03/03 20:31:16 MON_INC PLAZMN13 Completed 02/03/03 20:31:01 02/03/03 20:31:15 MON_INC PLAZMN14 Completed 02/03/03 20:31:01 02/03/03 20:31:12 MON_INC PLAZNZ01 Completed 02/03/03 20:31:01 02/04/03 08:19:38 MON_INC PLAZNC02 Restarted 02/03/03 20:31:01 02/03/03 20:31:11 MON_INC PLAZNC01 Started 02/03/03 20:31:01 02/03/03 20:31:14 MON_INC PLAZNC03 (?) 02/03/03 20:31:01 02/03/03 20:31:20 MON_INC AUSYD01MN601 (?) 02/03/03 20:31:01 02/03/03 20:41:24 MON_INC AUSYD01MZ001 Completed 02/03/03 20:31:01 02/03/03 20:31:14 MON_INC AUSYD01MZ201 Completed 02/03/03 20:31:01 MON_INC AUSYD01MZ401 Missed 02/03/03 20:31:01 02/03/03 20:31:13 MON_INC AUSYD01MZ601 Completed 02/03/03 20:31:01 02/03/03 23:39:10 MON_INC AUSYD01MN602 Completed 02/03/03 21:00:00 02/03/03 21:00:12 LLSYDDEV1 LLSYDDEV1 Completed 02/03/03 23:01:00 02/03/03 23:01:03 MON_NDS_INC PLAZNZ01 Completed
RES: TSM x ARCserve
Thank you Andy. Regards, Elenara ® Elenara Geraldo TSM System Administrator Curitiba - Parana - Brazil Number phone: 55 41 381 7849 Cellular phone: 55 44 91077262 -Mensagem original- De: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Enviada em: sábado, 1 de fevereiro de 2003 17:29 Para: [EMAIL PROTECTED] Assunto: Re: TSM x ARCserve The feature you describe sounds like a variation on hierarchical storage management (like TSM's HSM feature), although HSM is not available on all platforms. The TSM ARCHIVE command can delete the files after they have been archived, but has no feature to process files based on number of days last accessed. But I do not think it would be too difficult to create a script to traverse your file systems and build a list of files to archive based on the last access date. Then you can use the TSM ARCHIVE command (with the option to delete the files) to archive the files in your list. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. T_MML <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/31/2003 16:36 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:TSM x ARCserve Hi all, I have one option equal in the TSM Backup Client? `´ `´ Delete Files After Backup - ARCserve Delete source files from the source machine after they have been backed up to tape. Use this option to perform disk grooming. Set a filter to back up files that haven't been accessed for a certain period of time (say, 3 months or so), and then select this option to delete these old, unaccessed files from the source disk. Regards, Elenara Elenara Geraldo TSM System Administrator Curitiba - Parana - Brazil Number phone: 55 41 381 7849 Cellular phone: 55 44 91077262
TSM x ARCserve
Hi all, I have one option equal in the TSM Backup Client? `´ `´ Delete Files After Backup - ARCserve Delete source files from the source machine after they have been backed up to tape. Use this option to perform disk grooming. Set a filter to back up files that haven't been accessed for a certain period of time (say, 3 months or so), and then select this option to delete these old, unaccessed files from the source disk. Regards, Elenara ® Elenara Geraldo TSM System Administrator Curitiba - Parana - Brazil Number phone: 55 41 381 7849 Cellular phone: 55 44 91077262
