[Veritas-bu] Another stupid question
Hello All, How do I get the equivalent of the GUI Media and Device Management -- Devices -- Media Servers from the command line? At the moment my Admin Console says everything is good, but the Java Console says two are offline. I want to confirm this from the command line which is far more trustworthy. I tried bpstulist with many different options. Regards, Patrick Whelan NetBackup Specialist Wholesale Markets and Treasury Trading Lloyds Banking Group Desk: +44 (0) 207 158 6123 Loc: OBS 2C-132 This e-mail is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland, number 95000. Telephone: 0131 225 4555. Lloyds TSB Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales, number 2065. Telephone: 020 7626 1500. Lloyds TSB Scotland plc. Registered Office: Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone: 0131 225 4555. Cheltenham Gloucester plc. Registered Office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales, number 2299428. Telephone: 01452 372372. Cheltenham Gloucester Savings is a division of Lloyds TSB Bank plc. Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham Gloucester plc are authorised and regulated by the Financial Services Authority. Telephone calls may be monitored or recorded. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email _ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Another stupid question
Patrick Does VMOPRCMD help ? Simon From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan, Patrick Sent: Tuesday, April 13, 2010 10:42 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Another stupid question Hello All, How do I get the equivalent of the GUI Media and Device Management -- Devices -- Media Servers from the command line? At the moment my Admin Console says everything is good, but the Java Console says two are offline. I want to confirm this from the command line which is far more trustworthy. I tried bpstulist with many different options. Regards, Patrick Whelan NetBackup Specialist Wholesale Markets and Treasury Trading Lloyds Banking Group Desk: +44 (0) 207 158 6123 Loc: OBS 2C-132 This e-mail is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland, number 95000. Telephone: 0131 225 4555. Lloyds TSB Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales, number 2065. Telephone: 020 7626 1500. Lloyds TSB Scotland plc. Registered Office: Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone: 0131 225 4555. Cheltenham Gloucester plc. Registered Office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales, number 2299428. Telephone: 01452 372372. Cheltenham Gloucester Savings is a division of Lloyds TSB Bank plc. Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham Gloucester plc are authorised and regulated by the Financial Services Authority. Telephone calls may be monitored or recorded. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. -o- 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] Another stupid question
Never mind. vmoprcmd -EMM. Java was correct. Regards, Patrick Whelan NetBackup Specialist Wholesale Markets and Treasury Trading Lloyds Banking Group Desk: +44 (0) 207 158 6123 Loc: OBS 2C-132 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan, Patrick Sent: 13 April 2010 10:42 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Another stupid question Hello All, How do I get the equivalent of the GUI Media and Device Management -- Devices -- Media Servers from the command line? At the moment my Admin Console says everything is good, but the Java Console says two are offline. I want to confirm this from the command line which is far more trustworthy. I tried bpstulist with many different options. Regards, Patrick Whelan NetBackup Specialist Wholesale Markets and Treasury Trading Lloyds Banking Group Desk: +44 (0) 207 158 6123 Loc: OBS 2C-132 This e-mail is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments. Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland, number 95000. Telephone: 0131 225 4555. Lloyds TSB Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales, number 2065. Telephone: 020 7626 1500. Lloyds TSB Scotland plc. Registered Office: Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone: 0131 225 4555. Cheltenham Gloucester plc. Registered Office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales, number 2299428. Telephone: 01452 372372. Cheltenham Gloucester Savings is a division of Lloyds TSB Bank plc. Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham Gloucester plc are authorised and regulated by the Financial Services Authority. Telephone calls may be monitored or recorded. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email _ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] MS EXCHANGE CCR Cluster Backup ISSUE
Did you increase the limit of size for the volume shadow copies? Limit defaults to 1G per volume. On out exchange servers that got used up pretty quick and the shadow copy instance of exchange runs out of space and gets aborted. I don't recall if that resulted in a 50 status. It is easy to fix, go and bump up the limits. I set mine to 10G for each mailstore and log volume. You can watch the amount used during the course of the backup. On 4/13/2010 1:01 AM, NBU wrote: Hi Forum, My Environment MASTER / MEDIA on Solaris 10 with 6.5.5 Enterprise. Trying to backup MS Echange 2007 mail boxes as storage group. Intially successfully configured and tested. But now when i start any exchange backup just before completing the snapshots it is failing with error code 50. Because of this my other network/BCV backups also getting failed. Using VSS option. Backup selection looks like below. - NEW_STREAM Microsoft Information Store:\MBX01-SG01-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG02-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG03-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG09-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG10-VIP01 NEW_STREAM Microsoft Information Store:\MBX01-SG13-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG14-EMP Microsoft Information Store:\Public Folder SG NEW_STREAM Microsoft Information Store:\MBX01-SG04-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG05-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG06-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG07-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG08-EMP NEW_STREAM Microsoft Information Store:\MBX01-SG11-NonEMP NEW_STREAM Microsoft Information Store:\MBX01-SG12-EMP NEW_STREAM Microsoft Information Store:\MBX01_Temp_SG -- Thanks in Advance. Regards +-- |This was sent by qureshiu...@rediffmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run a Tape Backup I get one of three status codes: 200, 252 or 800. I have researched all three and still have not been able to come up with a solution. I am running NBU 6.5 for Windows on a Dell 2950 with Server 2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run from the tapeloader all seem to pass and the inventories run from within NBU all seem to be correct, but I can't get anything to begin to write. Thanks, James McDonald System Administrator SAIC - IISBU 410-312-2232 mcdonal...@saic.com mailto:mcdonal...@saic.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Cannot Write to Tape
Have you rebooted the Master just in case? Anything changed to cause this problem? Have you enabled any logging? Simon From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of McDonald II, James F. Sent: Tuesday, April 13, 2010 1:43 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Cannot Write to Tape My backups write to disk without any problem, but when I try to run a Tape Backup I get one of three status codes: 200, 252 or 800. I have researched all three and still have not been able to come up with a solution. I am running NBU 6.5 for Windows on a Dell 2950 with Server 2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run from the tapeloader all seem to pass and the inventories run from within NBU all seem to be correct, but I can't get anything to begin to write. Thanks, James McDonald System Administrator SAIC - IISBU 410-312-2232 mcdonal...@saic.com mailto:mcdonal...@saic.com This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. -o- 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] retrying Error on job keeps going status 13
The new machine took the original machines name and IP. The only network activity is master server/ media server chatter. No backup data goes across the network. This media server only backs itself up. It takes long enough to do that, it has 11 300gb drives with over 15 million little files per drive. I was able to do backups if VSS was disabled. Not a real solution. It appears it was a windows install issue. There were two files that did not have the right date or time for the files at the service pack and patch level running on the server. Found the error using vshadow.exe -wm2 vhadow.txt on this machine and on a working media server. Found the problem showing path = \ on the bad media server ch3ecked the good media server found the file should have been where the \ was and replaced those files. Theyt were syste protected files so reboots were in order. After replacing the two files I am now able to backup the server using VSS for open files and getting volume shadow components. Thanks all who replied. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 1:16 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Hi Doug Becuase you get this message socket read failed, An existing connection was forcibly closed by the remote host, I am sort of 60% sure its network / file related. I take it, there are no firewalls in place between the server and the clients and no MAC lockdowns at all? You stated its a new Server, so thought I would just ask. Also, can the backup be done using NTBackup as a test (ie: try doing a netbackup test of a C: Drive of a client machine and then try using NTBackup on the same client). Simon -Original Message- From: WEAVER, Simon (external) Sent: Tuesday, April 13, 2010 9:14 AM To: 'Preston, Douglas'; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Have you tried to do a backup, without Open File Backups being enabled (as a test of course). Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Monday, April 12, 2010 4:36 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday, April 12, 2010 6:51 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting
Re: [Veritas-bu] Cannot Write to Tape
Hi, Reboot the master, run robtest and run s d does it show the drives OK? Justin. On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote: Have you rebooted the Master just in case? Anything changed to cause this problem? Have you enabled any logging? Simon From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of McDonald II, James F. Sent: Tuesday, April 13, 2010 1:43 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Cannot Write to Tape My backups write to disk without any problem, but when I try to run a Tape Backup I get one of three status codes: 200, 252 or 800. I have researched all three and still have not been able to come up with a solution. I am running NBU 6.5 for Windows on a Dell 2950 with Server 2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run from the tapeloader all seem to pass and the inventories run from within NBU all seem to be correct, but I can't get anything to begin to write. Thanks, James McDonald System Administrator SAIC - IISBU 410-312-2232 mcdonal...@saic.com mailto:mcdonal...@saic.com This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. -o- 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] retrying Error on job keeps going status 13
Yes Steve Anderson at Symantec support found this for me, He helped me spot the issue and gave me the resolution to try. http://seer.entsupport.symantec.com/docs/315898.htm Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 7:34 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Was this identified by Symantec? Was there a Technote about this? Handy to know this. Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Tuesday, April 13, 2010 3:09 PM To: WEAVER, Simon (external); VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 The new machine took the original machines name and IP. The only network activity is master server/ media server chatter. No backup data goes across the network. This media server only backs itself up. It takes long enough to do that, it has 11 300gb drives with over 15 million little files per drive. I was able to do backups if VSS was disabled. Not a real solution. It appears it was a windows install issue. There were two files that did not have the right date or time for the files at the service pack and patch level running on the server. Found the error using vshadow.exe -wm2 vhadow.txt on this machine and on a working media server. Found the problem showing path = \ on the bad media server ch3ecked the good media server found the file should have been where the \ was and replaced those files. Theyt were syste protected files so reboots were in order. After replacing the two files I am now able to backup the server using VSS for open files and getting volume shadow components. Thanks all who replied. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 1:16 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Hi Doug Becuase you get this message socket read failed, An existing connection was forcibly closed by the remote host, I am sort of 60% sure its network / file related. I take it, there are no firewalls in place between the server and the clients and no MAC lockdowns at all? You stated its a new Server, so thought I would just ask. Also, can the backup be done using NTBackup as a test (ie: try doing a netbackup test of a C: Drive of a client machine and then try using NTBackup on the same client). Simon -Original Message- From: WEAVER, Simon (external) Sent: Tuesday, April 13, 2010 9:14 AM To: 'Preston, Douglas'; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Have you tried to do a backup, without Open File Backups being enabled (as a test of course). Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Monday, April 12, 2010 4:36 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday, April 12, 2010 6:51 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives
Re: [Veritas-bu] Jobs Que up but will not Start
Which client works with Red Hat Linux? Is there a different Linux client for a 64-bit install? From: Patrick [mailto:netbac...@whelan-consulting.co.uk] Sent: Wednesday, April 07, 2010 3:25 PM To: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Jobs Que up but will not Start Do they eventually fail? If so after how long? Have you run all the usual tests (bptestbpcd, bpclntcmd, telneting to port bpcd, etc) all these tests should be run from the master, media servers and respective clients (unless of course you find the problem)? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk http://www.linkedin.com/in/patrickjosephwhelan From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of McDonald II, James F. Sent: 07 April 2010 19:25 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Jobs Que up but will not Start I recently noticed that I have a handful of jobs that are qued up, but won't seem to actually run. There have been no changes to the NBU configuration and it was working before. The only change that has occurred is that our network has been re-IP'd (IT assigned new IP's to our servers). Is this the problem? If so, how do I correct the problem quickly? I need to get my backups running again quickly. Thanks, James McDonald System Administrator SAIC - IISBU 410-312-2232 mcdonal...@saic.com mailto:mcdonal...@saic.com image001.gif___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] BPRESTORE flags.
Hi again, Trying to submit an Exchange restore from the command line this morning, with the following attributes: - alternate Exchange restore server - One specific mailstore, and associated logs (last full, up to today) - point-in-time recovery - alternate Temporary location for log and patch files - Commit - Mount I created the folder /usr/openv/netbackup/logs/bprestore so I could get an idea what jnbSA spits out when I select my options and launch the restore. Looks something similar to: bprestore -S master -D alternate_client -C host_client -X -s 1270847294 -e 1271107810 -t 16 -M -k -td L:\temp -cm -md -L default_log_name_and_path -W -f file_containing_file_directives Which is great, except I can't track down what a few of the flags mean (looks like they're undocumented features ;-), so I'm hesitant to use them: -X -M -W Anyone have any insight about those bprestore flags? Cheers, Jon La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU 6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 32) access = 1 Contains Cartridge = Yes
Barcode = 01L4
SCSI ID from drive 1 is 0
READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot inventory.
01L4 was not included in the inventory, but I'm almost positive it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run a
Tape Backup I get one of three status codes: 200, 252 or 800. I have
researched all three and still have not been able to come up with a
solution. I am running NBU 6.5 for Windows on a Dell 2950 with Server
2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run
from
the tapeloader all seem to pass and the inventories run from within
NBU
all seem to be correct, but I can't get anything to begin to write.
Thanks,
James McDonald
System Administrator
SAIC - IISBU
410-312-2232
mcdonal...@saic.com mailto:mcdonal...@saic.com
This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
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] Cannot Write to Tape
NBU has been writing to disk for a while, but I just recently tried
setting up the tape backups, for off-site storage. I have run
inventories and it says the volume configuration is up-to-date with the
contents.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:55 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU 6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 32) access = 1 Contains Cartridge = Yes
Barcode = 01L4
SCSI ID from drive 1 is 0
READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run a
Tape Backup I get one of three status codes: 200, 252 or 800. I have
researched all three and still have not been able to come up with a
solution. I am running NBU 6.5 for Windows on a Dell 2950 with
Server
2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run
from
the tapeloader all seem to pass and the inventories run from within
NBU
all seem to be correct, but I can't get anything to begin to write.
Thanks,
James McDonald
System Administrator
SAIC - IISBU
410-312-2232
mcdonal...@saic.com mailto:mcdonal...@saic.com
This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
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] Cannot Write to Tape
Hi,
It is discussed here:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/media-id-generation-50402/
You need to fix your vm.conf, delete all the media (since you said its not
been used yet) and re-inventory with the correct barcode information..
But I suspect something else may be going on as well.
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
NBU has been writing to disk for a while, but I just recently tried
setting up the tape backups, for off-site storage. I have run
inventories and it says the volume configuration is up-to-date with the
contents.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:55 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU 6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 32) access = 1 Contains Cartridge = Yes
Barcode = 01L4
SCSI ID from drive 1 is 0
READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run a
Tape Backup I get one of three status codes: 200, 252 or 800. I have
researched all three and still have not been able to come up with a
solution. I am running NBU 6.5 for Windows on a Dell 2950 with
Server
2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run
from
the tapeloader all seem to pass and the inventories run from within
NBU
all seem to be correct, but I can't get anything to begin to write.
Thanks,
James McDonald
System Administrator
SAIC - IISBU
410-312-2232
mcdonal...@saic.com mailto:mcdonal...@saic.com
This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
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] Cannot Write to Tape
Hi,
It would be helpful if you could show the error information for each type
of failed job, 200, 800 etc. 800 usually means a tape drive or robot is
unavailable (resources/etc).. Did you set it up/configure it correctly?
Justin
On Tue, 13 Apr 2010, Justin Piszcz wrote:
Hi,
It is discussed here:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/media-id-generation-50402/
You need to fix your vm.conf, delete all the media (since you said its not
been used yet) and re-inventory with the correct barcode information..
But I suspect something else may be going on as well.
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
NBU has been writing to disk for a while, but I just recently tried
setting up the tape backups, for off-site storage. I have run
inventories and it says the volume configuration is up-to-date with the
contents.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:55 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU 6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 32) access = 1 Contains Cartridge = Yes
Barcode = 01L4
SCSI ID from drive 1 is 0
READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run a
Tape Backup I get one of three status codes: 200, 252 or 800. I have
researched all three and still have not been able to come up with a
solution. I am running NBU 6.5 for Windows on a Dell 2950 with
Server
2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run
from
the tapeloader all seem to pass and the inventories run from within
NBU
all seem to be correct, but I can't get anything to begin to write.
Thanks,
James McDonald
System Administrator
SAIC - IISBU
410-312-2232
mcdonal...@saic.com mailto:mcdonal...@saic.com
This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
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 maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Cannot Write to Tape
I don't see anything wrong with his barcode, 6 or 8 both are allowed you
just have to be consistent.
Things to look at
1) you can see the tape drives when looking at hardware on the windows
os
2) in the gui you have setup the robot and when looking at
devices/robots it shows enabled. And it belongs to the master server
(if device host is master - robot control should be blank - meaning same
server)
3) when you look at drives you see all your drives with device host to
whatever media server is trying to do the backup. And it shows enabled.
4) if you look at the details of a tape drive you see a serial number
for the drive and you see a Robot Drive Number. Verify (by looking at
the web interface of the robot) that the robot drive number has the same
serial number - this is where a lot of people have issues (but I don't
think this is your problem)
5) you say that you have both disk backups and now are starting tape
backups. Are your schedules both in the same policy? Any chance that
your frequency between the disk and the tape are such that when the tape
window opens it does not think it needs a backup because the frequency
has been fulfilled by the disk backup? If in the same policy try
setting up a different policy and see if it works.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: Tuesday, April 13, 2010 10:20 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
It is discussed here:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-
lists-3/symantec-netbackup-18/media-id-generation-50402/
You need to fix your vm.conf, delete all the media (since you said its
not
been used yet) and re-inventory with the correct barcode information..
But I suspect something else may be going on as well.
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
NBU has been writing to disk for a while, but I just recently tried
setting up the tape backups, for off-site storage. I have run
inventories and it says the volume configuration is up-to-date with
the
contents.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:55 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU
6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to
limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried
the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 32) access = 1 Contains Cartridge = Yes
Barcode = 01L4
SCSI ID from drive 1 is 0
READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run
a
Tape Backup I get one of three status codes: 200, 252 or 800. I
have
researched all three and still have not been able to come up with a
solution. I am running NBU 6.5 for Windows on a Dell 2950 with
Server
2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run
from
the tapeloader all seem to pass and the inventories run from within
NBU
all seem to be correct, but I can't get anything to begin to write.
Thanks,
James McDonald
System Administrator
SAIC - IISBU
410-312-2232
mcdonal...@saic.com mailto:mcdonal...@saic.com
This email (including any attachments) may contain confidential
and/or privileged information or
Re: [Veritas-bu] retrying Error on job keeps going status 13
The errors in NBU did not reflect this issue. The errors you see in the Technote are from the output of vshadow.exe -wm2 With debug logging and all logging turned on as high as they get there was no mention of anything that would indicate the issue that this technote refers to. But doing a search on their support site with this bpbkar to provide an Application Pop Up Error takes me in a roundabout way to the technote. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 7:48 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Was you getting these error messages in your logs? Simon -Original Message- From: Preston, Douglas [mailto:dlpres...@lereta.com] Sent: Tuesday, April 13, 2010 3:39 PM To: WEAVER, Simon (external); VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Yes Steve Anderson at Symantec support found this for me, He helped me spot the issue and gave me the resolution to try. http://seer.entsupport.symantec.com/docs/315898.htm Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 7:34 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Was this identified by Symantec? Was there a Technote about this? Handy to know this. Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Tuesday, April 13, 2010 3:09 PM To: WEAVER, Simon (external); VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 The new machine took the original machines name and IP. The only network activity is master server/ media server chatter. No backup data goes across the network. This media server only backs itself up. It takes long enough to do that, it has 11 300gb drives with over 15 million little files per drive. I was able to do backups if VSS was disabled. Not a real solution. It appears it was a windows install issue. There were two files that did not have the right date or time for the files at the service pack and patch level running on the server. Found the error using vshadow.exe -wm2 vhadow.txt on this machine and on a working media server. Found the problem showing path = \ on the bad media server ch3ecked the good media server found the file should have been where the \ was and replaced those files. Theyt were syste protected files so reboots were in order. After replacing the two files I am now able to backup the server using VSS for open files and getting volume shadow components. Thanks all who replied. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 1:16 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Hi Doug Becuase you get this message socket read failed, An existing connection was forcibly closed by the remote host, I am sort of 60% sure its network / file related. I take it, there are no firewalls in place between the server and the clients and no MAC lockdowns at all? You stated its a new Server, so thought I would just ask. Also, can the backup be done using NTBackup as a test (ie: try doing a netbackup test of a C: Drive of a client machine and then try using NTBackup on the same client). Simon -Original Message- From: WEAVER, Simon (external) Sent: Tuesday, April 13, 2010 9:14 AM To: 'Preston, Douglas'; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Have you tried to do a backup, without Open File Backups being enabled (as a test of course). Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Monday, April 12, 2010 4:36 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday,
Re: [Veritas-bu] Cannot Write to Tape
Judy
I suggested to young James to create a new Policy (and even reboot the
Master. I think Justin did too).
However; not had feedback on this yet.
I only made this request, due to the status codes being reported back.
Regards
Simon
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
judy_hinchcli...@administaff.com
Sent: Tuesday, April 13, 2010 4:31 PM
To: jpis...@lucidpixels.com; james.f.mcdonald...@saic.com
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
I don't see anything wrong with his barcode, 6 or 8 both are allowed you
just have to be consistent.
Things to look at
1) you can see the tape drives when looking at hardware on the windows
os
2) in the gui you have setup the robot and when looking at
devices/robots it shows enabled. And it belongs to the master server (if
device host is master - robot control should be blank - meaning same
server)
3) when you look at drives you see all your drives with device host to
whatever media server is trying to do the backup. And it shows enabled.
4) if you look at the details of a tape drive you see a serial number
for the drive and you see a Robot Drive Number. Verify (by looking at
the web interface of the robot) that the robot drive number has the same
serial number - this is where a lot of people have issues (but I don't
think this is your problem)
5) you say that you have both disk backups and now are starting tape
backups. Are your schedules both in the same policy? Any chance that
your frequency between the disk and the tape are such that when the tape
window opens it does not think it needs a backup because the frequency
has been fulfilled by the disk backup? If in the same policy try
setting up a different policy and see if it works.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: Tuesday, April 13, 2010 10:20 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
It is discussed here:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-
lists-3/symantec-netbackup-18/media-id-generation-50402/
You need to fix your vm.conf, delete all the media (since you said its
not been used yet) and re-inventory with the correct barcode
information..
But I suspect something else may be going on as well.
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
NBU has been writing to disk for a while, but I just recently tried
setting up the tape backups, for off-site storage. I have run
inventories and it says the volume configuration is up-to-date with
the
contents.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:55 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU
6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to
limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried
the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information) s d drive 1 (addr 32)
access = 1 Contains Cartridge = Yes Barcode = 01L4 SCSI ID from
drive 1 is 0 READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run
a
Tape Backup I get one of three status codes: 200, 252 or 800. I
have
researched
Re: [Veritas-bu] Cannot Write to Tape
As an after thought, re-run Device Configuration Wizard perhaps as well?
Simon
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
judy_hinchcli...@administaff.com
Sent: Tuesday, April 13, 2010 4:31 PM
To: jpis...@lucidpixels.com; james.f.mcdonald...@saic.com
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
I don't see anything wrong with his barcode, 6 or 8 both are allowed you
just have to be consistent.
Things to look at
1) you can see the tape drives when looking at hardware on the windows
os
2) in the gui you have setup the robot and when looking at
devices/robots it shows enabled. And it belongs to the master server (if
device host is master - robot control should be blank - meaning same
server)
3) when you look at drives you see all your drives with device host to
whatever media server is trying to do the backup. And it shows enabled.
4) if you look at the details of a tape drive you see a serial number
for the drive and you see a Robot Drive Number. Verify (by looking at
the web interface of the robot) that the robot drive number has the same
serial number - this is where a lot of people have issues (but I don't
think this is your problem)
5) you say that you have both disk backups and now are starting tape
backups. Are your schedules both in the same policy? Any chance that
your frequency between the disk and the tape are such that when the tape
window opens it does not think it needs a backup because the frequency
has been fulfilled by the disk backup? If in the same policy try
setting up a different policy and see if it works.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: Tuesday, April 13, 2010 10:20 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
It is discussed here:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-
lists-3/symantec-netbackup-18/media-id-generation-50402/
You need to fix your vm.conf, delete all the media (since you said its
not been used yet) and re-inventory with the correct barcode
information..
But I suspect something else may be going on as well.
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
NBU has been writing to disk for a while, but I just recently tried
setting up the tape backups, for off-site storage. I have run
inventories and it says the volume configuration is up-to-date with
the
contents.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:55 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU
6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to
limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried
the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information) s d drive 1 (addr 32)
access = 1 Contains Cartridge = Yes Barcode = 01L4 SCSI ID from
drive 1 is 0 READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run
a
Tape Backup I get one of three status codes: 200, 252 or 800. I
have
researched all three and still have not been able to come up with a
solution. I am running NBU 6.5 for Windows on a Dell 2950 with
Server
2003 as the OS. The
Re: [Veritas-bu] Cannot Write to Tape
Hi,
Good idea, and/or tpautoconf -a if you like command line :)
But he did run robtest and it did show the drives etc, he could also show
tpconfig -d and vmoprcmd -d ds.
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
As an after thought, re-run Device Configuration Wizard perhaps as well?
Simon
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
judy_hinchcli...@administaff.com
Sent: Tuesday, April 13, 2010 4:31 PM
To: jpis...@lucidpixels.com; james.f.mcdonald...@saic.com
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
I don't see anything wrong with his barcode, 6 or 8 both are allowed you
just have to be consistent.
Things to look at
1) you can see the tape drives when looking at hardware on the windows
os
2) in the gui you have setup the robot and when looking at
devices/robots it shows enabled. And it belongs to the master server (if
device host is master - robot control should be blank - meaning same
server)
3) when you look at drives you see all your drives with device host to
whatever media server is trying to do the backup. And it shows enabled.
4) if you look at the details of a tape drive you see a serial number
for the drive and you see a Robot Drive Number. Verify (by looking at
the web interface of the robot) that the robot drive number has the same
serial number - this is where a lot of people have issues (but I don't
think this is your problem)
5) you say that you have both disk backups and now are starting tape
backups. Are your schedules both in the same policy? Any chance that
your frequency between the disk and the tape are such that when the tape
window opens it does not think it needs a backup because the frequency
has been fulfilled by the disk backup? If in the same policy try
setting up a different policy and see if it works.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: Tuesday, April 13, 2010 10:20 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
It is discussed here:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-
lists-3/symantec-netbackup-18/media-id-generation-50402/
You need to fix your vm.conf, delete all the media (since you said its
not been used yet) and re-inventory with the correct barcode
information..
But I suspect something else may be going on as well.
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
NBU has been writing to disk for a while, but I just recently tried
setting up the tape backups, for off-site storage. I have run
inventories and it says the volume configuration is up-to-date with
the
contents.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:55 AM
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU
6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to
limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried
the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information) s d drive 1 (addr 32)
access = 1 Contains Cartridge = Yes Barcode = 01L4 SCSI ID from
drive 1 is 0 READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's
in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to
Re: [Veritas-bu] Cannot Write to Tape
What does the output of vmquery -list_media_genrule show?
Regards,
Patrick Whelan
NetBackup Specialist
Wholesale Markets and Treasury Trading
Lloyds Banking Group
Desk: +44 (0) 207 158 6123
Loc: OBS 2C-132
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Justin
Piszcz
Sent: 13 April 2010 15:55
To: McDonald II, James F.
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Please include the list in the future.
It appears you need to limit your labels to 6 characters.
Check the volume manager manual, you need to edit vm.conf for NBU 6.x++
the labels for LTOX should be no more than 6 characters long, if your
barcode reader reads more than the first 6 characters, you need to limit
it.
BTW, is this a new environment?
Or did this just start happening?
If it just started happening, have you run an inventory and retried the
backup?
Justin.
On Tue, 13 Apr 2010, McDonald II, James F. wrote:
Here is what I got when I ran the test:
Opening {4,0,33,1}
MODE_SENSE Complete
Enter tld commands (? returns help information) s d drive 1 (addr 32)
access = 1 Contains Cartridge = Yes Barcode = 01L4 SCSI ID from
drive 1 is 0 READ_ELEMENT_STATUS Complete
I tried double-checking the barcode result, by doing a robot
inventory.
01L4 was not included in the inventory, but I'm almost positive
it's in there.
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Tuesday, April 13, 2010 10:12 AM
To: WEAVER, Simon (external)
Cc: McDonald II, James F.; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cannot Write to Tape
Hi,
Reboot the master, run robtest and run s d does it show the drives
OK?
Justin.
On Tue, 13 Apr 2010, WEAVER, Simon (external) wrote:
Have you rebooted the Master just in case?
Anything changed to cause this problem?
Have you enabled any logging?
Simon
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
McDonald
II, James F.
Sent: Tuesday, April 13, 2010 1:43 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Cannot Write to Tape
My backups write to disk without any problem, but when I try to run a
Tape Backup I get one of three status codes: 200, 252 or 800. I have
researched all three and still have not been able to come up with a
solution. I am running NBU 6.5 for Windows on a Dell 2950 with
Server
2003 as the OS. The tape drive is a Dell PV-124T. Diagnostics run
from
the tapeloader all seem to pass and the inventories run from within
NBU
all seem to be correct, but I can't get anything to begin to write.
Thanks,
James McDonald
System Administrator
SAIC - IISBU
410-312-2232
mcdonal...@saic.com mailto:mcdonal...@saic.com
This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected from
disclosure. If you are not the intended recipient, please notify the
sender immediately, do not copy this message or any attachments and
do not use it for any purpose or disclose its content to any person,
but delete this message and any attachments from your system. Astrium
disclaims any and all liability if this email transmission was virus
corrupted, altered or falsified.
-o-
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
This e-mail is private and confidential and may contain privileged material. If
you have received this e-mail in error, please notify the sender and delete it
immediately. You must not copy, distribute, disclose or use any of the
information in it or any attachments.
Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ.
Registered in Scotland, number 95000. Telephone: 0131 225 4555.
Lloyds TSB Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN.
Registered in England and Wales, number 2065. Telephone: 020 7626 1500.
Lloyds TSB Scotland plc. Registered Office: Henry Duncan House, 120 George
Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone:
0131 225 4555.
Cheltenham Gloucester plc. Registered Office: Barnett Way, Gloucester GL4
3RL. Registered in England and Wales, number 2299428. Telephone: 01452 372372.
Cheltenham Gloucester Savings is a division of Lloyds TSB Bank plc.
Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham Gloucester plc
are authorised and regulated by the Financial Services Authority.
Telephone calls may be monitored or recorded.
Re: [Veritas-bu] Jobs Que up but will not Start
On Tue, Apr 13, 2010 at 9:51 AM, McDonald II, James F. james.f.mcdonald...@saic.com wrote: Which client works with Red Hat Linux? Is there a different Linux client for a 64-bit install? For NetBackup 6.x and earlier, all RHEL clients are 32-bit although they will install and run on 64-bit RHEL. For NetBackup 7.x, *only* 64-bit clients are available although you can use on a 6.x 32-bit client with a 7.x master/media server. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org Linkedin http://www.linkedin.com/in/ewilts ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Backup starts off strong, then does not complete.
http://seer.entsupport.symantec.com/docs/267292.htm Seen this before and easiest way to determine where the failure occurs, without changing your policy is to follow the above technote... DON'T LEAVE THE TOUCHFILE IN PLACE otherwise you will run out of space in your logs folder. Allow the job to complete, ie dont cancel (get a status 150) and the last path in your log will be where the issue occurs. This could be related to any of the items mentioned above (disk, path depths etc). When you identify where the problem is you can then assess whether the policy should be broken up or if housekeeping should be done. Cheers, Jason +-- |This was sent by jason.mcc...@it-virtualised.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] New tapes are frozen
Hi Thanks for the reply. The Tape drive we are using is HP MSL G3. We also have the same problem with the Virtual tape library using Data domain. I think label manually is a temp solution for this, however it should be able to auto label it. Thanks and Regards, Leo On Sun, Apr 11, 2010 at 5:25 AM, Martin, Jonathan jmart...@intersil.comwrote: Have you tried running HP’s library and tape tools? http://h2.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=406731locale=en_UStaskId=135prodSeriesId=406729prodTypeId=12169 I would run the suspected bad media and several known good media. I’ve had quirky issues like this before and generally speaking it’s been the drive. -Jonathan *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Leo Dream *Sent:* Saturday, April 10, 2010 3:49 PM *To:* Veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] New tapes are frozen Hi All Recently we are having some errors with the tapes. We add some new tapes to the library and inventory successfully (with bar code). However when we run backups, the tapes are frozen, following errors are shown in the bptm log: io_ioctl: ioctl (MTWEOF) failed on media id XX, drive index 1, The media is write protected. (19) (bptm.c.23992) The strange thing is: 1. The tape is not write protected for sure. 2. If i unfreeze the tape and rerun the backup, the tape can be used without any problem, so don't know why we have write error the first time. The master server is 6.5.5 on Windows 2003 Standard server (64 bit), the tape drive is HP. Anyone has any idea? Thanks! Leo ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
