Re: WNT TSM Client reinstall hang
H if your system is otherwise intact, I wonder if the setup program is trying to go in to repair mode. If you go to Add/Remove Programs, are you able to remove the TSM client? If so, then try installing after you remove. 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. Zoltan Forray/AC/VCU [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/29/2002 07:40 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:WNT TSM Client reinstall hang Got a strange situation. An NT box lunched one of its hard-drives/partitions. Unfortunately, it happens to be the partition that had the TSM client on it (not C:). Now, everytime we try to reinstall the client, it hangs on TSM_UPGRADE_PATH ! Ran REGCLEAN. Suggestions ?
Re: Backups going to disk Fail without Tape drive online?
A couple of things to check: - Is anyone using INCLUDE statements to bind files to management classes that go straight to tape? - Check the RETONLY in your copygroup settings. By default, the client will bind directories to the management class with the highest RETONLY value. If more than one class has this high value, then the class whose name is alphanumerically highest will be the one that is used. Maybe you have a copygroup whose destination is tape and whose RETONLY value happens to be the highest. 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. Chris Murphy [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/29/2002 09:07 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Backups going to disk Fail without Tape drive online? Greetings *SM'ers, Environment: Server: Win2K SP2, TSM 5.1.1 Clients: NT4 SP6a TSM 5.1.1 and Win2K SP2, TSM 5.1.1 I am relatively new to TSM, and not afraid of being humbled! Our library failed yesterday and is being repaired today. Last night most (but not all) of the backups failed on the clients with errors like the one below. All clients point to disk pools for their backups and the disk pools are/were online and available. I assumed the backups would continue despite the library not being available, am I wrong to assume this? I understand our migration/reclamation is not possible today until the library is repaired, but we specifically designed our diskpools to be able to handle 3-4 days of backups without migration for this very reason. As is evident by the Pct Migr. Number, the pool took on almost no data during the backups. Simultaneous writes to Copy Pools are disabled as well. I guess I am wondering why TSM needs the tape drive during the backups if the clients point to the disk which has plenty of space and is available? Any help would be greatly appreciated. In all likelihood, this is a PEBCAK problem. :-( In the future, is there a good or graceful way to take a library offline. I know it can be done with the VARY command against disks, but is there a similar option for libraries? snip 08/28/2002 18:00:31 --- SCHEDULEREC STATUS END 08/28/2002 18:00:31 ANS1312E Server media mount not possible 08/28/2002 18:00:31 --- SCHEDULEREC OBJECT END DAILY_INCR 08/28/2002 18:00:00 08/28/2002 18:00:31 ANS1512E Scheduled event 'DAILY_INCR' failed. Return code = 12. snip Storage Pool Name: GENERAL_BKP Storage Pool Type: Primary Device Class Name: DISK Estimated Capacity (MB): 209,920.0 Pct Util: 21.3 Pct Migr: 0.1 Pct Logical: 100.0 High Mig Pct: 100 Low Mig Pct: 60 snip Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No snip Chris Murphy IT Network Analyst ID Dept. of Lands (208) 334-0293 [EMAIL PROTECTED]
Re: tsm client is down-level with this server version
Would it be possible to provide a safe and tested script, or an APAR that introduces a new secret command, that can untangle this mess in some automated way? The current method of fixing it is way too costly. Coincidentally, I just had that conversation with one of our server developers, and they will look into doing this (no commitment right now, but the odds are pretty good). 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. Roger Deschner [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/29/2002 09:03 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: tsm client is down-level with this server version We've got half a dozen clients stuck like this right now. The first case I had was an important, tenured, and extremely impatient professor who had converted from Win 98 to Win XP, decided that XP stinks, and wanted to format his hard drive and restore his comfortable old Win 98 system from ITSM. (This is what backup is for, right?) Because this was basically a point-in-time restore, deleting the node was not a possible strategy. He was incredulous that it took me several days of communication with IBM support to straighten it out and peppered me with emails demanding that I work faster on it the whole time I was exchanging special commands and their outputs. The second was an aggressively confused user who was backing up two computers using one node, and who thereby un-did the fix mere hours after I had spent several hours with IBM Support fixing it. I refused to fix it again for this user and made their node restore-only until I communicated with their supervisor about our one computer per node policies. I have not even begun to figure out the rest, because I know it is a huge black hole for my time. Before I even call Support, I've got to reach each end-user and figure out how they caused this, to insure that they don't inadvertently un-do it after we (me and Support) spend several hours fixing it. Those who would want to try the solution on their own are misguided; it cannot be done - Andy Raibeck is absolutely correct in this regard. You must call Tivoli Support, but while they will be able to help, it will be a lengthly and complicated process. Budget several hours per case. And type carefully!!! I really wish the existence of a correcting APAR was made more public. I'm going to install it soon (today!), but I'll still have those half dozen clients who appear to have unicode cooties to untangle. Would it be possible to provide a safe and tested script, or an APAR that introduces a new secret command, that can untangle this mess in some automated way? The current method of fixing it is way too costly. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
Re: WNT TSM Client reinstall hang
Hi Zoltan, Does the client still show up in the Add/Remove Programs? If so, if you click Change, does it lead you to a repair option? If so, give that a shot. If that doesn't work, then what exactly did you do with the MSI cleanup utility? Also, can you run setup as follows: setup /v/l*v setup.log Also, give support a call and be sure to give them the setup.log file, as well as let them know how you got to where you are right now. Sorry I don't have a more immediate answer for you. 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. Zoltan Forray/AC/VCU [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/29/2002 08:49 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: WNT TSM Client reinstall hang Yes, we have tried un/reinstall. I also found some comments, in ADSM-L about trying the MSI Clean-up utility. We have tried it, as well. Current status: Tried the Add/Remove Programs . This time it asked for the MSI file. So we pointed it to it. It ran a few seconds and simply quit. Tried SETUP.EXE, again. Asks for LANGUAGE. Chugs a little and simply blinks-out. No errors, no messages, nadazip Andy Raibeck [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/29/2002 11:26 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: WNT TSM Client reinstall hang H if your system is otherwise intact, I wonder if the setup program is trying to go in to repair mode. If you go to Add/Remove Programs, are you able to remove the TSM client? If so, then try installing after you remove. 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. Zoltan Forray/AC/VCU [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/29/2002 07:40 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:WNT TSM Client reinstall hang Got a strange situation. An NT box lunched one of its hard-drives/partitions. Unfortunately, it happens to be the partition that had the TSM client on it (not C:). Now, everytime we try to reinstall the client, it hangs on TSM_UPGRADE_PATH ! Ran REGCLEAN. Suggestions ?
Re: tsm client is down-level with this server version
I should also add, this has been fixed to some extent in server 4.2.2.0, per APAR IC32075. Note that this will not fix any clients where the problem already exists, but it should prevent the problem from occurring once the PTF is installed. ABSTRACT: ANS1357S WHEN CONNECTING WITH NON-UNICODE CLIENT ERROR DESCRIPTION: Once a unicode TSM client (V4.2.0 or higher Windows NT/2000 or V4.2.1.15 or higher Windows XP client) has been used to connect to a TSM V4.2 server with a given node name, that node name can no longer be used by a non-unicode TSM client. If you attempt to connect with that node name using a non-unicode TSM client, you will receive the following error: . You may see the following error: ANR0428W Session 432 for node ENCRYP (WinNT) refused - client is down-level with this server version. .. ANS1357S Session rejected: Downlevel client code version . Any operation attempted by a non-unicode TSM client with this node name, will fail with the above error message. For example, if the V4.2 Windows 2000 client has done queries or restores for non-unicode filesystems for NODE1 to a V4.2 TSM server, a V4.1 Windows 2000 client can no longer connect to that V4.2 server as NODE1. Initial Impact: High LOCAL FIX: None. PROBLEM SUMMARY: * USERS AFFECTED: Non-unicode clients connecting to a V4.2 * * server once a unicode client (V4.2.0 or * * higher Windows NT/2000 or V4.2.1.15 or * * higher Windows XP ) has been used to* * access that server using the non-unicode * * client's nodename. * * PROBLEM DESCRIPTION: ANS1357S Session rejected: Downlevel* * client code version received after * * connecting to server. * * RECOMMENDATION: Install the PTF * Once a TSM unicode client (V4.2.0 or higher Windows NT/2000 or V4.2.1.15 or higher Windows XP ) node has connected to a TSM 4.2.0 or greater server (any platform) using a non-unicode client's node, the non-unicode client node may no longer connect to that server. A down level client message is received. PROBLEM CONCLUSION: The TSM unicode client (V4.2.0 or higher Windows NT/2000 or V4.2.1.15 or higher Windows XP ) can now be used for queries and restores, and a lower level or non-unicode 4.2 client can still connect to the server. As long as no unicode filespaces exist, the 4.2 and above TSM server will allow a lower level or non--unicode V4.2 client to connect to the server. If any unicode filespaces exist for a node, a unicode client will be required to connect to the server. If any unicode filespaces exist for a node, and lower level or non-unicode clients attempt to connect, the connection will be refused, and the down level client message will be displayed. 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. Andrew Raibeck/Tucson/IBM@IBMUS Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/28/2002 07:43 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: tsm client is down-level with this server version Matt, If you are experiencing this problem, then you need to contact IBM support. The procedures for resolving this are potentially dangerous, and are therefore undocumented. They are not intended to be shared publicly. 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. Adams, Matt (US - Hermitage) [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/28/2002 07:11 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: tsm client is down-level with this server version I would be interested in hearing what Tivoli support had to say on patching or correcting this. Thanks, Matt -Original Message- From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 8:58 AM To: [EMAIL PROTECTED] Subject
Re: Expiration
Hi Bill, What does QUERY LICENSE have to say? That should show you what you are using and what you are licensed for. 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. Bill Wheeler [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/26/2002 05:23 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Expiration Hello All, I have just upgraded my TSM server and client to 5.1 and now my expiration does not seem to be working. Every time I run the expiration this is what I get: ANR4391I Expiration processing node F50_CLIENT, filespace /pdprodrep3, fsId 26, domain STANDARD, and management class SATURDAY - for ARCHIVE type files. 08/26/02 08:11:18 ANR2841W Server is NOT IN COMPLIANCE with license terms. I am not sure why the server is not in compliance. Can someone help me out on this one? Server: TSM 5.1 Client: TSM 5.1 OS: AIX 4.3.3
Re: Bare Metal Restore for Tivoli Storage Manager
Back on July 19, Richard Harrison wrote (in part): While we have not yet released any product enhancements since the acquisition (enhancements are planned, pending the outcome of the reseller negotiations), we continue to provide technical support for BMR for TSM and have shipped two patches containing defect fixes. The currently available version of BMR for TSM is 3.2.1; it supports the following platforms: AIX 4.x, 5.1; Sun Solaris 2.6, 7, 8; HP-UX 10.20, 11.0, 11i; Windows NT 4.0 Workstation, Server, Enterprise Edition, Terminal Server Edition; Windows 2000 Professional, Server, Advanced Server. The BMR Server components run on AIX, Solaris, and HP-UX. TSM 5.1 and 4.2.2 both are currently not supported. Both have been tested and each have been found to have blocking defects when used with BMR for TSM 3.2.1. We are currently sizing the effort required to remedy these issues. If the blocking defects are with regard to Windows client APAR IC34296 (TSM CLIENT DOES NOT BACK UP BOOT.INI, NTLDR, NTDETECT.COM DURING BACKUP OF SYSTEM OBJECTS.), then this problem has been fixed in patches 4.2.2.8 and 5.1.1.3. Refer to my post of August 23, 2002, for more info: http://msgs.adsm.org/cgi-bin/get/adsm0208/931.html 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.
Re: Select problems in 5.1.1 ... again
Zlatko, I was replying to Paul, not Dennis. I did not see anyone else post about this problem. I did go back and look at the archives, though, and yes indeed, there is a post from Denis L'Huillier about this. So thanks for mentioning it. And sorry, Denis, I did not intentionally ignore you. IC34207 also covers 4.2.2.x (if you look at the complete APAR text, 4.2.2.x, 5.1.0.x, and 5.1.1.x are all mentioned). Patch level 4.2.2.10 includes the fix for this APAR. The follow-on patch to 5.1.1.3 is also targeted to include this fix. 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. Zlatko Krastev/ACIT [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/25/2002 01:48 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Select problems in 5.1.1 ... again Andy, but Dennis is reporting this on 4.2.2.9 as well so maybe the APAR have to updated (and worked on). Zlatko Krastev IT Consultant Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Re: Select problems in 5.1.1 ... again This looks like APAR IC34207, of which the pertinent text is shown below: === ABSTRACT: BACKUP/ARCHIVE INFO IS INCORRECT IN SUMMARY TABLES. ERROR DESCRIPTION: Backup/Archive stats are wrong in the TSM Server Summary Table. This is having on all platforms of the TSM Server V5.1.X.X. . The status are being truncated by the 1000... === 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. Paul van Dongen [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/21/2002 06:53 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Select problems in 5.1.1 ... again Hello all, I have just finished (about ten days now) an upgrade of TSM 4.2 to 5.1. Being aware of the zero bytes problem in the summary table, I upgraded to 5.1.1.2. Now, I don´t get zero bytes in my summary entries for backups, but all my files (examined and affected) counters are being divided by 1000 Someone got this problem too? Here is an example: Summary table: START_TIME: 2002-08-09 19:29:20.00 END_TIME: 2002-08-09 19:47:19.00 ACTIVITY: BACKUP NUMBER: 8015 ENTITY: COMMMETH: Tcp/Ip ADDRESS: 10.131.64.29:54333 SCHEDULE_NAME: EXAMINED: 40 AFFECTED: 39 FAILED: 0 BYTES: 3857289012 IDLE: 1076 MEDIAW: 0 PROCESSES: 1 SUCCESSFUL: YES VOLUME_NAME: DRIVE_NAME: LIBRARY_NAME: LAST_USE: Tivoli Storage Manager Command Line Backup/Archive Client Interface - Version 5, Release 1, Level 1.0 (C) Copyright IBM Corporation 1990, 2002 All Rights Reserved. Node Name: XX Session established with server YY: AIX-RS/6000 Server Version 5, Release 1, Level 1.2 Server date/time: 08/09/02 19:29:20 Last access: 08/09/02 18:59:46 Total number of objects inspected: 40,769 Total number of objects backed up: 39,934 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred: 3.59 GB Data transfer time: 221.48 sec Network data transfer rate:17,012.47 KB/sec Aggregate data transfer rate: 3,492.59 KB/sec Objects compressed by:0% Elapsed processing time: 00:17:58 Thank you all for your help Paul van Dongen
Re: Override include-exclude list in Unix-client for one session
You *can* do this, but you *should not* do this. If you override the regular include/exclude list, then you will get a backup of your database files during that backup. However, the next time you run a backup with your original include/exclude list, any backup versions of the database files will be expired (because they are excluded). In summary, you should think of EXCLUDE statements as telling TSM that you *never* want backups of the specified files. You could get the desired effect in this fashion: 1) Create a management class whose backup copygroup has a FREQUENCY setting of . 2) Update your include/exclude list to INCLUDE the database files and bind them to this new management class. 3) Shut down the database engine. 4) Use the TSM client to back up the database files. They should get bound to your new management class. 5) Restart your database engine. Now your regularly scheduled incremental backups won't back up the database files again because of the FREQUENCY= setting in the management class. But on those occasions when you want to do a controlled shutdown of the database engine, you can run SELECTIVE backups of the database files to back them up. An alternative to the above method is to simply register a new node name with the TSM server, and configure dsm.opt and dsm.sys such that this new node name will use an include/exclude list that does not exclude your database files. Then you can perform backups of the database files using the new node name. Whether you do this manually, or implement some automated scheme to shut down the database engine/run the backup/restart the database engine, is up to you. 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. Hi there, On a machine here, a database that uses files to store the data is running. The files used by that database are excluded in the inclexcl.lst file, because those files shouldn't be backed up when the database is running. (We use a TDP-client to backup that database while it's running.) However, I would like to be able to backup those database-files when the database isn't running. The problem is that those files are excluded in the inclexcl.lst file that's pointed to by dsm.sys. I don't want to remove that exclusion, because those files *should* normally be excluded. What I'd like is something like dsmc -inclexcl=other-inclexcl.lst. That way, I can specify on the commandline that I'd like to override the system wide inclexcl.lst just for this session. Is there a way this can be done cleanly? Thanks, -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: Override include-exclude list in Unix-client for one session
Hi Eric, Yes, you would have to tailor the copygroup settings for number of versions to keep, and for how long. And the archive suggestion is yet another valid alternative. 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. Loon, E.J. van - SPLXM [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/21/2002 06:50 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Override include-exclude list in Unix-client for one session Hi Andy! Thanks for filling me in! I forgot to mention this part! :-( Your management class will have to keep your inactive versions long enough! What about excluding the files with an exclude.backup? You can than archive the files when the database is down, not? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Andy Raibeck [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 21, 2002 15:08 To: [EMAIL PROTECTED] Subject: Re: Override include-exclude list in Unix-client for one session You *can* do this, but you *should not* do this. If you override the regular include/exclude list, then you will get a backup of your database files during that backup. However, the next time you run a backup with your original include/exclude list, any backup versions of the database files will be expired (because they are excluded). In summary, you should think of EXCLUDE statements as telling TSM that you *never* want backups of the specified files. You could get the desired effect in this fashion: 1) Create a management class whose backup copygroup has a FREQUENCY setting of . 2) Update your include/exclude list to INCLUDE the database files and bind them to this new management class. 3) Shut down the database engine. 4) Use the TSM client to back up the database files. They should get bound to your new management class. 5) Restart your database engine. Now your regularly scheduled incremental backups won't back up the database files again because of the FREQUENCY= setting in the management class. But on those occasions when you want to do a controlled shutdown of the database engine, you can run SELECTIVE backups of the database files to back them up. An alternative to the above method is to simply register a new node name with the TSM server, and configure dsm.opt and dsm.sys such that this new node name will use an include/exclude list that does not exclude your database files. Then you can perform backups of the database files using the new node name. Whether you do this manually, or implement some automated scheme to shut down the database engine/run the backup/restart the database engine, is up to you. 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. Hi there, On a machine here, a database that uses files to store the data is running. The files used by that database are excluded in the inclexcl.lst file, because those files shouldn't be backed up when the database is running. (We use a TDP-client to backup that database while it's running.) However, I would like to be able to backup those database-files when the database isn't running. The problem is that those files are excluded in the inclexcl.lst file that's pointed to by dsm.sys. I don't want to remove that exclusion, because those files *should* normally be excluded. What I'd like is something like dsmc -inclexcl=other-inclexcl.lst. That way, I can specify on the commandline that I'd like to override the system wide inclexcl.lst just for this session. Is there a way this can be done cleanly? Thanks, -- Jurjen Oskam PGP Key available at http://www.stupendous.org/ ** 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
Re: Override include-exclude list in Unix-client for one session
It means that they are treated as if you had deleted the file from your file system: the backup version would be marked INACTIVE, and all existing backup versions will be deleted from the TSM server database per the management class/copygroup retention settings. Whether this is acceptable to you is your decision. Personally, I would not manage my backup versions of existing files in this manner, as it is risky at best, and is not how TSM was intended to be used. 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. Jurjen Oskam [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/21/2002 13:11 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Override include-exclude list in Unix-client for one session On Wed, Aug 21, 2002 at 09:08:16AM -0400, Andy Raibeck wrote: files during that backup. However, the next time you run a backup with your original include/exclude list, any backup versions of the database files will be expired (because they are excluded). What do you mean exactly by expired? * Marked inactive, or * Deleted from the TSM database It's a bit confusing to see the TSM ba-client say that it has expired a file, while the TSM server means something entirely different with expiring (i.e.: permanently deleting things from the database). The client's expiring is the server's marking inactive. (Am I right in this? As I said, it's a bit confusing, especially for somebody whose first language isn't English :-) ) To get back to the story, if it's the former (marking inactive), that could be acceptable *if* the retain-only and versions-deleted parameters are acceptable. However, I think your solution (FREQUENCY setting at ) is much cleaner, and I'll implement that. Thanks for the excellent explanation! -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: ANS1075E : Program Memory Exhausted
Thanks for your post, as it prompted me to recheck my facts. I fear my memory is starting to go out the window (I just turned 40, a sure sign...). I just double-checked. I'd swear we fixed this in 5.1.1, but apparently we did not. I did verify, however, that it is fixed in 5.1.5, currently targeted for mid-October. 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. Adams, Matt (US - Hermitage) [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/20/2002 06:33 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: ANS1075E : Program Memory Exhausted Is it documented that (IC32797) is corrected in 5.1.1? Thanks, Matt Adams Tivoli Storage Manager Team Hermitage Site Tech Deloitte Touche USA LLP -Original Message- From: Don France [mailto:[EMAIL PROTECTED]] Sent: Monday, August 19, 2002 10:23 PM To: [EMAIL PROTECTED] Subject: Re: ANS1075E : Program Memory Exhausted Nice call, Andy; thanx, for the update. Don France Technical Architect -- Tivoli Certified Consultant Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390 San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Andy Raibeck Sent: Monday, August 19, 2002 3:18 PM To: [EMAIL PROTECTED] Subject: Re: ANS1075E : Program Memory Exhausted Rob didn't mention the client version he is using. But the problem you are referring to (IC32797) was fixed in 4.2.2 and 5.1.1 (it still exists in 5.1.0). 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. Don France [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/19/2002 13:16 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: ANS1075E : Program Memory Exhausted There's been some history of the TSM scheduler allocating then not freeing memory; maybe try using managed services (with polling mode), so the scheduler is periodically launched (and exits) from dsmcad... see the Using Clients book. Also, check your virtual memory settings; you may have so many dir-objects in your filesystem that you're exhausting available virtual memory. If all that fails, call SupportLine and/or collaborate with your NT server admins... they may need some HotFix (or have other ideas). Don France Technical Architect -- Tivoli Certified Consultant Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390 San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Rob Hefty Sent: Monday, August 19, 2002 10:20 AM To: [EMAIL PROTECTED] Subject: ANS1075E : Program Memory Exhausted Hello all, We have a win2k file server here running 4.2 that we have been doing incrementals on for months with journaling enabled and had no problems until recently. The error listed above outputs almost immediately after the initial run of it. We then rerun it (through a 3rd party scheduler) and it completes normally, backing up the normal amount. I tried the Tivoli website to no avail since this message is not documented and am waiting in a call back queue on it but have not heard back anything. Any help is appreciated. Thanks, Rob Hefty IS Operations Lab Safety Supply - 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 and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Re: ANS1075E : Program Memory Exhausted
Rob didn't mention the client version he is using. But the problem you are referring to (IC32797) was fixed in 4.2.2 and 5.1.1 (it still exists in 5.1.0). 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. Don France [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/19/2002 13:16 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: ANS1075E : Program Memory Exhausted There's been some history of the TSM scheduler allocating then not freeing memory; maybe try using managed services (with polling mode), so the scheduler is periodically launched (and exits) from dsmcad... see the Using Clients book. Also, check your virtual memory settings; you may have so many dir-objects in your filesystem that you're exhausting available virtual memory. If all that fails, call SupportLine and/or collaborate with your NT server admins... they may need some HotFix (or have other ideas). Don France Technical Architect -- Tivoli Certified Consultant Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390 San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Rob Hefty Sent: Monday, August 19, 2002 10:20 AM To: [EMAIL PROTECTED] Subject: ANS1075E : Program Memory Exhausted Hello all, We have a win2k file server here running 4.2 that we have been doing incrementals on for months with journaling enabled and had no problems until recently. The error listed above outputs almost immediately after the initial run of it. We then rerun it (through a 3rd party scheduler) and it completes normally, backing up the normal amount. I tried the Tivoli website to no avail since this message is not documented and am waiting in a call back queue on it but have not heard back anything. Any help is appreciated. Thanks, Rob Hefty IS Operations Lab Safety Supply
Re: ans1512e return code 12
You probably have one or more error messages in your dsmerror.log and/or dsmsched.log files that were unrelated to skipped files. For more info on the 5.1 return codes, see chapter 7 in the client manual, Automating Tasks, section Return Codes from the Command Line Interface. This info applies to the scheduler as well. 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. Selva, Perpetua [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/16/2002 05:57 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:ans1512e return code 12 we are running 4.2.11 tsm server client is running on 5.1.01 any idea why the scheduler reports failed backups eventhough there may be only couple of files that failed. this was not the case with clients running 4.2 any insights? thanks font face=Times New Roman size=3 p--/p p This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately./p p Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen./p p/p /font
Re: Backup Schedule Crashing for TSM client 4.1.2.18
Off-hand I am not sure why you are seeing what you are seeing; but I would recommend going to the 4.2.2.0 client, and see if that makes any difference. If it still crashes, then please provide the address where TSM is crashing. 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. Sung Y Lee/Austin/IBM@IBMUS Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/16/2002 14:10 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Backup Schedule Crashing for TSM client 4.1.2.18 Hello TSM administrators, Has anyone seen this happening? when I do q event * * status shows up as ? for scheduled backup node. I see this on selected few nodes. Both happening to WinNT and Windows 2000 client boxes. In dsmsched.log it has 08/16/2002 01:36:05 ANS1448E An error occurred accessing NTFS security information in dsmerror.log contains bunch of these messages 08/16/2002 01:36:04 Attempt to free unknown pointer. Addr 009938B4, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009938B4, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntfileio.cpp, Line 7320 08/16/2002 01:36:05 Attempt to free unknown pointer. Addr 009A05E8, File ntf Client version: Platform: WinNT Client OS Level: 5.00 Client Version: Version 4, Release 1, Level 2.18 Server version: Storage Management Server for AIX-RS/6000 - Version 4, Release 1, Level 5.0 running AIX 4.3.3 Examined the permission for the drive, it's set to full everyone. Also this occures sometimes. Thank you in advance for your assistance. Sung Y. Lee E-mail [EMAIL PROTECTED]
Re: Pre/Post-schedule commands problem
Could you maybe provide a little more detail on the nature of your problem? Information that might be helpful includes (but is not necessarily limited to): - What is the exact syntax of your pren/postnschedulecmd options? - What commands are you trying to process with your pren/postnschedulecmd options? If the commands are scripts, what do these scripts do? - What OS is the client running on (name and version)? - What TSM client version are you using (4.2.x.y)? - the client scheduler aborted is a little vague. What are the exact symptoms (does it crash, or just shut down, or what)? - When does the problem occur? When you start the scheduler? When it processes the prenschedulecmd? When it processes the postnschedulecmd? Somewhere between? - What messages are you seeing in your dsmsched.log and/or dsmerror.log files when this occurs? 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. Rupert Wood [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/14/2002 18:24 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Pre/Post-schedule commands problem (This is a second try - I can't find an entry for this question after searching at ADSM.ORG!) I have successfully managed to run a command sequence (via an Admin Client GUI) using the form -preschedulecmd='pathname1' -postschedulecmd='pathname2' , but when testing a nowait variant using the form -presNchedulecmd='pathname1' -postNschedulecmd='pathname2' , the client scheduler aborted. I used the above forms as recommended in a posting on adsm.org. What have I done wrongly? Our TSM level is 4.2. Thanks for any help, Rupert Wood Technical Specialist Strategic Outsourcing IBM (NZ) Ltd. Telephone: (+64 4) 576-9782 extn. 9782 Fax: (+64 4) 576-5808 e-mail: [EMAIL PROTECTED] - The contents of this e-mail are confidential. If you have received this communication by mistake, please advise the sender immediately and delete the message and any attachments. The views expressed in this e-mail are not necessarily the views of Westpac Banking Corporation. Westpac Banking Corporation is incorporated in New South Wales, Australia. -
Re: syntax for using like in select statement?
For somevalue, use a partially qualified string surrounded by single quotes. Pattern matching characters include '%', which means 0 or more characters, and '_', which means exactly one character. Examples: Match all strings beginning with ABC: like 'ABC%' Match all strings ending in XYZ: like '%XYZ' Match all strings containing LMN: like '%LMN%' Match all strings beginning with ABC and ending with Z: like 'ABC%Z' Match all strings beginning with ABC that are exactly 4 characters long: like 'ABC_' etc. Note that SQL string comparisons are case sensitive. For example, if you want to find all node names that begin with MICHELLE, then you need to use: select node_name from nodes where node_name like 'MICHELLE%' Since in TSM, all node names are in upper case. As a general rule, most of the TSM strings are upper case except for things like file names, file system names, and contact information. 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. Michelle DeVault [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/13/2002 10:25 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:syntax for using like in select statement? I'm sure this has been answered before, I just can't find it in the archived on adsm.org. How can I use a like in a select statement? I don't know the value exactly, just know a portion of it. ex. select * from sometable where somecolumn like somevalue __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com
Re: Incremental Backup (full/partial)
Mark, We've been discussing this internally amongst ourselves, and the client and server books are definitely out of sync. We will look into getting them corrected, and updating this forum with the final answer. Just to clarify a couple of points: - When incremental-by-date is used to back up a file system, the last backup date for the file space IS updated. - In an earlier post on this thread, you said, All PIT restores a relative to the previous LID, i.e. if the LID is 8/8/02 4:00 and you do a PIT restore specifying a pitdate and pittime of 8/8/02 8:00 it will roll back to the previous LID of 8/8/02 4:00. I'm not sure I really understand what you are getting at. When doing a point-in-time restore, if a backup version meets the point-in-time criteria, then it will be restored regardless of what method was used to back it up. PIT restore keys off the date/time the backup version was created, not when the file system was backed up. So if the LID was 08/08/2002 04:00, but at 06:00 someone subsequently backed up some additional files, then a PIT restore using date/time criteria of, say, 08/08/2002 07:00 would restore the backup versions created at 06:00. The volume's LID isn't really relevant. 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. Mark D. Rodriguez [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/12/2002 15:15 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Incremental Backup (full/partial) Alex, I have read through your response and I can understand your position. However, firat I would like to point out that the TSM documentation is not always clear and is not always consistant. The text you quoted from the Admin Guide is an example of them not being consistant. Clearly what they are describing there is a incremental -incrbydate type backup. And as I stated earlier you can consider it a partial incremental, but that does not mean that a partial incremental is only acheived by incremental -incrbydate, that's like saying I live in Texas therefore I am a Texan and an American based on that fact I can say all Texan's are Americans, but not all Americans are Texans. I will concede that there is places within the documentation that refers to the -incrbydate option as beeing a partial backup and I can show you IBM/Tivoli education material that describes a partial exactly as I did in my note. But rather than nit picking the symantics I would like to re-phrase my explanation, Instead of calling it full incremental and partial incremental maybe we should use full and non-full. The key here is what happens when you don't use full incrementals, in particular the Last Incremental Date ( what I refer to as the LID) does not get updated. This is a critical peice of information. Much of the documentations explanation for other processes are assumming that you are doing fulls since it keys off of the LID. In addition, what other processing is being effected by your non-full incremental (filespec limited or -incrbydate option), i.e. file expiration, rebinding, missed files etc. The point that I am really trying to make is you should always be doing full incremental backups! The only time to consider anything else is if there is a severe time constraint on the backup window. I think this thread has been great. It has given people a look at how, what and why TSM is doing what it does. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: Incremental Backup (full/partial)
Mark, I was indeed in error when I equated Partial Incremental with Incremental by date. You are correct about partial incremental being against one or more files or directories, vs. the entire file system. Best regards, Andy time to do some brushing up myself 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. Mark D. Rodriguez [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2002 21:02 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Incremental Backup (full/partial) KEN HORACEK wrote: Hi fellow listers, So here I am, Reading the Fine Manual, and it sez; an Incremental Backup can either be full or partial.. How can I tell if my backup(s) are requesting a full or partial backup? Ken [EMAIL PROTECTED] Hi Everyone, I am going to take a stab at this one. I have seen several others have as well. I do want to qualify my answer and say that when I here people refer to full or partial incremental then I give the explanation you will see below. I believe my explanation to be correct based on all of my reading of the documentation as well as the education material that IBM/Tivoli has been putting out for the last many(I think ed classes have been around for almost 10) years. Anyway, I certainly hope I am right since this is the way I have been teaching it for many years. A full incremental is when you issue an incremental command (command line or scheduled) that either has no filespecs or the filespec is an exact string of a filespace. The following are all considered full incremental: tsm i tsm i c: tsm i c:d: or on a unix box tsm i tsm i /home tsm i /home/opt This assumes that c:, d:, /home, /opt are all filespaces. A partial incremental is when you qualify the backup using a filespec that is not just a filespace name. The following are all considered partial incremental: tsm i c:\mydir\* tsm i c:\mydir\*d:\tmp\file or on a unix box tsm i /home/* tsm i /home/opt Both of these commands still process the include/exclude list in the same way. However, for the partial it will only backup the files based on the filespec, i.e. some include statements will not apply. The real big difference between the two is that the full incremental will update the value Last Incr Date (LID) that you see for the filespace when you do a q filespace. This is a very important date a couple of things key off of this date. One it is used when the -incrbydate option is specified(more on that later) and it is also used when your are doing a Point In Time(PIT) restore. All PIT restores a relative to the previous LID, i.e. if the LID is 8/8/02 4:00 and you do a PIT restore specifying a pitdate and pittime of 8/8/02 8:00 it will roll back to the previous LID of 8/8/02 4:00. The next item there seems to be a great deal of confusion about what the -incrbydate option really does. Please refer to my post on 8/8/02, the subject was incremental and incremental -incrbydate . There was one response that gave a completely erroneous answer, but I hope my answer will clarify the differences between incremental and incremental -incrbydate. I won't reiterate everything that I covered in that post, but I do want to speak to what some of the people posted in this thread. There were a couple of post that implied that a incremental -incrbydate was in fact a partial backup. I think that is somewhat correct but misleading. A partial backup is as I stated above, however what my references above and an incremental -incrbydate have in common is that neither will update the LID. The differences between the two are much greater, remember the -incrbydate option changes the way incremental decides what files will be backed up, it only compares the files data modified time stamp to the LID and if newer back it up. But more significant is what it does not do: * Will not recognize any deleted files, i.e. no files expire. * Will not rebind any files if management classes have changed. * Ignores the copygroups frequency settings. A partial incremental does effectively all the same processing as a full it just does it to a subset of the files in a filespace as defined by the filespec when the command was issued. BTW, for those of you who pull a lot of info directly from the TSM DB, the LID can be found in the table filespaces and the attribute is BACKUP_END, as you can see it is actual the time stamp of when the full incremental has completed. I apologize for such a long post, I just hate to see confusion about important concepts that TSM is based upon. I good understanding of the basic concepts and terminology goes a long way
Re: Incremental Backup (full/partial)
Hi Ken, There is no way (at least none that comes to mind at this time) from an administrative standpoint to determine this. Partial incremental is also known as incremental by date. To use this kind of incremental backup, the -incrbydate option would have to be passed to the client. For example: dsmc incremental -incrbydate You an also pass it through a schedule defined on the server, like this: define schedule standard mysched options=-incrbydate (If you have -incrbydate in the schedule definition, then you would know it). When a regular incremental backup is run, the client output will show when it is starting the backup for each volume like this: Incremental backup of volume 'C:' When incremental by date (partial) is run, the message will look like this: Incremental by Date of volume 'C:' 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. KEN HORACEK [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2002 10:36 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Incremental Backup (full/partial) Hi fellow listers, So here I am, Reading the Fine Manual, and it sez; an Incremental Backup can either be full or partial.. How can I tell if my backup(s) are requesting a full or partial backup? Ken [EMAIL PROTECTED]
Re: Incremental Backup (full/partial)
I think with COPYMODE, you are talking about how to get a complete backup of the file system regardless of whether the files have changed, versus a backup of changed files only. But Ken is talking about what we call Full incremental versus Partial incremental, which is different (and yes, the terminology can be quite confusing). Full incremental is a regular incremental backup with TSM, where the client queries the server for information about existing active backup versions, then traverses the client file systems, comparing each file's current attributes with the attributes of that file from the server information. If any of the attributes are different, then the file is considered to have changed, and it is eligible for backup. Partial incremental is another term for incremental by date. In this case, TSM just checks the date/time that the file system was last backed up. Then it traverses the client file sysem and checks each file's modification date/time. If the file's current modification date/time is greater than the date/time the file system was last backed up, then the file is eligible for backup. The difference is that Full incremental is more thorough in checking for changed files, at the expense of time. For large file systems, it can take a relatively long time to get query information back from the server; plus the client is doing more file attribute comparisons, which can also take longer. Partial incremental is faster, but because it's checks for changed files are less stringent, it may not capture all changed files. For example, copying a file will produce a new file whose modification date/time matches the original file. If this date/time is lower than the date/time the file system was last backed up, then it won't be captured by a Partial incremental. Also, Partial incremental doesn't expire deleted files. So as a rule, Partial incremental is recommended only if you are truly constrained on time for doing a Full incremental; and even then, you should schedule a Full incremental periodically (like once a week). 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. Edgardo Moso [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2002 12:35 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Incremental Backup (full/partial) Set copy mode parameter in the copy group to absolute for full and modified for incremental backup. For partial incremental: see manual ( ex. by date, etc...) From: KEN HORACEK [EMAIL PROTECTED] on 08/09/2002 01:36 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Incremental Backup (full/partial) Hi fellow listers, So here I am, Reading the Fine Manual, and it sez; an Incremental Backup can either be full or partial.. How can I tell if my backup(s) are requesting a full or partial backup? Ken [EMAIL PROTECTED]
Re: SQL results
The results of your SELECT statement look valid to me. You can check the results by running: select * from volumeusage where node_name='' And do a manual review of the data. I would expect to see that the node has 12 file spaces each on volumes 020259 and 030298, and 4 file spaces each on volumes 020266 and 030357. If you are just interested in a total volume count but not the specific volumes, then try this: select count(distinct volume_name) from volumeusage where node_name='' The 2 in Unnamed[2] means that it is the second column of output. If you want a more meaningful name, use AS to give the name an alias: select count(distinct volume_name) as VOLUME COUNT from volumeusage where node_name='' 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. Large, Matthew [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/05/2002 04:24 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:SQL results Hi all, We're trying to issue this tsm select volume_name,count(*) from volumeusage where node_name=xxx group by volume_name VOLUME_NAME Unnamed[2] -- --- 020259 12 020266 4 030298 12 030357 4 to find out how many volumes contain data from a particular node. What do these results tell me? From querying the contents of the vols, it looks like number of filespaces per volume. And my unnamed column seems to have the answer to my original question - '2'. Anyone seen this before or it is WAD? Regards Matthew Large TSM Infrastructure Engineer Lavington Street Int: 7430 4995 Ext: 07736 448 808 --- This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. evolvebank.com is a division of Lloyds TSB Bank plc. Lloyds TSB Bank plc, 71 Lombard Street, London EC3P 3BS. Registered in England, number 2065. Telephone No: 020 7626 1500 Lloyds TSB Scotland plc, Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone No: 0131 225 4555 Lloyds TSB Bank plc and Lloyds TSB Scotland plc are regulated by the Financial Services Authority and represent only the Scottish Widows and Lloyds TSB Marketing Group for life assurance, pensions and investment business. Signatories to the Banking Codes. ---
Re: Incremental Backup (full/partial)
Whps, you really didn't see me say this: For example, copying a file will produce a new file whose modification date/time matches the original file. If this date/time is lower than the date/time the file system was last backed up, then it won't be captured by a Partial incremental. This is not true, the copy would be backed up because it is new. But the other discussion about Partial vs. Full incremental still stands. Sorry for the confusion. 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. Andrew Raibeck/Tucson/IBM@IBMUS Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2002 13:05 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Incremental Backup (full/partial) I think with COPYMODE, you are talking about how to get a complete backup of the file system regardless of whether the files have changed, versus a backup of changed files only. But Ken is talking about what we call Full incremental versus Partial incremental, which is different (and yes, the terminology can be quite confusing). Full incremental is a regular incremental backup with TSM, where the client queries the server for information about existing active backup versions, then traverses the client file systems, comparing each file's current attributes with the attributes of that file from the server information. If any of the attributes are different, then the file is considered to have changed, and it is eligible for backup. Partial incremental is another term for incremental by date. In this case, TSM just checks the date/time that the file system was last backed up. Then it traverses the client file sysem and checks each file's modification date/time. If the file's current modification date/time is greater than the date/time the file system was last backed up, then the file is eligible for backup. The difference is that Full incremental is more thorough in checking for changed files, at the expense of time. For large file systems, it can take a relatively long time to get query information back from the server; plus the client is doing more file attribute comparisons, which can also take longer. Partial incremental is faster, but because it's checks for changed files are less stringent, it may not capture all changed files. For example, copying a file will produce a new file whose modification date/time matches the original file. If this date/time is lower than the date/time the file system was last backed up, then it won't be captured by a Partial incremental. Also, Partial incremental doesn't expire deleted files. So as a rule, Partial incremental is recommended only if you are truly constrained on time for doing a Full incremental; and even then, you should schedule a Full incremental periodically (like once a week). 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. Edgardo Moso [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2002 12:35 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Incremental Backup (full/partial) Set copy mode parameter in the copy group to absolute for full and modified for incremental backup. For partial incremental: see manual ( ex. by date, etc...) From: KEN HORACEK [EMAIL PROTECTED] on 08/09/2002 01:36 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Incremental Backup (full/partial) Hi fellow listers, So here I am, Reading the Fine Manual, and it sez; an Incremental Backup can either be full or partial.. How can I tell if my backup(s) are requesting a full or partial backup? Ken [EMAIL PROTECTED]
Re: Incremental Backup (full/partial)
Nope, I'm wrong yet again forget my last post on this topic, my example of copying a file is a valid case where partial incremental won't back it up. Sorry for even more confusion. Time to sleep now... =8-O 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. - Forwarded by Andrew Raibeck/Tucson/IBM on 08/09/2002 13:34 - Andrew Raibeck 08/09/2002 13:15 To: ADSM: Dist Stor Manager [EMAIL PROTECTED] cc: From: Andrew Raibeck/Tucson/IBM@IBMUS Subject:Re: Incremental Backup (full/partial) Whps, you really didn't see me say this: For example, copying a file will produce a new file whose modification date/time matches the original file. If this date/time is lower than the date/time the file system was last backed up, then it won't be captured by a Partial incremental. This is not true, the copy would be backed up because it is new. But the other discussion about Partial vs. Full incremental still stands. Sorry for the confusion. 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. Andrew Raibeck/Tucson/IBM@IBMUS Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2002 13:05 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Incremental Backup (full/partial) I think with COPYMODE, you are talking about how to get a complete backup of the file system regardless of whether the files have changed, versus a backup of changed files only. But Ken is talking about what we call Full incremental versus Partial incremental, which is different (and yes, the terminology can be quite confusing). Full incremental is a regular incremental backup with TSM, where the client queries the server for information about existing active backup versions, then traverses the client file systems, comparing each file's current attributes with the attributes of that file from the server information. If any of the attributes are different, then the file is considered to have changed, and it is eligible for backup. Partial incremental is another term for incremental by date. In this case, TSM just checks the date/time that the file system was last backed up. Then it traverses the client file sysem and checks each file's modification date/time. If the file's current modification date/time is greater than the date/time the file system was last backed up, then the file is eligible for backup. The difference is that Full incremental is more thorough in checking for changed files, at the expense of time. For large file systems, it can take a relatively long time to get query information back from the server; plus the client is doing more file attribute comparisons, which can also take longer. Partial incremental is faster, but because it's checks for changed files are less stringent, it may not capture all changed files. For example, copying a file will produce a new file whose modification date/time matches the original file. If this date/time is lower than the date/time the file system was last backed up, then it won't be captured by a Partial incremental. Also, Partial incremental doesn't expire deleted files. So as a rule, Partial incremental is recommended only if you are truly constrained on time for doing a Full incremental; and even then, you should schedule a Full incremental periodically (like once a week). 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. Edgardo Moso [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/09/2002 12:35 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Incremental Backup (full/partial) Set copy mode parameter in the copy group to absolute for full and modified for incremental backup. For partial incremental: see manual ( ex. by date, etc...) From: KEN HORACEK [EMAIL PROTECTED] on 08/09/2002 01:36 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Incremental Backup (full/partial) Hi fellow listers, So here I am, Reading the Fine Manual, and it sez
Re: Trapping TSM Messages on NT4 and W2K
See the chapter on Automating Tasks in the 5.1 client manual for information on return codes from the command line client. In Windows, return codes from the last command (or program) executed can be detected via the %errorlevel% variable. For example: dsmc incremental echo TSM return code is %errorlevel% 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. Michael Moore [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08/02/2002 13:30 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Trapping TSM Messages on NT4 and W2K Currently we are using the TSM scheduler service to drive the client backups. But, the direction of our company is to use ESP (scheduling package) to drive the backups and all TSM maintenance events (DB backups, reclamation, storage pool backups etc.). Our NT group will be responsible for the client backups. The problem they are having is trapping error codes from the backup client. What I am looking for is some code that traps the return code from the client, which can be used by ESP to determine if the backup completed successfully or not. For example, on our AIX clients, we allow a return code of 0 or 4. The 0 or 4 is returned to the ESP task, and ESP compeletes the job as normal. If the return code is anything else, ESP treats it as an abend, and notification begins. Thanks for any information!! Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544
Re: Old client versions
Where can I download clients older than ver 3.7? I can't find them anymore on the Tivoli website they are not supported any longer. That is true, but they can still be found on the IBM FTP site: ftp://ftp.software.ibm.com/storage/adsm/ From there, go to the fixes directory for official PTFs, or fixtests directory for fixtests (patches), and navigate to the desired clients. It is probably generally understood, but nonetheless I should still mention that these client versions are no longer supported. Thus you use them at your own risk. Best 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.
Re: Redirect Output in Windows dsmadmc
That one is a little tougher. The problem is that the Windows command
processor doesn't pass the '' symbol to the program (to any program, not
just TSM). You can verify this for yourself by compiling this simple C
program:
/* args.c */
#include stdio.h
int main(int argc, char *argv[])
{
int i = 0;
for (i = 0; i argc; i++)
printf(argv[%d] = %s\n, i, argv[i]);
return 0;
}
Example output:
C:\MyPrograms\argsargs select * from nodes where max_mp_allowed1
C:\MyPrograms\argstype 1
argv[0] = args
argv[1] = select
argv[2] = *
argv[3] = from
argv[4] = nodes
argv[5] = where
argv[6] = max_mp_allowed
As you can see, the program never even sees the symbol, so it can't
possibly process it.
One thing I tried that seems to work, is to embed the entire admin command
in quotes, like this:
dsmadmc -id=admin -pa=x
select * from nodes where max_mp_allowed1
and to redirect, you can do this:
dsmadmc -id=admin -pa=x
select * from nodes where max_mp_allowed1 sel.out
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.
Richard Cowen [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
07/25/2002 05:00
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: Redirect Output in Windows dsmadmc
When will we be able to do this with a select statement and use a greater
than symbol under windows?
-Original Message-
From: Andy Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 8:16 PM
To: [EMAIL PROTECTED]
Subject: Re: Redirect Output in Windows dsmadmc
Consider it noted.
Don't know if this will help, but if the Admin client is done in batch
mode, then the redirection will work:
dsmadmc -id=adminid -pa=x q se c:\test dir\qse.txt
Regards,
Andy
Re: Question about using global characters in a select statement
Try using: ... where node_name like 'AD1%' 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. Neil Rosenberg [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/24/2002 05:47 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Question about using global characters in a select statement I would like to use a global character in select statements on tsm servers to get information about groups of nodes For example if I use something like: select node_name, filespace_name from filespaces where node_name='AD1%' to get information about all nodes whose node_names begin with 'AD1' I get the following error: ANR2002E Missing closing quote character. I have tried Double quotes and used * instead of % - none of these work Any Suggestions? Thanks Neil Rosenberg [EMAIL PROTECTED] Neil Rosenberg 610-666-8936 [EMAIL PROTECTED]
Re: Redirect Output in Windows dsmadmc
Consider it noted. Don't know if this will help, but if the Admin client is done in batch mode, then the redirection will work: dsmadmc -id=adminid -pa=x q se c:\test dir\qse.txt 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. Seay, Paul [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/24/2002 16:00 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Redirect Output in Windows dsmadmc I would open a problem record on this. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 11:00 AM To: [EMAIL PROTECTED] Subject: Redirect Output in Windows dsmadmc Hi, how can I direct output of a command in dsmadmc (windows platform) to a file with a blank in its name. Example: q se E:\users\gerhard\Eigene Dateien\test.txt This gives message ANS8038E Unable to open file 'E:\users\gerhard\Eigene Dateien\test.txt' for redirection. Client is level 4.2.2.0 on Windows 2000 Professional. Server is 4.1.2.0 on AIX. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Re: Dr. Watson Error in drive C:\
I concur with Tim Rushforth's assessment from yesterday: based on the failing line of code, this is APAR IC33023. This APAR is fixed in TSM 4.2.2. I would recommend going to that level. 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. Christian Astuni/Argentina/IBM@IBMAR Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/22/2002 14:28 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Dr. Watson Error in drive C:\ Hi ... I have a client with TSM Client 4.2 Level 1.20 under NT 4 sp6a. And when I want to perform an archive backup of drive C:\ the backup crash with Dr. Watson error as this dsmcsvc.exe Exception: access violation (0xc005), Address: 0x0047b3b2 and in the dsmsched.log and dsierror.log there are empty without errors. But when run a incremental backup i dont have problems. Can anyone help me ??? Thanks very much. Can anyone help me ??? Thanks very much. Regards Christian Astuni
Re: pre and post sched on NT TSM 5.1.1
Unfortunately I don't think we can determine why your script is failing, at least not without more information. I don't believe that the change in TSM release is responsible for the script failure, as nothing has changed in the way the script is launched. What does your script look like? You should look at any commands that rely on certain environment settings that may not exist when running the scheduler (for example, PATH settings, program-specific environment variables, commands that will only run under a certain NT account, etc.). Also, if the script has more than one command in it, try to narrow it down to which exact command is failing. For example, if your script looked like this: @echo off dir e:\tsm\baclient\*.opt dir e:\xsm\baclient\*.opt Then you could put some echo statements around it, like this: @echo off @echo Issuing first dir command e:\tsm\baclient\myscript.out dir e:\tsm\baclient\*.opt @echo RC = %errorlevel% e:\tsm\baclient\myscript.out @echo Issuing second dir command e:\tsm\baclient\myscript.out dir e:\xsm\baclient\*.opt @echo RC = %errorlevel% e:\tsm\baclient\myscript.out In my rigged example, there is no directory e:\xsm, so the second dir command should fail. Here is what myscript.out looks like after the schedule runs: Issuing first dir command RC = 0 Issuing second dir command RC = 1 This way, I can narrow the problem down. 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. Lawrence Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/23/2002 08:10 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: pre and post sched on NT TSM 5.1.1 Well, yes, the preschedcmd failsThat's the question. It did not fail under the previous release, and when run apart from the backup by running the script by ilself, then doing the backup without the preschedcmd in the dsm.opt, it runs successfully. So the question is why does it fail when initiated vis the preschedscm parm. [EMAIL PROTECTED] 07/22/02 05:35PM The first error message below tells you what is happening - the pre command failed - the schedule is not executed. This is new with 5.11 - if the preschedulecmd fails, the schedule doesn't run. Tim Rushforth City of Winnipeg -Original Message- From: Lawrence Clark [mailto:[EMAIL PROTECTED]] Sent: July 22, 2002 2:49 PM To: [EMAIL PROTECTED] Subject: pre and post sched on NT TSM 5.1.1 We noticed after upgradeing the TSM client on NT that those servers with pre and post sched commands were not backing up. Anyone else experience this? DSM.OPT entries: preschedulecmd e:\adsmbackup\cinfoadsmprebackup.bat postschedulecmd e:\adsmbackup\cinfoadsmpostbackup.bat ERROR LOG ENTRIES: 07/17/2002 06:55:27 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed.
Re: query what you've set with set command
You can issue either: QUERY STATUS or SELECT * FROM STATUS To get *only* the licenseauditperiod, you can issue: SELECT LICENSEAUDITPERIOD FROM STATUS 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. Michelle DeVault [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/22/2002 08:13 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:query what you've set with set command How do you query what has been set with a set command? In particular I'd like to know what LICENSEAUDITPERIOD is set at. __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com
Re: pre and post sched on NT TSM 5.1.1
This is the correct behavior starting with the 5.1 client. Have you looked up message ANS1902E? It explains what you are seeing. Also, check out the client manual, chapter 7 Automating Tasks, section Return Codes from the Command Line Interface. This information applies to the scheduler as well. 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. Lawrence Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/22/2002 12:48 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:pre and post sched on NT TSM 5.1.1 We noticed after upgradeing the TSM client on NT that those servers with pre and post sched commands were not backing up. Anyone else experience this? DSM.OPT entries: preschedulecmd e:\adsmbackup\cinfoadsmprebackup.bat postschedulecmd e:\adsmbackup\cinfoadsmpostbackup.bat ERROR LOG ENTRIES: 07/17/2002 06:55:27 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 07/17/2002 06:55:27 ANS1512E Scheduled event 'DAILY_CINFO' failed. Return code = 12. 07/17/2002 06:55:34 ConsoleEventHandler(): Caught Logoff console event . 07/17/2002 06:55:34 ConsoleEventHandler(): Process Detached. 07/17/2002 06:55:34 ConsoleEventHandler(): Caught Logoff console event . 07/17/2002 06:55:34 ConsoleEventHandler(): Process Detached. 07/17/2002 06:55:38 ConsoleEventHandler(): Caught Shutdown console event . 07/17/2002 06:55:38 ConsoleEventHandler(): Cleaning up and terminating Process ... 07/17/2002 06:55:38 ConsoleEventHandler(): Caught Shutdown console event . 07/17/2002 06:55:38 ConsoleEventHandler(): Cleaning up and terminating Process ... 07/17/2002 18:16:07 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 07/17/2002 18:16:07 ANS1512E Scheduled event 'DAILY_CINFO' failed. Return code = 12. 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 18:48:49 The file is being used by another process 07/17/2002 19:22:05 fioScanDirEntry(): Can't map object 'C:\WINNT\?' into the local ANSI codepage, skipping ... 07/17/2002 19:22:05 fioScanDirEntry(): Can't map object 'C:\WINNT\?' into the local ANSI codepage, skipping ... 07/17/2002 19:22:08 The file is being used by another process 07/17/2002 19:22:11 The file is being used by another process 07/17/2002 19:22:11 The file is being used by another process 07/17/2002 19:22:22 The file is being used by another process 07/17/2002 19:22:22 The file is being used by another process 07/17/2002 19:22:22 The file is being used by another process 07/17/2002 19:22:23 The file is being used by another process 07/17/2002 19:54:53 ANS1005E TCP/IP read error on socket = 364, errno = 10035, reason : 'Unknown error'. 07/17/2002 19:54:53 Error reading http request. 07/17/2002 20:01:32 ANS1005E TCP/IP read error on socket = 400, errno = 10035, reason : 'Unknown error'. 07/17/2002 20:01:32 Error reading http request. 07/17/2002 20:23:43 ConsoleEventHandler(): Caught Ctrl-C console event . 07/17/2002 20:23:43 ConsoleEventHandler(): Cleaning up and terminating Process ... 07/18/2002 10:57:12 ANS1005E TCP/IP read error on socket = 364, errno = 10054, reason : 'Unknown error'. 07/18/2002 10:57:12 Error reading http request. 07/18/2002 18:07:24 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 07/18/2002 18:07:24 ANS1512E Scheduled event 'DAILY_CINFO' failed. Return code = 12. 07/19/2002 18:11:25 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 07/19/2002 18:11:25 ANS1512E Scheduled event 'DAILY_CINFO' failed. Return code = 12. 07/20/2002 18:00:25 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 07/20/2002 18:00:25 ANS1512E Scheduled event 'DAILY_CINFO' failed. Return code = 12. 07/21/2002 18:00:29 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 07/21/2002 18:00:29 ANS1512E Scheduled event 'DAILY_CINFO' failed. Return code = 12. DSMLOG ENTRIES: 07/15/2002 07:00:16 Finished command. Return code is: -1073741510 07/15/2002 07:00:16 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 07/15/2002 07:00:16 ANS1512E Scheduled event 'DAILY_CINFO' failed. Return code = 12. 07/15/2002 07:00:16 Sending results
Re: Scheduled TSM Policy Will Not Run
Ken, A node can belong to only one policy domain at a time, and I definitely do not recommend bouncing a node between two policy domains. Since I do not know the rationale for creating the new policy domain with the BACKUP_DAVINCI_DAILY node, I can not advise you on the best course of action. However, here are the options that come to mind immediately: 1) If you are just trying to get DAVINCI to execute the BACKUP_DAVINCI_DAILY schedule, then define that schedule in DAVINCI's existing domain (UNIX_SERVERS, I think), and associate DAVINCI with that schedule. 2) If your intent is to really move the DAVINCI node to a different domain because you want to manage it differently from other nodes in the current domain, then you can use the UPDATE NODE command to change DAVINCI's DOMAIN setting to the new domain. Then you care associate DAVINCI to the BACKUP_DAVINCI_DAILY schedule. If neither of these answers your question, then it would be helpful if you could provide more conceptual background on what it is you are trying to accomplish, and why, as opposed to just the immediate symptoms (so that we can see the bigger picture). 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. KEN HORACEK [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/17/2002 13:58 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Scheduled TSM Policy Will Not Run Andy, You are correct, when I do the q sch in dsmc, the node name is DAVINCI. Ok perhaps I am barking up the wrong tree. I do not need a new node name (BACKUP_DAVINCI_DAILY), the node name DAVINCI is perfectly acceptable and is, in fact, in use by the current backup policy/schedule. Can I share this node with a new policy that I am defining? How? When I get to the point where I select a node to associate with the new backup policy/schedule, and enter DAVINCI, I get the message(s)... ANR2653W Node DAVINCI cannot be processed because it is not registered or does not belong to the specified domain. ANR2625E No matching nodes registered in policy domain UNIX_SERVER_DAVINCI_DAILY. Thanks again for your patients with me. Ken [EMAIL PROTECTED] [EMAIL PROTECTED] 07/17/2002 8:54:44 AM Ken, it looks like your schedule is for node BACKUP_DAVINCI_DAILY, while your node name is just DAVINCI. Try this: 1) Run the admin CLI (command line interface) in console mode: dsmadmc -console 2) Run the backup-archive client to query the scheduler: dsmc q sch What node name shows up in the admin console? My guess is it will be DAVINCI. If so, then you need to update the nodename setting in your dsm.sys file. 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. KEN HORACEK [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/17/2002 07:59 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Scheduled TSM Policy Will Not Run Andy, Yes it is a new domain and it is reflected in the node (see below) Node Name Platform Policy Domain Days Since Days Since Locked? Name Last Password Access Set --- -- -- --- BACKUP_DAVINCI_DAILY (?) UNIX_SERVER_- 55 No DAVINCI_DAILY Why the (?) in platform? Did I miss something? I went over the processes for Creating and Automating a second time and did not find where I could enter a value here. My old Node Name shows. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last Password Access Set - -- -- -- --- DAVINCI AIX UNIX_SERVERS 1 135 No Should I have a value for Platform? How do I get it there? TIA Ken [EMAIL PROTECTED] [EMAIL PROTECTED] 07/16/2002 4:15:38 AM I would also add, make sure the scheduler daemon/service is running on each client machine. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
Re: Scheduled TSM Policy Will Not Run
Ken, it looks like your schedule is for node BACKUP_DAVINCI_DAILY, while your node name is just DAVINCI. Try this: 1) Run the admin CLI (command line interface) in console mode: dsmadmc -console 2) Run the backup-archive client to query the scheduler: dsmc q sch What node name shows up in the admin console? My guess is it will be DAVINCI. If so, then you need to update the nodename setting in your dsm.sys file. 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. KEN HORACEK [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/17/2002 07:59 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Scheduled TSM Policy Will Not Run Andy, Yes it is a new domain and it is reflected in the node (see below) Node Name Platform Policy Domain Days Since Days Since Locked? Name Last Password Access Set --- -- -- --- BACKUP_DAVINCI_DAILY (?) UNIX_SERVER_- 55 No DAVINCI_DAILY Why the (?) in platform? Did I miss something? I went over the processes for Creating and Automating a second time and did not find where I could enter a value here. My old Node Name shows. Node Name Platform Policy Domain Days Since Days Since Locked? Name Last Password Access Set - -- -- -- --- DAVINCI AIX UNIX_SERVERS 1 135 No Should I have a value for Platform? How do I get it there? TIA Ken [EMAIL PROTECTED] [EMAIL PROTECTED] 07/16/2002 4:15:38 AM I would also add, make sure the scheduler daemon/service is running on each client machine. 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. Tobias Hofmann [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/16/2002 02:07 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Scheduled TSM Policy Will Not Run Hi Ken, At 20:03 15.07.2002, you wrote: Hi, I'm new to TSM AIX (so new that, last month I could not spell TSM nor AIX). I am as new to this as you are, even though on Win2K, but that shouldn,t make too much a difference. Here is what I would do: So here's my dilemma. [...] The new policy does not run and I receive the following message on the TSM server. ANR2578W Schedule DAVINCI_BACKUP_DAILY in domain UNIX_SERVER_DAVINCI_DAILY for node BACKUP_DAVINCI_DAILY has missed its scheduled start up window. on the server, run q sched to see what schedules are planned. run q assoc to see if the nodes you want to have are associated (even though to me it seems like that davinci was scheduled, hence the missed notification). run q event *domain* *schedule* to see if the events are scheduled as intended. on the client, run (in dsmc) q sched to see if the node has picked up the schedule provided by the server. if i got this correctly, running this command on the client should update the schedule for the node (here it did, iirc). if no schedule shows up, in a next step i would check the schedmode setting for both the client and the server - see set schedmode in the admin-ref and the schedmode-line in the dsm.sys-file on the client. on a further node, the files dsmsched.log and dsmerror.log (which have to be defined in the dsm.sys of the client as well) might help you along. after a succesfull connection with the server, i find the next scheduled backup at the end of the dsmsched.log. take all this with a grain of salt - newbie-alert! :) hoping that this helps, and please do correct me if i went wrong somewhere, regards, tobi What did I miss? Where did I go wrong? Thanks in advance to anyone who wants to lead me through the process, or just clear up the error of my ways. Ken [EMAIL PROTECTED] -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische
Re: Scheduled TSM Policy Will Not Run
I would also add, make sure the scheduler daemon/service is running on each client machine. 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. Tobias Hofmann [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/16/2002 02:07 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Scheduled TSM Policy Will Not Run Hi Ken, At 20:03 15.07.2002, you wrote: Hi, I'm new to TSM AIX (so new that, last month I could not spell TSM nor AIX). I am as new to this as you are, even though on Win2K, but that shouldn,t make too much a difference. Here is what I would do: So here's my dilemma. [...] The new policy does not run and I receive the following message on the TSM server. ANR2578W Schedule DAVINCI_BACKUP_DAILY in domain UNIX_SERVER_DAVINCI_DAILY for node BACKUP_DAVINCI_DAILY has missed its scheduled start up window. on the server, run q sched to see what schedules are planned. run q assoc to see if the nodes you want to have are associated (even though to me it seems like that davinci was scheduled, hence the missed notification). run q event *domain* *schedule* to see if the events are scheduled as intended. on the client, run (in dsmc) q sched to see if the node has picked up the schedule provided by the server. if i got this correctly, running this command on the client should update the schedule for the node (here it did, iirc). if no schedule shows up, in a next step i would check the schedmode setting for both the client and the server - see set schedmode in the admin-ref and the schedmode-line in the dsm.sys-file on the client. on a further node, the files dsmsched.log and dsmerror.log (which have to be defined in the dsm.sys of the client as well) might help you along. after a succesfull connection with the server, i find the next scheduled backup at the end of the dsmsched.log. take all this with a grain of salt - newbie-alert! :) hoping that this helps, and please do correct me if i went wrong somewhere, regards, tobi What did I miss? Where did I go wrong? Thanks in advance to anyone who wants to lead me through the process, or just clear up the error of my ways. Ken [EMAIL PROTECTED] -- Dipl.-Ing. Tobias Hofmann Bauhaus-Universitaet Weimar D99423 Weimar Professur fuer Graphische Datenverarbeitung Projekt medienquadrat SnailMail: Bauhaus-Universitaet Weimar, Fak. Medien, D99421 Weimar Location: D99423 Weimar Karl-Haussknechtstr. 7 Zimmer 111 Fon: ++49-(0)3643-58-3780 Fax : -3701 e-mail: mailto:[EMAIL PROTECTED] --
Re: Antwort: executing commands before backup
Message ANS1036S Invalid option 'PRESHCEDULECMD' found in options file shows that in your options file, you misspelled PRESCHEDULECMD (the 5th and 6th characters are swapped). 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. Simeon Johnston [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/16/2002 07:27 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Antwort: executing commands before backup hrmmm... I tried this in the Linux client's dsm.opt file. preschedulecmd /path/to/script/vpnstart.sh But kept getting this error for that command - ANS1036S Invalid option 'PRESHCEDULECMD' found in options file '/opt/tivoli/tsm/client/ba/bin/dsm.opt' at line number : 17 Invalid entry : ' preshcedulecmd /path/to/script/vpnstart.sh' this is when starting dsmc sched command. So what am I missing? sim
Re: Unknown format
I think it is conceivable, depending on the circumstances. It sure would be helpful if you would provide more detail, such as the client level(s) involved, TSM server level, OS names/versions, backup and restore scenario information (i.e. who backed up the file, and with what client, who's trying to restore the file, and with what client), etc. 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. Fred Johanson [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/12/2002 10:51 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Unknown format Does message ANE4020E still mean that the client doing the restore is downlevel from the client that did the backup??
Re: dsm.opt / dsmerror.log / incl/excl oddity
In both environments A and B, try the QUERY INCLEXCL command to see the output differences. Maybe your MVS server has a client options set with the EXCLUDE statement you are asking about. 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. Wholey, Joseph (TGA\\MLOL) [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/11/2002 06:57 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:dsm.opt / dsmerror.log / incl/excl oddity Envirionment A: Client OS: NT 4 Client Version: Version 4, Release 2, Level 1.20 Server: Storage Management Server for MVS - Version 4, Release 2, Level 1.11 Environment B: Client OS: NT 4 Client Version: Version 4, Release 2, Level 1.20 Server: Storage Management Server for MVS - Version 4, Release 1, Level 3.0 These clients are cookie cutter builds Starting from the OS down to the dsm.opt (with the exception of the TSM server they point to). Question: Why is my dsmerror.log filling up with the following messages in environmet B and not A when the directory structure and dsm.opt are identical for both servers? ANS1115W File '\\l06101s001\e$\Services\BUEXECV7\NT\reports\saved\empty' excluded by Include/Exclude list Any help would be appreciated. Regards, Joe
Re: Need help with ADSM3.1 and WIN NT 4.0 SCSI
Did you try shutting down the Windows driver before starting the ADSMSCSI driver? 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. O. Oexmann [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/11/2002 15:03 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Need help with ADSM3.1 and WIN NT 4.0 SCSI Hello, i have to reactivate an old 3.1 installation which used a tape library with 6 cartridges. We do not have the old tape library anymore so i am currently trying to get an ordenary HP 1537A 4mm DAT to work. The Windows driver works fine and i can use the Windows backup program to backup and restore data to the tape but the ADSM SCSI just does not want to start. Is does not find the specific drive.. It is configured under Windows and the ADSM Wizard does find it, but the ADSM SCSI does not start. In the devconfig.out it says GENLIB1 and GENERIC_TAPE and \\.\tape0 Any suggestions or help is higly appreciated Kind regards O. Oexmann
Re: Need TSM 3.7
I would be remiss if I didn't caution against doing anything that might violate the TSM licensing agreement. Ray, while 3.7 is no longer supported, I would recommend that you contact your IBM rep for assistance if you have lost your original installation media. 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. Gene Greenberg [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/10/2002 13:58 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Need TSM 3.7 I'm not sure if there is another solution because I didn't encounter this last week when I upgraded to 5.1, but I'm pretty sure I have a copy of 3.7 for AIX. You can contact me if you don't find another solution. Gene Greenberg Jr. Lead, System Administrator, DBA, SMA 512-464-5162 Round Rock ISD Round Rock TX Ray Pratts ray.pratts@MARKITo: [EMAIL PROTECTED] IISYS.COM cc: Sent by: ADSM: Subject: Need TSM 3.7 Dist Stor Manager [EMAIL PROTECTED] .EDU 07/10/02 03:27 PM Please respond to ADSM: Dist Stor Manager Can I obtain TSM 3.7 Server for AIX. I have a system that I was about to upgrade to TSM 5.1. Well crashed and I need to restore the TSM database with 3.7 before I can upgrade. Any ideas. Thanks. Ray Pratts Senior Systems Engineer Mark III Systems, Inc 6575 West Loop South, Suite 675 Bellaire, TX 77401 713-664-9850 ext. 29
Re: Antwort: odbc ?
The ODBC driver is a completely separate entity from the rest of the backup-archive client. It has no dependencies on the b-a client, and the b-a client has no dependencies on the ODBC driver. Therefore, in order to help reduce the already substantial size of the client package, the ODBC driver was packaged separately. (Note: the ODBC driver used to be around 14 MB in size, but starting with version 5.1, we stopped shipping the English version of the MDAC. This significantly reduced the size of the ODBC driver package to around 5 MB. But for now, it is still a separate package.) As far as the API goes, it is always installed with the b-a client since certain b-a components rely on the API (such as the DSMCUTIL utility). The API SDK (not to be confused with the API) is included in the client package, but its size is negligible. 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. Burak Demircan [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/09/2002 04:09 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Antwort: odbc ? Merhaba Tsm, Then why is API is included in the client installation set? (it gives us the option to install or not) Thanks Burak [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09.07.2002 14:06 Please respond to ADSM-L To: [EMAIL PROTECTED] cc: Subject: Antwort: odbc ? Merhaba Burak An ODBC driver allows you to use a relational database product such as SQL to query the database and display the results. Client installation does not set include everything we need. You have to install API and ODBC separately. selamlar...
Re: TSM 4.1.1 on MS Windows 2K Cluster
This sounds like it could be APAR IC28338, which was fixed after 4.1.1. I would strongly recommend moving to the 4.1.3 client, which also disables the daylight savings time feature. 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. Jon Adams [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/03/2002 16:10 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:TSM 4.1.1 on MS Windows 2K Cluster Well, since Tivoli has officially cut support for 4.1.1, I have, what I hope to be, a simple question: TSM Server v4.1.4.5 running on AIX v4.3.3, supporting Windows client v4.1.1 ** Though I have successfully implemented the TSM Client solution on our clustered servers, I do not appear to have the ability to restore them via GUI. From the GUI, any cluster shared resources DO NOT appear anywhere. Obviously, it's difficult to restore something you can't see. I have indeed verified that the client has been getting it's daily backups and that the file spaces do exist on the server. If anyone can shed some light on this, I would really appreciate it. In case anyone was wondering, we plan on upgrading our server to v4.2, then the clients to v5.1 and finally the server to v5.1. This method, because of the compatibility differences between clients and server - it is a lot easier to upgrade the server twice than for the clients. We already knew that we had to get the clients up to v4.2 minimum (before this October) because of the daylight savings feature, anyway. Have great 4th of July everyone! Jon R. Adams IT IPS BST Infrastructure Premera Blue Cross Mountlake Terrace, WA 425-670-5770 [EMAIL PROTECTED]
Re: Why my LAN free backup even slower then my LAN backup---Was the 900KBps is the expected performance in this LAN free backup environment?
H.. try using namedpipes instead of tcpip for your commmethod, and see if that makes any difference. 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. Mike Brown [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/26/2002 11:21 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Why my LAN free backup even slower then my LAN backup---Was the 900KBps is the expected performance in this LAN free backup environment? Actually, I use the same Win2k host, all backup direct to tape, all no disk pool involed, backup same files (backup whole C:\ drive, delete the filespace before it run next time backup). To be more precisely, my question should be Was the 900KBps is the expected performance in this LAN free backup environment? Should I continue to find out some more fine tunning method? How should I continue the performance tuning in this environment? Thanks for you informantion any way. Mike rs6000 [EMAIL PROTECTED] wrote: Mike It depends of what your configuration looks like and what files you are backing up. Think of this: If you are backing up many small files on one SAN based machine and big files on another machine, it goes without saying that the machine backing up the bigger files will have better throughput times. LAN free versus LAN based on the other hand also has an easy explanation: With LAN free going straight to high speed LTO tape drives the small/big file dilemma also play a role because the LTO drive will now be shoeshining when backing up small files, whereas if the client was LAN based, the diskpool would recieve the backup before it went off to tape. When backing up small files via LAN free there is a good possibility that the LTO drives will not be streaming and hence the total backup thruput is less. Does this waffle make any sense? Rgds John - Original Message - From: Mike Brown To: Sent: Wednesday, June 26, 2002 5:26 PM Subject: Why my LAN free backup even slower then my LAN backup Why my LAN free backup even slower then my LAN backup? I got really bad performance, 1.2MBps for LAN, 900KBps for LANfree Backup. My TSM server is Version 4.2.1.11 in AIX 4.3.3, p640, 1 power3 processor, 1G memory; My TSM Storage Agent veriosn 4.2.1.11 on Win2k Advanced server, TSM client 4.2.1.20 on same machin, this is a compaq Deskpro EP/SB, 1 PII 350MHz processor, 256M memory, Emulex LP800 HBA; 3583 Library, 2109 Switch, 2108r03 bridge; During LANFree Backup, performance is about 900KBps, win2k host have 15% CPU utilization, 70% Disk I/O, memory utilization keep low, , even worse then LAN backup; Paramenters: TCPWINDOWSIZE 63(IBM recommaned in release notes); TCPBUFFSIZE 512; RESOURCEUTILIZATION 50 (looks like same as set to 10); During LAN backup, the tsm client win2k host have 95% CPU utilization, performance is about 1.2MBps; I hate this Compaq crap. None of the individual are full utilizated, e.g. CPU, Memory, or DISK IO, but the whole system together is just simply slow. What should be my performance expectation, how come my LAN free backup even slower then my LAN backup? For some other host, I am OK, e.g: When I use the other RS/6000 P640 box as the TSM LAN client, I can get 7.0MBps by using LAN backup; When I use the other IBM NetVista, 950MHz, Intel, 256M Memory, I can get 1.9MBps by using LAN, with 100% Disk IO Usage; Mike Brown - Do You Yahoo!? Sign-up for Video Highlights of 2002 FIFA World Cup - Do You Yahoo!? Sign-up for Video Highlights of 2002 FIFA World Cup
Re: NDS Backup Question
What have you tried? Have a look at the end of the V5.1 manual, which includes a discussion about include-exclude processing for the NDS. 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. Cory Heikel [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/12/2002 12:53 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:NDS Backup Question We are experiencing a problem backing up the nds on our netware servers. It is a known problem, novell claims it is working as designed, and suggest that we exclude the license objects from the backup (see below). I have tried several ways to exclude these objects but have not been successful. Anyone know how to do it? Thanks in advance, Cory from the dsmsched.log: 06/12/2002 01:06:17 ANS1228E Sending of object '.[Root].O=HMC.OU=Groupwise.NLS:Publisher=Novell+NLS:Product=NetWare 5 Server+NLS:Version=510.NLS:License ID=SN:300945821' failed 06/12/2002 01:06:17 ANS1301E Server detected system error 06/12/2002 01:06:18 ANS1228E Sending of object '.[Root].O=HMC.OU=Groupwise.NLS:Publisher=Novell+NLS:Product=NetWare 5 Server+NLS:Version=510.NLS:License ID=SN:300945834' failed 06/12/2002 01:06:18 ANS1301E Server detected system error 06/12/2002 01:06:18 ANS1228E Sending of object '.[Root].O=HMC.OU=Groupwise.NLS:Publisher=Novell+NLS:Product=NetWare 5 Server+NLS:Version=510.NLS:License ID=SN:300945853' failed 06/12/2002 01:06:18 ANS1301E Server detected system error Novell's reply: This document (10026730) is provided subject to the disclaimer at the end of this document. Fact Novell NetWare 5.1 Novell NetWare 5.0 NW5SP4.EXE NW51SP3.EXE Symptom Cannot backup license objects after applying NW5SP4.EXE. Getting error when backing up licenses on NW4.X, during NDS backup: license object is a corrupted file. Getting error backing up licenses on NW5.X during NDS backup: license object Insufficient rights. Error E3125 Failed to read Object Name data set, fffdfe83 in ArcServe log. Same error with Backup Exec 8.5 Cause This type of error is the result of some changes in licensing which were introduced with SP4/SP8 and SP3 for NW5.1. The new version of NLS is masking out all rights to read the license objects. This will not allow the licensing object to be backed up as designed. Fix When preforming a backup the licensing objects will need to be excluded. Upon making a restore from a backup the licenses will need to be reinstalled.
Re: Undocumented feature ?
Admin Reference, Chapter 2: Entering Administrative Commands, section Routing Commands. 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. David Rigaudiere [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/11/2002 09:08 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Undocumented feature ? Hi guys, I've just found a feature to send one command over many TSM servers at the same time. I don't find any reference in TSM's books, is it documented ? is it supported ? ---cut---cut--- tsm: TSM2(tsm1,tsm2)q dr ANR1699I Resolved TSM1,TSM2 to 2 server(s) - issuing command q dr against server(s). ANR1687I Output for command 'q dr' issued against server TSM1 follows: Library Name Drive Name Device Type On-Line --- --- STK9740 98401ECARTRIDGE Yes STK9740 98402ECARTRIDGE Yes ANR1688I Output for command 'q dr' issued against server TSM1 completed. ANR1687I Output for command 'q dr' issued against server TSM2 follows: Library Name Drive Name Device Type On-Line --- --- STK9740 98401ECARTRIDGE Yes STK9740 98402ECARTRIDGE Yes ANR1688I Output for command 'q dr' issued against server TSM2 completed. ANR1694I Server TSM1 processed command 'q dr' and completed successfully. ANR1694I Server TSM2 processed command 'q dr' and completed successfully. ANR1697I Command 'q dr' processed by 2 server(s): 2 successful, 0 with warnings, and 0 with errors. tsm: TSM2 ---cut---cut--- Regards David Sniper Rigaudiere __END__ --- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. ABN AMRO Bank N.V. (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. ---
Re: TSM 4.1.2.12 NT client installation.
Hi, I just took a (admittedly quick) look at the README file, but could not find it in the 4.1.2.12 README. I know it was in there at one time, but it should have been since removed. If you can point me to the text, I can look to have it removed from subsequent READMEs. Thanks, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend From: Brian L. Nick [EMAIL PROTECTED] Sure we can do that but the readme for this client indicates that these services will be installed automatically, or did I misinterpret this?
Re: TSM 4.1.2.12 NT client installation.
OK, now I see... well, yes, technically it is correct, in that the client acceptor and remote client agent executables are indeed installed on the system. It's the *configuration* of the associated services (a.k.a. installing the services) that is not performed at software install time. The client scheduler is similar: we install the software you need to run the client scheduler, but you still need to configure the associated scheduler service. Just the same, perhaps it would help if, in the future, we mentioned the distinction between installing the software vs. configuring the sevices to run the software. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Brian L. Nick [EMAIL PROTECTED]@VM.MARIST.EDU on 07/09/2001 12:07:29 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: TSM 4.1.2.12 NT client installation. Andy, Thanks for the reply. This might be confusion on my part as the read-me talks about the Web Client which I relate to the Client Acceptor and the Remote Client Agent,here is the entry that I am talking about: Installing the Client - * Please NOTE: The install dialogs are all new and different from the * * previous Version 3 Tivoli Storage Manager product. The 3rd dialog * * on the new install path is Setup Type. There are 2 choices, * * Complete (comparable to the old Typical) and Custom. Complete * * installs the Backup-Archive client, the Web client, and the Online * * documentation. * * - The Tivoli Storage Manager Administrator command line client is NOT * *a part of the Complete install. * * - There is not a response file install as there was in TSM Version 3. * Please let me know if this is something that I am missing. - Brian Andy Raibeck Andrew_Raibeck@TTo: [EMAIL PROTECTED] IVOLI.COM cc: Sent by: ADSM: Subject: Re: TSM 4.1.2.12 NT client Dist Storinstallation. Manager [EMAIL PROTECTED] .EDU 07/09/01 02:38 PM Please respond to ADSM: Dist Stor Manager Hi, I just took a (admittedly quick) look at the README file, but could not find it in the 4.1.2.12 README. I know it was in there at one time, but it should have been since removed. If you can point me to the text, I can look to have it removed from subsequent READMEs. Thanks, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend From: Brian L. Nick [EMAIL PROTECTED] Sure we can do that but the readme for this client indicates that these services will be installed automatically, or did I misinterpret this?
Re: TSM 4.1.2.12 NT client installation.
Hi Nick, You make a good point about installing the services via the setup program, and in principle I would tend to agree. But in order to install the services, you would need to know several items in advance, such as the desired node name, password, client options file(s) (which would require an additional wizard to create and configure), Windows account under which to run the services, etc. Then there are the cases where you want/need more than one of each kind of service. These issues are (arguably) beyond the scope of what we want to accomplish in the software install program, at least not without a high degree of customization, and so we left it as an additional item to be performed after the setup program completes. Not to make it too difficult, we did implement a setup wizard for configuring the scheduler and web client services (and the journal engine in 4.2). If dsm.opt does not exist, then when you start the GUI, it will invoke the TSM Setup Wizard, from which you can configure any of the basic sdervices (plus the Journal engine in 4.2). If dsm.opt does exist and you want to use the wizard to configure the services, just choose Setup Wizard from the Utilities menu in the GUI. For advanced service configuration capability, you can use dsmcutil.exe. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Brian L. Nick [EMAIL PROTECTED]@VM.MARIST.EDU on 07/09/2001 13:03:42 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: TSM 4.1.2.12 NT client installation. Andy, Thanks for the info. I think that you are on to something, if you specify the difference then you won't get silly questions from someone like me. I see your point with the doc and now that you explain it that way I feel silly. Just as an after thought would it be helpful to include the service configuration as part of the install? The installation is really useless until all or select services are configured on the client. It is helpful for someone like me who is not NT literate (I support the TSM server on OS/390) but still gets involved with client concerns. Let me know what you think, and thanks again. - Brian Andy Raibeck Andrew_Raibeck@TTo: [EMAIL PROTECTED] IVOLI.COM cc: Sent by: ADSM: Subject: Re: TSM 4.1.2.12 NT client Dist Storinstallation. Manager [EMAIL PROTECTED] .EDU 07/09/01 03:46 PM Please respond to ADSM: Dist Stor Manager OK, now I see... well, yes, technically it is correct, in that the client acceptor and remote client agent executables are indeed installed on the system. It's the *configuration* of the associated services (a.k.a. installing the services) that is not performed at software install time. The client scheduler is similar: we install the software you need to run the client scheduler, but you still need to configure the associated scheduler service. Just the same, perhaps it would help if, in the future, we mentioned the distinction between installing the software vs. configuring the sevices to run the software. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Brian L. Nick [EMAIL PROTECTED]@VM.MARIST.EDU on 07/09/2001 12:07:29 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: TSM 4.1.2.12 NT client installation. Andy, Thanks for the reply. This might be confusion on my part as the read-me talks about the Web Client which I relate to the Client Acceptor and the Remote Client Agent,here is the entry that I am talking about: Installing the Client - * Please NOTE: The install dialogs are all new and different from the * * previous Version 3 Tivoli Storage Manager product. The 3rd dialog * * on the new install path is Setup Type. There are 2 choices, * * Complete (comparable to the old Typical) and Custom. Complete * * installs the Backup-Archive client, the Web client, and the Online * * documentation. * * - The Tivoli Storage Manager Administrator command line client is NOT * *a part of the Complete install. * * - There is not a response file install as there was in TSM Version 3. * Please let me know if this is something that I am missing. - Brian Andy Raibeck
Re: TSM 4.2
Because someone uploaded the Win9x version of the README.FTP file instead
of the WinNT version. This has since been fixed.
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend
Kleynerman, Arthur [EMAIL PROTECTED]@VM.MARIST.EDU on
07/03/2001 08:09:39
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: TSM 4.2
Andy, why is it that the NT/2000 4.2.0 client's TSM420GA_NT_README.FTP.txt
file says - This package is for Windows 98 or Windows ME running on an
Intel (or similar) processor.
Arthur
-Original Message-
From: Andy Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 03, 2001 9:19 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM 4.2
The TSM servers contain the licensing files that enable you to use it. Any
time there is a new version or release of TSM, you need to pay for it. By
new version or release, I mean that the first or second nodes of the verson
number have changed (i.e. 4.2 = Version 4, Release 2). Only TSM server PTFs
and patches are made available on the ftp site, and those presume that you
have already bought the GA level of the code (which has the licensing
parts).
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend
Tom Tann{s [EMAIL PROTECTED]@VM.MARIST.EDU on 07/02/2001 04:53:57
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: TSM 4.2
Hello!
The 4.2-clients have been available on the ftp-server since Saturday.
Anyone know why the 4.2-servers still are missing?
GA was on July 1. for both?
The AIX-server is the one I'm waiting for..
---
The information contained in this e-mail message, and any attachment
thereto, is confidential and may not be disclosed without our express
permission. If you are not the intended recipient or an employee or agent
responsible for delivering this message to the intended recipient, you are
hereby notified that you have received this message in error and that any
review, dissemination, distribution or copying of this message, or any
attachment thereto, in whole or in part, is strictly prohibited. If you
have received this message in error, please immediately notify us by
telephone, fax or e-mail and delete the message and all of its attachments.
Thank you.
Every effort is made to keep our network free from viruses. You should,
however, review this e-mail message, as well as any attachment thereto, for
viruses. We take no responsibility and have no liability for any computer
virus which may be transferred via this e-mail message.
(See attached file: TSM420GA_NT_README.FTP.txt)
TSM420GA_NT_README.FTP.txt
Re: TSM 4.2
The TSM servers contain the licensing files that enable you to use it. Any
time there is a new version or release of TSM, you need to pay for it. By
new version or release, I mean that the first or second nodes of the verson
number have changed (i.e. 4.2 = Version 4, Release 2). Only TSM server PTFs
and patches are made available on the ftp site, and those presume that you
have already bought the GA level of the code (which has the licensing
parts).
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend
Tom Tann{s [EMAIL PROTECTED]@VM.MARIST.EDU on 07/02/2001 04:53:57
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: TSM 4.2
Hello!
The 4.2-clients have been available on the ftp-server since Saturday.
Anyone know why the 4.2-servers still are missing?
GA was on July 1. for both?
The AIX-server is the one I'm waiting for..
Re: ODBC driver that works with Office 2000?
I am not at liberty to divulge details about future product plans, but if were, I might say that Office 2000 support could be coming in the not-too-distant future. ;-) Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Keith Minster [EMAIL PROTECTED]@VM.MARIST.EDU on 06/22/2001 13:32:09 Please respond to [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: ODBC driver that works with Office 2000? Greetings all, The latest ODBC driver for Win32 that I can find is for 4.1.2.12. Its readme states that the only MS Office apps it works with are the '97 versions. Now that Microsoft has come out with its second release since then (2000, now XP)... Has anybody heard when Tivoli will update the TSM ODBC drivers to work with current versions of MS Office? Does anybody know why it hasn't been kept updated? Thanks. Keith Minster Sara Lee Corp. Winston-Salem, NC
Re: TSM 3.7.2 client
Jeff, You can check the Tivoli web site (www.tivoli.com) and look at the client requirements to determine which OS's are supported at which client versions. The direct page is http://www.tivoli.com/support/storage_mgr/clients.html. When we announce new products, the announcement includes the client platforms supported by that product. Aside from that, I really do not know what other mechanisms our Marketing team has to get the word out. If you have a relationship with your local IBM branch office, then hopefully they are keeping you apprised of new developments; you should check with them. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Jeff Bach [EMAIL PROTECTED]@VM.MARIST.EDU on 06/11/2001 11:50:27 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: TSM 3.7.2 client Andy, What Operating Systems need to be eliminated prior to this date to maintain a supported level of ADSM in an environment? How is this communicated to your customers? HP10.20, NCR, AIX 4 ..., Auspex 2.***, NT4.0 ?? Jeff Bach Home Office Open Systems Engineering Wal-Mart Stores, Inc. WAL-MART CONFIDENTIAL -Original Message- From: Andy Raibeck [SMTP:[EMAIL PROTECTED]] Sent: Friday, June 08, 2001 1:35 PM To: [EMAIL PROTECTED] Subject:Re: TSM 3.7.2 client Hello Brian, The TSM clients go out of service when their corresponding server version goes out of service. The end-of-service matrix shows that TSM 3.7 for OS/390 goes out of service on September 30; for other platforms it is October 31. This includes both server and client. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Brian Nick [EMAIL PROTECTED]@VM.MARIST.EDU on 06/08/2001 05:26:48 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TSM 3.7.2 client Hello everyone. I have been doing some research this morning trying to locate the end of service date for the TSM 3.7.2 client for all platforms. I have been able to locate the end of service for the TSM server (3.7.4) but not for the 3.7.2 client. I would like to go to the 4.1.2.12 client version for WIN but I am receiving some resistance. Could some one please point me to the site that contains this information? I have been on the Tivoli web site but I have been unable to locate dates for the clients. Thanks for all your help. - Brian Brian L. Nick Systems Technician - Storage Solutions Phoenix Home Life Mutual Ins. 100 Bright Meadow Blvd Enfield CT. 06082-1900 E-MAIL: [EMAIL PROTECTED] PHONE: (860)403-2281 ** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **
Re: TSM 3.7.2 client
Hello Brian, The TSM clients go out of service when their corresponding server version goes out of service. The end-of-service matrix shows that TSM 3.7 for OS/390 goes out of service on September 30; for other platforms it is October 31. This includes both server and client. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Brian Nick [EMAIL PROTECTED]@VM.MARIST.EDU on 06/08/2001 05:26:48 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TSM 3.7.2 client Hello everyone. I have been doing some research this morning trying to locate the end of service date for the TSM 3.7.2 client for all platforms. I have been able to locate the end of service for the TSM server (3.7.4) but not for the 3.7.2 client. I would like to go to the 4.1.2.12 client version for WIN but I am receiving some resistance. Could some one please point me to the site that contains this information? I have been on the Tivoli web site but I have been unable to locate dates for the clients. Thanks for all your help. - Brian Brian L. Nick Systems Technician - Storage Solutions Phoenix Home Life Mutual Ins. 100 Bright Meadow Blvd Enfield CT. 06082-1900 E-MAIL: [EMAIL PROTECTED] PHONE: (860)403-2281
Re: DBI Connections to TSM database
We do not test our ODBC driver with Perl, so there is no guarantee that it
will work. However, unofficially, at least some aspects of it will work...
with the correct Perl setup.
Go to http://www.adsm.org and do a search using this criteria:
+perl +odbc +raibeck
You will find an informative post from Mr. Gerhard Rentschler describing
how he was able to use Dave Roth's Win32:ODBC module to get a simple SELECT
statement to work in Perl.
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend
Chibois, Herve [EMAIL PROTECTED]@VM.MARIST.EDU on 06/07/2001
06:06:10 AM
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: DBI Connections to TSM database
Hi Mark
It's normal ! TSM DB is not a DB2 one. It is based on B-tree and
I've already tried to write a DBI::TSM driver. 99% of the job is
done but one out of 10 commands in the ODBC connection procedure
is different fro TSM. So I could not achieve my work.
When I have more time, I will ask a ODBC guru to help me to finish
my driver. At this time, if your admin box is NT, just install ODBC
and try to connect using this... But I did not manage to either using
PERL / PHP.
Keep in touch
rv
-Message d'origine-
De : Mark A. Adams [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi 6 juin 2001 22:43
À : [EMAIL PROTECTED]
Objet : DBI Connections to TSM database
I am running AIX 4.3.3.x with version 3.7.4 TSM.
I need to connect to the TSM database using perl, using the
DBI and the
DBD::DB2 module.
I am having trouble connecting to the database. Could anyone
give me a hand.
CODE
#!/usr/local/bin/perl
use DBI;
use DBD::DB2::Constants;
use DBD::DB2;
$db = DBI-connect(dbi:DB2:adsmsrv1, user, password);
if (!defined($db)) {
print Error connecting to server1 \n;
#print Error: . DBD::DB2::Error(). \n;
exit(1);
}
exit(0);
##
This is the error I am getting.
DBI-connect(adsmsrv1) failed: Total Environment allocation
failure! Did
you set up your DB2 client environment? at ./first.pl line 7
Error connecting to server1
#
Does any one have any ideas or could help me out?
Mark Adams
Systems Programmer
CSG Systems, Inc.
Re: backup tsm db
Offhand I can't say what the problem is, but it might not hurt to take a look at the individual SUMMARY table records that pertain to full database backups. That might lend a clue: select date(start_time) as START DATE, - time(start_time) as START TIME, - date(end_time) as END DATE, - time(end_time) as END TIME, - bytes - from summary - where activity='FULL_DBBACKUP' Then look at those entries pertaining to your time criteria, and see what they show. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Hy this is what my script looks like: set sqlmathmode round select count(*) as process, - case - when sum(bytes) 1073741824 then - cast(sum(bytes)/1073741824 as varchar(24))||'Gb' - when sum(bytes) 1048576 then - cast(sum(bytes)/1048576 as varchar(24))||'Mb' - when sum(bytes) 1024 then - cast(sum(bytes)/1024 as varchar(24))||'Kb' - else cast(sum(bytes) as varchar(24)) - end as Num Bytes, - activity as (17h till 17h)act. - from summary - where (date(start_time) = current date - 1 day - and time(start_time) '17:00') - or - (date(start_time) = current date - and time(start_time) '17:00') - group by activity any ideas yet? -Original Message- From: Lambelet,Rene,VEVEY,FC-SIL/INF. [mailto:[EMAIL PROTECTED]] Sent: 07 June 2001 12:16 To: [EMAIL PROTECTED] Subject: Re: backup tsm db hello, can we see your script ? René Lambelet Nestec S.A. / Informatique du Centre 55, av. Nestlé CH-1800 Vevey (Switzerland) *+41'21'924'35'43 7+41'21'924'28'88 * K4-117 email [EMAIL PROTECTED] Visit our site: http://www.nestle.com This message is intended only for the use of the addressee and may contain information that is privileged and confidential. -Original Message- From: Leijnse, Finn F SSI-ISES-31 [SMTP:[EMAIL PROTECTED]] Sent: Thursday, June 07, 2001 11:53 AM To: [EMAIL PROTECTED] Subject: backup tsm db Fellow *SM specialist, I have made a script to check what one of our TSM servers has done over a period of about 24H, here the result: count Num Bytes (17h till 17h)act. --- -- -- 3162540Gb ARCHIVE 811 87Gb BACKUP 1 0 EXPIRATION 2 1GbFULL_DBBACKUP 37 62Gb MIGRATION 34 52Gb RECLAMATION 31 217Mb RESTORE 2 0 STGPOOL BACKUP Please take a look at the database backup and can anyone explain why this shows only 1 GB over two full backups when my database is 22Gb!! in size. When I run the same script on another TSM server it shows that the full database backup is equal to its size? any ideas? met vriendelijke groeten, regards et salutations, Finn Leijnse Central Data Storage Management email: [EMAIL PROTECTED]
Re: DBI Connections to TSM database
Ah, now I see... sorry Mark, I think I missed your real point from your
original post.
That being the case, it is not possible to do what you want; there is no
way to access the TSM database outside of the Admin client or the ODBC
driver (which is only on Windows).
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend
Mark A. Adams [EMAIL PROTECTED]@VM.MARIST.EDU on 06/07/2001
08:09:53 AM
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: DBI Connections to TSM database
I really need this to run on an AIX platform.
Mark Adams
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Andy Raibeck
Sent: Thursday, June 07, 2001 8:40 AM
To: [EMAIL PROTECTED]
Subject: Re: DBI Connections to TSM database
We do not test our ODBC driver with Perl, so there is no guarantee that it
will work. However, unofficially, at least some aspects of it will work...
with the correct Perl setup.
Go to http://www.adsm.org and do a search using this criteria:
+perl +odbc +raibeck
You will find an informative post from Mr. Gerhard Rentschler describing
how he was able to use Dave Roth's Win32:ODBC module to get a simple SELECT
statement to work in Perl.
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend
Chibois, Herve [EMAIL PROTECTED]@VM.MARIST.EDU on 06/07/2001
06:06:10 AM
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: DBI Connections to TSM database
Hi Mark
It's normal ! TSM DB is not a DB2 one. It is based on B-tree and
I've already tried to write a DBI::TSM driver. 99% of the job is
done but one out of 10 commands in the ODBC connection procedure
is different fro TSM. So I could not achieve my work.
When I have more time, I will ask a ODBC guru to help me to finish
my driver. At this time, if your admin box is NT, just install ODBC
and try to connect using this... But I did not manage to either using
PERL / PHP.
Keep in touch
rv
-Message d'origine-
De : Mark A. Adams [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi 6 juin 2001 22:43
À : [EMAIL PROTECTED]
Objet : DBI Connections to TSM database
I am running AIX 4.3.3.x with version 3.7.4 TSM.
I need to connect to the TSM database using perl, using the
DBI and the
DBD::DB2 module.
I am having trouble connecting to the database. Could anyone
give me a hand.
CODE
#!/usr/local/bin/perl
use DBI;
use DBD::DB2::Constants;
use DBD::DB2;
$db = DBI-connect(dbi:DB2:adsmsrv1, user, password);
if (!defined($db)) {
print Error connecting to server1 \n;
#print Error: . DBD::DB2::Error(). \n;
exit(1);
}
exit(0);
##
This is the error I am getting.
DBI-connect(adsmsrv1) failed: Total Environment allocation
failure! Did
you set up your DB2 client environment? at ./first.pl line 7
Error connecting to server1
#
Does any one have any ideas or could help me out?
Mark Adams
Systems Programmer
CSG Systems, Inc.
Re: Japanese Filenames
USEUNICODEFILENAMES NO (The Default) TSM won't backup Japanese filenames unless you run the client on a Japanese NT server. Adding the Japanese codepage to a UK build won't work. USEUNICODEFILENAMES YES TSM will backup Japanese filenames most of the time, but occassionally dies a horrible death on certain filenames. With lots of people with lots of Japanese filenames, the client will fail more than it suceeeds. USEUNICODEFILENAMES is suppose to be used with Macintosh files, any other use is convenently unsupported by Tivoli. This is not a matter of convenience. USEUNICODEFILENAMES was *never* intended to provide the support you are seeking. It's purpose is strictly for support of Macintosh volumes on NTFS file systems (granted, though, the option would have been better named ENABLEMACFILESUPPORT, or something along those lines). Tivoli support (especially, the Japanese end) are no help whatsoever. As a company, Tivoli seem to have no concept that people do business in multiple languages, and as a backup product Tivoli need to support it. Recents failures, where the NT server product failed as soon as you run it under Japanese, German etc.. bears testiment to the fact, Tivoli aren't even testing their products under different languages. IBM/Tivoli fully understands the need for a global perspective, as we are a global company doing business all over the world. Please do not equate language support issues with have no concept that people do business in multiple languages. This is just not true. Agreed, the recent problems we have had with non-English character sets do not instill the greatest confidence in our NLS support. However, we do in fact have a large number of resources dedicated to NLS support, translation, and testing, and we are continuously working to improve our processes to (among other things) eliminate the kinds of problems you mention. Yes, we have stumbled in this arena, especially recently, but we have also made every effort to respond to the problems in as timely a fashion as possible, because we *do* understand the need for this support. Regarding support for file names comprised of characters from different character sets (i.e. Japanese file names on English systems), this is a long-standing requirement. It isn't here yet because we are ignoring it; rather, the implementation is not trivial. But it is something that we are actively working on and hope to deliver this year. (Standard caveat: this does not constitute a formal announcement or commitment.) Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend
Re: Installing TSM 4.1.0 Client in a WNT Server
Gerardo, Does this system have NTFS 8.3 file name creation disabled? If so, the following APAR (IC29085) probably describes your problem: == BEGIN APAR TEXT == ABSTRACT: THE WIZARD WAS INTERRUPTED BEFORE TIVOLI STORAGE MANAGER CLIENT COULD BE COMPLETELY INSTALLED. YOUR SYSTEM HAS NOT BEEN MODIFIED ERROR DESCRIPTION: When installing the TSM 4.1 client for Microsoft Windows, rather than seeing the Welcome dialog, you may see a dialog whose text reads: The wizard was interrupted before Tivoli Storage Manager Client could be completely installed. Your system has not been modified. To complete the installation at another time, please run setup again. If you run setup.exe with verbose logging active: setup /v/l*v setup.log The setup.log will show that the setup ends with return code 1603. This is a result of a failure in the StartUp action, which ends with return value 3. The following is a segment from a typical setup.log file showing the error in StartUp: Action start 8:19:57: StartUp. MSI (c) (2D:32): Transforming table Binary. MSI (c) (2D:32): Creating MSIHANDLE (37) of type 790542 for thread 306 Action ended 8:19:58: StartUp. Return value 3. The problem is in the InstallShield for Windows Installer software that is used to package the client. The problem occurs when 8.3 file name creation support for NTFS file systems has been disabled on Windows NT or 2000 (Windows 9x users should not experience this problem). If you are having problems installing the TSM 4.1 Windows client, run setup.exe with verbose logging enabled (as described above). After the failure, examine the resulting setup.log file for return code 1603 (near the bottom of the file) and the StartUp failure described above. If setup.log matches these two symptoms, then the next step is to verify whether 8.3 file name creation is disabled, as follows: 1) Examine the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem 2) Within that key, locate a value with the name: NtfsDisable8dot3NameCreation If this value is set to 1, then 8.3 file name creation is disabled, and this APAR is a match for the problem. If the value is 0, then 8.3 file name creation is enabled, and this APAR is not a match for the problem. Alternative: if you are unfamiliar or uncomfortable with accessing the registry, then you can run the following command from an OS prompt to obtain the same information. This command only reads certain values from the registry; it does not update the registry: regedit /e myreg.txt HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl Set\Control\FileSystem (Note: due to width restrictions, the above regedit command is shown on two lines although it is one long command. There are no spaces between CurrentControl at the end of the first line and Set at the beginning of the next line. The command will save the output to a file called myreg.txt. Review the myreg.txt file and look for the following line: NtfsDisable8dot3NameCreation=dword:0001 If the value following dword: is 0001 then 8.3 file name creation is disabled, and this APAR is a match for the problem. If the value is , then 8.3 file name creation is enabled and this APAR is not a match for the problem. LOCAL FIX: If 8.3 file name creation is disabled, you can circumvent the problem by temporarily reactivating the 8.3 file name creation. Here is how to do this: NOTE: Mistakes in editing the registry can introduce instability to your system, or even make it unusable or unbootable. It is recommended that you back up your registry before editing it. If you are unfamiliar or uncomfortable with editing the registry, you should ask someone else who has expertise in editing the registry to make this change for you. 1) Change NtfsDisable8dot3NameCreation value to 0. 2) Reboot Windows. 3) Run setup.exe to install TSM. 4) Disable 8.3 file name creation (if you wish) after the install runs by resetting NtfsDisable8dot3NameCreation to 1 and rebooting. Reference: Microsoft article Q210638 - How to Disable Automatic Short File Name Generation. === END APAR TEXT === Hope this helps, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Gerardo Zapata wrote: Hi, I'm trying to install the TSM client 4.1.0 in a Windows NT Server SP6 which is a node of an MS Cluster. When running the setup.exe the installation wizard stops with the following error message: The wizard was iterrupted before Tivoli Storage Manager could be completely installed. Your system has not been modified. To complete installation at another time, please run setup again Checking the NT Event Viewer, found an application error produced by the MS Installer with no more detailed information. Any suggestion, known
Re: AW: DSM.OPT override question.
If the product's vendor is making a recommendation about how to back up (or how not to back up) their product, it's probably a good idea to heed that recommendation. You do not want to be in a position where you need to restore, and the vendor can not help because you did not follow their recommended backup procedure. That said, it would be a good idea to ask the vendor why they make that recommendation, so that you can evaluate its technical merits. In this case, the vendor may have a very good reason for recomending against incremental backups; on the other hand, perhaps they do not understand what is meant by incremental backup, so again, a discussion as to why they make the recommendation is a good idea, so that all parties understand the issues. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend sal Salak Juraj [EMAIL PROTECTED]@VM.MARIST.EDU on 04/26/2001 11:06:16 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AW: DSM.OPT override question. not a direct help for your OPT problem but a general though about misconception it has been caused by: Much too often we speak - with our vendors and bosses and customers as well - about backup requirements. NOBODY HAS ANY BACKUP REQUIREMENTS, WE ALL DO ONLY HAVE RESTORE REQUIREMENTS. The backup is only a way to accomplish it, backup is only a tool and maybe a method, but not our target. If you happen to make your vendor understand this, the chances are better he will not matter what name of backup - incremental or selective - you use. regards Juraj Salak -Ursprüngliche Nachricht- Von: Alan Davenport [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 26. April 2001 21:03 An: [EMAIL PROTECTED] Betreff: DSM.OPT override question. One of our vendors insists that their product cannot be backed up incrementally and insists a selective backup is required. We've explained that a point in time restore is possible from incremental backups however they still insist that is no good. We've included their directory in our include/exclude list for the node bound the the management class that has been set up especially for this product's backups. The problem I'm having is that we have to use preschedule/postschedule commands to shut down and restart the database before/after the backups. We do not want to shut down the database for the normal nightly incremental backup for the node. I swear I read someplace that is possible to override the default DSM.OPT file for a backup schedule for a command line but I cannot remember where or how to do this. Can anyone help please? I would like to have the dir in question excluded from the normal incremental backup and for the selective backup include the needed pre/post schedule commands and the directory in question with an include statement. Al
Re: AW: DSM.OPT override question.
If you are essentially asking whether there is a way to dynamically load a new options file, then the answer is no. But even if you could, you do not want to use INCLUDE/EXCLUDE statements to include these files for selective backups in one options file, but exclude them for the incremental backups in another options file. If you try to do this, you will find that the backups taken with the selective backup will be expired via the EXCLUDE statement during your normal incremental backup. However, here are a couple of suggestions that might be useful and do not require a new options file: 1) If you want to combine the selective backup with your regular daily incremental backup, you can include your pre/post schedule commands to stop and restart the database in your regular dsm.opt file. In the special management class you created for the database's files, set the copy group's MODE to ABSOLUTE (normally it is set to MODIFIED). The ABSOLUTE mode will tell TSM to back up the files regardless of whether they have changed. Then set up your include/exclude list so that the database's files are bound to this special management class. The only drawback that I can think of is that depending on how long it takes to perform the scheduled backup of the machine, the database will be down for that time (as opposed to the time it takes to back up just the database files). Otherwise this is the easiest solution. 2) Create a batch file on the TSM client machine that does the following: - Issues the shutdown command for the database. - Issues a DSMC SELECTIVE backup for the database's files. - Issues the restart command for the database. To prevent the regular incremental backup from also backing up these files (in case they change between the selective backup and the incremental backup), set up the management class for these files so that the copy group's FREQUENCY parameter is set to a non-zero number like '7'. This will prevent the regular incremental backup from backing them up unless it has been at least 7 days since the last backup. As long as you do the daily selective backups, the 7-day criterion will not be met, so incremental backups will not try to back these files up. Here is a simple batch file example: @echo off echo --- echo Starting command on %date% %time% echo --- cd /d c:\tsm\baclient dsmc s dsm.opt echo --- echo Ending command on %date% %time% echo --- You would, of course, have to wrap your shutdown and startup commands around the cd and dsmc lines. The schedule definition could include these settings (this is for a scheduled command on Windows 2000): action=command objects=c:\tsm\baclient\mycmd.cmd c:\tsm\baclient\mycmd.out 21 This will cause the output from mycmd.cmd to be appended to a file named mycmd.out. You would have to implement some mechanism to handle the growing output file (i.e. to prune or delete it periodically). Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend Alan Davenport [EMAIL PROTECTED]@VM.MARIST.EDU on 04/27/2001 07:58:48 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: AW: DSM.OPT override question. Thank you Andy. Our group is under the impression that the vendor is thinking about the old-style (non-*SM) type of incremental backups where an operating system utility is used to take a full backup then incrementals throughout the week. In this scenario files that were deleted throughout the week could get restored if the full then all incrementals are restored. This could of course be a source of problems for some apps. In this case the vendor has a valid point. Of course *SM does not behave this way and a point in time restore can be done without restoring deleted files. What I'm doing is looking for ways to accommodate them if in fact, we must. IS it possible to specify a different client options file for a particular backup schedule? If this is the case there is no real problem. If not, then I have to look at trying something as ugly as defining two separate *SM nodes on the server. ): Al [EMAIL PROTECTED] wrote: From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Fri, 27 Apr 2001 07:33:48 -0700 Subject: Re: AW: DSM.OPT override question. If the product's vendor is making a recommendation about how to back up (or how not to back up) their product, it's probably a good idea to heed that recommendation. You do not want to be in a position where you need to restore, and the vendor can not help because you did not follow their recommended backup procedure. That said, it would be a good idea to ask
Re: TSM Support for Windows Me
Apparently the web page is not up to date. As of TSM 4.1.2.x, we do support Windows Me (it's mentioned in the READ1STC.TXT file that accompanies the client. So if you install 4.1.2.12 or 4.1.2.14, you can back up Windows Me. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. Dave Canan [EMAIL PROTECTED]@VM.MARIST.EDU on 04/22/2001 08:43:52 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TSM Support for Windows Me Can someone from Tivoli Support comment on the support for TSM and Windows Me? I realize that it is not on the supported page for Windows platforms, but how different is Windows Me from Windows 9x? Has anyone actually tried the TSM Windows client with this platform? I have a customer who has several machines with it and wants to know whether or not it will work. Any comments are welcome. Thanks. Money is not the root of all evil - full backups are.
Re: redirecting output
Hi Geoff, Both of these work for me: From the interactive Admin CLI: tsm: SS2_ADSM_GROUP_SERVERq drmedia x.out Output of command redirected to file 'X.OUT' From an OS command prompt, batch mode: C:\TSM\baclientdsmadmc -id=nnn -pa=xxx -tcps=ss2 q drmedia x.out Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Gill, Geoffrey L." [EMAIL PROTECTED]@VM.MARIST.EDU on 04/20/2001 06:58:50 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: redirecting output Hello all, I am trying to redirect the output of a server command script to a file and have been unable to do so. I'm getting: ANR2020E QUERY DRMEDIA: Invalid parameter - and ANR2020E QUERY DRMEDIA: Invalid parameter - |, depending on which character I try. This is in the help file if you "help 12" so why doesn't it work? I am on AIX 4.3.3 TSM 4.1.2.0 Thanks for the help, Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: SQL for Amount Backed up Daily:
Consider activating the accounting records feature on your TSM server. There is a lot of information to be had from the accounting records. Another alternative would be to look at the SUMMARY table on the TSM server. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Bill Robb [EMAIL PROTECTED]@VM.MARIST.EDU on 04/18/2001 04:22:09 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: SQL for Amount Backed up Daily: Folks... I'm running TSM 4.1 on an S390 server, and have 85 clients divided into two domains - Novell and AIX. Many of the clients run multiple backup sessions per day. I'm new to SQL, and have been trying to write the command that will show me the amount backed up, in MB per day, per client. My problem is that my command only shows me the amount from the last session, not the last 24 hours. Has anyone ever succeeded at writing such a command? Thanks. Bill Robb
file name too long when?
APAR IC27346 discusses this problem. This was fixed in an earlier 3.7.2.x patch, and the permanent fix went in to the 4.1.1.0 (and later) versions. I recommend that customers use either 3.7.2.19 or 4.1.2.12. I have included the text of the APAR below. Note that in the "RECOMMENDATION" section of the text, it says to not apply new maintenance until the fixing PTF is available. "Fixing PTF" was a reference to 4.1.1.0, which was not available at the time this APAR text was written. This fix was *not* available in 4.1.0.x, so the point of this caveat was to tell users who install 3.7.2.19 not to go to 4.1.0.x, but to wait for 4.1.1.0 (or higher). BEGIN APAR TEXT ABSTRACT: WINDOWS CLIENT CAN NOT BACK UP FILES WHOSE NAMES EXCEED THE WINDOWS OS LIMIT OF 260 CHARACTERS. ERROR DESCRIPTION: Windows permits a maximum path length of 260 characters (259 usable characters plus 1 for the string terminator). However, under certain conditions, the operating system permits files of greater lengths to be created. As a result, when the TSM Windows client attempts to access files whose path lengths exceed the OS limit, the I/O operation fails with Win32 return code 206 (ERROR_FILENAME_EXCED_RANGE). PROBLEM SUMMARY: * USERS AFFECTED: Windows client on NT and 2000. * * PROBLEM DESCRIPTION: The Windows client is unable to process * *files and directories whose names exceed the operating* *system-defined length of 259 characters. * * RECOMMENDATION: Apply fixing PTF when available. Users of* *fixtest 3.7.2.16 must not apply new maintenance until * *the fixing PTF for this APAR is available.* PROBLEM CONCLUSION: The Windows operating system defines a maximum path length of 260 characters (259 usable characters plus 1 character to terminate the path). However, under certain circumstances, it is possible to create files whose path lengths violate this limit. When this happens, many programs, including Windows Explorer, Notepad.exe, TSM, etc., can not access these files. The Microsoft Win32 API file I/O functions provide a circumvention to this problem that has been incorporated into the TSM client. The client will now be able to support (i.e. backup, restore, archive, retrieve) files that exceed the 259 character limit provided that the USEUNICODEFILENAMES NO client option is in effect. If USEUNICODEFILENAMES is set to YES, then the client will not be able to support these files. The following information should be noted with regard to this fix: - USEUNICODEFILENAMES NO must be in effect (as mentioned above). If USEUNICODEFILENAMES YES is in effect, then these longer file names are unsupported. Users should always use USEUNICODEFILENAMES NO unless they have Mac volumes. If users need to support both Mac volumes AND these longer file names, then they will need to make provisions to run backups for the Mac volumes separately from the non-Mac files, backing up the Mac volumes with USEUNICODEFILENAMES YES, and the non-Mac files with USEUNICODEFILENAMES NO. The default value for USEUNICODEFILENAMES is YES when LANGUAGE AMENG is in effect. For other LANGUAGE settings, the default for USEUNICODEFILENAMES is NO. Thus when LANGUAGE AMENG is in effect, users must explicitly code USEUNICODEFILENAMES NO in their client options file. - The maximum supported length of the file name itself (not including the directory in which it resides), is 255 characters. - The maximum supported length of the directory portion of the path in which the file resides (not including the file itself) is 1,024 characters. - The maximum supported length of any component within a directory path can not exceed 255 characters. "Component" refers to a part of a directory structure as delimited by the backslash character. To illustrate: Given a path of the form: x:/comp1/comp2/comp3/filename Each component "compx" can not exceed 255 characters. Likewise, "filename" can not exceed 255 characters in length. In addtion, "x:/comp1/comp2/comp3" can not exceed 1,024 characters. Paths whose components exceed any of these limits are not supported. Note: forward slashes are substituted for backslashes in the above example because backslashes are not displayable in this APAR text. ===== END APAR TEXT = Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." From: Glass, Peter [EMAIL PROTECTED] One of our NT
Re: file name too long when?
Anne, the book that is wrong. See APAR IC29922. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Short, Anne" [EMAIL PROTECTED]@VM.MARIST.EDU on 04/16/2001 08:18:20 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: file name too long when? Sorry, Andy, but you've just confused me. Per the "TSM Manager for Windows Using the Backup-Archive Client" manual, in Chapter 8 - Setting Common Options: - LANGUAGE - AMENG (American English) is the default - USEUNICODEFILENAMES - NO is the default So how can the statement in the APAR text below be true?? - The default value for USEUNICODEFILENAMES is YES when LANGUAGE AMENG is in effect. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: TSM client on HP-UX
I'm not sure what the problem is. I just downloaded the file (it's IP21930.tar.Z, not IP21930.tar), and used tar to unzip/untar the file: tar -z -xvf IP21930.tar.Z I did this on a Windows system using GNU tar, so I do not see why this would not work on HP-UX. IP21930.tar.Z is 20,362,089 bytes. The tar command extracted these files: README - 24,489 bytes README.API - 17,988 bytes README.OLD - 24,965 bytes README.WEBCLI - 10,492 bytes TIVsm - 42,045,440 bytes TIVsm64 - 3,522,560 bytes If I decompress the file using gzip (before running tar), the resulting IP21930.tar file is 45,660,160 bytes. You might check your .Z and/or .tar files against the sizes I provided above. Maybe you need to try downloading the file again. Also, see if you have enough disk space to do the extract. Lastly, I pulled the file down from the primary site, ftp.software.ibm.com. If you got it from a mirror site, maybe there is a problem with the copy on the mirror. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." -Original Message- From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 10 April, 2001 1:00 PM To: [EMAIL PROTECTED] Subject: TSM client on HP-UX Hi all , trying to install TSM clinet on HP-UX , but unable to extract the tar file . downloded from tivoli web site today. solaris , AIX tar files works fine ..any idea ? root@dimdu11 [/install] # ls IP21930.tar README.API TIVsm Maestro_License README.OLD lost+found README README.WEBCLIperl5.tar root@dimdu11 [/install] # tar -xvf IP21930.tar x README, 24489 bytes, 48 tape blocks x README.API, 17988 bytes, 36 tape blocks x README.OLD, 24965 bytes, 49 tape blocks x README.WEBCLI, 10492 bytes, 21 tape blocks x TIVsm, 42045440 bytes, 82120 tape blocks Tar: error! blocksize changed root@dimdu11 [/install] # uname -r B.10.20 root@dimdu11 [/install] Shekhar Dhotre AIX Certified Specilaist Sun certified Admin for solaris 7 MCSE
Re: Amount of Data Backed Up Each Night
I haven't been following this thread too closely, so maybe I missed it... but has anyone mentioned the TSM server accounting records? Back when I was a customer, I used to use them to get this kind of information. Check out the description in the TSM Admin Guide (look up "accounting records" in the index). Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Kelly J. Lipp" [EMAIL PROTECTED]@VM.MARIST.EDU on 04/06/2001 09:09:16 AM Please respond to [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Amount of Data Backed Up Each Night The schedule log file has this in it so you can do an incremental from the schedule rather than running a script to get the same information. This info is also kept in the server activity log and is available via select statements (I believe) from the node table. One of our SQL gurus should leap in at this point and show us how. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Poehlman, James Sent: Friday, April 06, 2001 9:51 AM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night My backups run a script on the client that executes the ''dsmc inc'' command for each file system to be backed up. The output is redirected into a log file for each filesystem. Add up all the ''bytes transferred'' in the log files. -Original Message- From: Dearman, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, April 06, 2001 11:09 AM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night I am new to the ADSM or TSM world. How do you guys find out how mcuh data you are backing up per night. Is there a command line in ADSM to show you this. -Original Message- From: Sean McNamara [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 1:14 PM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night Dwight, Just curious - how big are your disk storage pools and what tape robot are you using ? Sean McNamara Senior Analyst PJM Interconnection, L.L.C. 955 Jefferson Ave Norristown, PA 19403 (610)666-4206 (610)666-4285 (fax) -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 1:59 PM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night biggest single box is a 2.4 TB db that compresses down to 600 GB backes up every other day/night have tons of others that are 500-ish GB's that compress down to 100-200 GB and back up nightly across all the tsm servers we do 1.5 TB nightly DWight [EMAIL PROTECTED] -Original Message- From: Diana J.Cline [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 12:40 PM To: [EMAIL PROTECTED] Subject: Amount of Data Backed Up Each Night Is there anyone else out there who is backing up 300gb per night or more? If so, i'd love to converse with you. ***EMAIL DISCLAIMER** This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management (312) 996-3941.
Re: Amount of Data Backed Up Each Night
Actually the LASTSESS_SENT field is for data sent for *any* TSM client operation, not just for the last backup. So if between the time the backup finished and the SELECT statement is run, the user performs some other operation... even something like DSMC QUERY SESSION... then the LASTSESS_SENT field will reflect data from that operation, not the last backup. Thus I would not recommend using this, as it is not entirely reliable for this purpose. For example: DSMC INCREMENTAL LASTSESS_SENT reflects data sent during incremental backup DSMC SELECTIVE C:\MYFILE.TXT LASTSESS_SENT reflects data sent during backup of c:\myfile.txt DSMC QUERY SESSION LASTSESS_SENT reflects data sent (very small amount) for QUERY SESSION SELECT NODE_NAME, LASTSESS_SENT FROM NODES Output reflects value from the above QUERY SESSION command. As this sequence shows, you could get misleading information using this method. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Anderson, Chris D." [EMAIL PROTECTED]@VM.MARIST.EDU on 04/06/2001 09:48:38 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Amount of Data Backed Up Each Night Run this query command and it will give you the node name and how much data that node sent from it's last backup. select NODE_NAME,LASTSESS_SENT from nodes Chris Anderson WIC Systems Administrator [EMAIL PROTECTED] -Original Message- From: Kelly J. Lipp [SMTP:[EMAIL PROTECTED]] Sent: Friday, April 06, 2001 11:09 AM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night The schedule log file has this in it so you can do an incremental from the schedule rather than running a script to get the same information. This info is also kept in the server activity log and is available via select statements (I believe) from the node table. One of our SQL gurus should leap in at this point and show us how. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Poehlman, James Sent: Friday, April 06, 2001 9:51 AM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night My backups run a script on the client that executes the ''dsmc inc'' command for each file system to be backed up. The output is redirected into a log file for each filesystem. Add up all the ''bytes transferred'' in the log files. -Original Message- From: Dearman, Richard [mailto:[EMAIL PROTECTED]] Sent: Friday, April 06, 2001 11:09 AM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night I am new to the ADSM or TSM world. How do you guys find out how mcuh data you are backing up per night. Is there a command line in ADSM to show you this. -Original Message- From: Sean McNamara [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 1:14 PM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night Dwight, Just curious - how big are your disk storage pools and what tape robot are you using ? Sean McNamara Senior Analyst PJM Interconnection, L.L.C. 955 Jefferson Ave Norristown, PA 19403 (610)666-4206 (610)666-4285 (fax) -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 1:59 PM To: [EMAIL PROTECTED] Subject: Re: Amount of Data Backed Up Each Night biggest single box is a 2.4 TB db that compresses down to 600 GB backes up every other day/night have tons of others that are 500-ish GB's that compress down to 100-200 GB and back up nightly across all the tsm servers we do 1.5 TB nightly DWight [EMAIL PROTECTED] -Original Message- From: Diana J.Cline [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 05, 2001 12:40 PM To: [EMAIL PROTECTED] Subject: Amount of Data Backed Up Each Night Is there anyone else out there who is backing up 300gb per night or more? If so, i'd love to converse with you. ***EMAIL DISCLAIMER** This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or cont
Re: Confusion with retention values.
Hi Alex, The RETEXTRA and RETONLY values both start counting days from the time the versions go inactive. So in your example, the version that went inactive on day 4 (file was deleted) will be expired on day 10. Thus, with RETEXTRA and RETONLY both being 10, there is no distinction between the expiration of any of the versions. I can see the confusion because at the time the file is deleted on the system, it isn't necessarily the *only* remaining version, so I can see how RETONLY could lead you to think that it means "number of days to expire after it becomes the only version". But no, the counting starts from the time the backup version is marked inactive. The RETONLY just gives you that little bit of additional flexibility that says, "once I delete the file, keep the last (latest) remaining version for x days from the time I deleted it". Actually, it isn't from the time you deleted it, it's from the time it was inactivated; which, if you do daily backups, could be called "close enough"... :-) If you want to leave your users with one last "out" to restore a deleted file, then set RETONLY to something higher, say, like 20. Then users have up to 20 days to restore the last remaining version of a file that they deleted. In the case of Patrick's question, he had this for his versions: STATE LL_NAME BACKUP_DATEDEACTIVATE_DATE -- -- -- ACTIVE_VERSION 36E54BF0.000 2001-03-20 INACTIVE_VERSION 36E54BF0.000 2000-12-08 2001-02-17 INACTIVE_VERSION 36E54BF0.000 2001-02-17 2001-03-20 The oldest version was created on 8 December 2000. The next oldest version was created on 17 February 2001. Note that that is the deactivation date for the oldest version, so that is when the clock starts ticking. Thus the oldest version will be expired 90 days after 17 February 2001, which would be around May 18th (if I counted 90 days correctly). Thus the user has up to 90 days to restore that older version, should she decide that restore is necessary. Similarly, the most recent version was created on 20 March 2001, which is when the second oldest version was inactivated. At this time, the user has up to 90 days to restore the prior version, which will expire on June 18. If you do daily incremental backups, you can consider that each new backup represents a change to the file. With the 90 day RETEXTRA settings, the user has up to 90 days to "undo" a change that was made to the file and get it back to its prior state. Of course, the file may change several times during the day, so the "undo-ability" is only within a 24-hour granularity (again, assuming daily backups), which is sufficient for most files. For more critical files, you could do more frequent backups (i.e. multiple backups in a 24-hour period) but this would require that VEREXISTS and (optionally) VERDELETED have larger values, even maybe NOLIMIT, as I discussed previously in this thread. Now for the sake of discussion, let's assume that RETEXTRA worked the way that Patrick thought, which is that inactive versions will expire 90 days (in Patrick's case) from the date the backup was created. If it worked this way, then the 90-day clock would have started ticking on 12 December 2000, so when the user changed it on 17 February 2001, she would only have until 12 March 2001 to change her mind, which would be 23 days. Or, suppose the file was changed on, say, the 20th of February instead of the 17th. In that case, ther user would have only 20 days to restore the prior version. Taking this a step further, suppose the original backup was taken on 8 December, but the next backup didn't occur until, say, 20 March (because the file didn't change). In this case, if TSM worked so that the clock started ticking from the date the backup version was created, then the 8 December version would be expired as soon as the 20 March backup was taken, giving the user *no* opportunity to restore the prior version. So... if you consider it in this light, the way TSM actually works is more consistent since you have a predictable restorability. That is, in Patrick's case, the user has up to 90 days to restore a file to its prior state after changing it, regardless of when she changes it. This is as opposed to the latter cases I just described above where the restorability is not really predictable at all. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 03/30/2001 10:48:45 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Confusion with retention values. Andy, Does RetOnly START counting days after the versio
Re: Confusion with retention values.
By "keep versions for 90 days", I assume you mean the RETEXTRA setting. I think the confusion may come from thinking that this setting indicates how long to keep backup versions from the time they are created (?). This is not the case; rather, RETEXTRA indicates how long to keep the backup version after it goes in inactive. So if the next backup version after the one created on December 8 was taken, say, January 8, then the 90 day count for the Dec 8 version starts on Jan 8. Thus it would be eligible for expiration on April 8 (or thereabouts if I counted 90 days correctly). The idea is that if you are doing incremental backups on a daily basis, backing files up only when they have changed, then by setting RETEXTRA to 90 days, you are helping to ensure that users can recover a file up to 90 days after they made a change that they want to undo. RETEXTRA also works in tandem with VEREXISTS. This means that there is not necessarily any guarantee that the file will be around for 90 days. For example, if the file changes every day and VEREXISTS is set to, say, 5, then on day 6 when the 6th backup is taken, the 1st backup taken on day 1 will be expired regardless of the RETEXTRA setting. On the other hand, if VEREXISTS is set to 10 but the file changes only a monthly basis, then you will never have 10 backup versions at a time because any extra (inactive) versions older than 90 days will expire. So... if you want to provide a service that will almost always guarantee that your users can recover files up to 90 days after changing them, you could set VEREXISTS to 90 (or 91 if you want to "fudge" a day). Then even if the file changes daily causing your daily backups back it up every day, you'll have that 90 day restorability. Other food for thought: sometimes uesrs want multiple backups per day. In that case, if VEREXISTS is set to 90 and you make, say, 2 backups a day, then you'll only have 45 day restorability (2 backups per day, VEREXISTS=90 means 45 days to restore the oldest version before it expires). If this goes on a lot in your shop, consider setting VEREXISTS to NOLIMIT. Then you can take as many backups as you need, and all the inactve versions will be around for 90 days after they go inactive. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Patrick Boutilier [EMAIL PROTECTED]@VM.MARIST.EDU on 03/30/2001 06:43:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Confusion with retention values. Hello, I have a Backup Copy group defined as where I keep versions for 90 days and keep deleted files for 90 days (at least that what I think it should do). However I see files hanging around for more than 90 days when I do some looking. For instance there is an inactive file called 3744c320.000 that was backed up on Dec. 08, 2000. This file is older than 90 days so it should be expired. So far I have only seen this with Netware servers. Any ideas? Thanks. ADSM Server = 3.1.2.90 Copy Destination NETWAREDISK Frequency 0 Versions Data Exists Versions Data Deleted Retain Extra Versions 90 Retain Only Version 90 Copy Mode Modified Copy Serialization Shrstatic
Re: Confusion with retention values.
This way you might be able to restore something from more than 90 days ago. Makes it harder to tell your clients exactly how back you can restore from. :-) Well, that depends on what the "ago" means in "from more than 90 days ago". If you mean "from more than 90 days since I made the first backup" then yes, you are correct. But if you simply want to allow your users to restore an older backup version as far back as 90 days ago, then something like this would be the ticket: VEREXISTS=NOLIMIT RETEXTRA=90 VERDELETED=NOLIMIT RETONLY=180 Then what you have is a service that, as long as the file exists on the client file system and as long as you do at least one backup a day, assures that you can restore that file to the state it was in (within a 24-hour granularity) up to 90 days ago. "24-hour granularity" is just a caveat to account for multiple changes that might occur between daily backups. For instance, suppose I change the file several times in the course of a day, and do a daily backup. So the file goes through these transitions: state1 state2 state3 state4 state5 DAY 1: DAILY BACKUP OF FILE state6 state7 state8 DAY 2: DAILY BACKUP OF FILE Now I can't restore the file as it was in states 1-4, 6, or 7, but I can restore it as it was in states 5 and 8. Also, from the time the file changes after state 5, I have 90 days in which I can restore it to state 5. If the file is extremely critical, then I might want to back it up after *every* change. So I might do this: state1 DAY 1: SELECTIVE BACKUP OF FILE state2 DAY 1: SELECTIVE BACKUP OF FILE state3 DAY 1: SELECTIVE BACKUP OF FILE state4 DAY 1: SELECTIVE BACKUP OF FILE state5 DAY 1: SELECTIVE BACKUP OF FILE state6 DAY 2: SELECTIVE BACKUP OF FILE state7 DAY 2: SELECTIVE BACKUP OF FILE state8 DAY 2: SELECTIVE BACKUP OF FILE This is what the VEREXISTS=NOLIMIT buys you: After the backup of the file in state 'n', you can restore that file to an older state from a backup version taken any time between now and the last 90 days, regardless of how often you back it up. Note that in the latter scenario, you don't see any daily (scheduled) backups of the file. That's because assuming you back it up manually (SELECTIVE backup) every time you change it, when the scheduled incremental backups run, it will see that the file has not changed since the last time you backed it up, so it won't be backed up redundantly. The VERDELETED=NOLIMIT means that once you delete the file, then the next time your daily backup runs, it will detect that the file is gone from the file system and mark the latest version as inactive. From that time, you can still restore to an older state from a backup version taken within the last 90 days, and the latest backup version will be kept for 180 days (from the time it was inactivated), giving you *some* kind of fallback in case someone decides after, say, 120 days, that they want the file back. Of course, at that time you would only be able to get them the latest backup version because all the others would have expired, but at least its something. By the way, the RETONLY doesn't have to be more than 90 days, if you want to impose a strict 90-day policy, then you can set RETONLY to 90 days as well. But RETONLY just provides a means of giving your users one last "out" to restore a deleted file. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Patrick Boutilier [EMAIL PROTECTED]@VM.MARIST.EDU on 03/30/2001 11:41:32 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Confusion with retention values. Makes sense. I did a query on the BACKUPS table and that shows the deactivate date. Too bad the clients didn't show the deactivate date. :-) I always assumed that Retain Extra Versions = 90 meant that anything that was backed up 90 days ago would be deleted, not 90 days from the deactivation date. This way you might be able to restore something from more than 90 days ago. Makes it harder to tell your clients exactly how back you can restore from. :-) STATE LL_NAME BACKUP_DATEDEACTIVATE_DATE -- -- -- ACTIVE_VERSION 36E54BF0.000 2001-03-20 INACTIVE_VERSION 36E54BF0.000 2000-12-08 2001-02-17 INACTIVE_VERSION 36E54BF0.000 2001-02-17 2001-03-20 Quoting Andy Raibeck [EMAIL PROTECTED]: By "keep versions for 90 days", I assume you mean the RETEXTRA setting. I think the confusion may come from thinking that this setting indicates how long to keep backup versions from the time they are created (?). This is not the case; rather, RETEXTRA indicates how long to keep the backup version after it goes in inactive. So
Re: Comparison of Backup Products
I'm not sure from where this information comes, but it is news to me. I can't say I know for sure about newer TSA releases since I haven't worked closely with the NetWare platform for a long time. But in the past, I worked on many problems with NetWare that involved the TSA or SMDR, and there was never a case where Novell had to bring out a new set of modules to fix or work around one of our bugs. Rather I'd say they had to bring out a new TSA module in order to fix problems *exposed* by TSM/ADSM. Like I said, it's been a long time since I worked with NetWare, so I could be wrong... but I personally know the guys working on the NetWare client, and I'd be hard-pressed to believe that they would try to pawn off one of our bugs on another vendor... not to mention that I would be hard-pressed to believe that Novell would actually change their product to fix one of our bugs. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Mark, I would say not actually. The fact that the problems centralized around the TSA modules in many cases, was based on the fact that TSM/ADSM versions changed, not the TSA modules. In every case, Netware was the one to bring out a new TSA module (including some that weren't in SP's) in order to fix TSM/ADSM created problems. I personaly had this issue with 2 seperate client upgrades from IBM, upgrades which happened in a "same environment" Netware environment. Meaning that there were absolutely no changes to the Netware systems, but there were changes to the clients. [snip]
Re: Daylight Savings Fix for Windows NT Clients
Before anyone shakes their fists and yells, "not AGAIN!!!", please understand that this is really just a *reminder*, referring to the *same* problem as was discovered last October. If you installed the fixing patch for this last October, you are OK for the change to DST. The notice is not as clear as it could be, so in order to avoid further confusion, I have asked that it be changed to something like this: = REMINDER Daylight Savings Time Fix for Windows NT/2000 Last October a problem was discovered in the TSM client for Windows NT and 2000 that caused the first incremental backup following a change between Standard Time and Daylight Savings Time to back up all files. (Thereafter incremental backups would run normally, at least until the next change between Standard Time and Daylight Savings Time.) This problem is documented in APAR IC28544. It affects data only on NTFS volumes, so Windows 95 and 98 are not affected; Windows NT and 2000 FAT-formatted volumes are not affected. The problem affects TSM Windows client versions 3.7.2.0 - 3.7.2.16, and 4.1.0.0 - 4.1.1.0. The problem was fixed in TSM Windows client versions 3.7.2.17 - 3.7.2.19, 4.1.1.16, and 4.1.2.0. For TSM Windows clients running on the Alpha processor, the problem is fixed in version 3.7.2.19. If you have already applied a fixing version from last October (or later), then you do not need to do anything for the upcoming change to Daylight Savings Time. If you are currently running a version of the client that does not have the fix for this problem, then it is recommended that you apply one of the following patches: For the TSM version 4.1 client, patch 4.1.2.12 For the TSM version 3.7 client, patch 3.7.2.19 (both x86 and Alpha) = Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Daylight Savings Fix for Windows NT Clients The Tivoli Storage Manager Products Technical Support page (http://www.tivoli.com/support/storage_mgr/adsercli.htm) has the following notice: NOTICE Daylight Savings Fix for Windows NT Before April 1st, Tivoli Storage Manager 4.1 and 3.7 client users for Windows NT must apply the following fixtests: For the TSM V 4.1 client, fixtest 4.1.2.12 for Windows NT/2000 For the TSM V 3.7 client, fixtest 3.7.2.19 for Windows NT/2000
Re: Daylight Savings Fix for Windows NT Clients
Hi Tim, Actually I was referring only to the DST problem (IC28544), per the subject and content of the original post to which I responded. IC28969 has nothing to do with the DST problem; it is just another APAR fix that was included in the 4.1.1.16 client. Although I was not involved in fixing that problem, it is my understanding that it has been in the code for quite some time, and in fact is not limited to just Windows. If you are fairly current on your maintenance and are not experiencing the problem, then I wouldn't worry about it; you're fine. As far as DST goes, as long as you are one of the versions that fixes it (listed in my first post on this subject, text included below), you do not need to rush into installing new clients just for DST. Best regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Williams, Tim" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/28/2001 12:14:44 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Daylight Savings Fix for Windows NT Clients Andy/all, I read your update, I read apar ic28969 and ic28544. Are you saying that ic28544: "AUTOMATICALLY ADJUST CLOCK FOR DAYLIGHT SAVINGS CHANGES" CAUSES INCREMENTAL TO DO FULL BACKUP OF NTFS FILES and ic 28969 TSM CLIENT SHOWS SIGNS OF MEMORY LEAK DURING SCHEDULED BACKUPS. are referring to the *same* problem as was discovered last October. ic28969 (memory leak) has been seen or "This problem was witnessed on the 4.1.1.16 client for NT, but can affect all platforms. It may also affect earlier client levels." - quote from the apar.. This would contridict your update proposal (that...4.1.1.16 is ok). I opened up an etr/pmr asking to narrow the client platforms and levels. Shops with large TSM client installations can't respond quickly to upgrading TSM client codeon a dime... FYI Thanks Tim Andy Raibeck [EMAIL PROTECTED] 03/28/2001 12:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]@SMTP@Exchange To: [EMAIL PROTECTED]@SMTP@Exchange cc: Subject:Re: Daylight Savings Fix for Windows NT Clients Before anyone shakes their fists and yells, "not AGAIN!!!", please understand that this is really just a *reminder*, referring to the *same* problem as was discovered last October. If you installed the fixing patch for this last October, you are OK for the change to DST. The notice is not as clear as it could be, so in order to avoid further confusion, I have asked that it be changed to something like this: = REMINDER Daylight Savings Time Fix for Windows NT/2000 Last October a problem was discovered in the TSM client for Windows NT and 2000 that caused the first incremental backup following a change between Standard Time and Daylight Savings Time to back up all files. (Thereafter incremental backups would run normally, at least until the next change between Standard Time and Daylight Savings Time.) This problem is documented in APAR IC28544. It affects data only on NTFS volumes, so Windows 95 and 98 are not affected; Windows NT and 2000 FAT-formatted volumes are not affected. The problem affects TSM Windows client versions 3.7.2.0 - 3.7.2.16, and 4.1.0.0 - 4.1.1.0. The problem was fixed in TSM Windows client versions 3.7.2.17 - 3.7.2.19, 4.1.1.16, and 4.1.2.0. For TSM Windows clients running on the Alpha processor, the problem is fixed in version 3.7.2.19. If you have already applied a fixing version from last October (or later), then you do not need to do anything for the upcoming change to Daylight Savings Time. If you are currently running a version of the client that does not have the fix for this problem, then it is recommended that you apply one of the following patches: For the TSM version 4.1 client, patch 4.1.2.12 For the TSM version 3.7 client, patch 3.7.2.19 (both x86 and Alpha) ========= Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "
Re: Daylight Savings Fix for Windows NT Clients
Hi Tim,
Well, therein lies the confusion, and why I responded to that post! I
wanted to make it clear that it was not a new problem.
The IC28969 problem was discovered by someone using the 4.1.1.16, and that
is why it was originally reported that way. The "live" APAR abstract has
since been updated to say, "TSM CLIENT SHOWS SIGNS OF MEMORY LEAK DURING
SCHEDULED BACKUPS."
The leak has been fixed in 4.1.2.12. If you are already at 4.1.1.16 and
aren't seeing the problem, I wouldn't worry about it, at least for the
purposes of getting past the DST switch.
Best regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
"Williams, Tim" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/28/2001
01:10:28 PM
Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Daylight Savings Fix for Windows NT Clients
Andy/all.
The original post, I believe tht was referencing a "new" DST
problem, not a reminder
to the old DST problem.
see ftp read1stc info on ic28969...that has (daylight savings
fixtest) noted in the
readme...maybe the readme is wrong because pulling up the
apar...yes, it
doesn't reference DST...
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance
/client/v4r1/Windows/i386/LATEST/IP22151_12_read1stc.txt
* IC28969 TSM CLIENT 4.1.1.16 (DAYLIGHT SAVINGS FIXTEST) FOR
*
* NT/2000 SHOWS SIGNS OF A MEMORY LEAK DURING
*
* SCHEDULED INCREMENTAL BACKUPS.
Thanks for the quick response.
Tim
Andy Raibeck [EMAIL PROTECTED]
03/28/2001 01:36 PM
Please respond to "ADSM: Dist Stor Manager"
[EMAIL PROTECTED]@SMTP@Exchange
To: [EMAIL PROTECTED]@SMTP@Exchange
cc:
Subject:Re: Daylight Savings Fix for Windows NT Clients
Hi Tim,
Actually I was referring only to the DST problem (IC28544), per the
subject
and content of the original post to which I responded. IC28969 has
nothing
to do with the DST problem; it is just another APAR fix that was
included
in the 4.1.1.16 client. Although I was not involved in fixing that
problem,
it is my understanding that it has been in the code for quite some
time,
and in fact is not limited to just Windows. If you are fairly
current on
your maintenance and are not experiencing the problem, then I
wouldn't
worry about it; you're fine.
As far as DST goes, as long as you are one of the versions that
fixes it
(listed in my first post on this subject, text included below), you
do not
need to rush into installing new clients just for DST.
Best regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
"Williams, Tim" [EMAIL PROTECTED]@VM.MARIST.EDU on
03/28/2001
12:14:44 PM
Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Daylight Savings Fix for Windows NT Clients
Andy/all, I read your update, I read apar ic28969 and
ic28544.
Are you saying that
ic28544: "AUTOMATICALLY ADJUST CLOCK FOR DAYLIGHT SAVINGS
CHANGES"
CAUSES INCREMENTAL TO DO FULL BACKUP OF NTFS FILES
and
ic 28969 TSM CLIENT SHOWS SIGNS OF MEMORY LEAK DURING
SCHEDULED
BACKUPS.
are referring to the *same* problem as was discovered last
October.
ic28969 (memory leak) has been seen or "This problem was
witnessed
on the 4.1.1.16 client for NT, but
can affect all platforms. It may also affect earlier
client
levels." - quote from the apar..
This would contridict your update proposal (that...4.1.1.16
is
ok).
I opened up an etr/pmr asking to narrow the client
platforms
and
levels. Shops with large TSM client
installations can't respond quickly to upgrading TSM client
codeon a dime...
FYI Thanks Tim
Andy Raibeck [EMAIL PROTECTED]
03/28/2001 12:32 PM
Please respond to "ADSM: Dist Stor Manager"
[EMAIL PROTECTED]@SMTP@Exchange
To: [EMAIL PROTECTED]@SMTP@Exchange
cc:
Re: 4.1.2.12 Client Reporting Erroneous Elapsed Processing Time
Hi Anne, This is a known defect, and is documented in APAR IC29212. I don't have an ETA for an available fix, though. So sorry for the "fuzzy math". Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Short, Anne" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/26/2001 08:35:11 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: 4.1.2.12 Client Reporting Erroneous Elapsed Processing Time Anybody else notice this? Since the upgrade to TSM Client to version 4.1.2.12 on our NT 4.0 nodes, the elapsed time for our backups is getting reported wrong. The particular node I've documented below starts its backup at 8:00 pm (and yes, I've verified it's starting on time). You'll notice, that starting on 03/22/2001, the "Elapsed processing time" is getting reported to be 3 hours or less even though the backup isn't finishing until well past 2:00 am. Perhaps its only reporting the elapsed processing time for the last session that starts, as we let this client run multiple sessions. 03/22/2001 03:12:19 ANE4964I (Session: 7873, Node: GBNF01) Elapsed processing time: 00:03:33 03/23/2001 03:14:04 ANE4964I (Session: 9582, Node: GBNF01) Elapsed processing time: 00:00:44 03/24/2001 04:07:38 ANE4964I (Session: 840, Node: GBNF01) Elapsed processing time: 00:02:11 03/25/2001 02:20:52 ANE4964I (Session: 1753, Node: GBNF01) Elapsed processing time: 00:03:38 03/26/2001 02:26:19 ANE4964I (Session: 3168, Node: GBNF01) Elapsed processing time: 00:00:57 Before the upgrade (version 3.7.2), the elapsed processing time was getting reported correctly: 03/14/2001 03:16:18 ANE4964I (Session: 329, Node: GBNF01) Elapsed processing time: 07:15:18 03/16/2001 02:36:29 ANE4964I (Session: 361, Node: GBNF01) Elapsed processing time: 06:35:25 Considering we get measured on getting all our backups completed within an 8 hour window, I shouldn't complain as this new math will certainly make us look good!! :-) But, I guess I'll report it as a bug to Tivoli. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Patch 3.7.2.19 now available for Alpha Windows client
The 3.7.2.19 patch for alpha processors is now available on our ftp site. Here is where you will find it: ftp site: ftp.software.ibm.com directory: storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/alpha The file names all begin with IP21934_19. Be sure to review the IP21934_19_README.FTP for download and setup instructions, and IP21934_19_README.1ST for general info about the patch. Note: if you are already familiar with the 3.7.2.19 (IP21933_19) patch for the x86, it's the same material. This patch is functionally equivalent to the 3.7.2.19 code for x86 processors, and thus includes the fix for the Daylight Savings Time problem (among others). Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked."
Re: TSM 3.1 Server with IP21933?
I am not aware of any problems specific to running 3.7 clients with 3.1 servers. However, I strongly recommend that if you install IP21933 (3.7.2), you use the latest patch for that version, 3.7.2.19 (IP21933_19). It is located on the ftp site ftp.software.ibm.com in the storage/tivoli-storage-management/patches/client directory structure (you should be able to navigate to the fix from there). Note that support for Windows 2000 system objects requires a 3.7.3 (or higher) TSM server, so you will only be able to back up normal files with your current server; you will not be able to back up the Windows 2000 system objects. Please review the README.1ST file that accompanies the 3.7.2.19 fix for further information. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Fletcher, Leland D." [EMAIL PROTECTED]@VM.MARIST.EDU on 03/21/2001 07:38:27 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TSM 3.1 Server with IP21933? We are currently using TSM 3.1 server and will be for the next 2 months. We also have installed several Windows 2000 Advanced Server machines in a clustered environment. The backups are performing very slow(12 hours for 10G and 415,000 total files considered). I have information that the current client(IP21855) we are using knows nothing about Windows 2000 and clustering. The bottleneck is definitely the speed in which the client is reading and testing files for backup. I have tested a Windows 2000 machine with the IP21933 client and it seemed to work OK. Since TSM 3.1 is out of support and the last supported client for TSM 3.1 was IP21855 I have some reservations about installing IP21933 on our Windows 2000 machines. The question Does anyone know of any problems with running the IP21933 client and TSM 3.1? Has anyone had any experience with this configuration? Thanks in advance for any assistance! Lee Fletcher Network Project Integrator AmerenUE Callaway Plant [EMAIL PROTECTED]
Re: ADSM 3.1.0.3 to 3.7.2.19
I can't think of any reason to install 3.1.0.8 first. You should be able to jump right to 3.7.2.19. Just be sure to review the accompanying README.1ST file first. Probably the most obvious thing is starting with ADSM 3.1.0.5, the client now uses the UNC name of your drives for the filespace names instead of the volume labels. This (and other issues) are discussed in the README.1ST file. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Maria Ragan [EMAIL PROTECTED]@VM.MARIST.EDU on 03/20/2001 05:01:29 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: ADSM 3.1.0.3 to 3.7.2.19 Server: AIX 4.3.2 TSM 3.7.2Clients: NT 4 ADSM 3.1.03 Any reason to upgrade our NT clients currently at ADSM v 3.1.03 to ADSM v 3.1.08 before upgrading to 3.7.2.19 as Tivoli support suggested? Thanks, Maria
Re: Archive (inspected) vs Backup (inspected)
Actually, this is not entirely true. * and *.* are NOT exactly the same.
*.* means any file name with the '.' character anywhere in the name.
* means any file name.
So if you have this:
exclude c:\Mydir\*.*
And you have these files in C:\Mydir:
abc.txt
123.txt
myfile
Then myfile will be backed up, but abc.txt and 123.txt will be excluded.
If you want to exclude *all* files (which is usually the intent), you need
to specify this:
exclude c:\Mydir\*
Regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
Herv CHIBOIS [EMAIL PROTECTED]@VM.MARIST.EDU on 03/19/2001 02:59:38
PM
Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Archive (inspected) vs Backup (inspected)
Hello there
some hints...
re-read your REGEXP definition, you do NOT need to put many lines
* and *.* are EXACTLY the same for *SM
try to use exclude.dir instead of /.../, *SM won't store directory
definitions.
rv
- Original Message -
From: "Gerrit van Zyl" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 19, 2001 12:13 PM
Subject: Re: Archive (inspected) vs Backup (inspected)
Steffan,
No, not at all. It is the standard exclude statements:
Exclude "*:\macintosh volume\*"
Exclude "*:\macintosh volume\*.*"
Exclude "*:\macintosh volume\...\*"
Exclude "*:\macintosh volume\...\*.*"
Exclude "*:\microsoft uam volume\*"
Exclude "*:\microsoft uam volume\*.*"
Exclude "*:\microsoft uam volume\...\*"
Exclude "*:\microsoft uam volume\...\*.*"
Exclude "*:\...\EA DATA. SF"
Exclude *:\...\pagefile.sys
Exclude *:\IBMBIO.COM
Exclude *:\IBMDOS.COM
Exclude *:\MSDOS.SYS
Exclude *:\IO.SYS
Exclude *:\...\SYSTEM32\CONFIG\*.*
Exclude *:\...\SYSTEM32\CONFIG\...\*
Regards
Gerrit
arhoads wrote:
Gerrit,
Does your include-exclude file exclude ~ 50,000 files?
Steffan
Gerrit van Zyl wrote:
Steffan,
Why would ADSM skip 5 files for archiving. Their is about 20
files that
gives errors (open), the rest not.
number of objects inspected: 461,739
number of objects archived: 411,368
The schedule is to archive c: d: e:
Thanks and regards
Gerrit van Zyl
arhoads wrote:
Gerrit,
Yes. Archive is not using the Include-Exclude list.
Steffan
Gerrit van Zyl wrote:
Hi all TSM'ers,
TSM Client 3.1.0.8 on NT
TSM Server 3.1.2.58 on AIX
I have the following scenario and hope someone can explain this
to
me.
When archiving we get the following:
03/11/2001 03:54:57 ANE4952I (Session: 7758, Node: NTSRV01)
Total
number of objects inspected: 461,739
03/11/2001 03:54:57 ANE4953I (Session: 7758, Node: NTSRV01)
Total
number of objects archived: 411,368
When we do a incremental backup we get the following:
03/12/2001 22:57:23 ANE4952I (Session: 8193, Node: NTSRV01)
Total
number of objects inspected: 410,653
03/12/2001 22:57:23 ANE4954I (Session: 8193, Node: NTSRV01)
Total
number of objects backed up:3,414
Why is there suce a huge difference between objects inspected in
the two
cases (5 objects)? The files were not deleted!! This is the
same
everytime.
Is archiving inspecting files differently than incremental
backup?
Thanks and regards.
Gerrit van Zyl
IT Consultant
Faritec (Pty) Ltd
--
Gerrit van Zyl
IT Consultant
Faritec (Pty) Ltd
"This message may contain information which is confidential, private or
privileged in nature. If you are not the intended recipient, you may not
peruse, use, disseminate, distribute or copy this message or file which
is attached to this message. If you have received this message in error,
please notify the sender immediately by e-mail, facsimile or telephone
and thereafter return and/or destroy the original message.
Any views of this communication are those of the sender except where the
sender specifically states them to be those of Faritec (Proprietary)
Limited ("Faritec") and/or Midrange Distribution Services (Pty) Ltd.
Please note that the recipient must scan this e-mail and any attached
files for viruses and the like. While we do everything possible to
protect information from viruses, Faritec accepts no liability of
whatever nature for any loss, liability, damage or expense resulting
directly or indirectly from the access and/or downloading of any files
which are attached to this e-mail message."
Re: Windows NT/2000 Daylight Savings Time Problem
If you are not on a version of the client that includes the fix for IC28544 (the DST problem), then you will experience the problem. The version numbers I recommend all inlcude that fix, plus a number of other fixes as well. You can check the README files for those versions to see what is fixed in them. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/16/2001 09:23:40 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Windows NT/2000 Daylight Savings Time Problem What are the implications of not having these versions? Are they the same as back in October 2000 or is there some diference? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 10:49AM Have we reverted back to the last Sunday in April? I know that at one time, the change to DST used to occur on the last Sunday in April, but it was changed to the first Sunday in April back in the 1980's (at least in the US). If you are running the 3.7.x client, I recommend using 3.7.2.19. If you are running the 4.1.1.x client, you need to use IP22088_16 (there is no IP22088_17 as far as I know), which corresponds to version 4.1.1.16. If you are running the 4.1.2.x client, you need to use IP22151_12, which corresponds to version 4.1.2.12. We also verified that the DST fix stayed fixed in this level. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 03/16/2001 08:17:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Windows NT/2000 Daylight Savings Time Problem I believe we go to DST the last Sunday in April. I hope we get clear on this on this change and don't have a notice 3 days before telling us there is a problem. NO way I can update 100 clients with that notice. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/16/01 04:38AM Hello did I had to install the fix IP22088_17 on the NT/2000 servers, before next week'end, where we are going to summertime??? Sincerely, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 Albertslund E-mail: [EMAIL PROTECTED] Denmark -- Fra: Andy Raibeck[SMTP:[EMAIL PROTECTED]] Svar til: ADSM: Dist Stor Manager Sendt:28. oktober 2000 08:44 Til: [EMAIL PROTECTED] Emne: Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time Problem Hello, The fixtests for this problem are now available for download from the FTP site. Please note that the original note I sent out earlier erroneously stated that the version 4.1 fixtest was 4.1.1.17 and the file names to download begin wtih IP22088_17. In fact, the fixtest version is 4.1.1.16 and the file names begin with IP22088_16. The 3.7 fixtest was reported correctly as being version 3.7.2.17 and the file names beginning with IP21933_17. I have included the corrected version of the original note below for your reference. The files are located on our anonymous ftp site, ftp.software.ibm.com: Version 4.1.1.16: Directory /storage/tivoli-storage-management/patches/client/v4r1/Windows/v411/single Please review the IP22088_16_readme.ftp file for information on downloading and installing the fixtest. Version 3.7.2.17: Directory /storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386/s ingle Please review the IP21933_17_readme.ftp file for information on downloading and installing the fixtest. Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the
Re: Windows NT/2000 Daylight Savings Time Problem
Hi Nancy, There is no 4.1.0.x fix for this; you will need to go to 4.1.1.16 or 4.1.2.12. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Nancy Reeves [EMAIL PROTECTED]@VM.MARIST.EDU on 03/16/2001 02:30:16 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Windows NT/2000 Daylight Savings Time Problem Andy, What version of 4.1.0.x for Windows NT has the fix? Or should I upgrade to 4.1.1.16 or 4.1.2.12? I only have a couple dozen NT/2000 clients. Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860 If you are not on a version of the client that includes the fix for IC28544 (the DST problem), then you will experience the problem. The version numbers I recommend all inlcude that fix, plus a number of other fixes as well. You can check the README files for those versions to see what is fixed in them. Regards, Andy --- If you are running the 3.7.x client, I recommend using 3.7.2.19. If you are running the 4.1.1.x client, you need to use IP22088_16 (there is no IP22088_17 as far as I know), which corresponds to version 4.1.1.16. If you are running the 4.1.2.x client, you need to use IP22151_12, which corresponds to version 4.1.2.12. We also verified that the DST fix stayed fixed in this level. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the switch between Daylight Savings Time (DST) and Standard Time (STD) has just been discovered for the Windows TSM clients. BACKGROUND When Windows NT and 2000 systems automatically switch between DST and STD, the time attributes for files stored on NTFS file systems will be shifted by one hour. This is because NTFS displays time information as an offset from Greenwich Mean Time (GMT). Thus when the DST change is made, the offset from GMT is changed, causing the timestamps on your NTFS files to also change. (Note: Time information for Event Viewer events is affected in the same manner, but that is not pertinent to this discussion.) Further information on this subject is available in the Microsoft Knowledge Base, item Q129574. If you point your web browser to Microsoft's MSDN site, http://msdn.microsoft.com, and search on "Q129574" (without the quotes), you will find the information. THE PROBLEM When the system automatically adjusts between DST and STD, the TSM 3.7.2 (and higher) clients will see that the modification time has changed for all files on NTFS systems, and will proceed to back everything up accordingly, even if the file has not really changed. This will occur only once after the time change, and thereafter incremental backups will proceed as normal. However, this will almost certainly affect the amount of data backed up by each client, effectively causing a full backup on all NTFS file systems. This could have a large impact on network and TSM server resources. The following bullets summarize the conditions under which this problem can occur: - TSM client is running on Windows NT 4.0 or Windows 2000. TSM clients running on Windows 9x-based operating systems (Windows 95, 98) are not affected. - The TSM client level is 3.7.2.x or higher (including all 4.1.x levels). TSM client levels below 3.7.2.x are not affected, as the problem was introduced in the 3.7.2.x code. - The file systems are formatted for NTFS. FAT and FAT32 file systems are unaffected by this problem. - The operating system's time zone settings are configured to automatically adjust for DST. You can check this by right-clicking on the Windows task bar and selecting the "Adjust Date/Time" item in the pop-up menu. (Alternatively, you can double-click on the clock display in the task bar.) Either of these actions will bring up the "Date/Time Properties" dialog. Click on the "Time Zone" tab and you should see the "Automatically adjust clock for daylight saving changes" checkbox. If the box is checked (the default installation setting), then your system is configured to automatically adjust for DST. Users in regions that do not observe DST (such as Arizona) will be unaffected by this problem, provided that the system's time zone settings are similarly configured to not observe DST. WHAT IBM/TIVOLI IS DOING ABOUT THIS Here are the actions that we are taking or have taken to date: 1) We have opened a severity 1 APAR, IC28544, to address this problem. 2) We have designed and built fixtests for the 3.7.2 and 4.1.1 Windows clients. The fixtest vers
Re: Point-In-Time Restore
Allen, What causes a directory to appear as changed is operating system and/or file system dependent. We check for changed directories the same as we do for files. Modification date may be a very common indicator of a changed directory. For example, by moving a file in or out of a directory on my Windows 2000 workstation will cause that directory's modification date to be changed. Hence it will be eligible for incremental backup. Yes, the web interface would have the same issues as the native GUI with regard to PIT restores. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Allen Barth [EMAIL PROTECTED]@VM.MARIST.EDU on 03/13/2001 11:32:51 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Point-In-Time Restore Andy- You make mention of "Depending on how often your directories change, this could potentially impact the size of our TSM database." What is the definition of when a directory changes. We've got some dirs that haven't changed since inception with respect to permissions, access right, ACL's, etc. Yet, they get backed up daily with incrementals. As such we are in the midst of a PIT restore issue ourselves. Moreover, taking the position that the GUI is DESIGNED to be crippled is most disheartening. Is this cripple feature also in the web interface? If it is, it nulls out ANY potential benefit of such an interface because if I have to use the command line to make sure I can do my job, then I'm most likely already sitting in front of the machine in question. This all reminds me of a brand of VCR that one aspiring salesperson tried to sell me, touting all the neat things I could do with the remote. When I asked for a demo of how to program recording the machine from its' front panel, I was informed it couldn't be done. I shopped for another brand. You see it's not that I would program from the front panel, it's that I could if I chose to. The functionality was available in both interfaces. Sometimes the obvious is to plain to see. Andy Raibeck Andrew_Raibeck@TTo: [EMAIL PROTECTED] IVOLI.COM cc: Sent by: "ADSM: Subject: Re: Point-In-Time Restore Dist Stor Manager" [EMAIL PROTECTED] .EDU 03/07/01 09:58 AM Please respond to "ADSM: Dist Stor Manager" For those of you who remember ADSM Versions 2 or earlier, our backup-archive GUI used to obtain a list of *all* backup versions before displaying the restore tree. Because the list of all backup versions can grow extremely large (i.e. millions of files), this presented two problem areas: memory shortages on the client machine (to retain the list of files in memory) and performance (because it takes a long time to build the list). Starting with Version 3, we took a different approach to how we get file backup information. Rather than try to obtain a list of all backup versions initially, we only obtain a list of the objects that you can immediately see on the screen. For example, when you crack open (click on the + sign) the "File level" in the restore tree, we just show the available filespaces, so that is the only information we get from the server. When you click on one of the file spaces, we get a list of files that are in the root directory of that filespace, which is then displayed on the right-hand side of the GUI. When you crack open the filespace, we get a list of available directories directly beneath that filespace. When you click on a directory, we get the list of files immediately under that directory. And so on and so forth. Because we are only getting lists of files for what you can see on the screen, the list is much smaller, so the GUI performance is vastly improved. The problem you are seeing with PIT restores via the GUI is in order to see the files, you first need to be able to see the directories (so you can click on them to see the files or crack them open to view their subdirectories). But if there are no directories that were backed up prior to your PIT specification, then there is no directory that can be displayed. Thus if there is no displayed directory, there is nothing for you to click on or crack open. The command line interface does not rely on the ability to display directories before it can display its files and subdirectories, so this is why it does not have the problem. Directories are bound to the management class (within the policy domain) that has the highest "Retain only version" (RETONLY) se
Re: Point-In-Time Restore
Hi Bernhard, A policy domain may have many management classes, each with different file retention criteria. Within a given directory, it is possible to have some files bound to one management class, other files bound to another management class, still other files bound to a third management class, etc. Maybe one class says to keep files for 14 days, another says to keep files for 180 days, and the third management class says to keep files for 365 days. Also, you may add files to the directory over time, and set your INCLUDE processing to bind them to different management classes. Directories are bound to the management class with the longest RETONLY setting so that, after you delete the directory (and its files and subdirectories) from the client machine, you can at least recover the most recent backup copy and the directory in which that file resided. TSM has no way of knowing that you intend to keep *all* files on a particular machine, now and forever, for only 14 days, so it can not decide to use a management class for directories with a smaller RETONLY setting. But if *you* know you intend to keep all files on a particular machine for only 14 days (like in the example you gave), you can do a couple of things: 1) Use the DIRMC option to bind directories to the same management class that your files use. 2) Create a new policy domain to which the machine's node will belong that has only the one management class with the 14-day criterion. Regarding your questions about what is in a directory and what is stored for a directory: in older file systems like like the DOS FAT file system, directories were indeed nothing more than just a mechanism for organizing how files are stored withing the file system. But for other file systems like on UNIX and NetWare, and newer Windows file systems like NTFS, directories now have attributes (like security, ownership, etc.) associated with them that files stored withing those directories can inherit. So it is important that TSM be able to back up and restore the attributes for the directories as well. In answer to some of your specific questions that may not have been covered above: Q: What can I do with the directory if the files belonging to it are expired? A: Techincally you could restore the directory itself, although that would most likely be of little practical use. But other than that, there is nothing more you can really do with it. Q: What is the state or content of the directory restored PIT to day 1 (from the example below)? A: Whatever the state or content was at the time it was backed up. (I am not trying to be "flip" here, but I am not sure what the point of this question is.) Q: Is it possible to restore MyFile.txt to the version of day 1 if the directory backup belonging to it is expired? A: Yes, with the exception that you can not restore that version with the PIT restore feature from the GUI. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Bernhard Unold [EMAIL PROTECTED]@VM.MARIST.EDU on 03/08/2001 02:17:33 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Point-In-Time Restore Hello, Andy I understand your arguments, but want to know the benefits of the method to store the directory not in the same manner as the files. For Example from a certain computer we do a archive, we want to keep for 14 days. But the directories are kept for 365 days. So storage is wasted on tape and in the db. For special purpose we have a mgmtclass without any limits. Now some clients store their directories there at incremental backup. No good idea!! What is stored for a directory entry? What can i do with the directory, if the files belonging to it are expired? In your example: What is the state or content of the directory restored PIT to day 1? Is it possible to restore Myfile to the version of day 1 if the directory backup belonging to it is expired? My idea is to store the directories together with the files. This would solve a lot of problems. Best regard Bernhard Unold Andy Raibeck schrieb: For those of you who remember ADSM Versions 2 or earlier, our backup-archive GUI used to obtain a list of *all* backup versions before displaying the restore tree. Because the list of all backup versions can grow extremely large (i.e. millions of files), this presented two problem areas: memory shortages on the client machine (to retain the list of files in memory) and performance (because it takes a long time to build the list). Starting with Version 3, we took a different approach to how we get file backup information. Rather than try to obtain a list of all backup versions initially, we only obtain a list of the objects that you can immediately see on the screen.
Re: Point-In-Time Restore
For those of you who remember ADSM Versions 2 or earlier, our backup-archive GUI used to obtain a list of *all* backup versions before displaying the restore tree. Because the list of all backup versions can grow extremely large (i.e. millions of files), this presented two problem areas: memory shortages on the client machine (to retain the list of files in memory) and performance (because it takes a long time to build the list). Starting with Version 3, we took a different approach to how we get file backup information. Rather than try to obtain a list of all backup versions initially, we only obtain a list of the objects that you can immediately see on the screen. For example, when you crack open (click on the + sign) the "File level" in the restore tree, we just show the available filespaces, so that is the only information we get from the server. When you click on one of the file spaces, we get a list of files that are in the root directory of that filespace, which is then displayed on the right-hand side of the GUI. When you crack open the filespace, we get a list of available directories directly beneath that filespace. When you click on a directory, we get the list of files immediately under that directory. And so on and so forth. Because we are only getting lists of files for what you can see on the screen, the list is much smaller, so the GUI performance is vastly improved. The problem you are seeing with PIT restores via the GUI is in order to see the files, you first need to be able to see the directories (so you can click on them to see the files or crack them open to view their subdirectories). But if there are no directories that were backed up prior to your PIT specification, then there is no directory that can be displayed. Thus if there is no displayed directory, there is nothing for you to click on or crack open. The command line interface does not rely on the ability to display directories before it can display its files and subdirectories, so this is why it does not have the problem. Directories are bound to the management class (within the policy domain) that has the highest "Retain only version" (RETONLY) setting, without regard to the number of versions that are kept. If two management classes have the same RETONLY setting, then you can not predict which class will be used. If the management class with the largest RETONLY setting maintains only 1 version, this will still be the class to which directories are bound. Call this management class CLASS1 On the other hand, you might have files that are bound to another management class, say, CLASS2, with a lower RETONLY setting but maintains, say, 10 versions if the file exists (number of versions when file is deleted is not pertinent here). So here is a scenario: Day 1: File C:\MyDir\MyFile.txt is backed up. MyDir is bound to CLASS1 and MyFile.txt is bound to CLASS2. Day2: File C:\MyDir\MyFile.txt is changed. The MyDir directory is also changed. When the backup runs, MyDir will be backed up. Because only 1 version is kept, the version that was created on Day 1 is deleted. MyFile.txt is also backed up and bound to CLASS2. There are now 2 versions of MyFile.txt. Now you need to do a PIT restore back to Day 1. However, since there is only one backup version of MyDir, created on Day 2, it will not be displayed in the GUI when you PIT criteria specifies Day 1. The key for PIT restores from the GUI, then, is to ensure that each directory has a backup version that is at least as old as the oldest file or subdirectory contained within that directory. I don't think there is any great way to ensure that you can *always* do a PIT restore from the GUI unless you have a management class for directories that basically keeps all versions of directory backups forever (NOLIMIT). Depending on how often your directories change, this could potentially impact the size of our TSM database. The best compromise would be to establish a term of service with your users that states how far back you will support PIT restores via the GUI. Then you can create a managment class for your directories with VEREXISTS=NOLIMIT, VERDELETED=NOLIMIT, and RETEXTRA=ndays, where 'ndays' is the number of days to which you will guarantee PIT restores via the GUI. For example, if you want to be able to go back up to 30 days, then set RETEXTRA=30. Beyond 30 days, you will need to use the CLI. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Richard L. Rhodes" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/07/2001 12:36:50 AM Please respond to [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Point-In-Time Restore This brings up lots of questions: 1) How do you "keep enough directories" to enable PIT for the gui? 2) Ho
Re: Win2000 system objects
I agree that, at the very least, this issue should be documented, if not fixed. APAR IC29793 has been opened to address this shortcoming. I can not say how or when it will be closed at this time. APAR abstract: QUERY FILESPACE SYSTEM OBJECT LAST BACKUP START DATE, DAYS SINCE LAST BACKUP STARTED, ETC. NOT REPORTED IN STATISTICS. APAR text: QUERY FILESPACE FORMAT=DETAILED for the SYSTEM OBJECT filespace does not report any statistics for Last Backup Start Date/Time, Days Since Last Backup Started, Last Backup Completion Date/Time or Days Since Last Backup Completed. Sample output: ANS8000I Server command: 'q fi storman 'SYSTEM OBJECT' f=d' Node Name: STORMAN Filespace Name: SYSTEM OBJECT Platform: WinNT Filespace Type: NTFS Capacity (MB): 0.0 Pct Util: 0.0 Last Backup Start Date/Time: Days Since Last Backup Started: Last Backup Completion Date/Time: Days Since Last Backup Completed: These statistics should be filled in; if they can not be filled in for technical reasons, then at the very least this restriction should be documented. Also, the Capacity and Pct Util statistics are misleading. While it is difficult to attach any meaning to Capacity for the SYSTEM OBJECT (because it isn't a file system), perhaps Capacity could be set to the actual number of MB backed up, and Pct Util set to 100? Either that, or it should be documented that these values will always display as 0. LOCAL FIX: Check dsmsched.log on the client machine to verify that the SYSTEM OBJECT was backed up successfully. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Short, Anne" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/05/2001 09:21:34 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Win2000 system objects I opened a PMR with Tivoli for this very same problem. I was told "working as designed". If you peruse the dsmsched.log, you will see that all the different pieces of the system object are getting successfully backed up. I honestly can't remember the reasoning I was given by Tivoli support that explained this as working as designed...but at the time it seemed to make sense, though I disagree that this is not a problem with this version of the client. To report that something is not getting backed up when it clearly is, should be considered a problem and not a design change! Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: John Bremer [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 6:16 PM To: [EMAIL PROTECTED] Subject: Win2000 system objects Greetings, I'm new to the forum. I am upgrading my clients to TSM 4.1 from ADSM 3.1.8. A Win2000 client with three partitions C: D: P: backs up successfully. I'm using a domain statement, nothing else special in the options file. Since upgrading to TSM 4.1 client, I now see filespace 'System Object'. The documentation says servers at 3.7.3 and higher support the "feature" to backup system objects as a group. Fine by me, but when I query filespace for this node, there is no start time, no completion time, no capacity utilization, etc. for filespace 'System Object'. We run e-mail notification scripts off these date/time fields, and they're going to fail without these completion statistics. Nothing unusual in the dsmsched.log. In fact, the last message is "Successful incremental backup of Registry". Thanks to anyone for any input to this problem. John Bremer LANL
ATTN: All Windows Client Users
** PLEASE READ ** Patch 4.1.2.12 for the Windows client is now available for download. All files related to this patch begin with "IP22151_12". Please note that this patch fixes a number of APARs, including IC29552 (the problem with file names containing international characters, also known as "the umlaut problem"). If you are experiencing this problem, please be sure to review the files IP22151_12_TSMCLEAN_README.FTP and IP22151_12_TSMCLEAN_README.1ST *before* installing and using the 4.1.2.12 client. Be sure to also review IP22151_12_read1stc.txt for information about other APARs fixed in this patch. Note: While this patch has not been tested as extensively as our usual maintenance PTFs, it has undergone significantly more testing than prior fixtests. You can obtain the patch from our ftp site ftp.software.ibm.com in the following directory: storage/tivoli-storage-management/patches/client/v4r1/Windows/v412 Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked."
Re: How to find out what tape's a client data are on ?
H that doesn't look right to me, either. Just from observation, it looks as if the DISTINCT keyword is operating on either the first column in the result set, or maybe the sorting key, since you are now sorting by storage pool name. Either way, I'm pretty sure that DISTINCT is supposed to account for distinct rows in their entirety, and not just certain columns. I'll have to look into this. Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Walker, Lesley R" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/02/2001 11:16:27 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: How to find out what tape's a client data are on ? Just out of curiosity, since I've only casually been following this thread, was there a specific reason for the "group by" clause? I think what is desired is simplly an "order by" clause, e.g. Well, I'm really confused now. I came up with my own version of the query: select distinct volume_name,stgpool_name from volumeusage where node_name='FOO' and that produces an answer: VOLUME_NAMESTGPOOL_NAME -- -- ITF010 CPITFPOOL ITF013 CPITFPOOL ITF018 CPITFPOOL ITF026 CPITFPOOL ITF001 ITFPOOL ITF003 ITFPOOL ITF004 ITFPOOL ITF014 ITFPOOL ITF025 ITFPOOL ITF027 ITFPOOL ITF028 CPITFPOOL ITF006 ITFPOOL ITF002 CPITFPOOL BUT if I add "order by stgpool_name" it doesn't show all the tapes - eg: VOLUME_NAMESTGPOOL_NAME -- -- ITF010 CPITFPOOL ITF001 ITFPOOL So what's going on here?
Re: How to find out what tape's a client data are on ?
This is not a case (no pun intended) of TSM being case-sensitive. Rather, it is the standard SQL "is equal to" operator, '=', that is case sensitive when comparing strings. This is per the SQL standard, and is not specific to TSM's SQL implementation. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Shekhar Dhotre [EMAIL PROTECTED]@VM.MARIST.EDU on 03/01/2001 10:41:16 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: How to find out what tape's a client data are on ? Thanks .Worked .. .. i was thinking that TSM is not case sensitive application .. hmm.. Glen Churchfield [EMAIL PROTECTED]@VM.MARIST.EDU on 03/01/2001 11:57:38 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: How to find out what tape's a client data are on ? Shekhar, Remember that the node name is case sensitive and is all caps. -Original Message- From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 01, 2001 11:40 AM To: [EMAIL PROTECTED] Subject: Re: How to find out what tape's a client data are on ? I am trying same command for the One of my AIX Box , that is getting backed up regularly . I am not getting any output .. IS anything wrong here .. tsm: TSMselect volume_name,node_name from volumeusage where node_name='medrs2' group by volume_name,node_name ANR2034E SELECT: No match found using this criteria. ANS8001I Return code 11. "Sharp, Neil (London)" [EMAIL PROTECTED]@VM.MARIST.EDU on 03/01/2001 11:02:07 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: How to find out what tape's a client data are on ? Thanks for your help. It has answered my question. Neil -Original Message- From: Ruddy STOUDER [SMTP:[EMAIL PROTECTED]] Sent: Thursday, March 01, 2001 12:47 PM To: [EMAIL PROTECTED] Subject: Re: How to find out what tape's a client data are on ? Here is the SQL script : select volume_name,node_name from volumeusage where node_name='$1' group by volume_name,node_name Just give the server name as parameter 1 Ruddy Stouder System Engineer I.R.I.S. Rue du Bosquet 10 - Parc Scientifique de Louvain-La-Neuve B- 1435 Mont-Saint-Guibert [EMAIL PROTECTED] http://www.irislink.com Tel: +32 (0)10 48 75 10 - Fax: +32 (0)10 48 75 40 -Original Message- From: Sharp, Neil (London) [mailto:[EMAIL PROTECTED]] Sent: jeudi 1 mars 2001 13:44 To: [EMAIL PROTECTED] Subject: How to find out what tape's a client data are on ? I have a frustrating situation whereby if I perform a client restore it may call a tape from off-site. This tape is then recalled (usually 4 hours) and then placed in the library. The restore then continues but then stalls again requesting another tape. What I need to find out up front are all the tapes that could possibly be requested for the client and recall all tapes. I can find this out by running 'q vol client=X' but I have 2000 tapes to search and this will take a long time even if scripted . I think that what I need is a SQL query. I am running 3.1.2.22 (don't laugh I am upgrading shortly) Thanks for your time. Neil Sharp Merrill Lynch ADSM/TSM Administrator Work : 020-7573-0469 Mobile : 07769-741612 Pager : 01893-038277 e-mail : [EMAIL PROTECTED] (See attached file: $RFC822.eml) $RFC822.eml
Re: ATTN: All Windows 4.1.2 Client Users
QUESTION: Do you have possible eta on the fixtest for Windows 4.1.2 Client? ANSWER: Good question! We hope to have the fix available by some time next week at the very latest. Currently things are looking very good, and it may even be available by some time tomorrow (no guarantees, though!). A follow-up posting will be made when the fix is available. FYI, it is not the coding that is the tricky part; that was relatively easy. Rather, the bulk of the effort has gone into testing. We have been making every effort to perform comprehensive testing of the fix on all of our supported language environments to ensure that (1) we have indeed correctly addressed the problem, (2) we do not introduce any new problems, and (3) we do not regress any prior fixes (for example, we would *not* want to re-introduce the Daylight Savings Time problem, so we need to test that as well. While we very much desire to produce as timely a fix as possible, we do not want to be in such a hurry to get it out the door that we overlook something else. The most important criterion is quality, not time (although time is also very important). Thank you, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked."
Re: ATTN: All Windows 4.1.2 Client Users
Hi Andrew, This problem affects only the Western languages that we support (German, English, Spanish, French, Italian, Portuguese Brazilian), since the Eastern languages do not have upper and lower case. So this problem does not affect the Eastern languages (Chinese Simplified, Chinese Traditional, Japanese, and Korean). Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Andrew Webster [EMAIL PROTECTED]@VM.MARIST.EDU on 02/21/2001 09:38:04 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: ATTN: All Windows 4.1.2 Client Users Hi Andrew, Thanks for your excellent update. One question, that you may feel should be posted to list if how Far-East languages (like Japanese, Korean) are handled, obviously a Japanese/Chinese character (kanji) doesn't have a upper or lower case version, so how it TSM representing those characters? Regards Andrew Webster TSM/Storage Consultant Deutsche Bank, Australia Office : +61 3 9270-4229 Mobile : +61 (0) 4090 6515 Fax: +61 3 9270-4144 E-Mail : [EMAIL PROTECTED] Message History From: [EMAIL PROTECTED] on 21/02/2001 14:33 GMT Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: ATTN: All Windows 4.1.2 Client Users IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the way the TSM 4.1.2 client for Windows handles certain international characters in file and directory names has recently been discovered. APAR IC29552 has been opened for the problem, and the client has been removed from the Web site and anonymous FTP server. Fixtest 4.1.2.12 will correct the problem, and will be available soon from the Tivoli web page http://www.tivoli.com/support/storage_mgr/clients.html. The "Tivoli Storage Manager - Open Problems" page, http://www.tivoli.com/support/storage_mgr/open_problem.html, will contain more information on the fixtest and its utility as it becomes available. BACKGROUND Microsoft Windows allows file names to be created that contain any combination of upper- and lower-case characters, and the file system will maintain the given casing for a file. This is known as "case preserving". However, the casing of a file name by itself does not distinguish one file from another. This is known as "case insensitive". For example, MYFILE.TXT, MyFile.txt, and myfile.TXT are all considered to be the same file. This is as opposed to UNIX, where these would be considered three separate files. In order to facilitate TSM support for case preserving, case insensitive file names, all Windows file backups are stored on the TSM server with the file names converted to upper case. This is done in order for the TSM server to recognize that MYFILE.TXT, myfile.txt, and MyFile.txt all refer to the same file name. The information necessary to restore the files with their correct casing is kept elsewhere in the database. THE PROBLEM A problem in the TSM 4.1.2 client for Windows has recently been discovered that can cause files with certain international characters in their names (such as a 'u' with an umlaut: ) to be stored incorrectly on the TSM server. That is, the problem characters are not converted to uppercase (i.e. is not properly converted to ). As a result, incremental backup operations may not handle these files properly. Symptoms are varied, but may include the following: - Backup versions of files with these international characters that were created with a client version prior to 4.1.2 will be expired. Because this will cause the VERDELETED setting of the management class's copygroup to go into effect, older backup versions may be deleted from the server. These versions can no longer be recovered. - The existing files with these characters in their names will be backed up during each incremental backup cycle, regardless of whether the file has changed. Prior versions of the file will be deleted from the TSM server based on the VEREXISTS setting. As a result, the server may have multiple backup copies of the same state of the file, and truly different versions of the file may have been deleted. - The following messages will be displayed during backups, and logged to dsmerror.log: ANS1228E Sending of object filename failed ANS1304W Active object not found - If a directory name contains one of these characters, files and subdirectories within that directory will also be expired and may not be restorable. WHAT IBM/TIVOLI IS DOING ABOUT THIS Here are the actions that we are taking or have taken to date: 1) We have opened a severity 1 APAR, IC29552, to address this problem. 2) We have removed the TSM 4.1.2 Windows client from the FTP site. If you have download
ATTN: All Windows 4.1.2 Client Users
IMPORTANT - PLEASE READ THE FOLLOWING: A problem with the way the TSM 4.1.2 client for Windows handles certain international characters in file and directory names has recently been discovered. APAR IC29552 has been opened for the problem, and the client has been removed from the Web site and anonymous FTP server. Fixtest 4.1.2.12 will correct the problem, and will be available soon from the Tivoli web page http://www.tivoli.com/support/storage_mgr/clients.html. The "Tivoli Storage Manager - Open Problems" page, http://www.tivoli.com/support/storage_mgr/open_problem.html, will contain more information on the fixtest and its utility as it becomes available. BACKGROUND Microsoft Windows allows file names to be created that contain any combination of upper- and lower-case characters, and the file system will maintain the given casing for a file. This is known as "case preserving". However, the casing of a file name by itself does not distinguish one file from another. This is known as "case insensitive". For example, MYFILE.TXT, MyFile.txt, and myfile.TXT are all considered to be the same file. This is as opposed to UNIX, where these would be considered three separate files. In order to facilitate TSM support for case preserving, case insensitive file names, all Windows file backups are stored on the TSM server with the file names converted to upper case. This is done in order for the TSM server to recognize that MYFILE.TXT, myfile.txt, and MyFile.txt all refer to the same file name. The information necessary to restore the files with their correct casing is kept elsewhere in the database. THE PROBLEM A problem in the TSM 4.1.2 client for Windows has recently been discovered that can cause files with certain international characters in their names (such as a 'u' with an umlaut: ) to be stored incorrectly on the TSM server. That is, the problem characters are not converted to uppercase (i.e. is not properly converted to ). As a result, incremental backup operations may not handle these files properly. Symptoms are varied, but may include the following: - Backup versions of files with these international characters that were created with a client version prior to 4.1.2 will be expired. Because this will cause the VERDELETED setting of the management class's copygroup to go into effect, older backup versions may be deleted from the server. These versions can no longer be recovered. - The existing files with these characters in their names will be backed up during each incremental backup cycle, regardless of whether the file has changed. Prior versions of the file will be deleted from the TSM server based on the VEREXISTS setting. As a result, the server may have multiple backup copies of the same state of the file, and truly different versions of the file may have been deleted. - The following messages will be displayed during backups, and logged to dsmerror.log: ANS1228E Sending of object filename failed ANS1304W Active object not found - If a directory name contains one of these characters, files and subdirectories within that directory will also be expired and may not be restorable. WHAT IBM/TIVOLI IS DOING ABOUT THIS Here are the actions that we are taking or have taken to date: 1) We have opened a severity 1 APAR, IC29552, to address this problem. 2) We have removed the TSM 4.1.2 Windows client from the FTP site. If you have downloaded, but not installed the 4.1.2 client, we strongly urge you to not install this code; rather, you should delete the downloaded image from your systems. 3) The TSM 4.1.2 Windows client was originally included in the TSM 4.1.2 Windows server installation package. That server package has been removed from the FTP site, and replaced with a TSM 4.1.2 server package that has the client install disabled. Due to the complexities involved in removing the files that comprise the client, those files have not been physically removed from the server install package. However, using the SETUP.EXE program, the client will not be installable. We strongly urge you to not attempt to use any means external to the SETUP.EXE program to install the client files. 4) A fixtest is being developed and tested that will resolve this problem such that new backup versions of files will be properly converted to upper case when stored on the TSM server. The www.tivoli.com/support/storage_mgr web page sections for Flashes and for Downloads will be posted when the fixtest is actually available for download. 5) A special utility is being developed that will expire all the incorrectly cased versions of the files. The www.tivoli.com/support/storage_mgr web page sections for Flashes and for Downloads will be posted when the special utility client is actually available for download. Note that the details for using the utility will be included in a README file that accompanies the utility. 6) We are working on notifying all of our customers in the most expedient manner possible. 7) We are
Re: Incremental Restore
Perhaps the options -replace=all -ifnewer will work for you. The use the equivalent GUI options, from the Restore dialog, click on the 3rd button from the left (just above the tree view). Change "Action for files that already exist" to "Replace", and check the "Replace only if newer" option. You can refer to the online help and/or "Using the Backup-Archive Client" book for further info. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Caffey, Jeff L." [EMAIL PROTECTED]@VM.MARIST.EDU on 02/20/2001 08:51:40 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Incremental Restore Christoph, If you get a direct response, please forward it to me. I'm currently facing a VERY similar situation with a Windows 2000 server. I'm using TSM 4.1.2, and I "THINK" it will ask if I only want to restore the changes, but I'm not sure. TSM Server 4.1.2 running on AIX 4.3.3 TSM Client 4.1.2 running on Windows 2000 Server Thank you, Jeff Caffey Enterprise Systems Programmer Pier 1 imports, Inc. - Information Services [EMAIL PROTECTED] Voice: (817) 252-6222 Fax: (817) 252-7299 -Original Message- From: Christoph Pilgram [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 20, 2001 9:24 AM To: [EMAIL PROTECTED] Subject:Incremental Restore Hy all, within the next few days I have to restore some large disk-volumes to new disks on a Netware-Server. Because its in production, I can't stop the server for the whole restore time. The volumes are about 260GB in size. The backup-data are spanned over about 24 tapes (3590E), so restore takes a while. The data can not be mirrored. My idea is to restore the complete data to the new volumes while users work on the old ones. After finishing this restore, I want to do another incremental backup of the old volumes to get the meanwhile changed data. But : how do I get only these data to the new volumes without touching all the other older data on the tapes ??? TSM-Server : AIX 4.3 TSM 3.7.4 Netware-Version : 5.0 TSM-Client 3.7.2 Thanks for help Christoph
Re: Installation ERROR client 22088_16_BA
You might try going to the Microsoft MSDN site (http://msdn.microsoft.com) and do a search on: Q251274 This article describes a known problem that can cause the error you are seeing, along with a circumvention. Please be sure to read the article carefully! Also, make sure you are logged in as a local administrator when doing the install. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." "Janse, JI (Joost)" [EMAIL PROTECTED]@VM.MARIST.EDU on 02/06/2001 10:08:15 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Installation ERROR client 22088_16_BA Hello, I'm trying to install a new TSM4.1.1.16 Win32 client on a Windows NT4.0 SP6a client. After copying the files from the package (22088_16_BA) to the temporary directory, the installation starts configuring the Windows Installer. This process end in a "Internal Error 1631" and the client installation aborts. On some other NT machines (NT4.0 SP6a) the installation works fine. I have searched the ADSM search database but couldn't find the Error 1631 message. Also I have removed msiexec entries from the registry and tried the installation again. Still without any success! Hopefully some NT/TSM goeroe can point me in the right direction because the NT folks aren't very enthusiastic about reinstalling the complete system and we (storage management) are in a situation where TSM has to prove itself. Thanks in advance, Joost Janse [EMAIL PROTECTED] Rabobank ICT The Netherlands De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. The information contained in this message may be confidential and is intended to be exclusively for the addressee. Should you receive this message unintentionally, please do not use the contents herein and notify the sender immediately by return e-mail.
Re: ODBC install severe error
Hi Gerhard and Xavier, Xavier, you mention that you are trying to install TSM 3.7. Are you installing this on a U.S. English version of Windows? ODBC Driver versions below 4.1 are not supported on non-English systems. Gerhard, you must be trying to install a 4.1 level of the ODBC driver if you have the .msi file. Are you installing 4.1.2 or 4.1.1.x? If 4.1.1.x, there was a problem using setup.exe to complete the entire install on non-English systems (APAR IC27780), which is fixed in the 4.1.2 version. To both of you: I would recommend you download and install the latest ODBC driver level, 4.1.2. Please be sure to follow the install instructions in ODBCINST.TXT, as there are special instructions with regard to non-English machines (you need to obtain the correct language version of the Microsoft Data Access Components - MDAC). But it should work successfully. Best regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Gerhard Rentschler [EMAIL PROTECTED]@VM.MARIST.EDU on 02/05/2001 05:00:18 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: ODBC install severe error Hello Xavier, how did you install it? Did you use setup.exe or just execute the msi file? I also had problems first time when I used the setup.exe. I think it should be used only to install the MS installer on NT. The actual install should be done by doubleclicking the msi file. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Xavier Merlin Sent: Monday, February 05, 2001 11:58 AM To: [EMAIL PROTECTED] Subject: ODBC install severe error Importance: High Trying to install ODBC on a WIN/NT SP4 (TSM 3.7 for windows/NT) Getting severe error: could not load the setup or translator library IBM ODBC for ADSM Anyone familiar with this error? What am I missing and do I need to do ? Tnx, Xavier
Re: TSM 3.7.3 web client browser access probs??
I am not clear as to whether the TSM server is running on the same machine as your workstation. If the TSM server is running on a different machine, then you need to install and configure the client code on the TSM server machine. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Ken Sedlacek [EMAIL PROTECTED]@VM.MARIST.EDU on 01/25/2001 09:54:59 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TSM 3.7.3 web client browser access probs?? Situation: TSM server 3.7.3, TSM client 3.7.3, AIX 4.3.3 This NTwrkstn (my wrkstn, I can run Admin web client browser access ok. http://TSMserver:1580). Everything works OK. NO problems communicating w/TSM server. I have also installed on this wrkstn TSM NT client 3.7.3. The GUI interface runs and works ok. I have a backup schedule running ok. I have gone thru the GUI wizard to setup the web client agents. Those are running ok. However, I can't get the wrkstn web client browser access to work to the TSM server (http://TSMserver:1581). IExplorer 5.5 error message says it can't locate server @ http://TSMserver:1581. Any ideas?? Ken Sedlacek Kyrus Corporation Office: 864-322-4260; Cell: 864-444-8375 Text Page: 864-444-7243, follow prompts [EMAIL PROTECTED] Kyrus IT Support (Internal: 4399) (Greenville: 864-322-4399) (Toll-Free: 888-413-4399)
Re: TSM 3.7.3 web client browser access probs?? Lets try this again
In order to perform client operations on machineX via your web browser, you need to (1) configure the Web client on machineX, and (2) point your browser to machineX. Therefore, if you wish to perform client operations on you workstation, you need to point your browser to your workstation. If you are pointing your browser to http://TSMServer:1581, but TSMServer is not your workstation, then you are pointing to the wrong address. For example, if your workstation's TCP/IP address is kens.kyrus.com then you need to point your browser to http://kens.kyrus.com:1581. http://kens:1581 might also work if you are on a machine that is on the same network as kens.kyrus.com. If you are actually on the machine kens.kyrus.com, you can also use http://localhost:1581 Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Ken Sedlacek [EMAIL PROTECTED]@VM.MARIST.EDU on 01/25/2001 12:35:34 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TSM 3.7.3 web client browser access probs?? Lets try this again I am sorry I left so much relevant info out of my first email on this same subject. Lets try this again: TSM server Environment: TSM 3.7.3 server running on RS6K H70, AIX 4.3.3 TSM Client Environment: NT4 Wrkstn running TSM client 3.7.3. I have the client GUI running a scheduled backup with no problems. On this same NT wrkstn, I can also run the TSM admin browser web client to: http://TSMserver:1580 without any problems. On this same wrkstn, I want to run the TSM 3.7.3 browser web client for my backup/restore/archive wrkstn. I have installed via the GUI wizard the client agent services (TSM client acceptor and TSM remote client agent). Both are running. Problem: On this same wrkstn (where the TSM client GUI works TSM admin client web browser works), I can't seem to get the TSM client web browser to interface with the TSM server @:http://TSMserver:1581 to display the client access screen. Why?? everything else works right from this NT wrkstn (GUI Admin web client). Why won't the TSM client web browser work? Any ideas?? Ken Sedlacek Kyrus Corporation Office: 864-322-4260; Cell: 864-444-8375 Text Page: 864-444-7243, follow prompts [EMAIL PROTECTED] Kyrus IT Support (Internal: 4399) (Greenville: 864-322-4399) (Toll-Free: 888-413-4399)
Re: APAR IC28571 : NT EVENT VIEW REPORTS PERFLIB ERRORS AGAINST DSM CPERF.DLL - TSM 4.1.1
Hello, I believe that the following procedure should do the trick. Step 2 especially is the key (no pun intended). WARNING: This procedure involves editing the NT registry. THE REGISTRY EDITOR IS NOT FORGIVING OF MISTAKES! Errors in editing the registry have the potential to render the system unstable or even unbootable. If you are unfamiliar or uncomfortable with editing the registry, then either ask someone who is more experienced do this for you or install this fixtest (which automatically performs these operations for you). 1) From an MS-DOS command line prompt, enter the following commands: unlodctr "ADSM Client Performance" unlodctr "TSM Client Performance" If the performance counters were previously installed, you should see messages similar to this: Removing counter names and explain text for ADSM Client Performance Updating text for language 009 If the performance counters were not previously installed, you will see a message similar to this: Counters for ADSM Client Performance have not been installed yet 2) Using the registry editor, remove the following keys (including their values): HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ ADSM Client Performance HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ EventLog\ Application\ ADSM Client Performance Note: Also check for keys with "TSM" in the name instead of "ADSM". The performance counters and registry entries are now removed. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Hello TSMers, I have scoured the TSM Knowledge Base at http://www.tivoli.com/asktivoli on the subject error and found the APAR. However the work around does not work for us. First, the local fix using the unlodctr doesn't work because it is not called "TSM Client Performance", but "ADSM Client Performance". Then, the "lodctr perfctr.ini" command doesn't work because TSM Client Performance is hard-coded into the perfctr.ini file when it needs to say ADSM Client Performance. However, even when you make these modifications, it still does not get rid of the error messages. As for the changes to the registry, the registry key they mention doesn't exist. Any other options?
Re: General *SM database/ IP address question
Hi Christo, Thank you for pointing this out. I stand corrected. :-) Please note, though, that the information is not kept permanently, and will expire after the number of days specified by the Activity Summary Retention Period (via SET SUMMARYRETENTION). So it may not be complete. Best regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." Christo Heuër [EMAIL PROTECTED]@VM.MARIST.EDU on 12/19/2000 02:31:40 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: General *SM database/ IP address question Hi Andy, David, This info is kept in the summary table on Tsm3.7 servers. Here is an example of of a select * from summary query: (Note the address field). START_TIME: 2000-11-20 19:05:55.00 END_TIME: 2000-11-20 19:35:38.00 ACTIVITY: BACKUP NUMBER: 274 ENTITY: LEGALJHB COMMMETH: Tcp/Ip ADDRESS: 10.0.8.34:2177 SCHEDULE_NAME: EXAMINED: 2977 AFFECTED: 2977 FAILED: 0 BYTES: 638352864 IDLE: 99 MEDIAW: 0 PROCESSES: 1 SUCCESSFUL: YES Cheers Christo Actually this info isn't in the NODES table, either. The TSM server stores the IP addresses for nodes using the PROMPTED scheduling mode only, so the server knows which address to prompt when it is time to run scheduled events. However, the table in which this data resides has not been externalized, so it can not be accessed by any QUERY or SELECT statement. Regards, Andy Andy Raibeck IBM/Tivoli Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] "The only dumb question is the one that goes unasked." I am sory to correct you, but there is a field in the nodes table that stores the hex IP address of the client. Keith Davey On Mon, 18 Dec 2000, Williams, Tim wrote: I don't think that it really 'stores' that information, per se. IT, is however logged in the activity log q actlog.search=etc (help q actlog) hope this helps... David Longo [EMAIL PROTECTED] 12/18/2000 02:24 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED]@SMTP@Exchange To: [EMAIL PROTECTED]@SMTP@Exchange cc: Subject:General *SM database/ IP address question When you register a node name and the node first contacts the *SM Server, the server stores the IP address of the client. Where is this IP address stored on the server? David B. Longo Systems Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED]
