Re: ISC on WinXP or Unix
My PC has 512MB memory. I've just spoken to a collegue of mine and he managed to install the ISC on his PC (same specs as mine). Richard. Rainer Tammer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04-01-2005 08:29 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix Hello, how many memory does the PC have? Under AIX you need a minimum of 1GB memory to instell the ISC. I suspect that the same is true for Windows... Bye Rainer Tammer Richard van Denzel wrote: Nope, I've tried setting TMP, TEMP, TMPDIR to something else but no luck. Richard. Eivind Birkeland [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03-01-2005 12:54 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix Hi. On unix you may try to define the environment variable TMPDIR to a new tmp directory with enough space. This is a unix way to tell a system to use another tmp but it depend on the install script if it use the $TMPDIR. Regards Eivind Birkeland Richard van Denzel To: ADSM-L@VM.MARIST.EDU [EMAIL PROTECTED]cc: (bcc: Eivind Birkeland) LTN.NL Subject: ISC on WinXP or Unix Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 03.01.2005 12:11 Please respond to ADSM: Dist Stor Manager Hi All, Has anyone yet mastered to install the ISC on Windows XP? If so, what's the catch, because around 15-20% of installation it quits on my PC with an error. Also on Unix, is it possible to use another /tmp instead of /tmp? Because the Linux system I'm trying to install it on has not enough space available on /tmp and I don't feel like rearring all filesystems, just to make space in /tmp for the installation of ISC. Regards, Richard. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: ISC on WinXP or Unix
For some reason I'm getting Blind CCed on all responses on this list. Could somebody please check into this. I am a member of this list, but just noticed the blind cc. Perhaps it's normal?? Last week I was on vacation so that may have something to do with it as well. Thanks John Benik The information contained in this communication may be confidential, and is intended only for the use of the recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. Unencrypted, unauthenticated Internet e-mail is inherently insecure. Internet messages may be corrupted or incomplete, or may incorrectly identify the sender.
5.3 install
Hello, I have a question about the ISC/Admin 5.3v install. Should the ISC/Admin Center be installed before TSMv3 or does it matter? I know the ISC should be installed before the Admin Center. I also read that you need at least 2GB of menory if you plan on installing the ISC and Admin on the same system as TSMv5.3. Thanks in Advance!
Re: ISC on WinXP or Unix
Richard, It is my understanding that ISC is not supported on Windows XP. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard van Denzel Sent: Tuesday, January 04, 2005 7:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: ISC on WinXP or Unix My PC has 512MB memory. I've just spoken to a collegue of mine and he managed to install the ISC on his PC (same specs as mine). Richard. Rainer Tammer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04-01-2005 08:29 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix Hello, how many memory does the PC have? Under AIX you need a minimum of 1GB memory to instell the ISC. I suspect that the same is true for Windows... Bye Rainer Tammer Richard van Denzel wrote: Nope, I've tried setting TMP, TEMP, TMPDIR to something else but no luck. Richard. Eivind Birkeland [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03-01-2005 12:54 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix Hi. On unix you may try to define the environment variable TMPDIR to a new tmp directory with enough space. This is a unix way to tell a system to use another tmp but it depend on the install script if it use the $TMPDIR. Regards Eivind Birkeland Richard van Denzel To: ADSM-L@VM.MARIST.EDU [EMAIL PROTECTED]cc: (bcc: Eivind Birkeland) LTN.NL Subject: ISC on WinXP or Unix Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 03.01.2005 12:11 Please respond to ADSM: Dist Stor Manager Hi All, Has anyone yet mastered to install the ISC on Windows XP? If so, what's the catch, because around 15-20% of installation it quits on my PC with an error. Also on Unix, is it possible to use another /tmp instead of /tmp? Because the Linux system I'm trying to install it on has not enough space available on /tmp and I don't feel like rearring all filesystems, just to make space in /tmp for the installation of ISC. Regards, Richard. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: ISC on WinXP or Unix
How the am I going to administer my TSM Server(s). I sometimes have to do this on a 56k dial-up connection and I don't want to blow-up this line by running the java-sh.t remotely. Richard. Michael Hedden [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04-01-2005 13:28 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix Richard, It is my understanding that ISC is not supported on Windows XP. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard van Denzel Sent: Tuesday, January 04, 2005 7:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: ISC on WinXP or Unix My PC has 512MB memory. I've just spoken to a collegue of mine and he managed to install the ISC on his PC (same specs as mine). Richard. Rainer Tammer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04-01-2005 08:29 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix Hello, how many memory does the PC have? Under AIX you need a minimum of 1GB memory to instell the ISC. I suspect that the same is true for Windows... Bye Rainer Tammer Richard van Denzel wrote: Nope, I've tried setting TMP, TEMP, TMPDIR to something else but no luck. Richard. Eivind Birkeland [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03-01-2005 12:54 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix Hi. On unix you may try to define the environment variable TMPDIR to a new tmp directory with enough space. This is a unix way to tell a system to use another tmp but it depend on the install script if it use the $TMPDIR. Regards Eivind Birkeland Richard van Denzel To: ADSM-L@VM.MARIST.EDU [EMAIL PROTECTED]cc: (bcc: Eivind Birkeland) LTN.NL Subject: ISC on WinXP or Unix Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 03.01.2005 12:11 Please respond to ADSM: Dist Stor Manager Hi All, Has anyone yet mastered to install the ISC on Windows XP? If so, what's the catch, because around 15-20% of installation it quits on my PC with an error. Also on Unix, is it possible to use another /tmp instead of /tmp? Because the Linux system I'm trying to install it on has not enough space available on /tmp and I don't feel like rearring all filesystems, just to make space in /tmp for the installation of ISC. Regards, Richard. --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
Re: Strange time behaviour on Linux
On Jan 4, 2005, at 3:40 AM, Richard van Denzel wrote: Has anyone seen this strange time behaviour on Linux TSM Server (5.2.4.0)? I've specified TIMEformat 1 (24hr clock) in the dsmserv.opt, but it displays the time like TIMEformat is set to 4 (12hr clock). If so, has anyone got a cure for this behaviour? Well, not strange... Note that the Linux Admin Ref manual summary of server options does not include TIMEformat ... or DATEformat, or NUMBERformat. Those went away with TSM 3.7. Settings are now implicit by locale, which is governed by the LANGuage server option. We can't make detailed choices any more. Things change on us. Richard Sims http://people.bu.edu/rbs
Re: Strange time behaviour on Linux
Not every change is for the better :=( It however does not complain about the options being present in the dsmserv.opt file. Also when I do a q opt, I also see the options. Or do they call that backwards compatibility? Richard. Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04-01-2005 14:25 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: Strange time behaviour on Linux On Jan 4, 2005, at 3:40 AM, Richard van Denzel wrote: Has anyone seen this strange time behaviour on Linux TSM Server (5.2.4.0)? I've specified TIMEformat 1 (24hr clock) in the dsmserv.opt, but it displays the time like TIMEformat is set to 4 (12hr clock). If so, has anyone got a cure for this behaviour? Well, not strange... Note that the Linux Admin Ref manual summary of server options does not include TIMEformat ... or DATEformat, or NUMBERformat. Those went away with TSM 3.7. Settings are now implicit by locale, which is governed by the LANGuage server option. We can't make detailed choices any more. Things change on us. Richard Sims http://people.bu.edu/rbs
Volume History
Hello All! I am setting up a new TSM environment and I am using DRM for the first time. I have a couple of questions concerning volume history maintenance: 1. I had been doing delete volh type=dbb todate=today-15, but I have realized that if you set drmdbbackupexpiredays to 14 this should be the equivalent and then I won't lose tapes? 2. How often should I do a delete volh type=all? I usually do it as: delete volh todate=today-31 type=all. Would this be the correct standard? If I implement the above strategy, will I still have the ability to lose tapes? If so, how might I be able to prevent this? Thank you in advance! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
AW: Volume History
2) Don't do a delete volh type=all! Use multiple deletes to get rid of the entries you need to get rid of! Using type=all I once lost all entries for EXPORTed nodes. Kind regards Thomas Rupp Vorarlberger Illwerke AG -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Joni Moyer Gesendet: Dienstag, 04. Jänner 2005 14:53 An: ADSM-L@VM.MARIST.EDU Betreff: Volume History Hello All! I am setting up a new TSM environment and I am using DRM for the first time. I have a couple of questions concerning volume history maintenance: 1. I had been doing delete volh type=dbb todate=today-15, but I have realized that if you set drmdbbackupexpiredays to 14 this should be the equivalent and then I won't lose tapes? 2. How often should I do a delete volh type=all? I usually do it as: delete volh todate=today-31 type=all. Would this be the correct standard? If I implement the above strategy, will I still have the ability to lose tapes? If so, how might I be able to prevent this? Thank you in advance! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
strange reclaimation behavor
I have something strange going on with my reclaimations. I have the system issue a command in the afternoons to start reclaiming tapes by dropping the levels to 60%. I then have it issue another command around midnight to raise the levels back to 100%. When I get here in the morning I will usally find that reclaiming is still going on. I have verified that the stop_reclaim scripts are actually running by looking at the actlog for the time period involved. I end up doing a cancel process to get it to stop. I could understand it still running if it was in the middle of a 50-60 gig file but it's only moving small (several meg) files. It's had about eight hours to stop on it's own. I would have thought it would have found an opertunity to stop after eight hours. The contents of all of the scripts involved are correct. I have one starting the tapepool and another to start the copypool and another couple to raise the level back up. I alternate different pools each night. Any ideas here? I'm running 5.2.2 on a Win2k server with 4 LTO2 drives in a PV136T library. David Tyree Enterprise Backup Administrator South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
AW: strange reclaimation behavor
Copied from Richard Sims ADSM/TSM Quick Facts at http://people.bu.edu/rbs/ADSM.funcdir For an onsite storage pool, the new REClaim value is observed as the next volume is handled. For an offsite storage pool, the new REClaim value is *not* observed prior to the conclusion of the current process. Ref: Admin Guide manual topic Choosing a Reclamation Threshold, Lowering the Migration Threshold. -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Tyree, David Gesendet: Dienstag, 04. Jänner 2005 15:18 An: ADSM-L@VM.MARIST.EDU Betreff: strange reclaimation behavor I have something strange going on with my reclaimations. I have the system issue a command in the afternoons to start reclaiming tapes by dropping the levels to 60%. I then have it issue another command around midnight to raise the levels back to 100%. When I get here in the morning I will usally find that reclaiming is still going on. I have verified that the stop_reclaim scripts are actually running by looking at the actlog for the time period involved. I end up doing a cancel process to get it to stop. I could understand it still running if it was in the middle of a 50-60 gig file but it's only moving small (several meg) files. It's had about eight hours to stop on it's own. I would have thought it would have found an opertunity to stop after eight hours. The contents of all of the scripts involved are correct. I have one starting the tapepool and another to start the copypool and another couple to raise the level back up. I alternate different pools each night. Any ideas here? I'm running 5.2.2 on a Win2k server with 4 LTO2 drives in a PV136T library. David Tyree Enterprise Backup Administrator South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: strange reclaimation behavor
Hi, When you start reclamation it begins a process and decides which tapes it is going to reclaim based on the value given. These tapes can be seen in the activity log of the server. It will continue to reclaim until it has reclaimed all of the tapes in the list or you cancel the reclamation process. I have seen similar behavior in the migration process as well. If you set a storage pool to migrate (ie. By setting high=0 and low=0) then it will empty it out. If you subsequently reset the values (and the storage pool is now above the low value and below the high value) it will continue to migrate all of the data out. The migration_stop is there to set up the storage pools for the next day's backup. The reclamation stop doesn't seem to be terribly useful. I set my storage pools to a decent value all of the time (something like rec=90). Then on weekends (usually Friday afternoon) I set it to something deeper (currently rec=75 especially for the storage pools on the remote server). Michael Wheelock Integris Health -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tyree, David Sent: Tuesday, January 04, 2005 8:18 AM To: ADSM-L@VM.MARIST.EDU Subject: strange reclaimation behavor I have something strange going on with my reclaimations. I have the system issue a command in the afternoons to start reclaiming tapes by dropping the levels to 60%. I then have it issue another command around midnight to raise the levels back to 100%. When I get here in the morning I will usally find that reclaiming is still going on. I have verified that the stop_reclaim scripts are actually running by looking at the actlog for the time period involved. I end up doing a cancel process to get it to stop. I could understand it still running if it was in the middle of a 50-60 gig file but it's only moving small (several meg) files. It's had about eight hours to stop on it's own. I would have thought it would have found an opertunity to stop after eight hours. The contents of all of the scripts involved are correct. I have one starting the tapepool and another to start the copypool and another couple to raise the level back up. I alternate different pools each night. Any ideas here? I'm running 5.2.2 on a Win2k server with 4 LTO2 drives in a PV136T library. David Tyree Enterprise Backup Administrator South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ** This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). **
Creating a copy storage pool with a different retention time
Currently I have my policy set to retain file backups for 1 year. First I do my backups to my disk storage pools, I then have 2 copy pools, I copy the data to a non-collocated copy pool I send off site for 1 year, and then make a second copy which I keep onsite as a spare copy of my onsite-pool that gets migrated from the disk pool. What I would like to do is create another copy storage pool with a different retention, just 14 days. How would I do this, or the better question is is possible to do?? ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at postmaster at dor.state.ma.us. **
Re: strange reclaimation behavor
That's not right. I just proved it, inadvertently. I wanted to deliberately empty out a Disk Storage Pool. I had set lowmig=0 highmig=0 migprocess=4 and it had dutifully mounted 4 tapes and started emptying things out in a hurry. Then 10:00 came, and a daily schedule I had set months ago to shut down migration at that time, happened, and set it to highmig=75 lowmig=25. (Classic self-inflicted foot-shooting.) The effect was to cancel all of the migration processes, even though the storage pool was still 10% full. These process cancelations took effect when each process reached the end of the current file, so they didn't all happen at once although it was fairly quick. Fortunately all the tapes were still mounted so I got them started again quickly. But what I proved (again) was that Migration will stop as soon as you change the thresholds, not when the original lowmig has been reached. If you are seeing something different, I wonder if your client nodes are backing up very large individual files? Reclamation is different from migration. While it does not work on a pre-built list, you are correct that it continues until the end of the volume it is currently reclaiming. Once a reclamation process finishes work on a volume, then the server examines the thresholds all over again to see if it wants to reclaim another tape. So if the reclamation threshold for that storage pool has been changed, it will take effect at that time - at the end of the volume currently being processed, not after all volumes in some list have been processed. As a result, if you are doing this on some schedule, and you need the tape drives at a particular time for something else such as database backup, you can either change the reclamation theshold several hours in advance, or develop an OS script to query the process, parse the result, and cancel it by process number. Even then, the reclamation process cancelation will not take effect until the end of the file currently being processed. The strategy I use to make sure I get the tape drives for database backup at the scheduled time, is to run migration between reclamation and DB backup, since migration can stop itself and free the drives pretty quickly, in contrast to reclamation. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] ==I have not lost my mind -- it is backed up on tape somewhere.= Date: Jan 04, 09:45 From: Wheelock, Michael D nobody at nowhere.com Hi, When you start reclamation it begins a process and decides which tapes it is going to reclaim based on the value given. These tapes can be seen in the activity log of the server. It will continue to reclaim until it has reclaimed all of the tapes in the list or you cancel the reclamation process. =20 I have seen similar behavior in the migration process as well. If you set a storage pool to migrate (ie. By setting high=3D0 and low=3D0) then = it will empty it out. If you subsequently reset the values (and the storage pool is now above the low value and below the high value) it will continue to migrate all of the data out. The migration_stop is there to set up the storage pools for the next day's backup. The reclamation stop doesn't seem to be terribly useful. I set my storage pools to a decent value all of the time (something like rec=3D90). Then on weekends (usually Friday afternoon) I set it to something deeper (currently rec=3D75 especially for the storage pools on the remote server). =20 Michael Wheelock Integris Health -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Tyree, David Sent: Tuesday, January 04, 2005 8:18 AM To: ADSM-L AT VM.MARIST DOT EDU Subject: strange reclaimation behavor I have something strange going on with my reclaimations. I have the system issue a command in the afternoons to start reclaiming tapes by dropping the levels to 60%. I then have it issue another command around midnight to raise the levels back to 100%. When I get here in the morning I will usally find that reclaiming is still going on. I have verified that the stop_reclaim scripts are actually running by looking at the actlog for the time period involved. I end up doing a cancel process to get it to stop. I could understand it still running if it was in the middle of a 50-60 gig file but it's only moving small (several meg) files. It's had about eight hours to stop on it's own. I would have thought it would have found an opertunity to stop after eight hours. The contents of all of the scripts involved are correct. I have one starting the tapepool and another to start the copypool and another couple to raise the level back up. I alternate different pools each night. Any ideas here? I'm running 5.2.2 on a Win2k server with 4 LTO2 drives in a PV136T library. David Tyree Enterprise Backup Administrator South Georgia Medical Center 229.333.1155
Re: 5.3 install
Hello, you should install this way: 1. TSM Server 2.1. ISC 2.2. Admin Center The Admin Center could be on a separate machine. The ISC with the Admin Center is a big Java application. I think it is better to install this on a separate machine. Bye Rainer Timothy Hughes wrote: Hello, I have a question about the ISC/Admin 5.3v install. Should the ISC/Admin Center be installed before TSMv3 or does it matter? I know the ISC should be installed before the Admin Center. I also read that you need at least 2GB of menory if you plan on installing the ISC and Admin on the same system as TSMv5.3. Thanks in Advance!
baroc file
Hi list, im using TSM 5.1.5 and i enabled Uniquetecevents using the itsmuniq.baroc. The problem is that there are a lot of events that are parsing failling on TEC because that event classes are not declared in this baroc. Does anyone know anything abou that or has a complete baroc with all TSM event classes declared? TIA, === Demis Gonçalves Sr. Support Analyst NetControl Network Management São Paulo - Brazil Mobile: 55 11 9904-9684 ===
Re: ISC on WinXP or Unix
On Tuesday 04 January 2005 14:22, Richard van Denzel wrote: How the am I going to administer my TSM Server(s). I sometimes have to do this on a 56k dial-up connection and I don't want to blow-up this line by running the java-sh.t remotely. Welcome to the world of the new enterprise solutions :) Personally, I think the ISC will is a real disadvantage. We have a lot of small customers and having 1 GB of ram only for the ISC is ridiculous. We have an inhouse developed set of perl script that we use to monitor TSM and to do some administration that's not so easy to do with the web administrative interface (handling tapes, client option sets and so on). I think we will develop some more scripts and never use the ISC. Maybe we will never install it at all. Stef
Re: AIX Raw Logical Volumes, SSA RAID_1 mirroring w/ ITSM DB?
On Tuesday 04 January 2005 00:55, Roger Deschner wrote: I have heard that you should NOT use AIX JFS Mirroring on Raw Logical Volumes which are used to house the ITSM Log and Database. Instead, if you are using Raw Logical Volumes, you should use ITSM's mirroring facility. What I have heard is that there is a data integrity issue here. I am not doing this. The problem is that the LVM raid information is stored in the same data blocks used by tsm :( So this is no problem if you use hardware raid. Stef
Re: baroc file
Are all your TSM events failing to parse, or only
some of them?
I'm using TSM 5.2.3, so I don't really know what if
anything may have changed since 5.1.5, but my events
look like this:
TEC_CLASS :
IBMBACKUP ISA EVENT;
END
[...]
TEC_CLASS :
IBMTSM_BASE_SERVER ISA IBMBACKUP
DEFINES {
severity: SEVERITY, default= CRITICAL;
source: default = TSM;
tsm_message_severity: INTEGER;
tsm_message_number: INTEGER;
sub_source: default = TSM_SERVER;
tsm_server_platform: STRING;
};
END
[...]
TEC_CLASS:
TSM_SERVER_ANR ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0001 ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0002 ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0003 ISA IBMTSM_BASE_SERVER ;
END
[...]
The entire baroc file is about 800K, mainly because it
has an entry for every possible TSM message. I usually
just extract only the classes I plan to use and load
those in a custom baroc file.
Loren Cain
Digicon
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Demis
Gonçalves
Sent: Tuesday, January 04, 2005 12:15 PM
To: ADSM-L@VM.MARIST.EDU
Subject: baroc file
Hi list, im using TSM 5.1.5 and i enabled Uniquetecevents using the
itsmuniq.baroc. The problem is that there are a lot of events that are parsing
failling on TEC because that event classes are not declared in this baroc. Does
anyone know anything abou that or has a complete baroc with all TSM event
classes declared?
TIA,
===
Demis Gonçalves
Sr. Support Analyst
NetControl Network Management
São Paulo - Brazil
Mobile: 55 11 9904-9684
===
Re: 5.3 install
Thanks Rainer! Rainer Tammer wrote: Hello, you should install this way: 1. TSM Server 2.1. ISC 2.2. Admin Center The Admin Center could be on a separate machine. The ISC with the Admin Center is a big Java application. I think it is better to install this on a separate machine. Bye Rainer Timothy Hughes wrote: Hello, I have a question about the ISC/Admin 5.3v install. Should the ISC/Admin Center be installed before TSMv3 or does it matter? I know the ISC should be installed before the Admin Center. I also read that you need at least 2GB of menory if you plan on installing the ISC and Admin on the same system as TSMv5.3. Thanks in Advance!
Re: ISC on WinXP or Unix
Stef, The ISC is not required to use the Administration Center? Thanks Stef Coene wrote: On Tuesday 04 January 2005 14:22, Richard van Denzel wrote: How the am I going to administer my TSM Server(s). I sometimes have to do this on a 56k dial-up connection and I don't want to blow-up this line by running the java-sh.t remotely. Welcome to the world of the new enterprise solutions :) Personally, I think the ISC will is a real disadvantage. We have a lot of small customers and having 1 GB of ram only for the ISC is ridiculous. We have an inhouse developed set of perl script that we use to monitor TSM and to do some administration that's not so easy to do with the web administrative interface (handling tapes, client option sets and so on). I think we will develop some more scripts and never use the ISC. Maybe we will never install it at all. Stef
Multiple TSM servers on single machine.
Hi TSMers Did somebody has any experience with running more then one TSM5.2 servers on the same AIX machine? The problem I am having now it takes five days to run audit db. So I am thinking of splitting server to two and this way split database which now has 50G. My concerning here is how stable it will be? Does the servers do not interfere to each other because of bugs or any other reasons? May be some of you have some other concerning? Please share your experience. Sincerely Yuriy.
Re: baroc file
Hi Loren, until now all events has failing, then think the baroc im using
haven4t all classes. The baroc im using has only 80KB and came with the
version 5.2.3.2. The version 5.1.5 don4t have this baroc.
Demis
- Original Message -
From: Loren Cain [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Tuesday, January 04, 2005 3:58 PM
Subject: Re: baroc file
Are all your TSM events failing to parse, or only
some of them?
I'm using TSM 5.2.3, so I don't really know what if
anything may have changed since 5.1.5, but my events
look like this:
TEC_CLASS :
IBMBACKUP ISA EVENT;
END
[...]
TEC_CLASS :
IBMTSM_BASE_SERVER ISA IBMBACKUP
DEFINES {
severity: SEVERITY, default= CRITICAL;
source: default = TSM;
tsm_message_severity: INTEGER;
tsm_message_number: INTEGER;
sub_source: default = TSM_SERVER;
tsm_server_platform: STRING;
};
END
[...]
TEC_CLASS:
TSM_SERVER_ANR ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0001 ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0002 ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0003 ISA IBMTSM_BASE_SERVER ;
END
[...]
The entire baroc file is about 800K, mainly because it
has an entry for every possible TSM message. I usually
just extract only the classes I plan to use and load
those in a custom baroc file.
Loren Cain
Digicon
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Demis Gongalves
Sent: Tuesday, January 04, 2005 12:15 PM
To: ADSM-L@VM.MARIST.EDU
Subject: baroc file
Hi list, im using TSM 5.1.5 and i enabled Uniquetecevents using the
itsmuniq.baroc. The problem is that there are a lot of events that are
parsing failling on TEC because that event classes are not declared in this
baroc. Does anyone know anything abou that or has a complete baroc with all
TSM event classes declared?
TIA,
===
Demis Gongalves
Sr. Support Analyst
NetControl Network Management
Sco Paulo - Brazil
Mobile: 55 11 9904-9684
===
Re: baroc file
Demis,
I just sent you a copy of the itsmuniq.baroc file that
came with my TSM 5.2.3 system. Let's see if that fixes
the problem.
Loren Cain
Digicon
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Demis
Gonçalves
Sent: Tuesday, January 04, 2005 1:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: baroc file
Hi Loren, until now all events has failing, then think the baroc im using
haven4t all classes. The baroc im using has only 80KB and came with the
version 5.2.3.2. The version 5.1.5 don4t have this baroc.
Demis
- Original Message -
From: Loren Cain [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Tuesday, January 04, 2005 3:58 PM
Subject: Re: baroc file
Are all your TSM events failing to parse, or only
some of them?
I'm using TSM 5.2.3, so I don't really know what if
anything may have changed since 5.1.5, but my events
look like this:
TEC_CLASS :
IBMBACKUP ISA EVENT;
END
[...]
TEC_CLASS :
IBMTSM_BASE_SERVER ISA IBMBACKUP
DEFINES {
severity: SEVERITY, default= CRITICAL;
source: default = TSM;
tsm_message_severity: INTEGER;
tsm_message_number: INTEGER;
sub_source: default = TSM_SERVER;
tsm_server_platform: STRING;
};
END
[...]
TEC_CLASS:
TSM_SERVER_ANR ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0001 ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0002 ISA IBMTSM_BASE_SERVER ;
END
TEC_CLASS:
TSM_SERVER_ANR0003 ISA IBMTSM_BASE_SERVER ;
END
[...]
The entire baroc file is about 800K, mainly because it
has an entry for every possible TSM message. I usually
just extract only the classes I plan to use and load
those in a custom baroc file.
Loren Cain
Digicon
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Demis Gongalves
Sent: Tuesday, January 04, 2005 12:15 PM
To: ADSM-L@VM.MARIST.EDU
Subject: baroc file
Hi list, im using TSM 5.1.5 and i enabled Uniquetecevents using the
itsmuniq.baroc. The problem is that there are a lot of events that are
parsing failling on TEC because that event classes are not declared in this
baroc. Does anyone know anything abou that or has a complete baroc with all
TSM event classes declared?
TIA,
===
Demis Gongalves
Sr. Support Analyst
NetControl Network Management
Sco Paulo - Brazil
Mobile: 55 11 9904-9684
===
Re: Multiple TSM servers on single machine.
Yury, Not a problem running multiple instances of ITSM server on a single system. I have worked on machines with 4 ITSM servers on a single AIX system. Now the real question is why are you doing an audit db? This is not a command that should be run casually. You should only be running that when you absolutely have to. A 50 GB db although it is large it is not unusual nor unmanageable. You might want to give us some more of your reasons for doing an audit db as well as why you want to split the ITSM server. With more information we can give you some better informed answers. -- 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 === Yury Us wrote: Hi TSMers Did somebody has any experience with running more then one TSM5.2 servers on the same AIX machine? The problem I am having now it takes five days to run audit db. So I am thinking of splitting server to two and this way split database which now has 50G. My concerning here is how stable it will be? Does the servers do not interfere to each other because of bugs or any other reasons? May be some of you have some other concerning? Please share your experience. Sincerely Yuriy.
Windows Client v5.3.0
Hello all... I am looking for any experiences with this client version. We are experiencing lots of errors as they relate to W2K03 SystemState/SystemServices backups. I have found lots of IC's and APAR's relating to such. Going to a first relase of the client, is not that enticing, but does cover a lot of fixes. I have yet to find v5.2.4 that also has a lot of fixes as it related to W2K03 clients. Perhaps I am over looking. Is anyone using v5.3.0 yet? If not, what are some recommended TSM client levels for W2K03 servers? Just trying to do some research from those who know best before rolling it out to over 355 production W2K03 servers. Thanks in advance. Matt Adams Information Technology Services Deloitte Services LP 615-882-6861 www.deloitte.com This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Re: strange reclaimation behavor
Hi, I will attempt to clarify these issues here in regards to reclamation and migration. My explanation is based on several years of experience, course material that I have taught, and conversation with other ITSM experts. Another words I have not seen the actual code and without that no one can say for sure what it is doing. Migration: * Migration process(es) start with the himig threshold is passed. The number of processes started is controlled by maxproc value. * ITSM will evaluate which node has the most data in the storage pool at that time. * It then begins to move all of that nodes data on a per file space basis, i.e. each file space will get its own process. * If there are more processes available then there are file space for the node with the most data then it will start to move the node with the second most data, again a file space at a time. * It will move all the nodes data before it re-evaluates its threshold values. Therefore, once all the nodes data is moved it looks at the threshold and if it needs to continue migrating then it selects the node with the most data and start to move it. * This continues until the low threshold is achieved. * Therefore, it is possible for you to adjust the values and have migration continue for sometime, even to the point of emptying the pool beyond the low threshold value! Or it may stop right away depending one the situation. Reclamation of Primary Pools (note copy pools are discussed below) * When a reclamation value is adjusted down to trigger reclamation a list of tapes to be reclaimed is generated (visible in activity log) and these are the tapes to be reclaimed. * ITSM will start processing the tapes on the list. Each tape in this reclamation will be a separate process. * After completing a tape ITSM will re-evaluate the reclamation threshold and decide whether to continue. * Therefore, for primary storage pools you may in fact see the reclamation process end without completing all the tapes on the list, but it will not end (unless you cancel it) until the current tape has finished reclaiming. Reclamation of Copy Pools * The process is similar for copy pools but it is different. The big difference is that it process all the tapes at one time! * When reclaiming copy pool tapes that are off site it uses a primary copy of the data that is local. In order to improve the reclamation process ITSM will mount the primary tape and move all the NECESSARY files off that primary tape once it is mounted even if it means it is in fact reclaiming files from 2 or more different tapes. By doing this, there is no longer the concept of reclaiming a single copy pool tape it is in fact reclaiming all eligible tapes at once! * Therefore, when you adjust the reclamation threshold upwards it will not stop the reclamation of copy pool tapes. They only way that process ends is for it to finish all the tapes or you cancel it. Again I will reiterate, I have not seen the code for any of these processes, but I have through observation and through printed material deduced this as being the methodology that ITSM is using. I am open to others observations if they are different then mine. I wish that IBM would just clearly state what the algorithm truly is. BTW, there are many techniques that have been talked about on this list as ways of scripting around some of these difficulties. Good Luck and I hope this helped clear things up. -- 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 === Roger Deschner wrote: That's not right. I just proved it, inadvertently. I wanted to deliberately empty out a Disk Storage Pool. I had set lowmig=0 highmig=0 migprocess=4 and it had dutifully mounted 4 tapes and started emptying things out in a hurry. Then 10:00 came, and a daily schedule I had set months ago to shut down migration at that time, happened, and set it to highmig=75 lowmig=25. (Classic self-inflicted foot-shooting.) The effect was to cancel all of the migration processes, even though the storage pool was still 10% full. These process cancelations took effect when each process reached the end of the current file, so they didn't all happen at once although it was fairly quick. Fortunately all the tapes were still mounted so I got them started again quickly. But what I proved (again) was that Migration will stop as soon as you change the thresholds,
Re: Multiple TSM servers on single machine.
Well, The reason I ran audit this time was some weird behavior of server. Evidently I found a file space disappeared. But if was visible only if you query it with '*' in pattern. And you can't restore single file from that filespace, but only whole filespace. I am pretty confident that it was ok couple month ago. So when I removed that filespace from server all those files appeared as a part of root filesystem. Now I can query them without *. I was not sure how many such defects I had and run audit. Half year ago when I did audit, it took me 2.5 days, I ran it over weekends and it was acceptable, This time it lasted for 5 days, so half week company did not have any backup, oracle guys started screaming, because their backups eated almost all available diskspace. So in future I don't expect it to work faster, or having some kind of audit that you can run online, together with backup and reclamation. Simply I am trying to be proactive. Of cause here is always option to get better computer, but I don't believe that all of you are running your backups on the best computers in you company:) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: Tuesday, January 04, 2005 1:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Multiple TSM servers on single machine. Yury, Not a problem running multiple instances of ITSM server on a single system. I have worked on machines with 4 ITSM servers on a single AIX system. Now the real question is why are you doing an audit db? This is not a command that should be run casually. You should only be running that when you absolutely have to. A 50 GB db although it is large it is not unusual nor unmanageable. You might want to give us some more of your reasons for doing an audit db as well as why you want to split the ITSM server. With more information we can give you some better informed answers. -- 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 === Yury Us wrote: Hi TSMers Did somebody has any experience with running more then one TSM5.2 servers on the same AIX machine? The problem I am having now it takes five days to run audit db. So I am thinking of splitting server to two and this way split database which now has 50G. My concerning here is how stable it will be? Does the servers do not interfere to each other because of bugs or any other reasons? May be some of you have some other concerning? Please share your experience. Sincerely Yuriy.
Re: ISC on WinXP or Unix
On Tuesday 04 January 2005 19:14, Timothy Hughes wrote: Stef, The ISC is not required to use the Administration Center? Yep it is. But we don't need the Administraion Center :) Stef -- [EMAIL PROTECTED] Using Linux as bandwidth manager http://www.docum.org/
Re: strange reclaimation behavor
Mark thanks, This helped make things clearer for me also! Tim Mark D. Rodriguez wrote: Hi, I will attempt to clarify these issues here in regards to reclamation and migration. My explanation is based on several years of experience, course material that I have taught, and conversation with other ITSM experts. Another words I have not seen the actual code and without that no one can say for sure what it is doing. Migration: * Migration process(es) start with the himig threshold is passed. The number of processes started is controlled by maxproc value. * ITSM will evaluate which node has the most data in the storage pool at that time. * It then begins to move all of that nodes data on a per file space basis, i.e. each file space will get its own process. * If there are more processes available then there are file space for the node with the most data then it will start to move the node with the second most data, again a file space at a time. * It will move all the nodes data before it re-evaluates its threshold values. Therefore, once all the nodes data is moved it looks at the threshold and if it needs to continue migrating then it selects the node with the most data and start to move it. * This continues until the low threshold is achieved. * Therefore, it is possible for you to adjust the values and have migration continue for sometime, even to the point of emptying the pool beyond the low threshold value! Or it may stop right away depending one the situation. Reclamation of Primary Pools (note copy pools are discussed below) * When a reclamation value is adjusted down to trigger reclamation a list of tapes to be reclaimed is generated (visible in activity log) and these are the tapes to be reclaimed. * ITSM will start processing the tapes on the list. Each tape in this reclamation will be a separate process. * After completing a tape ITSM will re-evaluate the reclamation threshold and decide whether to continue. * Therefore, for primary storage pools you may in fact see the reclamation process end without completing all the tapes on the list, but it will not end (unless you cancel it) until the current tape has finished reclaiming. Reclamation of Copy Pools * The process is similar for copy pools but it is different. The big difference is that it process all the tapes at one time! * When reclaiming copy pool tapes that are off site it uses a primary copy of the data that is local. In order to improve the reclamation process ITSM will mount the primary tape and move all the NECESSARY files off that primary tape once it is mounted even if it means it is in fact reclaiming files from 2 or more different tapes. By doing this, there is no longer the concept of reclaiming a single copy pool tape it is in fact reclaiming all eligible tapes at once! * Therefore, when you adjust the reclamation threshold upwards it will not stop the reclamation of copy pool tapes. They only way that process ends is for it to finish all the tapes or you cancel it. Again I will reiterate, I have not seen the code for any of these processes, but I have through observation and through printed material deduced this as being the methodology that ITSM is using. I am open to others observations if they are different then mine. I wish that IBM would just clearly state what the algorithm truly is. BTW, there are many techniques that have been talked about on this list as ways of scripting around some of these difficulties. Good Luck and I hope this helped clear things up. -- 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 === Roger Deschner wrote: That's not right. I just proved it, inadvertently. I wanted to deliberately empty out a Disk Storage Pool. I had set lowmig=0 highmig=0 migprocess=4 and it had dutifully mounted 4 tapes and started emptying things out in a hurry. Then 10:00 came, and a daily schedule I had set months ago to shut down migration at that time, happened, and set it to highmig=75 lowmig=25. (Classic self-inflicted foot-shooting.) The effect was to cancel all of the migration processes, even though the storage pool was still 10% full. These process cancelations took effect when each process reached the end of the current file, so they
Re: Multiple TSM servers on single machine.
I would be cautious of the tendency to jump to the conclusion that the database had a problem because you could not query a filespace. As seen in numerous past postings, filespace visibility issues are often due to character set code page inconsistencies between the client which created the filespace and the thing doing the querying...which is to say, Unicode differences. Whatever the case, make sure your problem is very well defined before embarking upon anything as drastic as a db audit. (In ADSM QuickFacts, see entry dsmserv AUDITDB and the warning about doing them on your own.) Richard Sims http://people.bu.edu/rbs On Jan 4, 2005, at 2:10 PM, Yury Us wrote: he reason I ran audit this time was some weird behavior of server. Evidently I found a file space disappeared. But if was visible only if you query it with '*' in pattern. And you can't restore single file from that filespace, but only whole filespace. I am pretty confident that it was ok couple month ago. So when I removed that filespace from server all those files appeared as a part of root filesystem. Now I can query them without *. I was not sure how many such defects I had and run audit. Half year ago when I did audit, it took me 2.5 days, I ran it over weekends and it was acceptable, This time it lasted for 5 days, so half week company did not have any backup, oracle guys started screaming, because their backups eated almost all available diskspace. So in future I don't expect it to work faster, or having some kind of audit that you can run online, together with backup and reclamation. Simply I am trying to be proactive. Of cause here is always option to get better computer, but I don't believe that all of you are running your backups on the best computers in you company:)
Re: strange reclaimation behavor
I will attempt to clarify these issues here in regards to reclamation and migration. My explanation is based on several years of experience, course material that I have taught, and conversation with other ITSM experts. Another words I have not seen the actual code and without that no one can say for sure what it is doing. Migration: * Migration process(es) start with the himig threshold is passed. The number of processes started is controlled by maxproc value. The setting is migpr for migration. maxproc is an option on the backup stg command for how many processes to run. * ITSM will evaluate which node has the most data in the storage pool at that time. * It then begins to move all of that nodes data on a per file space basis, i.e. each file space will get its own process. I don't think this is necessarily correct. Each filespace does not get it's own (server) process, unless that is how it works for colloction by filespace. With Collocate set to yes, this certainly cannot work that way, as it would be contrary to the collocation setting on the storage pool. Each node would be dedicated to a server process. * If there are more processes available then there are file space for the node with the most data then it will start to move the node with the second most data, again a file space at a time. * It will move all the nodes data before it re-evaluates its threshold values. Therefore, once all the nodes data is moved it looks at the threshold and if it needs to continue migrating then it selects the node with the most data and start to move it. * This continues until the low threshold is achieved. * Therefore, it is possible for you to adjust the values and have migration continue for sometime, even to the point of emptying the pool beyond the low threshold value! Or it may stop right away depending one the situation. Reclamation of Primary Pools (note copy pools are discussed below) * When a reclamation value is adjusted down to trigger reclamation a list of tapes to be reclaimed is generated (visible in activity log) and these are the tapes to be reclaimed. * ITSM will start processing the tapes on the list. Each tape in this reclamation will be a separate process. * After completing a tape ITSM will re-evaluate the reclamation threshold and decide whether to continue. * Therefore, for primary storage pools you may in fact see the reclamation process end without completing all the tapes on the list, but it will not end (unless you cancel it) until the current tape has finished reclaiming. Reclamation of Copy Pools * The process is similar for copy pools but it is different. The big difference is that it process all the tapes at one time! * When reclaiming copy pool tapes that are off site it uses a primary copy of the data that is local. In order to improve the reclamation process ITSM will mount the primary tape and move all the NECESSARY files off that primary tape once it is mounted even if it means it is in fact reclaiming files from 2 or more different tapes. By doing this, there is no longer the concept of reclaiming a single copy pool tape it is in fact reclaiming all eligible tapes at once! * Therefore, when you adjust the reclamation threshold upwards it will not stop the reclamation of copy pool tapes. They only way that process ends is for it to finish all the tapes or you cancel it. Again I will reiterate, I have not seen the code for any of these processes, but I have through observation and through printed material deduced this as being the methodology that ITSM is using. I am open to others observations if they are different then mine. I wish that IBM would just clearly state what the algorithm truly is. BTW, there are many techniques that have been talked about on this list as ways of scripting around some of these difficulties. Good Luck and I hope this helped clear things up. -- 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 === Roger Deschner wrote: That's not right. I just proved it, inadvertently. I wanted to deliberately empty out a Disk Storage Pool. I had set lowmig=0 highmig=0 migprocess=4 and it had dutifully mounted 4 tapes and started emptying things out in a hurry. Then 10:00 came, and a
defining library path(device) in solaris
Hello all, I have installed tivoli in solaris 8 machine which is attached to a library storEdge L1000. It has 2 drives. The path of the drives are known as(/dev/rmt/1 , /dev/rmt/2) But i am not knowing what is the path for robotic arm. No idea what it should be.. please help me in configuring the device path of robotic arm in solaris 8. waiting for your replies. Advance Thanks Geetha Thanu -
Re: ISC on WinXP or Unix
Hello, Timothy Hughes wrote: Stef, The ISC is not required to use the Administration Center? Unfortunately not... The ISC is the base and the Administration Center is only a plug in. The ISC is like you order one bouillon cube and they delivers the bouillon cube on a freight train. Bye Rainer Thanks Stef Coene wrote: On Tuesday 04 January 2005 14:22, Richard van Denzel wrote: How the am I going to administer my TSM Server(s). I sometimes have to do this on a 56k dial-up connection and I don't want to blow-up this line by running the java-sh.t remotely. Welcome to the world of the new enterprise solutions :) Personally, I think the ISC will is a real disadvantage. We have a lot of small customers and having 1 GB of ram only for the ISC is ridiculous. We have an inhouse developed set of perl script that we use to monitor TSM and to do some administration that's not so easy to do with the web administrative interface (handling tapes, client option sets and so on). I think we will develop some more scripts and never use the ISC. Maybe we will never install it at all. Stef
Re: ISC on WinXP or Unix
Stef, I totally concur with you. I also use quite a lot of (ksh) scripts and I don't feel like throwing them overboard, especially because the guys are our servicedesk do the tapehandling and they have little knowledge of TSM. Richard. Stef Coene [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04-01-2005 18:25 Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: ISC on WinXP or Unix On Tuesday 04 January 2005 14:22, Richard van Denzel wrote: How the am I going to administer my TSM Server(s). I sometimes have to do this on a 56k dial-up connection and I don't want to blow-up this line by running the java-sh.t remotely. Welcome to the world of the new enterprise solutions :) Personally, I think the ISC will is a real disadvantage. We have a lot of small customers and having 1 GB of ram only for the ISC is ridiculous. We have an inhouse developed set of perl script that we use to monitor TSM and to do some administration that's not so easy to do with the web administrative interface (handling tapes, client option sets and so on). I think we will develop some more scripts and never use the ISC. Maybe we will never install it at all. Stef
