Re: [Veritas-bu] Tape counter missing
Are you logged on directly on the Windows console? RDP will not work. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Chris Freemantle Gesendet: Montag, 23. April 2007 15:08 An: Veritas List Betreff: [Veritas-bu] Tape counter missing I have no performance meter tape counters or NBConsole 'Drive Use History'. I think I've satisfied all the requirements. Suggestions anyone? I've recently installed the Veritas drivers, having been using HP drivers. I've ticked 'enable performance data collection', I do have permission to read the registry and I've looked when jobs are actively transferring data. I'm running NBU 5.1 MP6 under Windows server 2003 service pack 2, connected to an HP LTO-3 drive in an Overland Neo 4000 library. The master server is the media server. The tape driver is the Symantec driver dated 12.1.07 version 5.0.25.0 in file .../system32/DRIVERS/halfinch.sys TIA -- --- REMEMBER- There is only one certainty about storage systems - they *will* fail ! This includes backup and archiving systems. If you want to be paranoid, make your own backups as well. For FIL computer support issues, please email [EMAIL PROTECTED] rather than individual team members Chris Freemantle Data Manager Wellcome Trust Centre for Neuroimaging Tel. +44 (0)20 7833 7472 reception Tel. +44 (0)20 7833 7496 direct Fax +44 (0)20 7813 1420 Home Page: http://www.fil.ion.ucl.ac.uk ___ 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] SAP-Backup on Solaris 10 container/lofs
Hi there, i'm trying to back up the sap/oracle database of a solaris 10 container. The SAP logfile is fine, it says all datafiles got backed up. In my netbackup activity monitor the job shows only the first datafile, nothing gets backed up and a valid but empty image is written to the tape (status 0). The client log shows something like this: WRN - /oracle/SID/ is on file system type lofs. Skipping. Is there a way not to skip the files on a loopback filesystem? Standard policies work, when the checkbox "Follow NFS" is set, but in this SAP policy it does not help - the files are skipped by the backint on the client... Frerk ___ Veritas-bu maillist - [EMAIL PROTECTED] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] [Need Email Alerts] SSO Drives for SAN Media Servers
Hi, you could run vmoprcmd and grep through it for the drive and its control - if it is not accessible there should be an errorcode returned. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Wilkinson, Alex Gesendet: Donnerstag, 2. November 2006 08:53 An: veritas-bu@mailman.eng.auburn.edu Betreff: [Veritas-bu] [Need Email Alerts] SSO Drives for SAN Media Servers Hi all, We are using NB 6.0-MP3. I would like to be emailed alerts if my SSO Drives are not accessible by my SAN Media Servers. Is this possible ? And how ? Cheers -aW ___ 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] status 1 (was: Typical success rates?)
The Report does its job. But there were about 400 jobs with returncode 1 in the past 5 days, anything that could be automated would help. -Ursprüngliche Nachricht- Von: WEAVER, Simon [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 30. Juni 2006 14:25 An: Schindelasch, Frerk; veritas-bu@mailman.eng.auburn.edu Betreff: RE: [Veritas-bu] status 1 (was: Typical success rates?) Not sure about command line, but doesn't the problem reports go into details? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Schindelasch, Frerk [mailto:[EMAIL PROTECTED] Sent: 30 June 2006 13:15 To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] status 1 (was: Typical success rates?) Is it possible, to get a list of the files not backed up in a job exiting with RC 1 from the command line? -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von WEAVER, Simon Gesendet: Freitag, 30. Juni 2006 13:53 An: 'Jeff Lightner'; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Betreff: Re: [Veritas-bu] status 1 (was: Typical success rates?) Jeff Agree, as mentioned below in a Status 1 backup 1) exclude the file/files that are causing the status code 2) Investigate issue and if not relevant, revert to point 1. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: 30 June 2006 12:49 To: WEAVER, Simon; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] status 1 (was: Typical success rates?) Status 1 is not a failure UNLESS it's a database backup. For filesystems everywhere I've been we've shown that a status 1 is not a failure but a warning. Unfortunately you won't get Veritas to officially confirm that. Some things I've seen cause a status 1: Open files. Files changed between the time the list for backup and the actual write to tape occurred. Sun "Door" files. We verified extensively at a job that required FDA Validation that restores from such backups were indeed complete to the point in time the backup was started. At that job we simply had to document that a status 1 was a success for all but database backups. Note that due to the status 1 scheduling tools Tivoli Work Scheduler (Maestro) that show abends for non zero exit status need to be massaged. You basically have to have the Maestro job script check for status 1 and mark exit the script with status 0 to prevent this. "exit 0" is all you have to do in a script to make this work. It took me a while to get our schedulers to understand this concept but once they did and I gave them the syntax they were able to avoid reported abends for this. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon Sent: Friday, June 30, 2006 4:16 AM To: '[EMAIL PROTECTED]'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] status 1 (was: Typical success rates?) Bob As the image is stored in the DB, I still see Status 1 as a good backup. As long as you can get the data that needs to be backed up, and you identify the reason for the "1" you have 2 options in my view: 1) exclude the file/files that are causing the status code 2) Investigate and if not relevant, revert to point 1. Anything higher is what I class a failure. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: bob944 [mailto:[EMAIL PROTECTED] Sent: 30 June 2006 08:13 To: veritas-bu@mailman.eng.auburn.edu; WEAVER, Simon Subject: RE: [Veritas-bu] status 1 (was: Typical success rates?) > Exclude the "1"'s as I dont class them as failures :-) Which might be why NetBackup defines stat 1 as "partial success" _and keeps the image_. Final status <= 1 yields a restorable image; status > 1 does not (archives excluded). I think we agree that stat 1 beats the heck out of stat > 1. That said, Operations can not accept a stat 1 without investigation. What is a status 1--is it one of the 15-odd conditions in the Status 1 section of the NetBackup Troubleshooting Guide? Is it "just another goofy Windows busy perfdat file?" The definition Ops must apply is "of all the files which were to be backed up, some were and some were not." Example A: Files to be backed up (seletion minus excludes plus includes: 1,000,000 Files backed up: 999,999 Files not backed up: 1 Status: 1 Example B: Files to
Re: [Veritas-bu] status 1 (was: Typical success rates?)
Is it possible, to get a list of the files not backed up in a job exiting with RC 1 from the command line? -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von WEAVER, Simon Gesendet: Freitag, 30. Juni 2006 13:53 An: 'Jeff Lightner'; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Betreff: Re: [Veritas-bu] status 1 (was: Typical success rates?) Jeff Agree, as mentioned below in a Status 1 backup 1) exclude the file/files that are causing the status code 2) Investigate issue and if not relevant, revert to point 1. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: 30 June 2006 12:49 To: WEAVER, Simon; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] status 1 (was: Typical success rates?) Status 1 is not a failure UNLESS it's a database backup. For filesystems everywhere I've been we've shown that a status 1 is not a failure but a warning. Unfortunately you won't get Veritas to officially confirm that. Some things I've seen cause a status 1: Open files. Files changed between the time the list for backup and the actual write to tape occurred. Sun "Door" files. We verified extensively at a job that required FDA Validation that restores from such backups were indeed complete to the point in time the backup was started. At that job we simply had to document that a status 1 was a success for all but database backups. Note that due to the status 1 scheduling tools Tivoli Work Scheduler (Maestro) that show abends for non zero exit status need to be massaged. You basically have to have the Maestro job script check for status 1 and mark exit the script with status 0 to prevent this. "exit 0" is all you have to do in a script to make this work. It took me a while to get our schedulers to understand this concept but once they did and I gave them the syntax they were able to avoid reported abends for this. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon Sent: Friday, June 30, 2006 4:16 AM To: '[EMAIL PROTECTED]'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] status 1 (was: Typical success rates?) Bob As the image is stored in the DB, I still see Status 1 as a good backup. As long as you can get the data that needs to be backed up, and you identify the reason for the "1" you have 2 options in my view: 1) exclude the file/files that are causing the status code 2) Investigate and if not relevant, revert to point 1. Anything higher is what I class a failure. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: bob944 [mailto:[EMAIL PROTECTED] Sent: 30 June 2006 08:13 To: veritas-bu@mailman.eng.auburn.edu; WEAVER, Simon Subject: RE: [Veritas-bu] status 1 (was: Typical success rates?) > Exclude the "1"'s as I dont class them as failures :-) Which might be why NetBackup defines stat 1 as "partial success" _and keeps the image_. Final status <= 1 yields a restorable image; status > 1 does not (archives excluded). I think we agree that stat 1 beats the heck out of stat > 1. That said, Operations can not accept a stat 1 without investigation. What is a status 1--is it one of the 15-odd conditions in the Status 1 section of the NetBackup Troubleshooting Guide? Is it "just another goofy Windows busy perfdat file?" The definition Ops must apply is "of all the files which were to be backed up, some were and some were not." Example A: Files to be backed up (seletion minus excludes plus includes: 1,000,000 Files backed up: 999,999 Files not backed up: 1 Status: 1 Example B: Files to be backed up (seletion minus excludes plus includes: 1,000,000 Files backed up: 1 Files not backed up: 999,999 Status: 1 Hence the BBP requirement that intelligence, artificial or human, be applied to stat 1s every time. 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 This email is for the intended addressee only. If you have received it in error then you must not use, retain
