Re: Strange behaviour????
Hey Andy, The example that you've outlined here has to do with files that reside on one system. I can understand TSM working this way. What I don't understand is the following: System A: /tmp/ /logs/logfile1 /logs/logfile2 /usr/ System B: /home/ /export/home/ /export/home/myfile Both systems are part of the same policy domain. I have two management classes. One is called STANDARD and the other is called LOG_POLICY-MC. Managementclass STANDARD is the default. I included the following line in my include/exclude file on System A: INclude /logs/.../* LOG_POLICY-MC This would mean that all the directories below /logs/ and including /logs would be bound to managementclass LOG_POLICY-MC All other directories and files should be bound to the managementclass STANDARD because that is the default and I have not specified anything alse in my include/exclude file. This goes for /tmp/ en /usr/ on System A. And now System B: System B has nothing to do with the LOG_POLICY-MC. I haven't specified it anywhere in my include/exclude file nor in a client option set. But yet, directories /home/ and /export/home/ are bound to LOG_POLICY-MC. File /export/home/myfile is bound to managementclass STANDARD as you would expect. So I completely agree with the example that you just gave me. But in your example the files and directories reside on the same system. In my example you have two separate systems and they are both affected by the LOG_POLICY-MC managementclass. I think that's odd! Kind regards, Jerry Caupain >>> [EMAIL PROTECTED] 10/26/01 05:09PM >>> Hi Jerry, The reason that TSM works this way is to help ensure that when restoring deleted files, at least the most recent directory for those files will still be available. For example, suppose you had a directory structure like this: c:\mydir\file1 c:\mydir\file2 Suppose you have two management classes, A and B. A is the default, and has a RETONLY setting of 10 days. B has a RETONLY setting of 30 days. Now suppose (for whatever reason) you decide to bind file2 to management class B. If TSM did not behave as I describe, then you have this: c:\mydir bound to A c:\mydir\file1 bound to A c:\mydir\file2 bound to B Next, you delete the c:\mydir directory (and its files, of course). The next incremental backup detects that these files are deleted, and marks the backup versions inactive. In 10 days, the backups for c:\mydir and c:\mydir\file1 will be deleted from TSM's inventory. In 30 days, the backup for c:\mydir\file2 will be deleted from TSM's inventory. Now suppose it is 15 days later and you wish to restore c:\mydir\file2. The following would be true: - You won't be able to restore via the GUI, because using the GUI to navigate to c:\mydir\file2 means that you need to be able to first navigate to c:\mydir. Since no backups exist for c:\mydir, you will not be able to navigate to it, and thus you will not be able to navigate to c:\mydir\file2. - You can restore c:\mydir\file2 via the command line, but the c:\mydir will be created with default attributes vs. restored from TSM's inventory with its original attributes (because no backup for it exists). So this is why we make TSM behave the way it does. You could use DSM_DIR to tell TSM to bind the directories to your STANDARD management class, but I would not recommend it unless you have a very controlled environment, and you understand and are willing to accept the ramifications as I have described above. Note that the /logs directory and its subdirectories will also be bound to the STANDARD management class (the DSM_DIR option is absolute, and the INCLUDE statement binds only the *files* to the specified management class), so you could run into the problems I describe above. 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] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Jerry Caupain <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/26/2001 06:52 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Strange behaviour But why EVERY directory of EVERY system, even the ones that have nothing to do with this managementclass? Why don't all other systems just use the default managementclass? Do I really need to specify a dirmc for every system in order to get the policy I need? Regards, Jerry Caupain >>> [EMAIL PROTECTED] 10/26/01 12:05PM >>> hi, it will be used for directories if the retonly value is the highest in this DOMAIN, > -Original Message- > From: Jerry Caupain [SMTP:[EMAIL PROTECTED]] > Sent: Frida
Re: Strange behaviour????
But why EVERY directory of EVERY system, even the ones that have nothing to do with this managementclass? Why don't all other systems just use the default managementclass? Do I really need to specify a dirmc for every system in order to get the policy I need? Regards, Jerry Caupain >>> [EMAIL PROTECTED] 10/26/01 12:05PM >>> hi, it will be used for directories if the retonly value is the highest in this DOMAIN, > -Original Message- > From: Jerry Caupain [SMTP:[EMAIL PROTECTED]] > Sent: Friday, October 26, 2001 11:12 AM > To: [EMAIL PROTECTED] > Subject: Strange behaviour > > Hello everyone, > > I have noticed something strange. In my policy domain I have two > management classes. One is called STANDARD and the other is called > LOG_POLICY-MC. I want to use the last one only for my log server so I > included the following line in my include/exclude file: > INclude /logs/.../* log_policy-mc > > Managementclass STANDARD is the default managementclass. > > Why is it that all my other systems also use the LOG_POLICY-MC > managementclass? It seems that the directories on my other systems are > all bound to this managementclass. This can't be normalcan > it??? > > Jerry Caupain
Re: Strange behaviour????
Thanx everyone for the replies. It's all clear to me now.but I still find it strange;-) I defined a client option set and updated all my client nodes except the one that needs the LOG_POLICY-MC managementclass to make use of this option set. Kind regards, Jerry >>> [EMAIL PROTECTED] 10/26/01 04:13PM >>> Yes, this is perfectly normal. I am guessing that the LOG_POLICY-MC management class has a RETONLY value equal to or greater than that of your STANDARD management class. The TSM client binds directories to the management class with the largest RETONLY setting. If two or more management classes have the largest RETONLY setting, then it is undocumented as to which class will be selected. 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] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Jerry Caupain <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/26/2001 02:12 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Strange behaviour Hello everyone, I have noticed something strange. In my policy domain I have two management classes. One is called STANDARD and the other is called LOG_POLICY-MC. I want to use the last one only for my log server so I included the following line in my include/exclude file: INclude /logs/.../* log_policy-mc Managementclass STANDARD is the default managementclass. Why is it that all my other systems also use the LOG_POLICY-MC managementclass? It seems that the directories on my other systems are all bound to this managementclass. This can't be normalcan it??? Jerry Caupain
Strange behaviour????
Hello everyone, I have noticed something strange. In my policy domain I have two management classes. One is called STANDARD and the other is called LOG_POLICY-MC. I want to use the last one only for my log server so I included the following line in my include/exclude file: INclude /logs/.../* log_policy-mc Managementclass STANDARD is the default managementclass. Why is it that all my other systems also use the LOG_POLICY-MC managementclass? It seems that the directories on my other systems are all bound to this managementclass. This can't be normalcan it??? Jerry Caupain
TDP oracle
Hello everybody,
When I use TDP for Oracle the backup completes OK.
But when I issue the command
query filespace
TSM tells me the following:
Node NameFilespace Platform FilespaceCapacity Pct
Name Type (MB)
Util
-- --- -
-
SVRDBS02_ORC /WHEPPTDP API:ORAC- 0.00.0
Oracle LE
SUN
Question:
I can also see the files using the command show versions *
But why is the capacity and the Pct Util 0% ??
Does it have something to do with the DSMO_AVG_SIZE parameter?
Thanx in advance for any help!
Jerry Caupain
ADSM 3.1.0.8 for Solaris
Hi I want to install ADSM 3.1.0.8 on Solaris 5.8. Will this run properly? I read in the client requirements that only Solaris 2.6/2.7 is supported. Do I have to migrate to TSM 4.1 in order to backup a solaris 5.8 server? Kindest regards, Jerry Caupain >>> [EMAIL PROTECTED] 01/17/01 02:20pm >>> > I have a CopyPool volume, which is EMPTY and OFFSITE. The tape does not > remove from the pool and become a scratch volume again as it usually does. > > Moving data is not possible because it is empty > Deleting the volume is not possible because it contains data. (Even with > discard data) > Audit is not possible because the volume is offsite. When the volume returns to your site, run an 'AUDit Volume VolName Fix=Yes'. Richard Sims, BU
Re: Restoring a 3.7.3 database to a 4.1.2 server
Hey everyone, I'm the one who originally posted this subject. I installed 4.1 and applied the 4.1.2 patch. Then I restored the 3.7.2.database. My TSM server would't start. I ran an AUDITDB with FIX=NO and got the following message: ANR6646I AUDITDB: Auditing disaster recovery manager definitions. ANR4210I AUDITDB: Auditing physical volume repository definitions. ANRD tb.c(775): Column count mismatch for table MMS.Drives - expected 21, found 16 ANR0101E pvraudit.c(233): Error 18 opening table "MMS.Drives". ANR4142I AUDITDB: Database audit process terminated in error. I then tried the FIX=YES option and it still didn't work. As a last resort I did a DSMSERV UPGRADEDB.. It works fine now!! Thanx everyone, Jerry Caupain >>> [EMAIL PROTECTED] 01/15/01 04:25pm >>> Now _there_ is a good idea. Thanks once again, Richard. John Richard Sims wrote: > >...Our method of upgrading has always been to install the new > >version on a new machine, test it thoroughly, then to backup the DB on the old > >machine and restore it on the new one. This has the _enormous_ advantage that > >if anything goes wrong, we have only to turn the old machine back on and we're > >in business again, with a minimal loss of time. > > John - Proceeding carefully on a new machine is an excellent approach. >Given that the approach requires the same amount of db,log space on > both systems, an alternative to TSM db backup/restore would be to configure > the db,log space on the two systems to be equivalent, and then do a physical > copy of the db,log space to the other system, where the dsmserv start-up on > the new machine will upgrade the db. This should be much faster than a > logical db backup/restore, and a 3.7 CD would not be an issue. >Richard Sims, BU -- | John O'Neall | | | Centre de Calcul de l'IN2P3 | tel: +33 (0)4 78 93 08 80 | | Villeurbanne, France | fax: +33 (0)4 72 69 41 70 |
Restoring a 3.7.3 database to a 4.1.2 server
Hello everyone. I have a TSM 3.7.3 database backup and I want to restore thaht backup to a 4.1.2 server. Is this possible? I want to do this because I don't have the 3.7. software on CD anymore. Thanx, Jerry Caupain
Re: Monthly Full backups
Hello, I also make monthly full backups. I made another management class with a copymode of ABSOLUTE! Then I made an admin command schedule to make the absolute management class the default. I scheduled this admin command to run at the end of the month. Then I just run my normal INCREMENTAL backup schedules. They now make full backups. After completion I run another admin command schedule to make the old management class the default. Jerry >>> [EMAIL PROTECTED] 12/19/00 01:12pm >>> I am working on doing something similar. I hate the way a selective works, having to name all file systems etce etc. So I made another management class in the same policy that has copymode of ABSOLUTE. I am going to schedule a command instead of a backup. The command will be basically DSMC.exe incremental -OPTFILE=dsmfull.opt . THe DSMC.EXE has to have full path qualification. The dsmfull.opt is a copy of my normal option file with the new management class being defined in the INCLUDE/EXCLUDE statements. I added an INCLUDE ?:\...\* FULLMGMCLASS at the top. I have tested the line command and it works. I am now setting it up to test it as a scheduled event. My first attempt failed but I know it can work. It is similar to what we do to handle our DB2 backups which are scheduled through an external scheduler, (it schedules scripts to initiate backups using a different mgm class). Matt -Original Message- From: Forgosh, Seth [mailto:[EMAIL PROTECTED]] Sent: Monday, December 18, 2000 2:14 PM To: [EMAIL PROTECTED] Subject: Monthly Full backups Due to a failed server and the length of time required to restore it, my management has "requested" that we implement monthly full backups of all "critical" servers. How would I go about doing that? Any input would be greatly appreciated. Seth Forgosh
Re: What's the registration procedure on this ListServ again?
Send an email to the listserve and include this line in the body: SUBSCRIBE ADSM-L Greetz, Jerry >>> [EMAIL PROTECTED] 12/08/00 07:23am >>> Can anyone tell me what the steps are for registering a new person. I can' remember what the registration procedure is.
Re: TSM & remote procedure calls
Hey Mark, Thanx a lot for responding to my message. One thing is still very unclear to me. What happends when you set the TCPCLIENTPORT option in the options file? You said that the server-to-client is set through a port above 1024 randomly. Then I don't see the perpose of this option. Kind regards, Jerry Caupain [EMAIL PROTECTED] wrote: > > Mr. Caupain had commented that he had found the APAR that stated that ADSM does > not support backups through a firewall. > > While this is true, it is *not* due to the use of RPC calls. > > When an ADSM node and an ADSM server establish communication for a backup > or restore session, the client-to-server communication port is always 1500 > (unless otherwise set in the option files). The server-to-client > communication is set through a port above 1024 randomly chosen by the > server; this is so that the server can talk to multiple nodes concurrently > and easily. > > Unfortunately, the random setting is truly that; it cannot be changed to > use a desired port. If your firewall has the chosen port closed, there is > no comm and (therefore) no backup. If your firewall has all the possible > ports wide open...well, that defeats the purpose of a firewall. If your > firewall handles communication negotiation of the chosen port, your > connection will not work or your throughput will be *extremely* slow. > (That is our problem with the web servers we keep in a DMZ.) > > The number of workarounds is limited. > 1) You can create a second network for backups that bypasses the > firewall...but that again defeats the purpose of a firewall. (Unless, of > course, you choose to use a comm protocol other than TCP/IP for that > second connection.) > 2) You can put your ADSM server on the outside of the firewall, but that > solution opens itself up to a number of other problems. > 3) You can make access to the firewalled nodes available via username and > password. > > -- > Please respond to [EMAIL PROTECTED] > Mark Stapleton ([EMAIL PROTECTED])
TSM through Firewall **NOT** supported
Is this really true? I just can't imagine that TSM uses random ports like this. Can somebody please explain what this means? Anybody out there that uses TSM through a firewall? I know that this is not a strange thing! The official APAR: Apar IC27212 * USERS AFFECTED: All TSM Clients* * PROBLEM DESCRIPTION: Tivoli Storage Manager Client does not* * support the use of a firewall in the environment. When the * * client connects to the assigned port, the server rolls the * * client over to another random port to keep the initial port* * open for additional communication. Oncethe client is on * * another port, communication is severed unless the next* * selected port happens to be open in the firewall as well.* *** * RECOMMENDATION: It should be documented that TSM does not * * support access through a firewall.* *** PROBLEM CONCLUSION: The following statement has been documented in the readmes for all TSM clients: "The TSM clients work in conjunction with a TSM server to which they have access. Currently, TSM does not support the use of a firewall beween the server and the client."
Re: TSM & remote procedure calls
Hello Richard, I just got word that TSM through a firewall is NOT! supported. There is an official APAR for this. Apar IC27212 * USERS AFFECTED: All TSM Clients* * PROBLEM DESCRIPTION: Tivoli Storage Manager Client does not* * support the use of a firewall in the environment. When the * * client connects to the assigned port, the server rolls the * * client over to another random port to keep the initial port* * open for additional communication. Oncethe client is on * * another port, communication is severed unless the next* * selected port happens to be open in the firewall as well.* *** * RECOMMENDATION: It should be documented that TSM does not * * support access through a firewall.* *** PROBLEM CONCLUSION: The following statement has been documented in the readmes for all TSM clients: "The TSM clients work in conjunction with a TSM server to which they have access. Currently, TSM does not support the use of a firewall beween the server and the client." -- I haven't seen this in any readme file so far..have you?? And isn't this a form of RPC? Jerry Caupain Pink Elephant Business Online Services Richard Sims wrote: > > >I would like to know if TSM uses RPC (remote procedure calls) in any way. > > >From all that I've seen, ADSM and TSM have always used direct socket > communication, not RPC calls. You can verify this with the 'rpcinfo -p' > command to see what services are portmap-registered, and use something > like 'lsof' to see what processes are listening on those RPC ports. >Richard Sims, BU
TSM & remote procedure calls
Hello everyone, I would like to know if TSM uses RPC (remote procedure calls) in any way. We're going to use TSM across firewalls so it would be nice to know if this is the case. Anyone have more information about this? Kind regards, Jerry Caupain
Error with Novell Netware 5 backup
Hello everyone, When backing up my Netware 5 client I get the following error message: TSA500.NLM 5.3 259 This program cannot allocate a directory handle. ANS1087E Access to the specified file or directory is denied. I didn't get this error message the first time I backed up this client. Anyone know of any problems? My client is at 3.1.0.8 My server is at 3.1.2.54 Thanx a lot in advance, Jerry Caupain
Re: TSM V4.1
Hi, I have TSM 3.7. TSM 4.1 will soon be released. Will it just be a matter of going to the site and download 4.1 code or will we have to purchase 4.1? My guess is that we will have to buy 4.1 but I was hoping.. Jerry Charlotte Brooks wrote: > > This isn't meant to be a sales pitch - but thought listmembers might be > interested to know that V4.1 of TSM is now officially announced. You can > see details of new features(such as subfile backup, client file encryption, > LAN-free backup, integration with EMC Timefinder for Oracle db backup etc) > and associated products (including announcement letters and all the new > manuals) at the website,http://www.tivoli.com/tsm. > > Regards, Charlotte > Email: [EMAIL PROTECTED] > Ph (408) 927-3641 Fax (408) 927-3616 T/L 8-457-3641 > Project Leader, Storage Management, ITSO Almaden > http://ibm.com/redbooks
TSM vs Legato
Hello everyone, Does anyone have a documentation on the difference between TSM en Legato? I know TSM but I don't know anything about Legato. I could check out the web site but I know that real life experiences are also VERY important. Thanx a lot in advance, Jerry Caupain
