TDP for mail 5.1.2 and Exchange2003 SP1
Hello Does anyone know if Exchange2003 with SP1 is supported? We are running Exchange2003 and TDP for mail ver 5.1.2 now and the exchange-admin wants to upgrade Exchange2003 to SP1. Regards Niklas Lundström Swedbank
Re: restore causing mount tape to status reserved?
On Sun, 6 Jun 2004 21:51:19 -0500 Alexander Lazarevich [EMAIL PROTECTED] wrote: TSM 5.1.6.5 on windows 2K server. When I run a simple restore, nothing that I haven't done a hundred times before, the restore hangs after a minute or two, and doesn't do squat, forever. The only thing I notice is the q mount command shows something odd: tsm:q mount ANR8376I Mount point reserved in device class LTOCLASS1, status: RESERVED. ANR8334I 1 matches found. I've never set anything in the server to be 'reserved'. This is happening completely unexpectedly. I have no idea on what to do, as the actlog shows zipo on this error. I don't even think TSM thinks it's an error. I will work on it in the monring, but maybe someone has a quick fix. Didn't find one in the list... It sounds like your restore process needs a tapedrive but no drives are on-line... Any ideas? Alex -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 3000Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Re: restore causing mount tape to status reserved?
TSM 5.1.6.5 on windows 2K server. When I run a simple restore, nothing that I haven't done a hundred times before, the restore hangs after a minute or two, and doesn't do squat, forever. The only thing I notice is the q mount command shows something odd: tsm:q mount ANR8376I Mount point reserved in device class LTOCLASS1, status: RESERVED. ANR8334I 1 matches found. I've never set anything in the server to be 'reserved'. This is happening completely unexpectedly. I have no idea on what to do, as the actlog shows zipo on this error. I don't even think TSM thinks it's an error. I will work on it in the monring, but maybe someone has a quick fix. Didn't find one in the list... I believe that the only quick fix is to restart the TSM server. A Reserve is a special device command to retain control of a tape drive or the like in an environment where the drive is shared by multiple hosts, over multiple open-close processing sequences. In AIX, this is accomplished at the driver level by issuing an ioctl() to perform an SIOC_RESERVE command. You can do 'SHow MP' and possibly 'SHow LIBrary' to verify this status and fully identify the drive at issue. I would check back in the Activity Log to determine what circumstances were involved in that drive becoming reserved, to try to possibly identify an issue with an operation sequence or allied software component which precipitates the condition, to avoid or correct it. Elevating the maintenance level of your TSM server may or may not alleviate the possibility of recurrence. Richard Sims
Re: TDP for mail 5.1.2 and Exchange2003 SP1
Niklas, Yes. Exchange 2003 with the recently released SP1 is supported. Del ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/07/2004 04:27:54 AM: Hello Does anyone know if Exchange2003 with SP1 is supported? We are running Exchange2003 and TDP for mail ver 5.1.2 now and the exchange-admin wants to upgrade Exchange2003 to SP1. Regards Niklas Lundström Swedbank
Re: archive - inactive files?
With my idea, you would export dude2, so you won't lose the inactive files. Here's the order: 1. Rename dude1 to dude2 2. Register new dude1 3. Export dude2 Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. Alexander Lazarevich [EMAIL PROTECTED] To C.EDU[EMAIL PROTECTED] Sent by: ADSM:cc Dist Stor Manager Subject [EMAIL PROTECTED] Re: archive - inactive files? .EDU 06/05/2004 11:30 AM Please respond to ADSM: Dist Stor Manager I still can't get confirmation from the manual: Does exporting a node preserve all the inactive (deleted) files? Secondarily, if I rename dude1 to dude2, won't I lose all the deleted files? I have to export dude1 to preserve the inactive files, assuming export preserves those, right? Thanks for the help, Alex On Fri, 4 Jun 2004, Nicholas Cassimatis wrote: Or rename node dude1 to dude2, and export dude2, register new dude1... Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. Stapleton, Mark [EMAIL PROTECTED] ERBEE.COM To Sent by: ADSM: [EMAIL PROTECTED] Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: archive - inactive files? 06/04/2004 07:49 PM Please respond to ADSM: Dist Stor Manager From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Cassimatis Unfortunately, that won't work to keep everything as it is now. The inactive files will expire per the rules established for them - after your RetainExtra duration passes, you'll only have active files (except for the Last Versions, retained per the RetainLast setting). You can setup a new management class with all settings at /no limit, configure the client to use that for all files (new domain may work best) run one last backup to rebind everything, then do the node rename. I can't think of an easier way to do what Alex is trying to accomplish. I can: export node dude1 devc=tape_device_class The export will keep forever. dude1's data can be imported whenever it is needed. Oh, and name the new node dude2. -- Mark Stapleton inline: graycol.gifinline: pic00688.gifinline: ecblank.gif
Re: TSM, Novell and Groupwise, a menage a trois from hell or a polygamous match made in heaven?
TSM does not use the TSA's for doing Groupwise backups. The only thing you can really do is backup the domain/po directories using an Open File Agent. You are correct about TSM using the TSA's for files and NDS however. Troy Frank Network Services University of Wisconsin Medical Foundation 608.829.5384 [EMAIL PROTECTED] 6/6/2004 11:26:12 PM Hi all, This one is for Netware and groupwise admins. I'm looking at putting TSM servers into some small sites which run Netware servers. Part of the equation is that they run Groupwise post offices as well. I'm not a Novell person, but I've looked at the TSM, Novell and Groupwise documentation and this is how it seems to me. The SMDR component and TSAFS provide SMS services which allow objects to be presented to a backup product. When you run *any* other product's tsa, then the product's objects are expressed within the SMS object tree and *should* therefore be accessible to any backup product which uses SMS services. As an example, the TSM product uses TSANDS to backup the edirectory using exactly this mechanism. However, the TSM client seems to have a different interface built in for each TSA - to work with NDS objects, it is necessary to specify nds: as part of the name, ie, NDS Support has been added into the TSM client rather than extending the general functionality of SMS backup. BackupExec can backup Groupwise objects as easily as any other SMS object. I've heard that TSM cannot. 1. Is it still the case that TSM can't backup Groupwise objects? 2. Is my limited understanding of the Novell backup environment and its interaction with TSM correct? 3. Is there any way to couple the Groupwise and TSM APIs other than SMS? I'm aware of the DBCOPY and GWBACKUP utilities, but they leave a lot to be desired and are not incremental in nature. Many thanks for your comments Steve. PS I've only had the one reply to my post about backup rates for file servers. Please, if you have any data, share it. Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia *** This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone or by return email. You should also delete this email and destroy any hard copies produced. *** Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: restore causing mount tape to status reserved?
On Mon, 7 Jun 2004 07:48:50 -0400 Richard Sims [EMAIL PROTECTED] wrote: TSM 5.1.6.5 on windows 2K server. When I run a simple restore, nothing that I haven't done a hundred times before, the restore hangs after a minute or two, and doesn't do squat, forever. The only thing I notice is the q mount command shows something odd: tsm:q mount ANR8376I Mount point reserved in device class LTOCLASS1, status: RESERVED. ANR8334I 1 matches found. I've never set anything in the server to be 'reserved'. This is happening completely unexpectedly. I have no idea on what to do, as the actlog shows zipo on this error. I don't even think TSM thinks it's an error. I will work on it in the monring, but maybe someone has a quick fix. Didn't find one in the list... I believe that the only quick fix is to restart the TSM server. A Reserve is a special device command to retain control of a tape drive or the like in an environment where the drive is shared by multiple hosts, over A reserv also happens when a process needs multiple devices (eg two tapedrives) in different deviceclasses and only one is available. That one is then reserved, while the process waits for the other to become available, making sure the reserved drive is still available for use when the other resource becomes available. Happens to us all the time. I'd check 'q dr' and 'q path'. -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 3000Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Primary Pool and Copypool Relationship
Hi All, I moved a lot of data out of Primary Pool #1 and into Primary Pool # 2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool #2. It appears that the Copy Pool # 1 still has the backup of this data...which I expected. The problem is that it appears the data was also backed up to copy pool #2 as I moved the datathis was not expected. Does this sound like expected behavior? If so, any ideas for how to clean up the extra copy in Copy Pool #1??? Thanks! Dave Nicholson Whirlpool Corporation
Generate backupset problem, solution and question
Hi there, You guys have been great and helpful in the past, therefore I have one more question/mystery to solve. Situation : windows 2000SP3, TSM Version 5, Release 1, Level 5.0 Ibm lto3600 library with single drive. 2 storage pools : 'diskbackup' migrating to 'tapebackup' And tape backup (the stgpoolnames speak for themselves so I'm not explaining what they mean :)) client A computer backups network shares. This computer belongs to standart policy domain and its files land in the diskbackup storage pool. The usual way was to migrate this storage pool to tape after a while. However, a need arose to regulary create backupsets from the A's data. So, since I have only a single drive and make backupsets to tape I needed to have my data on disk. I changed the migration settings and stopped the migration from happening, executed selective backup command and backed up all the shares that are usually backuped up with the 'incremental' schedule (the shares are part of the domain). So it seemed to me that now I must have all my data on disk and ready to create a backupset. Sadly, but no ! The process gets terminated and message telling 'insufficient mount points' is written to actlog. I try generating backups for single A client's filespaces (which is the exact string as in my selective backup command) - same error. Ok, from the error I get I make a logical conclusion that the backupset process wants to load some data from tapes but since there is only one drive it fails). So I load up the GUI tsm client, go to the restore section and see that 'backup date' of all the files is the day of the selective backup. I check a single filespace and click restore. The tsm tries to mount a tape that has 'last written' to it 10 days ago. After canceling this, checking a single file (or a bunch of them) the restore process completes successfully. After that I can already successfully restore the whole filespace and even generate backupsets. So my question : I have a problem, I have a solution (found out by trial and error method), but what's happening in the background ? Why does restore function want to load older files from tapes instead of newer ones (selective backup) from disk ? Why does single file restore somehow 'rebind' files to another storage pool. Or maybe I could just execute some commands in verbose or debug mode and get more information about what's happening ? I will grateful for pointing out any help section, article or previous posts (I tried to search but found nothing useful). Thanks for your time. [EMAIL PROTECTED]
Re: Primary Pool and Copypool Relationship
Yes this is how TSM works. You can have multiple copy pools for 1 Primary Pool. See http://msgs.adsm.org/cgi-bin/get/adsm0404/221.html for one way to delete this data. (This assumes that there is still domr data that you want on Copy Pool #1) -Original Message- From: David Nicholson [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: Primary Pool and Copypool Relationship Hi All, I moved a lot of data out of Primary Pool #1 and into Primary Pool # 2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool #2. It appears that the Copy Pool # 1 still has the backup of this data...which I expected. The problem is that it appears the data was also backed up to copy pool #2 as I moved the datathis was not expected. Does this sound like expected behavior? If so, any ideas for how to clean up the extra copy in Copy Pool #1??? Thanks! Dave Nicholson Whirlpool Corporation
Re: ANS3408W The volume /xxx/xxxx contains bad blocks
Phil, You will find the message is in the dsmc help facility and the messages manual... after a fashion. Look up message ANS13408W and you should find information there. It's listed as 13408 instead of 3408 due to how the message number is represented internally (and that needs to be investigated on our end). But otherwise the message is there just in an unlikely place. Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] 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. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/04/2004 02:35:52: Hi all, Can anyone shed any light on the above message from an AIX 5.2 (recently upgraded from AIX 4.3.3) client at TSM client 5.1.6, when doing an image backup? Server is AIX at ver 5.1.5. I can't find any reference anywhere. Many Thanks Phil Jones e-mail: remove-this[EMAIL PROTECTED]
Re: ANS3408W The volume /xxx/xxxx contains bad blocks
The message manual content is derived from the same source as what we include in the product help facility (dsmc help). Differences from the published/online manuals would only be due to a lag between the time we add/change a message in the help facility and the time it takes to get the changes into the formal publications. Because of how we develop the messages, barring a build or package defect, if we can issue the message, we can at least display help for it via dsmc help. See my response to the originator of this thread for the specifics behind this messaging issue. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] 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. ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 06/04/2004 05:22:18: Can anyone shed any light on the above message from an AIX 5.2 (recently upgraded from AIX 4.3.3) client at TSM client 5.1.6, when doing an image backup? Server is AIX at ver 5.1.5. I can't find any reference anywhere. http://www.google.com/search?hl=enie=UTF-8edition=usq=ANS3408W Which lead to the old, ADSM meaning for ANS3408W. The message number seems to have been repurposed - but the developer neglected to pass its doc on to the publications people. I see no inkling of that message anywhere, by number or textual keywords. IBM owes us some explanation of the message's meaning. Richard Sims
Re: 3590 cleaning scheduling
The problem with this setting is that with 100+ clients backing up to a collocated tape pool, performs at least 100 mounts every day (the ATL LM says over 250 tape mounts per day), it is cleaning the drives 2-3 times a day. I have decided to take IBM's recommendation and try letting the drives control the cleaning process, rather than the ATL LM. Thorson, Paul [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/04/2004 07:43 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: 3590 cleaning scheduling Hello, If you read in the 3494 Operator's Guide, it mentions that the performance of the drive is monitored to determine when to clean it, which I believe is done by measuring voltages across the head. For most TSM servers, this monitored cleaning will occur much sooner and more often than the scheduled cleaning defaults. So, Zoltan, you should not have to adjust the scheduled cleaning option. If the current setting is to clean the drives every 65 mounts, you may be seeing those cleanings in addition to the as needed cleanings initiated by the LM. I would be tempted to set it back up to 999, and see if the cleanings are reduced without causing any TSM I/O errors. Check with your CE first though - maybe he/she knows the history of why it was reduced in the first place. Perhaps it was to address a problem with older technology drives (i.e, 3490). Milton, that's a clever idea to keep an eye on the cleaning history - I've back-tracked that information often when trouble-shooting drive problems. Knowing it beforehand would be an excellent way to predict failures. - Paul -Original Message- From: Johnson, Milton [mailto:[EMAIL PROTECTED] Sent: Friday, June 04, 2004 2:10 PM To: [EMAIL PROTECTED] Subject: Re: 3590 cleaning scheduling Clean Me requests are also generated when the drive encounters a problem. A faulty/failing drive can cause an abnormal spike in cleaning requests. I monitor these requests daily as an indicator of drive health. I have found that an increase in Clean Me messages correlates with an Attn Drive message on the LCD of the 3590E1A. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Friday, June 04, 2004 1:10 PM To: [EMAIL PROTECTED] Subject: OT?: 3590 cleaning scheduling Lately, I have been noticing lots of Clean Me messages in ERRPT of the TSM AIX system, for the 3590E1A drives it uses. So, I started looking into the setting on the 3494, which controls cleaning. Currently, it is set to clean by usage (65). Upon digging through the IBM TotalStorage Enterprise Tape - A Practical Guide Redbook, I found the paragraph: We recommend that drive cleaning be based on a drive request. Use time-based cleaning only if drive usage is very low. For 3590 tape drives, use a value of 999 mounts to perform cleaning based on a drive request rather than an initiated library. So, what do you use to control the cleaning cycle for your 3494/3590 drives ? Do you follow the above recommendation ?Is this a global recommendation that can be applied to *ALL* 359x drives ? Inquiring minds want to know ?
TDP for Exchange
I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? Thanks, Ralph
Re: TDP for Exchange
generate a backupset. keep that. -Original Message- From: Levi, Ralph [SMTP:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: TDP for Exchange I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? Thanks, Ralph
ANS3604s
Hello all, config Novell os 6 TSM client 5.2.2 When I click on backup or restore on the Web client Gui I get the following message: ANS2604s the web client agent was unable to authenticate the the server Can anyone tell me what might be wrong? This server is part of a cluster we are setting up
Re: TDP for Exchange
From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. -- Mark Stapleton
Re: TDP for Exchange
Sorry, then I am out of ideas. Well, how about setting up a separate pool, just for the long retention data, and do a special backup to that pool? ... Just a thought. Obviously backupset kind of thing would be preferrable. -Original Message- From: Stapleton, Mark [SMTP:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 12:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. -- Mark Stapleton
Re: TDP for Exchange
I need to take the oldest version I have an keep that one (forever...). After that, I can continue keeping my normal retention. Thanks all for any suggestions. Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack Sent: June 07, 2004 1:30 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange Sorry, then I am out of ideas. Well, how about setting up a separate pool, just for the long retention data, and do a special backup to that pool? ... Just a thought. Obviously backupset kind of thing would be preferrable. -Original Message- From: Stapleton, Mark [SMTP:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 12:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. -- Mark Stapleton
Re: TDP for Exchange
From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. From: Stapleton, Mark [SMTP:[EMAIL PROTECTED] I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack Sorry, then I am out of ideas. Well, how about setting up a separate pool, just for the long retention data, and do a special backup to that pool? ... Just a thought. Obviously backupset kind of thing would be preferrable. An alternative is to run a second daily backup of your Exchange data using an alternate management class that never allows expiration. You can then pile your extra backups onto a separate set of tape volumes. At least that way, you don't have a really nasty one-backup-one-tape situation. (Keep in mind, of course, that this means a stream of tape volumes going to the vault, never to return.) However, this will only help you with ongoing backups, not the ones you already have. About the only thing to do with his existing backups is to run an export of the node to tape volume(s). I can't think of another way to guarantee getting the last backup on the existing backup list. Ralph, are you sure that you have to keep a copy of old Exchange backups *forever*? (It sounds like pie-in-the-sky lawyer talk to me; as I understand it, the current legal atmosphere doesn't require it.) -- Mark Stapleton
Re: TDP for Exchange - The answer is not nice!
Hi Ralph, I believe you have 2 options. 1. Restore and re-save to a permanent management class... goto 3 2. remove the tape with the backup on it, protect from overwrite ... goto 3 3. Save the current TSM Database, Volhist, Devconfig and prepare files. (Use NT Backup or something that you can trust to be able to read in the future!!! DVD ROM's are too short lifetime for what you need) (2) You can still get to your data if you set the system date to today (7th June 2004) before you build a restore environment... I have done it!!! (Arrrhhh!!!) It rather depends on whether you expect to ever have to read the data again!!! It will be a pain in (2) but is the least work for now. BTW: Don't forget to record the EXACT Version of Exchange, and TSM, and ALL the SP's/hotfixs.. and have ALL the software media available for the restore in the future... its not going to be available on the web. Record any current passwords before you start - you won't remember them! Also, you need an NT domain controller to re-install Exchange, so make sure that is available to a current point in time too. Maybe an idea to hold onto an old PC or two and an NT install... The current technology won't run NT very well in the future. Feel free to contact me direct if you get stuck. I am serious about the above, although it looks like I am joking (Its a really hard task to protect MS Exchange to this level) It could be worse... I am currently trying to get Exchange back to 2000 from Arcserve 6.0!!! Best Regards Good Luck Tony Morgan [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: 07 June 2004 18:23 To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. -- Mark Stapleton This e-mail and any files transmitted with it, are confidential and intended solely for the use of the addressee. The content of this e-mail may have been changed without the consent of the originator. The information supplied must be viewed in this context. If you have received this e-mail in error please notify our Helpdesk by telephone on +44 (0) 20-7444-8444. Any use, dissemination, forwarding, printing, or copying of this e-mail or its attachments is strictly prohibited.
Re: TDP for Exchange
Mark, Thanks. You just jogged my memory. I did this once before for the legal dept. We keep it for a couple of months and then got the okay to delete it. As I now remember (from you response), I ran an export to save everything once. Thanks for the info and have a great day. Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: June 07, 2004 1:42 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. From: Stapleton, Mark [SMTP:[EMAIL PROTECTED] I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack Sorry, then I am out of ideas. Well, how about setting up a separate pool, just for the long retention data, and do a special backup to that pool? ... Just a thought. Obviously backupset kind of thing would be preferrable. An alternative is to run a second daily backup of your Exchange data using an alternate management class that never allows expiration. You can then pile your extra backups onto a separate set of tape volumes. At least that way, you don't have a really nasty one-backup-one-tape situation. (Keep in mind, of course, that this means a stream of tape volumes going to the vault, never to return.) However, this will only help you with ongoing backups, not the ones you already have. About the only thing to do with his existing backups is to run an export of the node to tape volume(s). I can't think of another way to guarantee getting the last backup on the existing backup list. Ralph, are you sure that you have to keep a copy of old Exchange backups *forever*? (It sounds like pie-in-the-sky lawyer talk to me; as I understand it, the current legal atmosphere doesn't require it.) -- Mark Stapleton
Re: TDP for Exchange
You could restore that version then do a file level archive of the DB using the regular TSM b/a client. (Easiest to do if you have a recovery Server.) -Original Message- From: Levi, Ralph [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: TDP for Exchange I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? Thanks, Ralph
Re: TDP for Exchange - The answer is not nice!
Hi Tony, Thanks for the response. I think I will try the export server methodology first. It should be simpler but I will use this as my fallback should that not suffice. Thanks for the quick turnaround. Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tony Morgan Sent: June 07, 2004 1:45 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange - The answer is not nice! Hi Ralph, I believe you have 2 options. 1. Restore and re-save to a permanent management class... goto 3 2. remove the tape with the backup on it, protect from overwrite ... goto 3 3. Save the current TSM Database, Volhist, Devconfig and prepare files. (Use NT Backup or something that you can trust to be able to read in the future!!! DVD ROM's are too short lifetime for what you need) (2) You can still get to your data if you set the system date to today (7th June 2004) before you build a restore environment... I have done it!!! (Arrrhhh!!!) It rather depends on whether you expect to ever have to read the data again!!! It will be a pain in (2) but is the least work for now. BTW: Don't forget to record the EXACT Version of Exchange, and TSM, and ALL the SP's/hotfixs.. and have ALL the software media available for the restore in the future... its not going to be available on the web. Record any current passwords before you start - you won't remember them! Also, you need an NT domain controller to re-install Exchange, so make sure that is available to a current point in time too. Maybe an idea to hold onto an old PC or two and an NT install... The current technology won't run NT very well in the future. Feel free to contact me direct if you get stuck. I am serious about the above, although it looks like I am joking (Its a really hard task to protect MS Exchange to this level) It could be worse... I am currently trying to get Exchange back to 2000 from Arcserve 6.0!!! Best Regards Good Luck Tony Morgan [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: 07 June 2004 18:23 To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. -- Mark Stapleton This e-mail and any files transmitted with it, are confidential and intended solely for the use of the addressee. The content of this e-mail may have been changed without the consent of the originator. The information supplied must be viewed in this context. If you have received this e-mail in error please notify our Helpdesk by telephone on +44 (0) 20-7444-8444. Any use, dissemination, forwarding, printing, or copying of this e-mail or its attachments is strictly prohibited.
Re: TDP for Exchange - The answer is not nice!
Make sure that the export server works with the Exchange TDP... I don't know, but I imagine it would. Best Of Luck Tony -Original Message- From: Levi, Ralph [mailto:[EMAIL PROTECTED] Sent: 07 June 2004 18:54 To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange - The answer is not nice! Hi Tony, Thanks for the response. I think I will try the export server methodology first. It should be simpler but I will use this as my fallback should that not suffice. Thanks for the quick turnaround. Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tony Morgan Sent: June 07, 2004 1:45 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange - The answer is not nice! Hi Ralph, I believe you have 2 options. 1. Restore and re-save to a permanent management class... goto 3 2. remove the tape with the backup on it, protect from overwrite ... goto 3 3. Save the current TSM Database, Volhist, Devconfig and prepare files. (Use NT Backup or something that you can trust to be able to read in the future!!! DVD ROM's are too short lifetime for what you need) (2) You can still get to your data if you set the system date to today (7th June 2004) before you build a restore environment... I have done it!!! (Arrrhhh!!!) It rather depends on whether you expect to ever have to read the data again!!! It will be a pain in (2) but is the least work for now. BTW: Don't forget to record the EXACT Version of Exchange, and TSM, and ALL the SP's/hotfixs.. and have ALL the software media available for the restore in the future... its not going to be available on the web. Record any current passwords before you start - you won't remember them! Also, you need an NT domain controller to re-install Exchange, so make sure that is available to a current point in time too. Maybe an idea to hold onto an old PC or two and an NT install... The current technology won't run NT very well in the future. Feel free to contact me direct if you get stuck. I am serious about the above, although it looks like I am joking (Its a really hard task to protect MS Exchange to this level) It could be worse... I am currently trying to get Exchange back to 2000 from Arcserve 6.0!!! Best Regards Good Luck Tony Morgan [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: 07 June 2004 18:23 To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. -- Mark Stapleton This e-mail and any files transmitted with it, are confidential and intended solely for the use of the addressee. The content of this e-mail may have been changed without the consent of the originator. The information supplied must be viewed in this context. If you have received this e-mail in error please notify our Helpdesk by telephone on +44 (0) 20-7444-8444. Any use, dissemination, forwarding, printing, or copying of this e-mail or its attachments is strictly prohibited. This e-mail and any files transmitted with it, are confidential and intended solely for the use of the addressee. The content of this e-mail may have been changed without the consent of the originator. The information supplied must be viewed in this context. If you have received this e-mail in error please notify our Helpdesk by telephone on +44 (0) 20-7444-8444. Any use, dissemination, forwarding, printing, or copying of this e-mail or its attachments is strictly prohibited.
Re: TDP for Exchange - The answer is not nice!
Looks like it will work. I just ran the preview and got results that look reasonable. BTW - To set the record straight in case someone else needs this info, I'm using Export Node . Export Server exports the TSM server info not the client info I am needing. Thanks again, Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tony Morgan Sent: June 07, 2004 1:57 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange - The answer is not nice! Make sure that the export server works with the Exchange TDP... I don't know, but I imagine it would. Best Of Luck Tony -Original Message- From: Levi, Ralph [mailto:[EMAIL PROTECTED] Sent: 07 June 2004 18:54 To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange - The answer is not nice! Hi Tony, Thanks for the response. I think I will try the export server methodology first. It should be simpler but I will use this as my fallback should that not suffice. Thanks for the quick turnaround. Ralph -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tony Morgan Sent: June 07, 2004 1:45 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange - The answer is not nice! Hi Ralph, I believe you have 2 options. 1. Restore and re-save to a permanent management class... goto 3 2. remove the tape with the backup on it, protect from overwrite ... goto 3 3. Save the current TSM Database, Volhist, Devconfig and prepare files. (Use NT Backup or something that you can trust to be able to read in the future!!! DVD ROM's are too short lifetime for what you need) (2) You can still get to your data if you set the system date to today (7th June 2004) before you build a restore environment... I have done it!!! (Arrrhhh!!!) It rather depends on whether you expect to ever have to read the data again!!! It will be a pain in (2) but is the least work for now. BTW: Don't forget to record the EXACT Version of Exchange, and TSM, and ALL the SP's/hotfixs.. and have ALL the software media available for the restore in the future... its not going to be available on the web. Record any current passwords before you start - you won't remember them! Also, you need an NT domain controller to re-install Exchange, so make sure that is available to a current point in time too. Maybe an idea to hold onto an old PC or two and an NT install... The current technology won't run NT very well in the future. Feel free to contact me direct if you get stuck. I am serious about the above, although it looks like I am joking (Its a really hard task to protect MS Exchange to this level) It could be worse... I am currently trying to get Exchange back to 2000 from Arcserve 6.0!!! Best Regards Good Luck Tony Morgan [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stapleton, Mark Sent: 07 June 2004 18:23 To: [EMAIL PROTECTED] Subject: Re: TDP for Exchange From: Levi, Ralph [SMTP:[EMAIL PROTECTED] I need to keep a single backup for legal reasons of our oldest Exchange DB full backup. Does anyone know how I can keep this without changing my existing management class and normal backup retention ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Coats, Jack generate a backupset. keep that. I do not believe you can make a backupset from API-generated backups, such as TDP for Exchange. -- Mark Stapleton This e-mail and any files transmitted with it, are confidential and intended solely for the use of the addressee. The content of this e-mail may have been changed without the consent of the originator. The information supplied must be viewed in this context. If you have received this e-mail in error please notify our Helpdesk by telephone on +44 (0) 20-7444-8444. Any use, dissemination, forwarding, printing, or copying of this e-mail or its attachments is strictly prohibited. This e-mail and any files transmitted with it, are confidential and intended solely for the use of the addressee. The content of this e-mail may have been changed without the consent of the originator. The information supplied must be viewed in this context. If you have received this e-mail in error please notify our Helpdesk by telephone on +44 (0) 20-7444-8444. Any use, dissemination, forwarding, printing, or copying of this e-mail or its attachments is strictly prohibited.
TSM client on Red Hat Linux
I have installed the TSM client version 4.2.0 on two IBM x335 servers running Red Hat Linux Advanced Server 2.1, and I did all the dsm.sys and dsm.opt file fixes, plus the environmental variable changes to the .bash_profile for root. The dsmc commands work correctly and I can talk to our TSM Host Server, but if I try to do a backup or an incremental on /home (using dsmc inc /home as root user), I get two different error answers on identical setups of TSM on both servers. On the first one, I get: Incremental backup of volume '/home' ANS1076E *** Directory not found *** And on the second one I get: ANS1071E Invalid domain name entered: '/home' Yet both servers have a valid /home directory, mounted for the default /dev/sda5 file system under Linux, with root ownership and 755 permissions. Which one is the correct error and how can I fix them? Thanks! Raymond J Ramirez Distributed System Supervisor Puerto Rico Telephone
Re: TSM client on Red Hat Linux
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Raymond Ramirez I have installed the TSM client version 4.2.0 on two IBM x335 servers running Red Hat Linux Advanced Server 2.1, and I did all the dsm.sys and dsm.opt file fixes, plus the environmental variable changes to the .bash_profile for root. The dsmc commands work correctly and I can talk to our TSM Host Server, but if I try to do a backup or an incremental on /home (using dsmc inc /home as root user), I get two different error answers on identical setups of TSM on both servers. On the first one, I get: Incremental backup of volume '/home' ANS1076E *** Directory not found *** And on the second one I get: ANS1071E Invalid domain name entered: '/home' Yet both servers have a valid /home directory, mounted for the default /dev/sda5 file system under Linux, with root ownership and 755 permissions. Which one is the correct error and how can I fix them? The version of TSM client you chose is very much out-of-date. Go to the IBM ftp site and get a more recent version. Also, read the TSM UNIX client manual for the version you download. There is a discussion about which filesystem types are supported. Then go to http://search.adsm.org and search for the keywords +linux, +client, and +virtualmountpoint. -- Mark Stapleton
Re: ANS3408W The volume /xxx/xxxx contains bad blocks
The message manual content is derived from the same source as what we include in the product help facility (dsmc help). Differences from the published/online manuals would only be due to a lag between the time we add/change a message in the help facility and the time it takes to get the changes into the formal publications. Because of how we develop the messages, barring a build or package defect, if we can issue the message, we can at least display help for it via dsmc help. Andy - Thanks for clearing up the mystery message number. Unfortunately, documentation of 'dsmc help' in the client manuals is lazy, failing to say much of anything about what it can provide, and says nothing about the information it provides also including ANS* message numbers. And even then, because of the linear rather than hierarchical presentation of dsmc help command generated list, the available messages info is rather hidden. As a result, I expect that only a tiny fraction of TSM customers realize that messages help is available via the CLI. The client manuals need to advise customers on what info is available via 'dsmc help'. The way it is, it's largely a lost opportunity: some developer(s) go to all the trouble to incorporate all that info into the command, and almost no one knows it's there. It would be much better to have 'dsmc help' work like the admirable tapeutil command, which very nicely lays out, on a primary screen, its main ingredients. The design of 'dsmc help' harks back to v1, and sorely needs redesign to meet contemporary (ASCII) interface standards of usability. thanks, Richard Sims
Re: TSM client on Red Hat Linux
Raymond Ramirez wrote: I have installed the TSM client version 4.2.0 on two IBM x335 servers running Red Hat Linux Advanced Server 2.1, and I did all the dsm.sys and dsm.opt file fixes, plus the environmental variable changes to the .bash_profile for root. The dsmc commands work correctly and I can talk to our TSM Host Server, but if I try to do a backup or an incremental on /home (using dsmc inc /home as root user), I get two different error answers on identical setups of TSM on both servers. On the first one, I get: Incremental backup of volume '/home' ANS1076E *** Directory not found *** And on the second one I get: ANS1071E Invalid domain name entered: '/home' Yet both servers have a valid /home directory, mounted for the default /dev/sda5 file system under Linux, with root ownership and 755 permissions. Which one is the correct error and how can I fix them? Download a newer client. That version sounds like it doesn't have support for your type of filesystems which I presume is ext3 ? Thanks! Raymond J Ramirez Distributed System Supervisor Puerto Rico Telephone
Re: ANS3604s
This doesn't sound like a cluster problem, more of a general client install problem. After you installed the client , but BEFORE you ran dsmcad , did you run dsmc , and do a q tsa? That should've asked you to setup a username/password for the backups to run under. Then, when registering the node with TSM (i.e. running dsmcad), it should've helped you create a TSM administrator-level username/password for that node. When you try to do a backup/restore from the web client, it will ask you for the TSM username/password you want to use to connect to the node. You need to give it either the TSM username password for that node, or your main TSM admin username password. Troy Frank Network Services University of Wisconsin Medical Foundation 608.829.5384 [EMAIL PROTECTED] 6/7/2004 12:26:05 PM Hello all, config Novell os 6 TSM client 5.2.2 When I click on backup or restore on the Web client Gui I get the following message: ANS2604s the web client agent was unable to authenticate the the server Can anyone tell me what might be wrong? This server is part of a cluster we are setting up Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Primary Pool and Copypool Relationship
I tried this cmd, but all my copy pool volumes are UNAVAIL (offsite). any other suggestions? Dave Nicholson Whirlpool Corporation Rushforth, Tim [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/07/2004 11:20 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Primary Pool and Copypool Relationship Yes this is how TSM works. You can have multiple copy pools for 1 Primary Pool. See http://msgs.adsm.org/cgi-bin/get/adsm0404/221.html for one way to delete this data. (This assumes that there is still domr data that you want on Copy Pool #1) -Original Message- From: David Nicholson [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: Primary Pool and Copypool Relationship Hi All, I moved a lot of data out of Primary Pool #1 and into Primary Pool # 2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool #2. It appears that the Copy Pool # 1 still has the backup of this data...which I expected. The problem is that it appears the data was also backed up to copy pool #2 as I moved the datathis was not expected. Does this sound like expected behavior? If so, any ideas for how to clean up the extra copy in Copy Pool #1??? Thanks! Dave Nicholson Whirlpool Corporation
Re: Primary Pool and Copypool Relationship
I guess the proper sequence should have been: 1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will use the data on Primary Pool #1 as the source data) 2. Move nodedata from Primary Pool #1 to Primary Pool #2 I'm not sure if there is any way other than to bring the volumes back onsite and do the move node data then. Depending on how much other data is in Copy Pool #1 - you could do this but I wouldn't recommend it. Delete all data in Copy Pool #1 then backup Primary Pool #1. -Original Message- From: David Nicholson [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 1:39 PM To: [EMAIL PROTECTED] Subject: Re: Primary Pool and Copypool Relationship I tried this cmd, but all my copy pool volumes are UNAVAIL (offsite). any other suggestions? Dave Nicholson Whirlpool Corporation Rushforth, Tim [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/07/2004 11:20 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Primary Pool and Copypool Relationship Yes this is how TSM works. You can have multiple copy pools for 1 Primary Pool. See http://msgs.adsm.org/cgi-bin/get/adsm0404/221.html for one way to delete this data. (This assumes that there is still domr data that you want on Copy Pool #1) -Original Message- From: David Nicholson [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: Primary Pool and Copypool Relationship Hi All, I moved a lot of data out of Primary Pool #1 and into Primary Pool # 2. Primary Pool #1 used Copy Pool #1 and Primary Pool # 2 used Copy Pool #2. It appears that the Copy Pool # 1 still has the backup of this data...which I expected. The problem is that it appears the data was also backed up to copy pool #2 as I moved the datathis was not expected. Does this sound like expected behavior? If so, any ideas for how to clean up the extra copy in Copy Pool #1??? Thanks! Dave Nicholson Whirlpool Corporation
Re: Primary Pool and Copypool Relationship
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim I guess the proper sequence should have been: 1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will use the data on Primary Pool #1 as the source data) 2. Move nodedata from Primary Pool #1 to Primary Pool #2 Unfortunately, step #1 is not possible. MOVE NODEDATA supports data moves within a single copy pool, but not between two copy pools. -- Mark Stapleton
TSM, Solaris, and more then 4 CPU's: Trouble in Paradise?
My company runs TSM 5.1.8.1 on Sun E4500's with 4 procs and 4GB of RAM. I have tried twice now, once on 4.2 and now on 5.1 to add more processors (either 2 or 4) and TSM performance drops through the floor. Has anyone else seen this behavior? Normally, starting the server fresh only takes 10-15 minutes to mount all of the volumes and bring everything online, but with the additional processors, it takes hours. I have tried it on several machines with different code levels with the same effect. I have also tried it on both Solaris 2.6 and 8, same effect. Any suggestions from the peanut gallery? Michael French Savvis Communications Enterprise Storage Engineer (314)628-7392 -- desk (408)239-9913 -- mobile
Re: Primary Pool and Copypool Relationship
Ooops forgot about that restriction. To do this without bringing back offsite tapes or deleting all copy pool data for some nodes temporarily: 1. Move nodedata from Copy Pool #1 to Copy Pool #1 (to new volumes) for the nodes you want to move. 2. Move nodedata Primary Pool #1 to Primary Pool #2 3. Backup primary pool #2 to Copy Pool #2 4. Delete the new volumes from 1. 1. move nodedata for the smaller group of data of the copy stgpool to new copy stg pool volumes in the same pool -Original Message- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: June 7, 2004 2:54 PM To: [EMAIL PROTECTED] Subject: Re: Primary Pool and Copypool Relationship From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim I guess the proper sequence should have been: 1. Move nodedata from Copy Pool #1 to Copy Pool #2 (this way TSM will use the data on Primary Pool #1 as the source data) 2. Move nodedata from Primary Pool #1 to Primary Pool #2 Unfortunately, step #1 is not possible. MOVE NODEDATA supports data moves within a single copy pool, but not between two copy pools. -- Mark Stapleton
Odd Linux client problem
Hi, I am having a problem with the 5.2 or 5.1 client running under Redhat 9.0. The client installs properly and seems to connect to the server. I have coded the dsm.sys file to point to the server. However, any statements I place in the dsm.opt file will cause the following error to be displayed: ANS1036S Invalid option 'NODENAME' found in options file '/opt/tivoli/tsm/ client/ba/bin/dsm.opt Similar errors appear for any other valid option. If I remove all options from the dsm.opt file and invoke the GUI and do the configuration from there, none of the options I select in the GUI will be placed in the dsm.opt file. The attrib and owner rights on the dsm.opt and dsm.sys are correct. The two DSM_CONFIG and DSM_DIR environment variables are also set. I am at a loss. Has anyone seen this problem? Thanks in advance.
Re: Odd Linux client problem
Take a closer look at the Unix client manuals. Some options (Nodename is one of them) can only be placed in the dsm.sys file. If you want to use something other than the hostname for the node, include it in the server stanza. Ted At 05:06 PM 6/7/2004, you wrote: Hi, I am having a problem with the 5.2 or 5.1 client running under Redhat 9.0. The client installs properly and seems to connect to the server. I have coded the dsm.sys file to point to the server. However, any statements I place in the dsm.opt file will cause the following error to be displayed: ANS1036S Invalid option 'NODENAME' found in options file '/opt/tivoli/tsm/ client/ba/bin/dsm.opt Similar errors appear for any other valid option. If I remove all options from the dsm.opt file and invoke the GUI and do the configuration from there, none of the options I select in the GUI will be placed in the dsm.opt file. The attrib and owner rights on the dsm.opt and dsm.sys are correct. The two DSM_CONFIG and DSM_DIR environment variables are also set. I am at a loss. Has anyone seen this problem? Thanks in advance.
backup set or archive copy group w/ 7 year retention
Input appreciated. 2 AIX servers and I want to have something very similar to a End Of Month Backup set that I run. I would like to know if anyone sees any problems with using a long term archive copy group to fulfill the same job as a backup set. If you ask why I dont use a backup set, a legacy configuration is in place to just have a long term archive copy group be utilized (just as a backup set would be). The LTO's would be shipped offsite with a full backup tape sent at the same time. Let me know if anyone sees a problem with using an archive copy group instead of a backup set. Rick.
OpenAFS backup using TSM via XBSA - procedure for compiling
Currently, we are running OpenAFS on Redhat Linux 7.2 (AS) and looking for a backup solution using IBM TSM. After reading from mail-archive there appears to be a way to compile OpenAFS with TSM XBSA (X-open-api) so that the OpenAFS butc can communicate with TSM. Looking for a procedure on how to compile XBSA and what to compile? Please suggest any other backup methods you are successfully using with OpenAFS on Linux. Example, how has TIBS worked for you? Need help. [EMAIL PROTECTED] - Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger
How to remove the httpclient banner version
Hi *SMers, my security officer asks me to remove the Server: TSM_HTTP/0.1 banner on TSM HTTPClient. Could you put me on the way ? I have no idea... Regards David Sniper Rigaudiere GPG KeyID 0x2D243742
Re: OpenAFS backup using TSM via XBSA - procedure for compiling
Hi, The following URL http://www.berningeronline.net/docstacks/HTML/relnotes/tsmbackup.html contains some info. Regarding OpenAFS support for TSM hope it is useful Regards, Nitin Ubhayakar ( 3989111 x 69182 * [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Loni Ly Sent: Tuesday, June 08, 2004 3:26 AM To: [EMAIL PROTECTED] Subject: OpenAFS backup using TSM via XBSA - procedure for compiling Currently, we are running OpenAFS on Redhat Linux 7.2 (AS) and looking for a backup solution using IBM TSM. After reading from mail-archive there appears to be a way to compile OpenAFS with TSM XBSA (X-open-api) so that the OpenAFS butc can communicate with TSM. Looking for a procedure on how to compile XBSA and what to compile? Please suggest any other backup methods you are successfully using with OpenAFS on Linux. Example, how has TIBS worked for you? Need help. [EMAIL PROTECTED] - Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger
