TSM Client on SGI
I've installed TSM version 5.1 on an IRIX box but get the following when I tried to start it: 32052:dsm: rld: Fatal Error: Cannot Successfully map soname 'libdm.so' under any of the filenames /usr/lib32/libdm.so:/usr/lib32/internal/libdm.so:/lib32/libdm.so:/opt/lib32/ libdm.so:/usr/lib32/libdm.so.1:/usr/lib32/internal/libdm.so.1:/lib32/libdm.s o.1:/opt/lib32/libdm.so.1: I searched the archives and found the following exchange: Fred, we went through that...answer: eoe.sw.dmi is the package.found this by running this command: versions long|grep libdm.so Kent Monthei GlaxoSmithKline Fred Johanson [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 20-Mar-2002 14:14 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L Subject:ADSM on sgi system I received this from one of my users. This is a platform that we do not support internall, but if anyone wants to use it, we try to answer any questions they have. Can any one help me on this?? I am trying to install ADSM on a sgi system but get the error on start up can not Successfully map soname 'libdm.so' under any of the filenames //... and so on. Could you run a query on this I need to find out were to get this file. Ian But I'm not sure what to do with that information. An IRIX guru I'm not! How do I fix the libdm.so problem and what does eoe.sw.dmi have to do with it?? Also, when I downloaded the version 5.1 software, there was a note that said that it was at v4.2 functionality; what does that mean? They just slapped a new version number on the old version? Would that be 4.2 with or without all the latest fixes? Any help would be appreciated...Thanks! Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 20879 301-240-6184 CODA/I Storage Management
Re: Bare Metal Restore for TSM
I got the same story from Veritas regarding what used to be called OTG DiskXtender. They vehemently denied pulling TSM support for the product and were in fact, quite interested in selling us some more licenses. They have an agreement with IBM that IBM would get the source code should Veritas decide in the future to no longer support it. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 20879 301-240-6184 CODA/I Storage Management -Original Message- From: Daniel Sparrman [mailto:[EMAIL PROTECTED]] Sent: Friday, July 19, 2002 1:42 AM To: [EMAIL PROTECTED] Subject: Re: Bare Metal Restore for TSM Hi I was in contact with Veritas only a few weeks ago, and I can insure you that they are still developing the product (and supporting it) for TSM. We've got two large customers running approx. 70 BMR clients, and I don't think Veritas is interested in making this customers unhappy. I also know that Tivoli has sold a large number of BMR licenses, so the product is wide spread. However, as this is a forum for TSM, a lot of people is worried, as Veritas is the formost competitor to Tivoli. As I see it, Veritas has nothing to gain by removing support for TSM in BMR. As it is now, Veritas can sell products to customers that they normally don't sell anything to, customers that belong to Veritas formost competitor. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 HÄGERNÄS Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51
Re: Question. Tivoli Backup Client Version 3.7.2
What about the define clientaction command from the server for the missed clients? That too, writes to the log files, doesn't it? Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Gent, Chad E. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 12:53 PM To: [EMAIL PROTECTED] Subject: Re: Question. Tivoli Backup Client Version 3.7.2 Thanks for the help Wanda. This will work perfectly.. Thanks again. Chad -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 11:18 AM To: [EMAIL PROTECTED] Subject: Re: Question. Tivoli Backup Client Version 3.7.2 YOu can do that by running the command line version of the client from a DOS window. You could create a .bat file to do this and assign it to an icon on the desktop. You can even use instead of and append the output to dsmsched.log if you want. CD c:\pathname\tivoli\tsm\baclient dsmc incremental c:\whatever.log -Original Message- From: Gent, Chad E. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 10:17 AM To: [EMAIL PROTECTED] Subject: Question. Tivoli Backup Client Version 3.7.2 Hello. I have several backups that run using the TSM Scheduler. Sometimes the backups will be missed and we have someone go in and run the back ups manually, This works great but it doesn't write to a log file. The Scheduled backups write to Dsmsched.log and Dsmerror.log. Is there any way for to get the manual backups to write to a log file. Any help is appreciated. Thanks Chad
Re: TSM 4.2.1
One thing I noticed with the new 4.2.0 client code, is that for the W2K clients only (not NT and not UNIX), when I do a q inclexcl, the list now includes Operating System excludes. Can't find this new feature documented anywhere...at least not in the places I've looked. Can anyone shed some light on this? TIA Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Henk ten Have [mailto:[EMAIL PROTECTED]] Sent: Monday, October 22, 2001 10:29 AM To: [EMAIL PROTECTED] Subject: Re: TSM 4.2.1 On 22-Oct-01 Gill, Geoffrey L. wrote: For all those who are thinking of upgrading to 4.2.1, my opinion is don't. I have been up on it for 10 days and have already experienced 3 crashes. I also have a tape problem that I'm told was supposed to have been fixed. I have 2 PMR's open, both at level 2. I'm on AIX 4.3.3 and not sure if other platforms have had similar problems.
Re: wrong stgpool
Sounds like the new management class, notesclass, has a longer retention period than the original, ntclass. Directories will automatically be bound to whatever management class has the longest retention period so that you don't accidentally have data hanging around longer then directories. If you want to keep the directories bound to the shorter management class, you will now need to use the DIRMC option to bind them that way. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: David DeCuir [mailto:[EMAIL PROTECTED]] Sent: Friday, May 18, 2001 9:12 AM To: [EMAIL PROTECTED] Subject: wrong stgpool I have 20 NT servers with a dsm.opt that has an include * ntclass line. These run a nightly backup that has worked fine for months, backing up to the backup copygroup of mgmtclass ntclass with a dest. of ntdiskpool. This is all normal. Here is my problem. I created a new mgmtclass called notesclass, which has a backup copygroup with a dest. of notespool (this is a tape pool). Now, keep in mind the 20 NT servers have include * ntclass as the only mgmtclass. I'm seeing that q content of some of the volumes in notespool show data paths from most of the 20 NT servers. Notesclass is not a default mgmtclass and the notespool volumes were aquired empty from scratch. How could this data get on the wrong stgpool volumes? Also, the NT servers data paths on the volumes in notespool point to directories only, no files. I'm also seeing this with my UNIX mgmtclass (having data paths on notespool). I am new to this and have never run any audits or unloads or anything on the database or volumes. Could that help? Still too new and dumb to know why this is happening. Thanks.
Using TSM OBDC Driver with Excel
Has anyone seen this problem and know how to overcome it? Using the TSM OBDC Drivers with Excel to import information regarding the admin schedules into a spreadsheet, the STARTTIME column always shows up with all zeros (00:00:00) for the time. If I issue the very same select statement from either the DSMADMC command line, or via a macro running in the background, the STARTTIME column shows the correct times in HH:MM:SS format. In trying to schedule the million housekeeping chores that need to get done in one 24-hour period, the start times are very important to us. And having it put in a spreadsheet automatically, as opposed to a flat file created by the macro, or massaging the flat file by hand into a spreadsheet, is very much preferred. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: Installing TSM 4.1.0 Client in a WNT Server
We had this problem when we were installing 4.1.2.12. We downloaded the code from the Tivoli web site and when we tried to install on the server that actually housed the code, we got this error. When we ran the install from a net used file system, it ran just fine. And this just didn't happen once, it happened on multiple servers. If the server actually housed the code, we got this error. If we then moved the software to some other server, or issued a net use against its own drive to trick out the software, it would install with no errors. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Remeta, Mark [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 3:07 PM To: [EMAIL PROTECTED] Subject: Re: Installing TSM 4.1.0 Client in a WNT Server I kind of remember this problem. I think you need a newer version of the client. The latest for NT is 4.1.2.14 Mark -Original Message- From: Gerardo Zapata [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 2:48 PM To: [EMAIL PROTECTED] Subject: Installing TSM 4.1.0 Client in a WNT Server 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 experience or idea of the cause? Thanks in advance ___ Gerardo Zapata IT Specialist Infrastructure Systems Management IBM Mexico (525) 270 5889 e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] Get free email and a permanent address at http://www.netaddress.com/?N=1 Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
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 -Original Message- From: Andy Raibeck [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 9:40 AM To: [EMAIL PROTECTED] Subject: 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"
Another cloptset Question regarding inclexcl
I've been trying to create exclude statements for our cloptset where the excluded directory path includes a space in the name (i.e., program files, Temporary Internet Files). I've used every combination of single and double quotation marks that I can think of, and even though, from the server's point of view, these statements are valid, when I get on the client and do a "q inclexcl", these things either do not show up at all, or show up incorrectly (only text up to the first space is shown). Anyone else gotten these type of statements to work in a cloptset? I have no trouble when they are in a dsm.opt or dsm.sys file, only from the cloptset. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: Another cloptset Question regarding inclexcl
Thank you, that worked!!! I've used every combination of single and double quotation marks that I can think of... Guess I hadn't tried that combination yet!! :) Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Kleynerman, Arthur [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 10, 2001 2:58 PM To: [EMAIL PROTECTED] Subject: Re: Another cloptset Question regarding inclexcl When you define the option for the option set, do the following: def clientopt option_set_name inclexcl 'Exclude "*:\...\Temporary Internet Files\...\"' seq=0 force=yes Arthur. -Original Message----- From: Short, Anne [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 10, 2001 2:47 PM To: [EMAIL PROTECTED] Subject: Another cloptset Question regarding inclexcl I've been trying to create exclude statements for our cloptset where the excluded directory path includes a space in the name (i.e., program files, Temporary Internet Files). I've used every combination of single and double quotation marks that I can think of, and even though, from the server's point of view, these statements are valid, when I get on the client and do a "q inclexcl", these things either do not show up at all, or show up incorrectly (only text up to the first space is shown). Anyone else gotten these type of statements to work in a cloptset? I have no trouble when they are in a dsm.opt or dsm.sys file, only from the cloptset. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management --- 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, check 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.
Re: Uninstall old client when upgrading to TSM 4.1.2?
When we moved our NT clients from 3.7x to 4.1x, an upgrade left behind some desktop icons and the Uninstall icon in the program folder (which no longer exists in 4.1x) that didn't get cleaned up. So I switched to the uninstall/install option for a cleaner implementation. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: LYNN HAMILTON [mailto:[EMAIL PROTECTED]] Sent: Friday, April 06, 2001 9:55 AM To: [EMAIL PROTECTED] Subject: Uninstall old client when upgrading to TSM 4.1.2? --- Received from SIG.HAMILTL LYNN HAMILTON 04/06/01 755a We are upgrading our TSM clients from v.3.1.0.6 to v.4.1.2 for Novell and Windows NT file servers. Is it best to uninstall the old client first and then install the new client or can I simply install the new client on top of the old client. Looking for best practice, pros and cons. Thanks, Lynn 04/06/01 755a Sent to - [EMAIL PROTECTED]
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
Re: DB restore
We just did a DB restore a couple of weeks ago. First we tried with the same number of db volumes, but the volumes added up to less space than was in the original volumes (we had lost a hard drive so we had less space in our array). That failed because the amount of space was less than the original, even though the db was only 50% full and didn't really need all that space (confirmation of the comment that the RESTORE TO db needs to be AT LEAST as big as the original). We then allocated an additional db volume with lots of space (confirmation that the exact same number of db volumes IS NOT required), and the first thing that happened as part of the restore, was that the db was REDUCED to match the exact size of the original. The restore was a success after that, but I thought it was interesting how the db was reduced to match the original size. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Monday, March 19, 2001 5:37 PM To: [EMAIL PROTECTED] Subject: Re: DB restore Well, I'll take a stab at this. I know when you do a DB restore, the same disk layout (i.e., number of DBVOLS) is NOT required, been there done that. I believe the requirement is that the RESTORE TO data base (and recovery log) must have AT LEAST as much space available as the original, although I cannot remember where that is documented. If this is a one-time move, what I would do is use the REDUCE command to pare the source DB down to 5 GB, then back it up, then restore it to the new location. If this is a DR drill, then I think you have a problem, but congratulations on asking the right questions before it's too late! -Original Message- From: Joe Faracchio [mailto:[EMAIL PROTECTED]] Sent: Monday, March 19, 2001 5:26 PM To: [EMAIL PROTECTED] Subject: Re: DB restore Good question. I'd like to know from someone that has experienced a restore. Somewhere it implies that you have to have the same disk layout because its a record backup and not logical. Is this true? Is it documented? I haven't found it, yet! ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley On Mon, 19 Mar 2001 [EMAIL PROTECTED] wrote: If I have a 20GB database that is spread accross 10 dbvols but is only 10% utilized can I restore that database onto a server with 5 dbvols totaling 10GB since the 5 dbvols will hold over the 10% of utilization.
Using client option sets with multiple active policy sets.
Hoping someone can either give me some advice or tell me about similar experiences We have NT clients in 4 different active Policy Sets, and each Policy Set has a uniquely named Default Management Class. I now want to create a Client Option Set to be used for ALL clients. The client option set is to contain include/exclude statements (to associate certain files with a new Management Class I will be creating and which I now realize I will have to create in every Policy Set), as well as a DIRMC option (to force the directories to continue to be associated with the default MC as opposed to the new one). Since Client Options Sets are not associated with any particular Policy Domain/Set, am I going to be forced to create 4 different Client Option Sets to accommodate the different default MC names in each Set?? I need the DIRMC statement, as the new MC class I will be creating will have a longer retention period than the default MC. But I do not want the directories to rebind with the new MC as that would eat up way too many resources (tapes, disk, db, etc). The new MC I want to create is to be able to keep 365 copies of just 3 files that change every day on every client (over 100). I don't need to keep ALL the directories for 365 days when I only want to keep 3 files located on the C: drive for that long. The other option that has been proposed is to use the archive function on these 3 files as opposed to a backup. I'm beginning to think that would make more sense due to the number of active Policy Sets we have. Anyone have any advice/experience? Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: Using client option sets with multiple active policy sets.
But if I had a single client option set that contained the following: Dirmc=name_of_default_management_class I don't think that would work because each DOMAIN's name_of_default_management_class is different. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Talafous, John G. [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 20, 2001 1:36 PM To: [EMAIL PROTECTED] Subject: Re: Using client option sets with multiple active policy sets. Anne, Only one client optionset should be necessary. For example, you could create a cloptset of WINDOWS with the include/exclude statements you require for your WINDOWS clients. Notice the REG NODE and UPD NODE commands. You specify the CLOPTSET in addition to the DOMAIN. They should work to compliment one another. Good luck! John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com -Original Message- From: Short, Anne [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 20, 2001 12:53 PM To: [EMAIL PROTECTED] Subject: Using client option sets with multiple active policy sets. Hoping someone can either give me some advice or tell me about similar experiences We have NT clients in 4 different active Policy Sets, and each Policy Set has a uniquely named Default Management Class. I now want to create a Client Option Set to be used for ALL clients. The client option set is to contain include/exclude statements (to associate certain files with a new Management Class I will be creating and which I now realize I will have to create in every Policy Set), as well as a DIRMC option (to force the directories to continue to be associated with the default MC as opposed to the new one). Since Client Options Sets are not associated with any particular Policy Domain/Set, am I going to be forced to create 4 different Client Option Sets to accommodate the different default MC names in each Set?? I need the DIRMC statement, as the new MC class I will be creating will have a longer retention period than the default MC. But I do not want the directories to rebind with the new MC as that would eat up way too many resources (tapes, disk, db, etc). The new MC I want to create is to be able to keep 365 copies of just 3 files that change every day on every client (over 100). I don't need to keep ALL the directories for 365 days when I only want to keep 3 files located on the C: drive for that long. The other option that has been proposed is to use the archive function on these 3 files as opposed to a backup. I'm beginning to think that would make more sense due to the number of active Policy Sets we have. Anyone have any advice/experience? Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: Commands Scripts
You don't say what platform your server is on, but why not run the commands via "cron" (for UNIX) or "at" for NT. We have both kinds of servers and have both types of jobs set up. The scripts set the environment and the location of the output file, then calls the sql macro, such as: set path=c:\"program files"\Tivoli\TSM\baclient;%PATH% set DSM_CONFIG=c:\program files\tivoli\tsm\baclient\dsm.opt set DSM_DIR=c:\program files\tivoli\tsm\baclient dsmadmc -id=admin_id -pa=admin_id_password -outfile c:\tsm_reports\missed.file.txt macro c:\tsm_macros\missed.files.bat The contents of the macro associated with the above is: set sqldisplaymode wide select date_time,TRIM(nodename),TRIM(message) from actlog where (msgno=4987 or msgno=4007) and ((current_timestamp-DATE_TIME)minutesINTERVAL '1440' minutes) We have a job that runs daily on all our TSM servers that creates the following reports and mails them to us: * Missed files * Completion status of previous 24 hour's backups * Read-only unavailable volumes * Status of copypool job * Status of DB backup job * File systems with last backup greater than 24 hours * Client nodes whose last access is greater than 24 hours After receiving the info in the mail, you can save it, edit it or use it with your favorite tools. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 28, 2001 5:39 PM To: [EMAIL PROTECTED] Subject: Commands I've been dabbling in trying to get the output of a command, through the scheduler, to run and send the output to a file, either on the TSM server or another computer. That file will be ftp'd to another computer and deciphered there. I've been able to run the command from a TSM admin command prompt on my computer but not through a command I made and put in a server command script I can run through the scheduler. I'm not a programmer for sure so I need some help. This can either be a select statement or query command as long as I get a text output file. Here is what works from a dsmc command prompt: adsm query drmedia * wherestate=mo \\servername\temp\drmmo.txt I tried to run the command from the command line on the web browser and a server command script but get this output: ANR2020E QUERY DRMEDIA: Invalid parameter - . I tried to run the command to redirect to the adsm server but it looks like I don't have the syntax right because I haven't been able to do that either. Unable to upen file blah blah blah for redirection. If someone can help with this I'd truly appreciate it. Sorry I can't offer prizes like Kelly can. Geoff Gill NT Systems Support Engineer SAIC Computer Systems Group E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: NT Restore Question?
We have done this multiple times with NT with no problem, other than a couple of little gotchas with differences in hardware drivers. Install the new drivers and you're ready to go! Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Fletcher, Leland D. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 07, 2001 3:19 PM To: [EMAIL PROTECTED] Subject: NT Restore Question? We have many different hardware configurations running Windows NT and Windows 2000. We are not having any problems with the backups. If we have a server failure, can we setup new hardware which is different than the hardware we used to make the ADSM backups and restore successfully? We would ensure that we matched the new hardware to the old in regard to a single processor (kernel) and a multi-processor (kernel). Lee Fletcher Network Project Integrator AmerenUE Callaway Plant [EMAIL PROTECTED] 573-676-4106
System Object Reported as Not Backed Up
I posted last week regarding a problem with the W2K clients running 4.1.2 TSM client code not having their system objects backed up. I received some helpful information and I think I am now successfully backing this up. My problem is, though, that the TSM server still doesn't think so! The scenario is: 2 - TSM servers; one AIX 4.3.3 running TSM 4.1.1 server; one W2K running TSM 4.1.2 server 2 - TMS clients; one W2K Pro; one W2K Server; both running TSM 4.1.2 client The only truly common thread is the 4.1.2 client code. Per the attached snippet from the client's dsmsched.log, the following is supposed to get backed up: 02/06/2001 04:00:03 --- SCHEDULEREC OBJECT BEGIN DAILY0400 02/06/2001 04:00:00 02/06/2001 04:00:03 Incremental backup of volume '\\xmnssrv1\c$' 02/06/2001 04:00:03 Incremental backup of volume '\\xmnssrv1\e$' 02/06/2001 04:00:03 Incremental backup of volume '\\xmnssrv1\f$' 02/06/2001 04:00:03 Incremental backup of volume '\\xmnssrv1\g$' 02/06/2001 04:00:03 Incremental backup of volume '\\xmnssrv1\h$' 02/06/2001 04:00:03 Incremental backup of volume '\\xmnssrv1\i$' 02/06/2001 04:00:03 Incremental backup of volume 'SYSTEM OBJECT' 02/06/2001 04:00:03 Backup System Object: 'COM+ Database'. 02/06/2001 04:00:03 Backup System Object: 'Event Log'. 02/06/2001 04:00:03 Backup System Object: 'System and Boot Files'. 02/06/2001 04:00:03 Backup System Object: 'Registry'. 02/06/2001 04:00:03 Backup System Object: 'RSM Database'. Later on in the log, I get a: "Successful incremental backup of ..." for every one of those objects listed above. So why does "select node_name,filespace_name,backup_end from filespaces where backup_end is null" show me that the SYSTEM OBJECT has never been backed up?? I just opened a PMR with Tivoli, but was wondering if anyone else was seeing this. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: Problems after 4.1 Upgrade and Resolutions
We also get many ANR8302 errors. We are W2K server with TSM 4.1.2 server (before 4.1.2, we were 4.1.0). Since this is a new server and never had anything other than 4.1.x on it, and we have many other problems with the tape drives, such as tapes getting stuck, we attributed these errors to bad drives. Though the drives have been replaced twice now and we are still getting these same errors. Maybe it's not the drives after all. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 9:31 AM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I am aslo getting ANR8301E ANR8302E op=write errors. This started happening after we upgraded to TSM 4.1. We are on WIN 2000 environment. Raminder -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 6:55 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Problems after 4.1 Upgrade and Resolutions
Ditto on all counts. (Actually, I'm not sure I even have drive logs on the unit we use (EXB-440). And it's remote, so I can't easily check that out.) Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 1:24 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions In our case the errors show up in activity log. The drive logs do not show any errors. I don't have any objection of you passing the emails to Tucson. Raminder Braich SAP/Oracle DBA The Davey Tree Expert Company Kent OH 44240 330-673-9515 Ext 270 -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 12:27 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions Are the drives themselves showing errors? That's one of the weird things we've got...our CE has checked the drive logs and there are absolutely no errors to be found. I'm going to give our CE printed copies of all these emails so that he can pass this along to Tuscon, unless anyone has any objections. Diana, did you ever get that microcode? If you did, have you had the opportunity to see if it fixes the problem? Thanks all! Kathleen |+--- || "Short, Anne"| || anne.short@L| || MCO.COM | || | || 02/05/2001 | || 09:53 AM | || Please | || respond to | || "ADSM: Dist | || Stor Manager"| || | |+--- - ---| | | | To: [EMAIL PROTECTED] | | cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) | | Subject: Re: Problems after 4.1 Upgrade and Resolutions | - ---| We also get many ANR8302 errors. We are W2K server with TSM 4.1.2 server (before 4.1.2, we were 4.1.0). Since this is a new server and never had anything other than 4.1.x on it, and we have many other problems with the tape drives, such as tapes getting stuck, we attributed these errors to bad drives. Though the drives have been replaced twice now and we are still getting these same errors. Maybe it's not the drives after all. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Braich, Raminder [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 9:31 AM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I am aslo getting ANR8301E ANR8302E op=write errors. This started happening after we upgraded to TSM 4.1. We are on WIN 2000 environment. Raminder -Original Message- From: Kathleen M Hallahan [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 6:55 PM To: [EMAIL PROTECTED] Subject: Re: Problems after 4.1 Upgrade and Resolutions I haven't heard back yet as to whether the code is available, or even if our problem is definitely the same problem. Our CE mentioned her PMR number in our PMR, and he and I have both spoken to someone in Tuscon, so hopefully I'll have more data on that soon. What error codes are you getting, and what is your environment? Have you taken it up with IBM yet? I'd love to know if there really are others seeing the same problems besides just a couple of us. Kathleen "Braich, Raminder" [EMAIL PROTECTED] on 02/02/2001 11:17:04 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Kathleen M Hallahan/ISS/HQ/FHLMC) Subject Re: Problems after 4.1 Upgrade and Resolutions : Kathleen, I read your post on ADSM forum regarding the tape IO errors Diana Noble was having. I am also having the same errors. You mentioned they were working on some microcode and should be released soon. Did they ever release it, if so from where can I download it. Raminder
Re: Which client version is best for a Win2000-server ?
Level 4.1.2 - This level has only been available since December. No reports so far of the EXPORT RSM bug. Wanda, you can update your list...I am getting the EXPORT RSM bug. Luckily, it's the last thing that tries to get backed up, so all other backups are successful. I guess I'll call this into Tivoli. I have tried this with RSM set to Disabled and set to Manual and get the same results both times. Don't want to set it to Automatic Start as then it tries to steal control of my library (EXB-440) from TSM and causes all sorts of problems. (Configuration: W2K server running TSM server 4.1.2 and TSM client 4.1.2) Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: Which client version is best for a Win2000-server ?
We have a TSM 4.1.2 server on W2K, as well as the 4.1.2 client to back itself up. TSM has consistently reported that there has never been a backup of the SYSTEM OBJECT. After reading through all the helpful information in the subject post by Wanda and Tim, I modified my include/exclude list to ensure that the adsm.sys directory gets backed up, assuming that was my problem. I can confirm this morning via the dsmerror.log and dsmsched.log that those objects are now getting backed up, but it still reports that the SYSTEM OBJECT has not been backed up. What am I missing? What exactly is the SYSTEM OBJECT it is complaining about? I use the dumpel.exe to dump the event logs so they get backed up as part of the normal back up of the C: drive. And per the dsmsched.log, I get a successful backup of the Registry every night. I'm a UNIX person at heart, so excuse me if this is some obvious NT thing I'm missing. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
Re: Dsmcad
You need a unique name for each process. If you are already using "tsm" for the scheduler, you need to use something like "tsmweb" for the second process. We use this on all our AIX boxes running TSM with no problem. Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management -Original Message- From: Christophe Guerin [mailto:[EMAIL PROTECTED]] Sent: Friday, January 19, 2001 6:26 AM To: [EMAIL PROTECTED] Subject: Dsmcad Hi all, I want to launch automatically dsmcad on Unix (AIX 4.3.3) clients. What is the solution ? When I add the following entry to the /etc/inittab file: tsm::once:/usr/tivoli/tsm/client/ba/bin/dsmcad /dev/null 21 # TSM Client Acceptor It's not good. (Note : tsm::once:/usr/tivoli/tsm/client/ba/bin/dsmc sched /dev/null 21 # TSM Scheduler works !!). Thanks in advance ___ Do You Yahoo!? -- Pour dialoguer en direct avec vos amis, Yahoo! Messenger : http://fr.messenger.yahoo.com
I/O Error at End-of-Volume
I am running TSM 4.1.1 on W2K with an Exabyte 440 library with Mammoth drives. I have noticed that when a write operation reaches the end of the tape, TSM reports an I/O error and marks the tape as "read-only". At the same time, a query of the volume indicates that the tape's status is "Filling" and is only partially used (usually somewhere in the 80% range). Anyone know why I'm getting this disconnect (indication that the end of the tape is reached, but TSM reporting it as only partially full)? Any help would be appreciated! Anne Short Lockheed Martin Enterprise Information Systems Gaithersburg, Maryland 301-240-6184 CODA/I Storage Management
