Re: Deleting a Volume in TSM
'Del vol XYZ' should work. If it is a copypool volume you can try to update access to readwrite, then it should be deleted from the storage pool. If you have problem in deleting the volume you can try Kurt´s suggenstion. Search for similar problems/solution once written bu Kelly Lipp years ago.. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Beyers Sent: den 25 januari 2006 06:50 To: ADSM-L@VM.MARIST.EDU Subject: Re: Deleting a Volume in TSM Arthur, Just run an 'audit vol volume_name fix=yes'. regards, Kurt Van: ADSM: Dist Stor Manager namens Kleynerman, Arthur Verzonden: wo 1/25/2006 3:34 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] Deleting a Volume in TSM Hi everyone, Does anyone know of a way to delete this volume? Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status --- -- - - *WSRV_TAPEFP LTO_DEVC 0.0 0.0 Empty Thanks, Arthur - The information contained in this e-mail message, and any attachment thereto, is confidential and may not be disclosed without our express permission. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message, or any attachment thereto, in whole or in part, is strictly prohibited. If you have received this message in error, please immediately notify us by telephone, fax or e-mail and delete the message and all of its attachments. Thank you. Every effort is made to keep our network free from viruses. You should, however, review this e-mail message, as well as any attachment thereto, for viruses. We take no responsibility and have no liability for any computer virus which may be transferred via this e-mail message. --- 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: Ghost volumes
Hi, Try: upd vol XX acc=reado audit vol XX fix=yes Most likely, message about fixing things will come by and volume is deleted from stg pool. Not sure about the cause of this. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Meadows, Andrew Sent: woensdag 25 januari 2006 4:18 To: ADSM-L@VM.MARIST.EDU Subject: Ghost volumes Hi all, I have a tsm 5.3 server on aix using lto Gen 1 drives. In some of my offsite storage pools I have some tapes that are showing 0.1 percent full. Reclamation never pulls these tapes back. If I do a q content on them they show no data. If I do a Del vol discard=yes it says there is no data on the volumes but still they never go to vault retrieve status. Other tapes come back fine just not these. How can I get these tapes back? Has anyone else seen this behavior? If so what causes it? Any help you can give would be appreciated. Thanks, Andrew This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien de integriteit van het bericht niet veilig gesteld is middels verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden voor de inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing. Deze worden u op aanvraag direct kosteloos toegezonden. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Origin supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Origin exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
Re: System object restore problem
Thomas I'm not sure that you can actually do this. While from a high level logical view, you might think that the steps that you are taking will work; however, all BMR's that I have performed, especially in the Windows environment, I would always restore back to a target machine that has an identical name and I think that any Windows BMR documentation would always allude to this also. My guess is that you have a need to give the machine a different name because you are restoring it on your live network. Obviously in a full DR test or real DR, the original machine would not be visable and therefore you can give the target machine for the restore, the actual name. For DR tests, I find it useful to have a dedicated DR restore VLAN. You can then firewall/traffic filter this VLAN from your live prod VLANs. You only need enable port 1500 outbound from the VLAN (or what ever port you have configured for TSM data access). This enables you to give the identical machine names to the servers you are restoring and also ensures that when the restore is complete, they don't interfere with your live prod servers. Failing this, if you have a spare NIC in your TSM server, create a restore LAN segment from this. Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: 24 January 2006 21:25 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] System object restore problem We just went through a disaster recovery test, using the following process for each Windows 2000 system involved: 1.Give the replacement system a different computer name than its production counterpart. 2.Execute a 'rename node' command against the recreated TSM database to change the node name matching the production computer name to a node name matching the replacement system computer name. 3.Execute 'rename filespace' commands to make the corresponding changes to computer names embedded in UNC volume names. 4.Restore the C drive. 5.Restore the system object. 6.Restore the remaining drives. At step 5 the attempt to restore the system object finished almost instantly, with no data movement. This was true whether the GUI or the command line client was used. The 'query systemobject' claimed that there were no matching files. I called IBM and was told that a system object cannot be restored to a system with a different computer name than the system that backed up the system object. We were using 5.2.6.0 server code under mainframe Linux. We were, in most cases, installing 5.3.2.0 client code on the replacement Windows systems (one Windows administrator tried the 5.1.5.0 client code and got the same results). Some of the original production systems had been running 5.3.2.0 client code, and some had been using lower client levels. Several of the Windows administrators confirmed my recollection that the process described above had been used successfully at our previous disaster recovery test 14 months earlier. We are then using 5.2.2.0 server code and a variety of 5.1 and 5.2 client code levels. This raises a number of questions: 1.Why did our test recovery process stop working? 2.Is there any way to get the process to start working again? 3.Nearly every book or article about disaster recovery emphasizes the importance of testing. Why did Tivoli introduce a restriction that seems to have been designed to make disaster recovery testing nearly impossible?
Re: System object restore problem
Thomas, One other thing. You mention that you have actually managed to complete this method successfully with 5.1.x.x and 5.2.x.x code. Bear in mind that there were a number of bugs with the early levels of code regarding the backup of W2K system objects. So while it may have worked for you, there may have been underlying problems for others, which have subsequently been solved, but unfortunately have scuppered your internal DR procedures. I really think that your only option is to build a dedicated restore LAN segment and then use the original machine names for the Windows BMRs. Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: 24 January 2006 21:25 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] System object restore problem We just went through a disaster recovery test, using the following process for each Windows 2000 system involved: 1.Give the replacement system a different computer name than its production counterpart. 2.Execute a 'rename node' command against the recreated TSM database to change the node name matching the production computer name to a node name matching the replacement system computer name. 3.Execute 'rename filespace' commands to make the corresponding changes to computer names embedded in UNC volume names. 4.Restore the C drive. 5.Restore the system object. 6.Restore the remaining drives. At step 5 the attempt to restore the system object finished almost instantly, with no data movement. This was true whether the GUI or the command line client was used. The 'query systemobject' claimed that there were no matching files. I called IBM and was told that a system object cannot be restored to a system with a different computer name than the system that backed up the system object. We were using 5.2.6.0 server code under mainframe Linux. We were, in most cases, installing 5.3.2.0 client code on the replacement Windows systems (one Windows administrator tried the 5.1.5.0 client code and got the same results). Some of the original production systems had been running 5.3.2.0 client code, and some had been using lower client levels. Several of the Windows administrators confirmed my recollection that the process described above had been used successfully at our previous disaster recovery test 14 months earlier. We are then using 5.2.2.0 server code and a variety of 5.1 and 5.2 client code levels. This raises a number of questions: 1.Why did our test recovery process stop working? 2.Is there any way to get the process to start working again? 3.Nearly every book or article about disaster recovery emphasizes the importance of testing. Why did Tivoli introduce a restriction that seems to have been designed to make disaster recovery testing nearly impossible?
Re: Exchange restore slowdown
Steve, It's a shot in the dark, but did you see Del Hoobler's posting regarding the slowdown in backup performance of TDP Exchange when you apply TSM 5.3 client/API code. You don't mention your client code level and I appreciate that the posting related to backup performance, but I thought it might be worth a shout. http://msgs.adsm.org/cgi-bin/get/adsm0512/204.html Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schaub, Steve Sent: 24 January 2006 21:58 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Exchange restore slowdown Environment: 5.2.2.0 TSM server on AIX using 3592 tape ESS disk. TDP 5.2.1.0 on Exchange 2003 server running as a vm under ESX 2.5.2 We have several corrupted mailboxes in the 2 stores on a particular Exchange server. We are trying to restore to a recovery group on a different server, where we will then use export and merge to piece the affected users back to health. What is happening is that we get the first 8-9GB (compressed figure) within half an hour, but then the restore slows to a crawl - it has been running for 4.5 hours now and is only up to 14.7GB (guessing we have around 22GB total to restore). The same tape has been mounted the entire time, there is no other process running to conflict, the TSM server and the recovery server are both underutilized in terms of cpu/memory/network. Has anyone ever seen this type of behavior or have a suggestion where I can look next to try to find the bottleneck? did I mention that this store is the one used by the execs? nuff said on that. Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: DB LOG Volume layout - new
I had also such an experience. I was at a customer who had a 250 (!) GB TSM DB allocated on 8x34GB LUNs of a DMX box. Obviously the LUNs where part of RAID groups in the DMX that were shared with other applications (in this case, a production Oracle DB). While the access was random, things went fairly well, but when we needed more of the DB (expiration and especially dbbackup) things would go crazy. Full Dbbckups took in excess of 5 hours, and we saw plenty of hot disks during the process. I wasn't a big fan of striping all myself, bu I decided to give it a try. The customer's storage admin told me simply It won't work, but I went on. I deleted the TSM DB and created eight striped RLVs, each of them using 4 8,5GB pieces of each LUN. The RLVs had 32k stripe size (So the average 256k dbbackup IO would be satisfied using all four disks) and were allocated in a sort of round-robin way (first RLV from disks 1-2-3-4, second RLV from disks 2-3-4-5 and so on). To cut it short, db backups are now made in 1h40m. And they have now time to do expirations and storage pool backups. Hope this helps, Paul -Original Message- From: ADSM: Dist Stor Manager on behalf of Richard Rhodes Sent: Tue 1/24/06 18:26 To: ADSM-L@VM.MARIST.EDU Cc: Subject: Re: DB LOG Volume layout - new I don't think you will ever get a definitive answer. There are too many ways to setup a disk system, and different people have different philosophies. For example, here's what we do . . . . kind of radical, so hang on . . . For our Oracle databases (random I/O type transactions) we've moved from the standard everything on it's own spindle to where now we cross stripe - use disk stripping (stripped meta vols on symm/dmx and raid5 luns on clariion), then, stripe across that at the OS level. It gives a complete uniform workload across your spindles for RANDOM access jobs. EMC is amazed at how well our DMX's and symms perform on our SAP systems. They told us NOT to do this . . . .now they really like the idea . . .as does Oracle. I have TSM setup the same way - It uses raid5 luns in Clariion storage - one lun from each raidset, so I've got a part of all spindles in the clariion, then, I have stripped AIX logical volumes (32k) across all the Clariion luns. From what I can see, it flies Yes, other applications are on those raidsets . . . that's life with 140gb disk drives. My storage pools are on a different disk subsystem and are NOT cross stripped, since their access is mostly sequential. In general for just about ANY system we set storage up for, we stripe as far and wide as possible. A disk drive in an expensive disk subsystem that isn't doing many I/O's is a waste of money, and, a lun confined to one or a couple spindles is not guaranteed bandwidth, but rather a guaranteed bandwidth limit. So, there you have it . . . another way to set it up. Lloyd Dieter [EMAIL PROTECTED] R.RR.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: DB LOG Volume layout - new 01/24/2006 02:48 PM Please respond to [EMAIL PROTECTED] om I've been watching this thread with interest, as some of the posts contradicted what I thought I knew. Using nmon, I've watched a couple of systems (AIX, TSM 5.2) running expiration and DBbackups that have the DB vols set up according to the one volume per spindle premise that appeared to have spotty hot disks, that is the I/O was not distributed evenly across the different volumes. One drive would have a lot of I/O, then another, etc. I've always striped them, in hardware if it was available, and using LVM if it was not. This gave fairly even I/O, but I admit that doesn't mean that it was the fastest method. I'd love to have a definitive answer here, because I've heard it both ways, and when I've asked support, they didn't seem to know. I'd like
CLIENTACTION Command
Hi to all I am using the command DEFINE CLIENTACTION to schedule a client to process a command for a one-time action. The command i am giving is as follow: define clientaction BIZTALK-DAILY domain=BIZTALK_DAILY action=command object='C:\TSMUSER\PROD\WNA1BZT.bat' wait=yes On the client side i have the following settings about the tsm scheduler: Prompted - TCP/IP address:localhost - TCP/IP port: 1501 - session Init.:server only The above command is defined successfully but the job C:\TSMUSER\PROD\WNA1BZT.bat is not executed at once. Do i have to change something? TSM SERVER version: 5.3.1 (windows 2000) TSM Client: 5.2.3.11 Thanks in advance Thanks
Re: DB LOG Volume layout - new
You are absolutely correct - if I loose a lun I loose everything. And it HAS happened. One time, when the TSM db was still on a DMX, we suffered a double disk failure which took out a bunch of stuff, including our TSM db. The DMX was new and EMC had set it up and turned it over to us. It suffered a disk failure but failed to call home. It sat like that for several months before a second disk failed. Why didn't it dial home? Because EMC forgot to perform an initial dial-home, which is what triggers their central support site that there is a new DMX out in the world. Our DMX's dial home attempts were refused Also, we've suffered through a bunch of full Clarrion array outages (full crash of a Clariion). These were all microcode bugs (a hdwr problem that microcode wasn't able to handle). Agressive stripping, like most things, is it's own worse enemy. Rick Allen S. Rout [EMAIL PROTECTED] Sent by: ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager cc [EMAIL PROTECTED] .EDU Subject Re: DB LOG Volume layout - new 01/24/2006 05:01 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU On Tue, 24 Jan 2006 15:26:27 -0500, Richard Rhodes [EMAIL PROTECTED] said: [ stripe ] So, there you have it . . . another way to set it up. My neurotic tendencies have prevented me from striping that aggressively. I envision one failed RAID taking out... well, _everything_. Mine is perhaps excessive caution in a day of hot spares and such. - Allen S. Rout - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Ghost volumes
On Jan 24, 2006, at 10:18 PM, Meadows, Andrew wrote: ...what causes it?... Phantom data on volumes is a problem that just won't go away in the server software. Your case may be related to the cause in APAR IC48152. You might pass it by TSM Support. It would provide valuable perspective for your pursuit to ascertain the last write datestamp for that volume: sometimes it is the case that the problem was instantiated under a prior version/release, and only evidences itself once the data on the old volume finally expires. Richard Sims
Strange behaviour on Small Business Server Client
Hi All, On one of our Small Business Server (W2K3 SP1) we have some strange behaviour. After (re)starting the services (Client Acceptor and TDP Exchange) all backups run fine for 2-3 days and then the services get stuck and have to be restarted. On another SBS we do not have those problems. Failing SBS: TSM Client 5.3.2.0 Good SBS: TSM Client 5.3.0.15 (this also did not work on the other SBS) TSM Server is 5.2.6.4 on AIX. Anyone knows a cure? Richard.
SCHEDLOGNAME extraneous setting
Hi *smers, While confirming some Exchange scheduler configs through the GUI I found this setting for SCHEDLOGNAME C:\Program Files\Tivoli\TSM\TDPExchange\DailyExc_Scheduler.log:yes Can anyone please tell me what the ':yes' does? I notice there is an option for dsmcutil /autostart:yes but I don't see how that can have affected this setting. Many Thanks, Matthew TSM Consultant ADMIN ITI Rabobank International 1 Queenhithe, London EC4V 3RL _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
compression question
Our aix admin had a question about client compression that I couldn't find an answer to in the docs. He was wondering where the compression actually takes place on the client end. Does the compressed file get written to disk as it's being created, then deleted after it's sent? Or does the compressed version of the file get created in memory temporarily until it's sent? Or is it happening some other way that didn't occur to me. 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: compression question
File data is compressed on-the-fly, as the data is read off the client disk and sent to the server. There is no buffering of the entire file (in memory or disk) in order to first compress it before sending it to the server. Likewise, with restore, the data is decompressed as it is sent from the server and written back to client disk. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html 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 ADSM-L@VM.MARIST.EDU wrote on 01/25/2006 07:49:10 AM: Our aix admin had a question about client compression that I couldn't find an answer to in the docs. He was wondering where the compression actually takes place on the client end. Does the compressed file get written to disk as it's being created, then deleted after it's sent? Or does the compressed version of the file get created in memory temporarily until it's sent? Or is it happening some other way that didn't occur to me. 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.
DB2 version
Hi Everybody, Does naybody know how I can determine what my DB2 TDP client version is on AIX ? I know there is a command called tdpoconf showenv in Oracle which shows what version of TDP client I have installed . Is there a similar command for DB2 ? I need to audit all my clients just to make sure I don't get any surprises when upgrading from TSM 5.1.6 to TSM 5.2 in the next few weeks. Rich
Re: DB2 version
Rich, Just run a q node f=d. And the backup of DB2 does not require or uses a TDP cient as both the database and backup software are from IBM. It comes 'free' with the database, just as is now the case with Informix IDS10. regards, Kurt Van: ADSM: Dist Stor Manager namens Richard Mochnaczewski Verzonden: wo 1/25/2006 16:19 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] DB2 version Hi Everybody, Does naybody know how I can determine what my DB2 TDP client version is on AIX ? I know there is a command called tdpoconf showenv in Oracle which shows what version of TDP client I have installed . Is there a similar command for DB2 ? I need to audit all my clients just to make sure I don't get any surprises when upgrading from TSM 5.1.6 to TSM 5.2 in the next few weeks. Rich
TSM/Cristie question
I'm testing Cristie on a machine that is running Windows 2000 SP3, TSM v5.3.0 and getting the following in CBMR logs (disrec, etc...) Volume Name: PHARMWIT1 Operation Started: Wed Jan 25 09:20:11 2006 Current Mode: Overwrite The drive(s) [C] were opened on [25-01-06 09:22:11] Return value = 0. [25-01-06 09:22:11] Dataset Name: C: Including security Information C:\ 26-11-02 13:55186 boot.ini [25-01-06 09:22:11] ERROR: FSS0012: File not found ENTRY: F:\boot.ini Etc... Apparently, it is changing C: to F: Huh? Anyone run into this that has tested/used Cristie BMR? Thanks! - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Re: System object restore problem
Can't you just boot the host in LOCAL mode, and not join the network while the restore is in progress? TSM just uses TCP/IP, doesn't care about Microsoft/Windows/Domain authorization... -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Leigh Reed Sent: Wednesday, January 25, 2006 4:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: System object restore problem Thomas, One other thing. You mention that you have actually managed to complete this method successfully with 5.1.x.x and 5.2.x.x code. Bear in mind that there were a number of bugs with the early levels of code regarding the backup of W2K system objects. So while it may have worked for you, there may have been underlying problems for others, which have subsequently been solved, but unfortunately have scuppered your internal DR procedures. I really think that your only option is to build a dedicated restore LAN segment and then use the original machine names for the Windows BMRs. Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: 24 January 2006 21:25 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] System object restore problem We just went through a disaster recovery test, using the following process for each Windows 2000 system involved: 1.Give the replacement system a different computer name than its production counterpart. 2.Execute a 'rename node' command against the recreated TSM database to change the node name matching the production computer name to a node name matching the replacement system computer name. 3.Execute 'rename filespace' commands to make the corresponding changes to computer names embedded in UNC volume names. 4.Restore the C drive. 5.Restore the system object. 6.Restore the remaining drives. At step 5 the attempt to restore the system object finished almost instantly, with no data movement. This was true whether the GUI or the command line client was used. The 'query systemobject' claimed that there were no matching files. I called IBM and was told that a system object cannot be restored to a system with a different computer name than the system that backed up the system object. We were using 5.2.6.0 server code under mainframe Linux. We were, in most cases, installing 5.3.2.0 client code on the replacement Windows systems (one Windows administrator tried the 5.1.5.0 client code and got the same results). Some of the original production systems had been running 5.3.2.0 client code, and some had been using lower client levels. Several of the Windows administrators confirmed my recollection that the process described above had been used successfully at our previous disaster recovery test 14 months earlier. We are then using 5.2.2.0 server code and a variety of 5.1 and 5.2 client code levels. This raises a number of questions: 1.Why did our test recovery process stop working? 2.Is there any way to get the process to start working again? 3.Nearly every book or article about disaster recovery emphasizes the importance of testing. Why did Tivoli introduce a restriction that seems to have been designed to make disaster recovery testing nearly impossible?
Upcoming Feb 3 worm attack on Microsoft Windows systems
Is anyone considering special archives for all their windows servers because of this worm or is someone here is over reacting? Antivirus vendors are warning of a rapidly spreading worm that is carrying a potentially destructive set of instructions. The Nyxem worm -- also nicknamed the Kama Sutra worm -- is programmed to overwrite all of the files on computers it infects on Feb. 3, said Mikko Hypponen, chief research officer at F-Secure Corp. F-Secure researchers found the worm truncates files to 20 bytes and causes an error message when one is opened, he said.
Re: Upcoming Feb 3 worm attack on Microsoft Windows systems
...Wouldn't it make more sense to spend the effort updating your virus software ? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gee, Norman Sent: Wednesday, January 25, 2006 11:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Upcoming Feb 3 worm attack on Microsoft Windows systems Is anyone considering special archives for all their windows servers because of this worm or is someone here is over reacting? Antivirus vendors are warning of a rapidly spreading worm that is carrying a potentially destructive set of instructions. The Nyxem worm -- also nicknamed the Kama Sutra worm -- is programmed to overwrite all of the files on computers it infects on Feb. 3, said Mikko Hypponen, chief research officer at F-Secure Corp. F-Secure researchers found the worm truncates files to 20 bytes and causes an error message when one is opened, he said.
Re: CLIENTACTION Command
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/25/2006 05:46:40 AM: Hi to all I am using the command DEFINE CLIENTACTION to schedule a client to process a command for a one-time action. The command i am giving is as follow: define clientaction BIZTALK-DAILY domain=BIZTALK_DAILY action=command object='C:\TSMUSER\PROD\WNA1BZT.bat' wait=yes On the client side i have the following settings about the tsm scheduler: Prompted - TCP/IP address:localhost - TCP/IP port: 1501 - session Init.:server only The above command is defined successfully but the job C:\TSMUSER\PROD\WNA1BZT.bat is not executed at once. Do i have to change something? After you define the clientaction, do a query sched * * from the server and look for a client schedule that starts with @ and numbers after it, like @045 for BIZTALK-DAILY. See what the status of the schedule is - repeat the command for a few minutes. Also, the clientaction isn't exactly immediate, it may take one or two minutes. If the clientaction actually runs, or says in process then the server is contacting the client correctly. From there, you'll have to check the dsmsched.log on the client and possibly dsmerror.log on the client to check for client side errors. If the server never contacts the client correctly then something is wrong in the setup of your client and/or scheduler service (ie the immediateaction stays in pending status until it times out). __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com
Re: System object restore problem
Seems like this didn't work the last time I tried it - TSM required the client to be named EXACTLY the same in order to do a system object restore, including being in the same domain. We created a segregated network to test these types of restores. Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Wednesday, January 25, 2006 11:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] System object restore problem Can't you just boot the host in LOCAL mode, and not join the network while the restore is in progress? TSM just uses TCP/IP, doesn't care about Microsoft/Windows/Domain authorization... -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Leigh Reed Sent: Wednesday, January 25, 2006 4:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: System object restore problem Thomas, One other thing. You mention that you have actually managed to complete this method successfully with 5.1.x.x and 5.2.x.x code. Bear in mind that there were a number of bugs with the early levels of code regarding the backup of W2K system objects. So while it may have worked for you, there may have been underlying problems for others, which have subsequently been solved, but unfortunately have scuppered your internal DR procedures. I really think that your only option is to build a dedicated restore LAN segment and then use the original machine names for the Windows BMRs. Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: 24 January 2006 21:25 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] System object restore problem We just went through a disaster recovery test, using the following process for each Windows 2000 system involved: 1.Give the replacement system a different computer name than its production counterpart. 2.Execute a 'rename node' command against the recreated TSM database to change the node name matching the production computer name to a node name matching the replacement system computer name. 3.Execute 'rename filespace' commands to make the corresponding changes to computer names embedded in UNC volume names. 4.Restore the C drive. 5.Restore the system object. 6.Restore the remaining drives. At step 5 the attempt to restore the system object finished almost instantly, with no data movement. This was true whether the GUI or the command line client was used. The 'query systemobject' claimed that there were no matching files. I called IBM and was told that a system object cannot be restored to a system with a different computer name than the system that backed up the system object. We were using 5.2.6.0 server code under mainframe Linux. We were, in most cases, installing 5.3.2.0 client code on the replacement Windows systems (one Windows administrator tried the 5.1.5.0 client code and got the same results). Some of the original production systems had been running 5.3.2.0 client code, and some had been using lower client levels. Several of the Windows administrators confirmed my recollection that the process described above had been used successfully at our previous disaster recovery test 14 months earlier. We are then using 5.2.2.0 server code and a variety of 5.1 and 5.2 client code levels. This raises a number of questions: 1.Why did our test recovery process stop working? 2.Is there any way to get the process to start working again? 3.Nearly every book or article about disaster recovery emphasizes the importance of testing. Why did Tivoli introduce a restriction that seems to have been designed to make disaster recovery testing nearly impossible? Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
TSM Database Size Growing Since Upgrading to 5.2.4.5
On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks.
Re: TSM Database Size Growing Since Upgrading to 5.2.4.5
No unusual new clients being added? Retaining more data? Change of include/exclude files? ... Just grasping for straws... -Original Message- Subject: [ADSM-L] TSM Database Size Growing Since Upgrading to 5.2.4.5 On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: TSM Database Size Growing Since Upgrading to 5.2.4.5
Have your Expirations been running successfully? David Longo [EMAIL PROTECTED] 01/25/06 2:05 PM On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: TSM Database Size Growing Since Upgrading to 5.2.4.5
I've noticed similar symptoms. Ice just been chalking it up to more use. -Original Message- From: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU ADSM-L@VM.MARIST.EDU Sent: Wed Jan 25 13:05:12 2006 Subject: TSM Database Size Growing Since Upgrading to 5.2.4.5 On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks. This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Re: TSM Database Size Growing Since Upgrading to 5.2.4.5
I might have thought that too if it wasn't all 3 instances. I graphed my database sizes back to 2004 (I have them in a mysql database), and it is striking the growth curve since 11/12/2005. Jack Coats wrote: No unusual new clients being added? Retaining more data? Change of include/exclude files? ... Just grasping for straws... -Original Message- Subject: [ADSM-L] TSM Database Size Growing Since Upgrading to 5.2.4.5 On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: TSM Database Size Growing Since Upgrading to 5.2.4.5
Good question, I didn't think of that one. It does appear that expiration is working (at least it says it is working - it is expiring objects, and a fairly normal amount). David Longo wrote: Have your Expirations been running successfully? David Longo [EMAIL PROTECTED] 01/25/06 2:05 PM On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: TSM Database Size Growing Since Upgrading to 5.2.4.5
Graph your occupancy (num_files) by domain for each server and see if it shows uniform growth. If not, drill down to node occupancies (num_files), and so on. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Wednesday, January 25, 2006 2:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM Database Size Growing Since Upgrading to 5.2.4.5 I might have thought that too if it wasn't all 3 instances. I graphed my database sizes back to 2004 (I have them in a mysql database), and it is striking the growth curve since 11/12/2005. Jack Coats wrote: No unusual new clients being added? Retaining more data? Change of include/exclude files? ... Just grasping for straws... -Original Message- Subject: [ADSM-L] TSM Database Size Growing Since Upgrading to 5.2.4.5 On November 11th, we upgraded our 3 tsm instances from 5.2.1 to 5.2.4.5. Since then, our three databases have grown at an alarming rate. They have grown: 56GB to 75GB (33%, 19Gb growth) 46GB to 65GB (41%, 19Gb growth) 53GB to 63GB (18%, 10Gb growth) Anyone have problems like this? Thanks. Privileged and Confidential: The information contained in this e-mail message is intended only for the personal and confidential use of the intended recipient(s). If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. SPECIAL NOTICE All information transmitted hereby is intended only for the use of the addressee(s) named above and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of confidential and privileged information is prohibited. If the reader of this message is not the intended recipient(s) or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that you must not read this transmission and that disclosure, copying, printing, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. Anyone who receives confidential and privileged information in error should notify us immediately by telephone and mail the original message to us at the above address and destroy all copies. To the extent any portion of this communication contains public information, no such restrictions apply to that information. (gate02)
How do I restore a database using a virtual volume?
Our configuration manager for our group of tsm servers has gone down and we need to restore the database for it. The thing is, it was backed-up using virtual volumes to one of the other tsm servers. We know which tape it is, but are unsure of how to do the restore. Mel Dennis
Backup Veritas Clusters on Solaris
Any one backing up veritas clusters on Solaris using a virtural node name. 5.3 has a asnodename option but we are running 5.2.6.3. I would like register a virtual node name and desinate a cluster resource to backup the different filespaces as they fail over. 5.2 have abilitie to grant access to restore, but do not see options to backup. Kenny Barnes Enterprise Storage Team GMAC Insurance 336-770-8280 [EMAIL PROTECTED] -- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. --
Re: How do I restore a database using a virtual volume?
On Wed, 25 Jan 2006 15:29:11 -0500, Dennis Melburn W IT743 [EMAIL
PROTECTED] said:
Our configuration manager for our group of tsm servers has gone down and
we need to restore the database for it. The thing is, it was backed-up
using virtual volumes to one of the other tsm servers. We know which
tape it is, but are unsure of how to do the restore.
You've got the VOLHIST and the DEVCONFIG, right? Then this is just
like any other DB restore.
here's the procedure (shell script) I use for one of my TSM servers,
which does its database backup to remote volumes.
dbsize=1024
lgsize=256
ppsize=64
ndb=`expr \` expr $dbsize / $ppsize \` + 1`
nlg=`expr \` expr $lgsize / $ppsize \` + 1`
echo Making DB volume in $vg: $dbsize MB, $ndb PPs
mklv -y ttestdblv_01a $vg ${ndb}
echo Making DB volume in $vg: $lgsize MB, $nlg PPs
mklv -y ttestlglv_01a $vg ${nlg}
echo dsmserv format 1 /dev/rttestlglv_01a 1 /dev/rttestdblv_01a
dsmserv format 1 /dev/rttestlglv_01a 1 /dev/rttestdblv_01a
echo dsmserv restore db TOD=TODAY TOT=NOW
dsmserv restore db TOD=TODAY TOT=NOW
Define the DB and log volumes, format them, restore. The 'which tape'
and 'where do I get it' are taken care of by reference to the volhist
and devconfig.
I'll put in a plug here for TEST YOUR RESTORE PROCEDURES. We're in
uniquely poor positions to be caught with our pants down on that
issue. I aim to be able to say If you can't script it, you don't
understand it, without shuddering inside.
- Allen S. Rout
Re: CLIENTACTION Command
The command should be q event * *. Sorry about that. __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com John Monahan/Computech 01/25/2006 11:01 AM To ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU cc Subject Re: CLIENTACTION Command ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/25/2006 05:46:40 AM: Hi to all I am using the command DEFINE CLIENTACTION to schedule a client to process a command for a one-time action. The command i am giving is as follow: define clientaction BIZTALK-DAILY domain=BIZTALK_DAILY action=command object='C:\TSMUSER\PROD\WNA1BZT.bat' wait=yes On the client side i have the following settings about the tsm scheduler: Prompted - TCP/IP address:localhost - TCP/IP port: 1501 - session Init.:server only The above command is defined successfully but the job C:\TSMUSER\PROD\WNA1BZT.bat is not executed at once. Do i have to change something? After you define the clientaction, do a query sched * * from the server and look for a client schedule that starts with @ and numbers after it, like @045 for BIZTALK-DAILY. See what the status of the schedule is - repeat the command for a few minutes. Also, the clientaction isn't exactly immediate, it may take one or two minutes. If the clientaction actually runs, or says in process then the server is contacting the client correctly. From there, you'll have to check the dsmsched.log on the client and possibly dsmerror.log on the client to check for client side errors. If the server never contacts the client correctly then something is wrong in the setup of your client and/or scheduler service (ie the immediateaction stays in pending status until it times out). __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com
Re: CLIENTACTION Command
Actually Q EV * @* will filter only the clientaction events. Bill Boyer Some days you're the bug, some days you're the windshield - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of John Monahan Sent: Wednesday, January 25, 2006 5:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: CLIENTACTION Command The command should be q event * *. Sorry about that. __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com John Monahan/Computech 01/25/2006 11:01 AM To ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU cc Subject Re: CLIENTACTION Command ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/25/2006 05:46:40 AM: Hi to all I am using the command DEFINE CLIENTACTION to schedule a client to process a command for a one-time action. The command i am giving is as follow: define clientaction BIZTALK-DAILY domain=BIZTALK_DAILY action=command object='C:\TSMUSER\PROD\WNA1BZT.bat' wait=yes On the client side i have the following settings about the tsm scheduler: Prompted - TCP/IP address:localhost - TCP/IP port: 1501 - session Init.:server only The above command is defined successfully but the job C:\TSMUSER\PROD\WNA1BZT.bat is not executed at once. Do i have to change something? After you define the clientaction, do a query sched * * from the server and look for a client schedule that starts with @ and numbers after it, like @045 for BIZTALK-DAILY. See what the status of the schedule is - repeat the command for a few minutes. Also, the clientaction isn't exactly immediate, it may take one or two minutes. If the clientaction actually runs, or says in process then the server is contacting the client correctly. From there, you'll have to check the dsmsched.log on the client and possibly dsmerror.log on the client to check for client side errors. If the server never contacts the client correctly then something is wrong in the setup of your client and/or scheduler service (ie the immediateaction stays in pending status until it times out). __ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com
FW: TSM Reporting - Error
Hi, Can anybody help me with this error message. I've installed TSM Operational Reporting and when I tried to update Properties - Automatic Notofication and when I clicked Query , I get this message : Unable to obtain node information . RC 4294967246 I hope somebody can help me with this. Thanks NORITA BINTI HASAN Senior Programmer Enterprise Systems Services Information Communications Tech. Div 6th Floor,Pos Malaysia HQ 50670 Kuala Lumpur Tel : 03 - 22756638 Pos Malaysia Berhad is Malaysia's national postal company Visit us online at www.pos.com.my NOTICE This message may contain privileged and/or confidential information. If you are not the addressee or authorised to receive this email, you must not use, copy, disclose or take any action based on this email. If you have received this email in error, please advise the sender immediately by reply e-mail and delete this message. Pos Malaysia Berhad takes no responsibility for the contents of this email.
Re: TSM/Cristie question
Well, seems like it should be a question to a Cristie forum or support... I think it is when CBMR does its snapshot it inernally rename C: to F:. But I havent tested that product for 2 years now and I have no plans to do that so my answer might not be 100% valid. Did you install the open file manager from the console or via terminal server client? //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bell, Charles (Chip) Sent: den 25 januari 2006 16:48 To: ADSM-L@VM.MARIST.EDU Subject: TSM/Cristie question I'm testing Cristie on a machine that is running Windows 2000 SP3, TSM v5.3.0 and getting the following in CBMR logs (disrec, etc...) Volume Name: PHARMWIT1 Operation Started: Wed Jan 25 09:20:11 2006 Current Mode: Overwrite The drive(s) [C] were opened on [25-01-06 09:22:11] Return value = 0. [25-01-06 09:22:11] Dataset Name: C: Including security Information C:\ 26-11-02 13:55186 boot.ini [25-01-06 09:22:11] ERROR: FSS0012: File not found ENTRY: F:\boot.ini Etc... Apparently, it is changing C: to F: Huh? Anyone run into this that has tested/used Cristie BMR? Thanks! - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information. --- 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.
