[Veritas-bu] Move of BackupExec 10d problem
Hello Does anybody have a procedure for moving BackupExec 10d ? I have found this http://seer.support.veritas.com/docs/260054.htm for 9.X. Unfortunately the servers guys didn't follow it to the letter, so now we can't get backupexec to start I think the big problem is that they didn't export the registry keys Any suggestions/ideas is welcome Regards Michael -- 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] Move of BackupExec 10d problem
Whoa there... Following documents to the letter costs extra. =P -J -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 21, 2007 8:00 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Move of BackupExec 10d problem Hello Does anybody have a procedure for moving BackupExec 10d ? I have found this http://seer.support.veritas.com/docs/260054.htm for 9.X. Unfortunately the servers guys didn't follow it to the letter, so now we can't get backupexec to start I think the big problem is that they didn't export the registry keys Any suggestions/ideas is welcome Regards Michael -- Cybercity Webhosting (http://www.cybercity.dk) ___ 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] Move of BackupExec 10d problem
In my experience not following documents to the letter cost a shitload of extra work. On Wed, 21 Mar 2007 08:58:22 -0400, Martin, Jonathan (Contractor) wrote Whoa there... Following documents to the letter costs extra. =P -J -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 21, 2007 8:00 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Move of BackupExec 10d problem Hello Does anybody have a procedure for moving BackupExec 10d ? I have found this http://seer.support.veritas.com/docs/260054.htm for 9.X. Unfortunately the servers guys didn't follow it to the letter, so now we can't get backupexec to start I think the big problem is that they didn't export the registry keys Any suggestions/ideas is welcome Regards Michael -- Cybercity Webhosting (http://www.cybercity.dk) ___ 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 -- Cybercity Webhosting (http://www.cybercity.dk) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Move of BackupExec 10d problem update
I get this in the application event log: Event Type: Error Event Source: Backup Exec Event Category: (65535) Event ID: 57802 Date: 3/22/2007 Time: 1:15:07 AM User: N/A Computer: AU01SN004 Description: The Backup Exec Server Service did not start. An internal error (1627652097) occurred in object -1. For more information, click the following link: http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml unfortunately none of the technotes in the link solves my problem Michael -- Cybercity Webhosting (http://www.cybercity.dk) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Online Catalog backups
Solaris 9 Netbackup 6.0 MP2, does anyone know if the online HOT backups, FULL and INCR contain a copy of the /usr/openv/db/data files, I cannot see them with bprecover -l -tpath .etc ... Eustace Fernandes Technical Support mailto:[EMAIL PROTECTED] voice (403) 237-1534 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Symantec ?!Support?!
I read the threads, and had the same conclusion several of you did even before reviewing the issues presented here. Is anyone else having problems getting through or using https://mysupport.symantec.com/ I get this about 95% of the time, sometimes even before I can login. -8--- MySupport Application Error The MySupport application has encountered a program error. You can either try again or contact Symantec Technical Services Thank you for your patience. 8-- Raising the issue to my local sales/support staff here in Southern California has occasionally generated a sympathetic response, but not much else. I think the wrong company got bought. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Exclusion lists based on policy?
Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Drive Cleaning Frequency for SSO Drives
Yes, our manufacture recommended we clean our tape drives based on usage hours. I will look into TapeAlert and ensure it is enabled since it looks like the only way to clean our tape drives with the current version of NetBackup we have. Thanks for the information all! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 -Original Message- From: bob944 [mailto:[EMAIL PROTECTED] Sent: Sunday, March 18, 2007 3:20 PM To: veritas-bu@mailman.eng.auburn.edu; Ellis, Jason Subject: RE: [Veritas-bu] Drive Cleaning Frequency for SSO Drives In our NBU 6.0 MP4 environment we can clean SSO drives, but we also have three NBU 5.1 MP4 environments, which will not let us clean SSO drives. [...] Is there a why to specify the cleaning frequency on SSO drives? The cleaning frequency setting under Device Monitor, accessed by right-clicking on the drive and selecting Drive Cleaning Set Cleaning Frequency, is grayed out on all our SSO drives. Additionally there does not seem to be a way to change the attributes of the tape drive to specify a cleaning frequency from the Change Drive dialogue box for our SSO drives. Are you still trying to set frequency-based cleaning on your drives? Why? Unless you have antique drives, they will almost certainly implement the TapeAlert standard and/or self-clean. Do you have your drive manufacturer's recommendation to clean them based on usage hours? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
You need to create the exclude list on the client. if each client is only backed up by one policy, you can just call it exclude_list, but if the client is backed up by more than one policy, you need to call it exlcude_list.POLICY_NAME. I'm not sure if that's what you're asking, or if you're asking how to somehow specify from the master/policy, to backup ALL_LOCAL_DRIVES but not C and System_State:\ which you cannot. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: March 21, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 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] Exclusion lists based on policy?
You can do this locally on each system, Bring up the backup archive and restore window on the client Select the Netbackup Client options In there you will find Exclude and Include tabs. Thais should Help Matt From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: Wednesday, March 21, 2007 9:29 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] content of hot catalog backup
Hello, I'm running Netbackup 6.0 MP4 and I'm doing everyday full hot catalog backup to a tape drive. Is there a command to check and list the content of each catalog image ( bplist command with some specific arguments ) produced during this hot catalog backup ?? I look for an equivalent of the bprecover -l for cold catalog backup. Thanks Gilles. Gilles POUSSARD-BORREL Mailto:[EMAIL PROTECTED] This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
In windows you can use the gui to exclude certain drives from certain policies. Either goto host properties -- client -- client name or use the backup / restore gui. Just tell it what policy (or all policies) and which schedule (or all schedules) you want to exclude the data from and add those drives. That's our primary way to exclude data from backups here such as Exchange or Oracle data drives / directories. -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: Wednesday, March 21, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
Ellis; Here is some info on excluding files. Go to Google and search on exclude_list., there is an entire document about it The syntax of the include_list and exclude_list configuration is the same across all of the platforms that are supported (Macintosh, UNIX or Windows). For all UNIX platforms and MacOSX the files for inclusion and exclusion are always located as /usr/openv/netbackup/include_list and /usr/openv/netbackup/exclude_list. The files on MacOS 7.x ? 9.x are to be found in the installed directory (usually in the /System Folder/Preferences/NetBackup/ folder). In Windows, the files are edited through the NetBackup application by going following pull-down menu: Actions-Configure-Exclude List or Include List.. = Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] Ellis, Jason [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/21/2007 12:29 PM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we?d like to exclude C:\ and system state information as we don?t perform bare metal restores in our environment, but want to ensure we backup all the ?data? drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Oracle DB backup issue
Hi, when I run my oracle backup policy, the dbclient logs shows that the host name and client name is wrong causing my backups to fail with a status 239. I have checked the hosts file, dns, server and no where does it references this other name. Can anyone help? -- DLew97 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Oracle DB backup issue
In RMAN scripts you pass in the name of hosts and policies to NetBackup. Have you checked to insure these are correct? Also you don't mention what hosts you are seeing and which ones you expect to see instead. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DLew97 Sent: Wednesday, March 21, 2007 1:04 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Oracle DB backup issue Hi, when I run my oracle backup policy, the dbclient logs shows that the host name and client name is wrong causing my backups to fail with a status 239. I have checked the hosts file, dns, server and no where does it references this other name. Can anyone help? -- DLew97 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
Yes, I was looking to see if there was some way to create an exclude list per policy, but as I suspected it doesn't sound like there is. Thanks! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Wednesday, March 21, 2007 9:35 AM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? You need to create the exclude list on the client. if each client is only backed up by one policy, you can just call it exclude_list, but if the client is backed up by more than one policy, you need to call it exlcude_list.POLICY_NAME. I'm not sure if that's what you're asking, or if you're asking how to somehow specify from the master/policy, to backup ALL_LOCAL_DRIVES but not C and System_State:\ which you cannot. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: March 21, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 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] Exclusion lists based on policy?
He was asking if you could create one central exlcude list on the master/media that applied to all the clients in a given policy. ie, a backup unselection entry, so that you can specify ALL_LOCAL_DRIVES except C in your policy, rather than on a per client basis. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: March 21, 2007 1:22 PM To: Ellis, Jason; nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? His reply is that there IS a way to do it by policy. You need to reread what he wrote. The way you originally phrased your question it sounded like you wanted one exclude list that worked for all policies. Your restatement sounds like you one an exclude for EACH policy. His reply told you how to do it either way. _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: Wednesday, March 21, 2007 1:11 PM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? Yes, I was looking to see if there was some way to create an exclude list per policy, but as I suspected it doesn't sound like there is. Thanks! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Wednesday, March 21, 2007 9:35 AM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? You need to create the exclude list on the client. if each client is only backed up by one policy, you can just call it exclude_list, but if the client is backed up by more than one policy, you need to call it exlcude_list.POLICY_NAME. I'm not sure if that's what you're asking, or if you're asking how to somehow specify from the master/policy, to backup ALL_LOCAL_DRIVES but not C and System_State:\ which you cannot. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: March 21, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 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.
Re: [Veritas-bu] Exclusion lists based on policy?
His reply is that there IS a way to do it by policy. You need to reread what he wrote. The way you originally phrased your question it sounded like you wanted one exclude list that worked for all policies. Your restatement sounds like you one an exclude for EACH policy. His reply told you how to do it either way. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: Wednesday, March 21, 2007 1:11 PM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? Yes, I was looking to see if there was some way to create an exclude list per policy, but as I suspected it doesn't sound like there is. Thanks! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Wednesday, March 21, 2007 9:35 AM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? You need to create the exclude list on the client. if each client is only backed up by one policy, you can just call it exclude_list, but if the client is backed up by more than one policy, you need to call it exlcude_list.POLICY_NAME. I'm not sure if that's what you're asking, or if you're asking how to somehow specify from the master/policy, to backup ALL_LOCAL_DRIVES but not C and System_State:\ which you cannot. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: March 21, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 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] Oracle DB backup issue
It is not part of the policy, try tailing the logs (if in UNIX). tail -f /usr/openv/netbackup/logs/*/*date Try bppllist and then run bpplclients and check to make sure the client is in the policy. Justin. On Wed, 21 Mar 2007, DLew97 wrote: Hi, when I run my oracle backup policy, the dbclient logs shows that the host name and client name is wrong causing my backups to fail with a status 239. I have checked the hosts file, dns, server and no where does it references this other name. Can anyone help? -- DLew97 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Upgrading to 6.0 planning
Solaris 9 nb 5.p mp6 We are starting the process planning to go from 5.0 to 6.0. We currently have 1 master and 6 media servers. Would anyone like to share their plans in upgrading? Did you setup a separate set of 6.0 servers and then import the db? Did you make a copy of your 5.0 hard disks for safe keeping and then performed the upgrade on the original disks keeping the new ones for a fall back? Anything would be helpful. Thanks Greg This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
Ooh In that case, on the NBU Master, no. Best bet is to create the exclusion, export the registry entry and then apply that to all the clients. -J From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Wednesday, March 21, 2007 1:22 PM To: Ellis, Jason; nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? His reply is that there IS a way to do it by policy. You need to reread what he wrote. The way you originally phrased your question it sounded like you wanted one exclude list that worked for all policies. Your restatement sounds like you one an exclude for EACH policy. His reply told you how to do it either way. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: Wednesday, March 21, 2007 1:11 PM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? Yes, I was looking to see if there was some way to create an exclude list per policy, but as I suspected it doesn't sound like there is. Thanks! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Wednesday, March 21, 2007 9:35 AM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? You need to create the exclude list on the client. if each client is only backed up by one policy, you can just call it exclude_list, but if the client is backed up by more than one policy, you need to call it exlcude_list.POLICY_NAME. I'm not sure if that's what you're asking, or if you're asking how to somehow specify from the master/policy, to backup ALL_LOCAL_DRIVES but not C and System_State:\ which you cannot. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: March 21, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 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
[Veritas-bu] Return code 84
All,
Environment:
Media server:
Host: Windows 2003 SP1
Hardware HP DL380 G4
HBA TYPE: Emulex LP9802-E
Emulex LightPulse LP9802 2 Gigabit PCI Fibre Channel Adapter
WWN: 20:00:00:00:C9:3F:48:52
Diver version : 5-1.30A6; HBAAPI v2.2.b, 02-17-05
Firmware version: 1.91A5
Driver Name: elxstor
STK Tape T9940B tape drive:
Drive Type: sktt9940b
Code Version: 1.35.412/4.08
Interface: Fiber
STK Windows 2003 tape driver:
Mfg: StorageTek
Driver date: 2/26/2003
Driver version: 6.0.0.1
Veritas Netbackup 5.1MP6
Fabric:
Silkworm 3800
code version
Kernel: 5.4
Fabric OS: v3.2.1a
Made on:Fri May 12 15:20:59 PDT 2006
Flash: Fri May 12 15:21:57 PDT 2006
BootProm: Tue Oct 30 10:24:38 PST 2001
I have a Windows 2003 media server that is getting constant 84s' when it
attempts to write to media. The media is new, and other hosts can write
to it. The Emulex drivers are storport with the required Microsoft hot
fix but it still fails repeatedly. I have opened many cases with
VERITAS, STK, SUN, Emulex but thay all seemed puzzled. Suggestions, or
help would be greatly appreciated.
Here is an excerpt from the BPTM log
01:14:45.188 [5628.1504] 2 write_data: absolute block position prior
to writing backup header(s) is 2, copy 1
01:14:45.188 [5628.1504] 2 io_write_back_header: drive index 1,
adc-enf-sls1_1174453694, file num = 1, mpx_headers = 0, copy 1
01:14:45.188 [5628.1504] 2 write_data: completed writing backup
header, start writing data when first buffer is available, copy 1
01:14:45.188 [5628.1504] 2 write_data: first write, twin_index: 0
cindex: 0 dont_process: 1 wrote_backup_hdr: 1 finished_buff: 0
01:14:45.188 [5628.1504] 2 write_data: received first buffer (65536
bytes), begin writing data
01:14:50.312 [5628.1504] 2 write_data: write of 65536 bytes indicated
only 0 bytes were written, err = 1
01:14:50.312 [5628.1504] 2 logconnections: bpdbm CONNECT FROM
172.19.5.41.3920 TO 172.29.2.14.13721
01:14:50.312 [5628.1504] 2 logconnections: BPDBM CONNECT FROM
172.19.5.41.3920 TO 172.29.2.14.13721
01:14:50.766 [5628.1504] 4 write_data: WriteFile failed with:
Incorrect function. (1); bytes written = 65536; size = 0
01:14:50.766 [5628.1504] 2 is_possible_recoverable_error: not
attempting error recovery, errno = 1
01:14:50.766 [5628.1504] 2 set_job_details: Done
01:14:50.766 [5628.1504] 2 logconnections: bpdbm CONNECT FROM
172.19.5.41.3921 TO 172.29.2.14.13721
01:14:50.766 [5628.1504] 2 logconnections: BPDBM CONNECT FROM
172.19.5.41.3921 TO 172.29.2.14.13721
01:14:51.203 [5628.1504] 16 write_data: cannot write image to media id
HA0671, drive index 1, Incorrect function.
01:14:51.203 [5628.1504] 2 log_media_error: successfully wrote to
error file - 03/21/07 01:14:51 HA0671 1 WRITE_ERROR
01:14:51.203 [5628.1504] 2 check_error_history: called from bptm line
17599, EXIT_Status = 84
01:14:51.203 [5628.1504] 2 check_error_history: drive index = 1, media
id = HA0671, time = 03/21/07 01:14:51, both_match = 0, media_match =
0, drive_match = 0
01:14:51.203 [5628.1504] 2 io_close: closing C:\Program
Files\VERITAS\NetBackup\db\media\tpreq/HA0671, from bptm.c.15695
01:14:51.203 [5628.1504] 2 tpunmount: tpunmount'ing C:\Program
Files\VERITAS\NetBackup\db\media\tpreq/HA0671
01:14:51.203 [5628.1504] 2 get_tape_path: drive index 1, DOS name:
\\.\Tape2, PnP name:
\\?\scsi#sequentialven_stkprod_t9940brev_1.35#63
072439b300#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
Thanks,
Chris Hall
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Number of restore tape drives
Hi. We have a Netbackup 5.1 MP6 master/media server with 8 tape drives. We run a large standard backup (1.5 TB data size w/multistreaming and no multiplexing) that uses all 8 of the drives during the backup. The backups run successfully and we have no problem in this area. We see an issue when we attempt to perform a full restore of the above mentioned data. When the restore process occurs, all 8 drives are populated and the restore starts and appears to be laying data down on the client. Because all 8 of the drives are in use, all other backup jobs sit in the queue and cannot run. Is there anyway to limit the number of drives the restore will use during the restore process? Is there a touch file or a configuration we could put in place to accomplish this? Thanks for the help. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we'd like to exclude C:\ and system state information as we don't perform bare metal restores in our environment, but want to ensure we backup all the data drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. You understand, I believe, that the basic design of NetBackup classes (a far better name than policies, IMO) was/is to specify parameters that are appropriate for as large a group of systems as possible, and, in the case of the selection list, to allow local administrative control to system owners so they can exclude /SecretProprietaryCode or /DBFsLiveHere as necessary. So, no, there isn't a way on the master (_from_ the master is a different story, as others have noted) to say ALL_LOCAL_DRIVES -and !C:. But doing what you want is easy, even if it looks ugly: go ahead and make the selection list D:\, E:\, ... for as high a drive letter as any system in the class has. As long as one item in the selection list exists*, you won't get a status 71 (none of the files in the list exist). Again, it's the overall design of NetBackup: back up the greatest number of systems with the fewest classes--they don't have to all be alike. * One item in each stream, that is. If your class generates multiple streams per client (via Allow multiple data streams and/or use of NEW_STREAM directives, a stream with nothing to back up (say, f:\ in a job by itself and no drive F) will report, appropriately, that none of the files in that job's list exist. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
I guess I could have mentioned that, since it is what I do. ;o) -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bob944 Sent: March 21, 2007 2:33 PM To: veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] Exclusion lists based on policy? But doing what you want is easy, even if it looks ugly: go ahead and make the selection list D:\, E:\, ... for as high a drive letter as any system in the class has. As long as one item in the selection list exists*, you won't get a status 71 (none of the files in the list exist). Again, it's the overall design of NetBackup: back up the greatest number of systems with the fewest classes--they don't have to all be alike. 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] Drive Cleaning Frequency for SSO Drives
Is there a why to specify the cleaning frequency on SSO drives? The cleaning frequency setting under Device Monitor, accessed by right-clicking on the drive and selecting Drive Cleaning Set Cleaning Frequency, is grayed out on all our SSO drives. Additionally there does not seem to be a way to change the attributes of the tape drive to specify a cleaning frequency from the Change Drive dialogue box for our SSO drives. Are you still trying to set frequency-based cleaning on your drives? Why? Unless you have antique drives, they will almost certainly implement the TapeAlert standard and/or self-clean. Do you have your drive manufacturer's recommendation to clean them based on usage hours? Yes, our manufacture recommended we clean our tape drives based on usage hours. That's interesting. I don't remember you specifying the drive; what make and model of drives are these? I will look into TapeAlert and ensure it is enabled since it looks like the only way to clean our tape drives with the current version of NetBackup we have. TapeAlert goes back to DLT7000 days (late '90s) IIRC, but I do remember firmware updates for some drives which added TapeAlert or perhaps didn't implement it the way HP specified--so don't overlook the firmware possibility if your drives don't have TapeAlert as-is. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Exclusion lists based on policy?
It is actually set by client, is it not? = Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] Jeff Lightner [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/21/2007 01:22 PM To Ellis, Jason [EMAIL PROTECTED], nbu Veritas-bu@mailman.eng.auburn.edu cc Subject Re: [Veritas-bu] Exclusion lists based on policy? His reply is that there IS a way to do it by policy. You need to reread what he wrote. The way you originally phrased your question it sounded like you wanted one exclude list that worked for all policies. Your restatement sounds like you one an exclude for EACH policy. His reply told you how to do it either way. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: Wednesday, March 21, 2007 1:11 PM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? Yes, I was looking to see if there was some way to create an exclude list per policy, but as I suspected it doesn?t sound like there is. Thanks! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Wednesday, March 21, 2007 9:35 AM To: nbu Subject: Re: [Veritas-bu] Exclusion lists based on policy? You need to create the exclude list on the client. if each client is only backed up by one policy, you can just call it exclude_list, but if the client is backed up by more than one policy, you need to call it exlcude_list.POLICY_NAME. I'm not sure if that's what you're asking, or if you're asking how to somehow specify from the master/policy, to backup ALL_LOCAL_DRIVES but not C and System_State:\ which you cannot. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Jason Sent: March 21, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Exclusion lists based on policy? Is there a way to setup an exclusion list for an entire policy? Currently we are using the directive ALL_LOCAL_DRIVES to backup our clients. However, we?d like to exclude C:\ and system state information as we don?t perform bare metal restores in our environment, but want to ensure we backup all the ?data? drives. What makes it difficult is that in our environment there is no standard, so one system might have only a D:\ drive, while another system might have a D:\, E:\, and F:\ drive. Being able to use ALL_LOCAL_DRIVES and excluding C:\ and system state would be helpful. Thanks in advanced! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements
Re: [Veritas-bu] content of hot catalog backup
I'm running Netbackup 6.0 MP4 and I'm doing everyday full hot catalog backup to a tape drive. Is there a command to check and list the content of each catalog image ( bplist command with some specific arguments ) produced during this hot catalog backup ?? I look for an equivalent of the bprecover -l for cold catalog backup. It's not exactly equivalent, but you can view the files saved with 'bplist' or 'bpflist'. For instance on my machine, these come from the actual DB backup: 1 0 37 57 7 1 0 0 2065 /veritas/openv/db/staging/EMM_DATA.db 33206 root root 26226688 1174132803 1174132813 1174132813 2 0 38 57 51233 1 0 0 2065 /veritas/openv/db/staging/EMM_INDEX.db 33206 root root 26226688 1174132813 1174132825 1174132825 3 0 33 56 102459 1 0 0 2065 /veritas/openv/db/staging/NBDB.db 33206 root root 2723840 1174132801 1174132803 1174132803 4 0 36 57 107781 1 0 0 2065 /veritas/openv/db/staging/NBDB.log.1 33206 root root 20340736 1174132831 1174132832 1174132832 5 0 40 51 147511 1 0 0 2065 /veritas/openv/db/staging/databases.conf 33152 root root 37 1174132831 1174132831 1174132831 6 0 37 52 147514 1 0 0 2065 /veritas/openv/db/staging/server.conf 33152 root root 201 1174132831 1174132831 1174132831 7 0 37 52 147517 1 0 0 2065 /veritas/openv/db/staging/vxdbms.conf 33152 root root 417 1174132831 1174132831 1174132831 The other portion of the hot backup is just a file backup and includes images and things. 1 0 31 49 4 1 0 0 2065 /veritas/openv/volmgr/database/ 16877 root bin 0 1174129400 1173750927 1173750927 2 0 48 50 5 1 0 0 2065 /veritas/openv/volmgr/database/ndmp.nap-01.mc0 33152 root root 0 1164755905 1143064298 1161119996 3 0 47 50 6 1 0 0 2065 /veritas/openv/volmgr/database/ndmp.test7.mc0 33152 root root 0 1164755905 1140048255 1161119996 4 0 32 52 8 1 0 0 2065 /veritas/openv/netbackup/bp.conf 33188 root root 619 1174132973 1173906438 1174009234 [...] -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU Aptare - Real World Benefits
Hello, In part to the question posed about validating the purchase of Aptare and stating its benefits does anyone have experience with Aptare in comparison to Netbackup 6.0 NOM that they could state reasons to favor one over the other? Does anyone have comments about Symantec Backup Reporter in relation to the previously two mentioned products? I'm in the same situation of validating purchasing improved reporting software to my companies' hierarchy. Thank you, Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hindle, Greg Sent: Tuesday, March 20, 2007 11:42 AM To: Liddle, Stuart; David Rock; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU Aptare - Real World Benefits Thanks! Greg -Original Message- From: Liddle, Stuart [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 20, 2007 2:39 PM To: Hindle, Greg; David Rock; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NBU Aptare - Real World Benefits Greg, I can tell you that we run the command: bppllist -allpolicies -U and put the resulting output into a file which we then put into a revision control system (we use subversion). Plus we have a Change Control system where our users request changes to the backups like adding/removing systems, path changes, etc. These work orders are then referenced when we check in a change to the policy list. --stuart -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hindle, Greg Sent: Tuesday, March 20, 2007 11:28 AM To: David Rock; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU Aptare - Real World Benefits David, How do you track policy changes? Greg -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Rock Sent: Tuesday, March 20, 2007 2:10 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU Aptare - Real World Benefits * Ed Wilts [EMAIL PROTECTED] [2007-03-19 22:23]: These are benefits from StorageConsole that we get all the time - some exclusively from StorageConsole and some in combination with our own tools. I'm pretty sure that there are features that we're not using yet (some just because they're not as applicable to our environment as they could be to others and perhaps some just because I haven't mastered it all (like automated reporting)). I can mirror most of this, plus add a few more. One of the more recent additions is tracking of policy changes. We are just starting to use this as an audit control of what changes are made in a given policy. It makes for a good balance check against our change management process. We have also saved many hours of our operations staff's time by giving them a single screen to monitor off-hours rather than have seven distinct NBU Activity Montiors running to track job status. The consolidated views simplify and help target what we react to. My favorite report is probably the Backup Duration SLA report. It gives a simple view of what backups are taking a long time to complete, allowing us to target those systems as potential items to optimize. -- David Rock [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP1 ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Upgrading to 6.0 planning
On 3/21/2007 12:36 PM, Hindle, Greg wrote: Solaris 9 nb 5.p mp6 We are starting the process planning to go from 5.0 to 6.0. We currently have 1 master and 6 media servers. Would anyone like to share their plans in upgrading? Did you setup a separate set of 6.0 servers and then import the db? Did you make a copy of your 5.0 hard disks for safe keeping and then performed the upgrade on the original disks keeping the new ones for a fall back? Anything would be helpful. We went from 5.1 to 6.0. We shut down, took good backups, and then upgraded the only systems we had. Log a call with Veritas before you start to let them know you're doing the upgrade, plan it well in advance, clearly do all of the pre-req stuff first, and leave yourself time to fight any EMM battles when you're done. You should be okay... We only had 2 media servers to upgrade - one Solaris and one Windows. .../Ed -- Ed Wilts, RHCE, BCFP 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
[Veritas-bu] Database Cluster Policy Strategy
I'm curious how people manage database backups in a an active-active or N+1 cluster in NetBackup. I have four 2-node active-active SQL Server clusters (8 unique SQL instances) that share the same backup parameters and same backup window. The layout is as follows: Cluster1 Node1 hosts SQLVS1\Instance1 Node2 hosts SQLVS2\Instance2 Cluster 2 Node3 hosts SQLVS3\Instance3 Node4 hosts SQLVS4\Instance4 …. you get the picture. I'd like to configure a single policy to backup all 8 SQL instances. I created a .bch file for each instance with a generic name (SQL_Full.bch) and copied it to the dbext\mssql directory of the node that is primary for each instance. My policy includes all 8 virtual SQL server names and calls SQL_Full.bch. When all nodes of the cluster host their primary instance (i.e., all nodes are online) everything works perfectly. However, when one node of a cluster fails or is taken down for maintenance, the other node hosts both SQL instances. In that case, the primary instance is backed up twice and the instance that failed over is not because the batch file on the single working node (that now hosts both SQL virtual server names) only contains the details about it's primary instance. I've thought about putting the .bch file on each SQL instance's data LUN and then referencing it in the policy but alas, there is no standard drive letter among the 4 clusters (one uses X: Y:, the other V: W:, the third T: U:, etc.). How do others manage database backup policies on multi-node clusters? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Return code 84
On 3/21/2007 1:11 PM, Hall, Christian N. wrote: Environment: Media server: Host: Windows 2003 SP1 Hardware HP DL380 G4 HBA TYPE: Emulex LP9802-E Emulex LightPulse LP9802 2 Gigabit PCI Fibre Channel Adapter WWN: 20:00:00:00:C9:3F:48:52 Diver version : 5-1.30A6; HBAAPI v2.2.b, 02-17-05 Firmware version: 1.91A5 Driver Name: elxstor STK Tape T9940B tape drive: Drive Type: sktt9940b Code Version: 1.35.412/4.08 Interface: Fiber STK Windows 2003 tape driver: Mfg: StorageTek Driver date: 2/26/2003 Driver version: 6.0.0.1 Veritas Netbackup 5.1MP6 Fabric: Silkworm 3800 code version Kernel: 5.4 Fabric OS: v3.2.1a Made on:Fri May 12 15:20:59 PDT 2006 Flash: Fri May 12 15:21:57 PDT 2006 BootProm: Tue Oct 30 10:24:38 PST 2001 I have a Windows 2003 media server that is getting constant 84s' when it attempts to write to media. The media is new, and other hosts can write to it. The Emulex drivers are storport with the required Microsoft hot fix but it still fails repeatedly. I have opened many cases with VERITAS, STK, SUN, Emulex but thay all seemed puzzled. Suggestions, or help would be greatly appreciated. We've seen 84s pop up that were fibre related - they were simply being reported in the system error logs as SCSI errors. Make sure that the drivers and firmware are current (I haven't checked online, but that driver version looks like it might be old) and that you're not logging any errors on your switch ports. That goes for not only the fibre drivers but also the tape drivers - anything dating back 4 years doesn't sound right. Double-check the distances of your fibre and make really sure you're not exceeding any lengths - for example, if you're going to another building, make absolutely sure you haven't hit the limits, espeically if the fibre is 62.5 micron stuff. Clear the port stats on the 3800, run your backups, and check the stats. We ran into an issue where our switch ISLs were too long for the speed we were running them at. We dropped the speeds and they were fine until we eventually put in single-mode fibre. Consider replacing the fibre - check for kinks, tight loops, etc. Consider logging a call with Brocade if you have that option. The 3800 isn't exactly a modern switch... Since most of the parts here appear to be old, has this configuration ever worked? What changed since it was working last? Instead of looking in the bptm logs, go to the system event logs and see if anything is hiding in there. .../Ed -- Ed Wilts, RHCE, BCFP 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
