RE: [Veritas-bu] Database help
Sandy Have you tried using a different tape to backup the DB? How large is it? Is there any logging enabled to see at what point the backup of the DB Fails? Also, is it stored on a disk with sufficient space? What is the retention periods? You could use bpexpdate to force them out of Netbackup, and assuming the tapes are ok, you would need to Import ALL of the tapes in 2 phases (from experience I can say it's a real nightmare to do and takes approx 5 hours PER tape!) Simon Weaver Technical Support Windows Domain Administrator EADS Astrium Tel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message- From: Elrick, Sandy [mailto:[EMAIL PROTECTED] Sent: 03 January 2006 18:06 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Database help Hello all, NBDC 3.4.6/Solaris instance with NB Database backup issues. I am pretty much constantly getting 84's. I know it's an old instance and before I go down the road of modifying the database backups (I have narrowed it down to the fact that the databases are too large / cannot span tape) I want to check with you folk. Is there any way to determine the specific failure point on the database backup? Can I remove some older tapes from the database and be able to import them again? If I can reimport, are there any gotchas I should be aware of? Thank you Sandy Elrick Calgary, Alberta The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Exchange license
Title: Message I did believe (when I used to backup Exchange) that one license coverd all the exchange servers. With Symantec now holding the NBU License rules, it could well change Hope this helps Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: King, Cheryl [mailto:[EMAIL PROTECTED] Sent: 03 January 2006 16:08To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Exchange license Last week there was a discussion about licensing the Exchange client. One of the responses said something about running any number of exchange clients with one license. I ordered one license per client. Did I overpay? This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
Re: [Veritas-bu] Restore NBU tape with tar command?
Hello Andrew Here is what I have from an earlier mail (for extract just change t to x) I have had succes with listing the files on a tape with Netbackup tar when I know the blocksize. For nonmultipexed tape, blocksize 256k: /usr/openv/netbackup/tar -itvf norewind device -b 512 For multipexed tape, blocksize 256k: /usr/openv/netbackup/tar -iMtvf norewind device -b 512 If remember correctly /usr/openv/netbackup/tar ++help gives a list of options Regards Michael On Tue, 03 Jan 2006 11:13:37 -0500, Andrew Armstrong wrote I am in the process of putting together a disaster recovery plan in case our primary server goes down. This server is a stand-alone NBU server, backing up only itself, etc. I have no problems using NBU to do the recovery (bare metal restore, etc.), but those above me also require a vendor- independent recovery plan, in case there are problems using NBU to recover the data. I have experimented with using the NBU version of tar, and have successfully restored files from the tape. My only question is this: is it possible to make tar continue to the next backup set on the tape automatically? Currently, I am only able to restore small pieces of the system at a time (looks like 2000k or so). I am familiar with the option to span multi-volume archives, but I would like to see if there is an option to (for lack of a better way to put it) start at a certain point on the tape and restore everything from that point on, without prompts for user intervention. (The requirements for the DR plan dictate that a user with little or no admin experience should be able to do the recovery... this is NOT my requirement, but one put on me by those above) Any help/advice would be greatly appreciated! Andrew Armstrong Network Engineer CNE CCNA MCP VCP T S Brass and Bronze Works [EMAIL PROTECTED] (864) 834-6785 -- Cybercity Webhosting (http://www.cybercity.dk) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] DLT drives going down
Title: Message Hm what about Firmware for the SDLT tape drives? Any loose cables / connections or possible to change Scsi connectors? Not too sure why they feel the software is polling a drive could cause a problem?- if anything I would say polling a device is probably good as Netbackup confirms it can see it! The thing that makes me wonder if its cable / firmware issue is the comment "MEDIUM NOT PRESENT". Thanks Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:10To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] DLT drives going down We have an issue of drives randomly going down every night. NBU 5.0 mp5 HP-UX 11.11 STK L180 w/ STK 3400 scsi bridge. For some reason, 1 or more drives go down at random every night when backups run. Different tapes and different drives. Backups will be running fine and then drives begin to go down. These are SDLT320 drives. once they go down, you can't use robtest to move the tapes (medium not present error) or use the robtest unload command (device not present). If we power cycle the scsi bridge, we can talk to the drives and do what ever we want. STK is claiming that there is something coming from the host that is "polling" the library from the physical layer (assume HBA). We have had the SA for the master/media server disable any polling and load the latest patches from HP to no avail. We have changed from auto index to a manual map index as well. This was working from the end of June up until the second week in October. Thoughts/suggestions? Log snippets from last night: syslog entriesJan 4 05:37:42 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 05:50:10 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 11:27:52 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0800c0 I/O error during closeJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) Move_medium errorJan 4 11:34:36 ujachr01 tldd[4233]: TLD(1) drive 5 (device 4) is being DOWNED, status: Robotic dismount failureJan 4 11:34:36 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 5 (addr 504) access = 0 Contains Cartridge = yesSource address = 1119 (slot 120)Barcode = JA1156 Jan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) Move_medium errorJan 4 11:55:12 ujachr01 tldd[4233]: TLD(1) drive 1 (device 0) is being DOWNED, status: Robotic dismount failureJan 4 11:55:12 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 1 (addr 500) access = 0 Contains Cartridge = yesSource address = 1106 (slot 107)Barcode = JA1064 This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
RE: [Veritas-bu] DLT drives going down
Title: Message They have upgraded the FW to the latest/greatest and checked cables. I agree on the polling. From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 08:21To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down Hm what about Firmware for the SDLT tape drives? Any loose cables / connections or possible to change Scsi connectors? Not too sure why they feel the software is polling a drive could cause a problem?- if anything I would say polling a device is probably good as Netbackup confirms it can see it! The thing that makes me wonder if its cable / firmware issue is the comment "MEDIUM NOT PRESENT". Thanks Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:10To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] DLT drives going down We have an issue of drives randomly going down every night. NBU 5.0 mp5 HP-UX 11.11 STK L180 w/ STK 3400 scsi bridge. For some reason, 1 or more drives go down at random every night when backups run. Different tapes and different drives. Backups will be running fine and then drives begin to go down. These are SDLT320 drives. once they go down, you can't use robtest to move the tapes (medium not present error) or use the robtest unload command (device not present). If we power cycle the scsi bridge, we can talk to the drives and do what ever we want. STK is claiming that there is something coming from the host that is "polling" the library from the physical layer (assume HBA). We have had the SA for the master/media server disable any polling and load the latest patches from HP to no avail. We have changed from auto index to a manual map index as well. This was working from the end of June up until the second week in October. Thoughts/suggestions? Log snippets from last night: syslog entriesJan 4 05:37:42 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 05:50:10 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 11:27:52 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0800c0 I/O error during closeJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) Move_medium errorJan 4 11:34:36 ujachr01 tldd[4233]: TLD(1) drive 5 (device 4) is being DOWNED, status: Robotic dismount failureJan 4 11:34:36 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 5 (addr 504) access = 0 Contains Cartridge = yesSource address = 1119 (slot 120)Barcode = JA1156 Jan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) Move_medium errorJan 4 11:55:12 ujachr01 tldd[4233]: TLD(1) drive 1 (device 0) is being DOWNED, status: Robotic dismount failureJan 4 11:55:12 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 1 (addr 500) access = 0 Contains Cartridge = yesSource address = 1106 (slot 107)Barcode = JA1064 This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
RE: [Veritas-bu] DLT drives going down
Title: Message I assume its been physically powered down / restarted the drives / robot? Also, do the tapes go into a DOWN STATE during the middle of a backup, or beginning or would you say very random? Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:34To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down They have upgraded the FW to the latest/greatest and checked cables. I agree on the polling. From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 08:21To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down Hm what about Firmware for the SDLT tape drives? Any loose cables / connections or possible to change Scsi connectors? Not too sure why they feel the software is polling a drive could cause a problem?- if anything I would say polling a device is probably good as Netbackup confirms it can see it! The thing that makes me wonder if its cable / firmware issue is the comment "MEDIUM NOT PRESENT". Thanks Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:10To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] DLT drives going down We have an issue of drives randomly going down every night. NBU 5.0 mp5 HP-UX 11.11 STK L180 w/ STK 3400 scsi bridge. For some reason, 1 or more drives go down at random every night when backups run. Different tapes and different drives. Backups will be running fine and then drives begin to go down. These are SDLT320 drives. once they go down, you can't use robtest to move the tapes (medium not present error) or use the robtest unload command (device not present). If we power cycle the scsi bridge, we can talk to the drives and do what ever we want. STK is claiming that there is something coming from the host that is "polling" the library from the physical layer (assume HBA). We have had the SA for the master/media server disable any polling and load the latest patches from HP to no avail. We have changed from auto index to a manual map index as well. This was working from the end of June up until the second week in October. Thoughts/suggestions? Log snippets from last night: syslog entriesJan 4 05:37:42 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 05:50:10 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 11:27:52 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0800c0 I/O error during closeJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) Move_medium errorJan 4 11:34:36 ujachr01 tldd[4233]: TLD(1) drive 5 (device 4) is being DOWNED, status: Robotic dismount failureJan 4 11:34:36 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 5 (addr 504) access = 0 Contains Cartridge = yesSource address = 1119 (slot 120)Barcode = JA1156 Jan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) Move_medium errorJan 4 11:55:12 ujachr01 tldd[4233]: TLD(1) drive 1 (device 0) is being DOWNED, status: Robotic dismount failureJan 4 11:55:12 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 1 (addr 500) access = 0 Contains Cartridge = yesSource address = 1106 (slot 107)Barcode = JA1064 This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this
RE: [Veritas-bu] DLT drives going down
Title: Message ACtually just one more thing I noticed - you said they checked cables - what about REPLACE? Reason I say this, is due to the amount of time its been working (June to Oct) and we are now in Jan, so I think its safe to say it sounds like H/W Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:34To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down They have upgraded the FW to the latest/greatest and checked cables. I agree on the polling. From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 08:21To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down Hm what about Firmware for the SDLT tape drives? Any loose cables / connections or possible to change Scsi connectors? Not too sure why they feel the software is polling a drive could cause a problem?- if anything I would say polling a device is probably good as Netbackup confirms it can see it! The thing that makes me wonder if its cable / firmware issue is the comment "MEDIUM NOT PRESENT". Thanks Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:10To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] DLT drives going down We have an issue of drives randomly going down every night. NBU 5.0 mp5 HP-UX 11.11 STK L180 w/ STK 3400 scsi bridge. For some reason, 1 or more drives go down at random every night when backups run. Different tapes and different drives. Backups will be running fine and then drives begin to go down. These are SDLT320 drives. once they go down, you can't use robtest to move the tapes (medium not present error) or use the robtest unload command (device not present). If we power cycle the scsi bridge, we can talk to the drives and do what ever we want. STK is claiming that there is something coming from the host that is "polling" the library from the physical layer (assume HBA). We have had the SA for the master/media server disable any polling and load the latest patches from HP to no avail. We have changed from auto index to a manual map index as well. This was working from the end of June up until the second week in October. Thoughts/suggestions? Log snippets from last night: syslog entriesJan 4 05:37:42 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 05:50:10 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 11:27:52 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0800c0 I/O error during closeJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) Move_medium errorJan 4 11:34:36 ujachr01 tldd[4233]: TLD(1) drive 5 (device 4) is being DOWNED, status: Robotic dismount failureJan 4 11:34:36 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 5 (addr 504) access = 0 Contains Cartridge = yesSource address = 1119 (slot 120)Barcode = JA1156 Jan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) Move_medium errorJan 4 11:55:12 ujachr01 tldd[4233]: TLD(1) drive 1 (device 0) is being DOWNED, status: Robotic dismount failureJan 4 11:55:12 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 1 (addr 500) access = 0 Contains Cartridge = yesSource address = 1106 (slot 107)Barcode = JA1064 This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute
RE: [Veritas-bu] DLT drives going down
Title: Message Everything has been power cycled several times. The drives appear to go down at the end of a job. From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 08:47To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down I assume its been physically powered down / restarted the drives / robot? Also, do the tapes go into a DOWN STATE during the middle of a backup, or beginning or would you say very random? Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:34To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down They have upgraded the FW to the latest/greatest and checked cables. I agree on the polling. From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 08:21To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down Hm what about Firmware for the SDLT tape drives? Any loose cables / connections or possible to change Scsi connectors? Not too sure why they feel the software is polling a drive could cause a problem?- if anything I would say polling a device is probably good as Netbackup confirms it can see it! The thing that makes me wonder if its cable / firmware issue is the comment "MEDIUM NOT PRESENT". Thanks Simon WeaverTechnical SupportWindows Domain Administrator EADS AstriumTel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message-From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:10To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] DLT drives going down We have an issue of drives randomly going down every night. NBU 5.0 mp5 HP-UX 11.11 STK L180 w/ STK 3400 scsi bridge. For some reason, 1 or more drives go down at random every night when backups run. Different tapes and different drives. Backups will be running fine and then drives begin to go down. These are SDLT320 drives. once they go down, you can't use robtest to move the tapes (medium not present error) or use the robtest unload command (device not present). If we power cycle the scsi bridge, we can talk to the drives and do what ever we want. STK is claiming that there is something coming from the host that is "polling" the library from the physical layer (assume HBA). We have had the SA for the master/media server disable any polling and load the latest patches from HP to no avail. We have changed from auto index to a manual map index as well. This was working from the end of June up until the second week in October. Thoughts/suggestions? Log snippets from last night: syslog entriesJan 4 05:37:42 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 05:50:10 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0801c0 I/O error during closeJan 4 11:27:52 ujachr01 vmunix: SCSI TAPE: dev = 0xcd0800c0 I/O error during closeJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:34:36 ujachr01 tldcd[18968]: TLD(1) Move_medium errorJan 4 11:34:36 ujachr01 tldd[4233]: TLD(1) drive 5 (device 4) is being DOWNED, status: Robotic dismount failureJan 4 11:34:36 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 5 (addr 504) access = 0 Contains Cartridge = yesSource address = 1119 (slot 120)Barcode = JA1156 Jan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT PRESENTJan 4 11:55:12 ujachr01 tldcd[19684]: TLD(1) Move_medium errorJan 4 11:55:12 ujachr01 tldd[4233]: TLD(1) drive 1 (device 0) is being DOWNED, status: Robotic dismount failureJan 4 11:55:12 ujachr01 tldd[4233]: Check integrity of the drive, drive path, and media drive 1 (addr 500) access = 0 Contains Cartridge = yesSource address = 1106 (slot 107)Barcode = JA1064 This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
RE: [Veritas-bu] DLT drives going down
Check that the /dev/rmt/* entries match the devices in the robot. You can see if they do by inserting a tape into the drive and then issuing a mt -f /dev/rmt/* status for the /dev/rmt/ number you have the drive configured to. It should show a device is present, if not then you have a configuration issue. --On Wednesday, January 04, 2006 9:04 AM -0600 Barber, Layne (Contractor) [EMAIL PROTECTED] wrote: tapes stay in the drives and must be manually ejected. The robot doesn't remove the tapes because it thinks they are not there. It is acting as if the OS is losing communication with the device since robtest's unload command comes back with device not present. __ From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 08:58 To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down IF it happens at the end of the job, may be worth checking the robot itself perhaps? Do the tapes STAY in the tape drives when the error appears? In other words, does the Robot manage to REMOVE the tape from the Drive? Simon Weaver Technical Support Windows Domain Administrator EADS Astrium Tel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message- From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:56 To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down Everything has been power cycled several times. The drives appear to go down at the end of a job. __ From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 08:47 To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down I assume its been physically powered down / restarted the drives / robot? Also, do the tapes go into a DOWN STATE during the middle of a backup, or beginning or would you say very random? Simon Weaver Technical Support Windows Domain Administrator EADS Astrium Tel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message- From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED] Sent: 04 January 2006 14:34 To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down They have upgraded the FW to the latest/greatest and checked cables. I agree on the polling. __ This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] zoming survey/question
Title: Message Just curiousthose of you who admin your own zones/FC switches. How do you zone your drives/servers? for each HBA port, do you create a zone for the HBA port and all drives visable to it? ie. one HBA and 3 drives = 1 zone? ZONE_A = Server1_HBA0 DRIVE0 DRIVE1 DRIVE2 (then assuming SSO) ZONE_B = Server2_HBA0 DRIVE0 DRIVE1 DRIVE2 or do you set up a zone for each device? ie. one HBA and 3 drives = 3 zones. ZONE_A = SERVER1_HBA0 DRIVE0 ZONE_B = SERVER1_HBA0 DRIVE1 ZONE_C = SERVER1_HBA0 DRIVE2 (again assuming SSO) ZONE_D = SERVER2_HBA0 DRIVE0 ZONE_E = SERVER2_HBA0 DRIVE1 ZONE_F = SERVER2_HBA0 DRIVE2
[Veritas-bu] NB 6.0 DSSU's
Hi, I have a SAN with two DSSU's on the same partition(probably not the best thing).I need to free up some space on my DSSU's because I'm running out of space. Should i be using rm on the files i want to delete? Thanks Karl
RE: [Veritas-bu] NB 6.0 DSSU's
Title: Message Definitely NOT. Use the GUI and expire the PRIMARY IMAGE of backups that have been moved off to tape already. ~Kate -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]Sent: Wednesday, January 04, 2006 11:01 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NB 6.0 DSSU'sHi, I have a SAN with two DSSU's on the same partition(probably not the best thing).I need to free up some space on my DSSU's because I'm running out of space. Should i be using rm on the files i want to delete? Thanks Karl This e-mail may contain confidential or privileged information. If youthink you have received this e-mail in error, please advise the senderbyreply e-mail and then delete this e-mail immediately. Thank you.Aetna
RE: [Veritas-bu] NB 6.0 DSSU's
Title: Message I agree with kate :-) Shekhar Dhotre ICTStorage Engineering. v 404.846.7483 | f 404.848.1077 [EMAIL PROTECTED]48 Perimeter Center East | Atlanta, GA 30346 Remember the difference between a boss and a leader; a boss says "Go!" - a leader says "Let's go!" From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greenberg, Katherine ASent: Wednesday, January 04, 2006 11:07 AMTo: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] NB 6.0 DSSU's Definitely NOT. Use the GUI and expire the PRIMARY IMAGE of backups that have been moved off to tape already. ~Kate -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]Sent: Wednesday, January 04, 2006 11:01 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NB 6.0 DSSU'sHi, I have a SAN with two DSSU's on the same partition(probably not the best thing).I need to free up some space on my DSSU's because I'm running out of space. Should i be using rm on the files i want to delete? Thanks Karl This e-mail may contain confidential or privileged information. If youthink you have received this e-mail in error, please advise the senderbyreply e-mail and then delete this e-mail immediately. Thank you.Aetna "This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country."
RE: [Veritas-bu] NB 6.0 DSSU's
Steven Cashman [EMAIL PROTECTED] wrote on 01/04/2006 10:21:35 AM: Also be aware of how DSSUs operate. They will keep images that have been moved onto tape available on the disk until the disk starts getting full. Then as NBU needs more space it will start removeing older images. DSSU drives are almost always near full You should work to remove 2 DSSU pointing to the same device for this reason. Yea i found that out. I just need to free up some space until i'm able to partition the disk. Which means i might have to rm anyway. Karl
RE: [Veritas-bu] DLT drives going down
Title: RE: [Veritas-bu] DLT drives going down Try running "sgscan tapes" to see if you could see all your tape drives. If you dont see all your tape drives, you need to fix that problem first, then remap the drives. From: Xu, Ying [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 9:58 AMTo: 'Diane Marcotte'; Barber, Layne (Contractor); WEAVER, Simon; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down You need to remap the tape drives with device tree. This problem might occur if you reboot the server while one tape drive had issues, so the mapping messed up on OS. It happened a couple of time in our environment. -Original Message- From: Diane Marcotte [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 04, 2006 9:25 AM To: Barber, Layne (Contractor); WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down Check that the /dev/rmt/* entries match the devices in the robot. You can see if they do by inserting a tape into the drive and then issuing a mt -f /dev/rmt/* status for the /dev/rmt/ number you have the drive configured to. It should show a device is present, if not then you have a configuration issue. --On Wednesday, January 04, 2006 9:04 AM -0600 "Barber, Layne (Contractor)" [EMAIL PROTECTED] wrote: tapes stay in the drives and must be manually ejected. The robot doesn't remove the tapes because it thinks they are not there. It is acting as if the OS is losing communication with the device since robtest's unload command comes back with "device not present". __ From: WEAVER, Simon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 04, 2006 08:58 To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down IF it happens at the end of the job, may be worth checking the robot itself perhaps? Do the tapes STAY in the tape drives when the error appears? In other words, does the Robot manage to REMOVE the tape from the Drive? Simon Weaver Technical Support Windows Domain Administrator EADS Astrium Tel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message- From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED]] Sent: 04 January 2006 14:56 To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going downEverything has been power cycled several times. The drives appear to go down at the end of a job. __ From: WEAVER, Simon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 04, 2006 08:47 To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down I assume its been physically powered down / restarted the drives / robot? Also, do the tapes go into a DOWN STATE during the middle of a backup, or beginning or would you say very random? Simon Weaver Technical Support Windows Domain Administrator EADS Astrium Tel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message- From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED]] Sent: 04 January 2006 14:34 To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going downThey have upgraded the FW to the latest/greatest and checked cables. I agree on the polling. __This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu The information in this message may be proprietary and/or confidential,and protected from disclosure. If the reader of this message is notthe intended recipient, or an employee or agent responsible fordelivering this message to the intended recipient, you are herebynotified that any dissemination, distribution or copying of thiscommunication is strictly prohibited. If you have received thiscommunication in error, please notify First Data immediately byreplying to this message and deleting it from your computer.
RE: [Veritas-bu] DLT drives going down
After running getting them back, put an "ENABLE_AUTO_PATH_CORRECTION" entry in the vm.conf file. "Xu, Ying" [EMAIL PROTECTED] 1/4/2006 10:08:39 am Try running "sgscan tapes" to see if you could see all your tape drives. If you dont see all your tape drives, you need to fix that problem first, then remap the drives. From: Xu, Ying [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 9:58 AMTo: 'Diane Marcotte'; Barber, Layne (Contractor); WEAVER, Simon; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] DLT drives going down You need to remap the tape drives with device tree. This problem might occur if you reboot the server while one tape drive had issues, so the mapping messed up on OS. It happened a couple of time in our environment. -Original Message- From: Diane Marcotte [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 04, 2006 9:25 AM To: Barber, Layne (Contractor); WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down Check that the /dev/rmt/* entries match the devices in the robot. You can see if they do by inserting a tape into the drive and then issuing a mt -f /dev/rmt/* status for the /dev/rmt/ number you have the drive configured to. It should show a device is present, if not then you have a configuration issue. --On Wednesday, January 04, 2006 9:04 AM -0600 "Barber, Layne (Contractor)" [EMAIL PROTECTED] wrote: tapes stay in the drives and must be manually ejected. The robot doesn't remove the tapes because it thinks they are not there. It is acting as if the OS is losing communication with the device since robtest's unload command comes back with "device not present".__ From: WEAVER, Simon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 04, 2006 08:58 To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down IF it happens at the end of the job, may be worth checking the robot itself perhaps? Do the tapes STAY in the tape drives when the error appears? In other words, does the Robot manage to REMOVE the tape from the Drive? Simon Weaver Technical Support Windows Domain Administrator EADS Astrium Tel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message- From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED]] Sent: 04 January 2006 14:56 To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going downEverything has been power cycled several times. The drives appear to go down at the end of a job.__ From: WEAVER, Simon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 04, 2006 08:47 To: Barber, Layne (Contractor); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going down I assume its been physically powered down / restarted the drives / robot? Also, do the tapes go into a DOWN STATE during the middle of a backup, or beginning or would you say very random? Simon Weaver Technical Support Windows Domain Administrator EADS Astrium Tel: 02392-708598 Email: [EMAIL PROTECTED] -Original Message- From: Barber, Layne (Contractor) [mailto:[EMAIL PROTECTED]] Sent: 04 January 2006 14:34 To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] DLT drives going downThey have upgraded the FW to the latest/greatest and checked cables. I agree on the polling.__This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu The information in this message may be proprietary and/or confidential,and protected from disclosure. If the reader of this message is notthe intended recipient, or an employee or agent responsible fordelivering this message to the intended recipient, you are herebynotified that any dissemination, distribution or copying of thiscommunication is strictly prohibited. If you have received thiscommunication in error, please notify First Data immediately byreplying to this message and deleting it from your computer.
RE: [Veritas-bu] Raw Partition Restore
Title: Raw Partition Restore I just rebuilt a server, new OS (WIN2003) and new hardware, but same network location, server name etc etc... When I go into archive and restore I can seethe oldserver's past backups but for some reason the media server cannot connect to this machine. I've removed it from all policies and added it again but still nothing. Any ideas? Jonathan Martin Intersil Corporation Server and Security Operations [EMAIL PROTECTED] (321) 724-7314
RE: [Veritas-bu] zoming survey/question
This makes it much easier if you ever have to swap an HBA (and we have had one fail on our master/media server) - I only have to update 1 zone. If you configure port based zoning ,then you even don't have to make zone changes -just swap the failed HBAs or drives . Shekhar Dhotre ICT Storage Engineering. v 404.846.7483 | f 404.848.1077 [EMAIL PROTECTED] 48 Perimeter Center East | Atlanta, GA 30346 Remember the difference between a boss and a leader; a boss says Go! - a leader says Let's go! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Wednesday, January 04, 2006 3:11 PM To: Paul Keating Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] zoming survey/question On Wed, Jan 04, 2006 at 10:50:46AM -0500, Paul Keating wrote: Just curiousthose of you who admin your own zones/FC switches. How do you zone your drives/servers? for each HBA port, do you create a zone for the HBA port and all drives visable to it? ie. one HBA and 3 drives = 1 zone? Yup. We create 1 zone per host (per fabric). ZONE_A = Server1_HBA0 DRIVE0 DRIVE1 DRIVE2 (then assuming SSO) ZONE_B = Server2_HBA0 DRIVE0 DRIVE1 DRIVE2 In our case, our media server has a single zone on each fabric. It contains the WWNs of the HBA, the Fibre/SCSI bridges, and the storage arrays for its DSSUs. This makes it much easier if you ever have to swap an HBA (and we have had one fail on our master/media server) - I only have to update 1 zone. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] UNIX RAW PARTITION RESTORE QUESTION....
Title: UNIX RAW PARTITION RESTORE QUESTION All.. My original e-mail got stepped on by someone replying with another question in it, so I changed my subject and will ask my question again, here goes.. Our environment is HP-UX 11.11, Netbackup 5.1 MP3 backing up mostly HP unix with some Sun and Windows backups. I am doing a raw backup on one of the Sun servers and need to test the restore. I cant find any info on the steps for a raw restore, searched Symantics site and got lost, looked in the archives for this mailing list and came up with nothing. Looked in the System Administrators Guide and found very little. Can anyone point me to any Unix raw partition restore examples? My backup policy consists of 87 /dev/rdsk/c**t**d* entries. Can the restore be done via the gui? I know there is a Raw Partition Backups under the Restore Type pull down. But Im not sure what to do after that. I looked at the bprestore command and do not see anything referring to a raw restore. Any help or direction will be appreciated, thanks in advance. Wayne BeDour IT Unix System Administrator PH: 313-240-3374 FAX: 313-240-3065 Internet: [EMAIL PROTECTED] ** ** LEGAL DISCLAIMER ** ** This E-mail message and any attachments may contain legally privileged, confidential or proprietary information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this E-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this E-mail message from your computer.
RE: [Veritas-bu] EMC SIME with Exchange 2003
Title: Message Yes, I am mounting it to the SIME server. Yes, I can see the database files. Yes, I even tried copying these files to a different directory. That is what I dont understand. I have no exclude list yet when a backup runs for that directory, only the directories are backed up, not the files themselves. I only know this is because when I bring up the restore screen, I only see directories. The backup has a returned code of zero. Ken -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Wednesday, January 04, 2006 9:46 AM To: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] EMC SIME with Exchange 2003 Not with SIME. SIME integrates with Exchange to take a snapshot of the exchange database to a flatfile that can be backed up to tape, mounted on another exchange server. basically the same as telling SQL to do a hotbackup to a flat file, then using netbackup to backup the flat fileno need for the SQL agent. Kenneth, are you mounting the snap on an second exchange server, starting exchange services and backingit up from thereif so, then yeah, you would need to use the exchange agent to backup that server. you should be just mounting the volume as a share on a regular windows server, and backing it up as D:\, E:\ or whatever. can you see the database files when you browse for restore, before performing the actual restore? Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eliza Yam Sent: January 4, 2006 12:16 PM To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] EMC SIME with Exchange 2003 Exchange database backup requires NBUExchange Agent. From: Lee, Kenneth (SBS US) [EMAIL PROTECTED] To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] EMC SIME with Exchange 2003 Date: Tue, 3 Jan 2006 18:20:13 -0500 NetBackup 5.1 Solaris Client: Exchange 2003 server. I am using EMC SIME to backup Exchange. On the SIME server where the copy of the Exchange database is mounted, when I do a flat file backup of the Exchange database, I receive a return code of zero. But when I tried to restore the Exchange files, I only see the directories and never the actual database files. What am I missing and has anyone run into this problem? Thanks, Ken ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] vmphyinv File name already exists
Hello! I get this output whenever I do vmphyinv: vmphyinv -rn 0 -slot_range 1 7 -d hcart -non_interactive Waiting for mount of media from TLD(0), slot # 1 on host mktibackup Could not mount media from TLD(0), slot # 1 File name already exists We're running NB 5.0 MP5 with two TLDs, TLD(0) and TLD(1). Any clues? Thanks, Jan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RE: vmphyinv File name already exists
Got it. Found some old MNT_BY_SLOT_x_x files lying around in volmgr/misc. Duh :) Thanks, Jan -Original Message- From: Chaves, Jan Amcil L. Sent: Thursday, January 05, 2006 10:26 AM To: veritas-bu@mailman.eng.auburn.edu Subject: vmphyinv File name already exists Hello! I get this output whenever I do vmphyinv: vmphyinv -rn 0 -slot_range 1 7 -d hcart -non_interactive Waiting for mount of media from TLD(0), slot # 1 on host mktibackup Could not mount media from TLD(0), slot # 1 File name already exists We're running NB 5.0 MP5 with two TLDs, TLD(0) and TLD(1). Any clues? Thanks, Jan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
