Re: [Veritas-bu] Windows 2-node cluster backup
Hi Cameron Well, in simple terms, 2 Node win2k3 cluster, 1 Virtual SQL Server, No NetBackup software configured in a cluster. The application (SQL) is configured to perform the backup using its virtual server name. Obviously during a backup, if it fails, Netbackup will abort, but its not a big deal as it re-runs many times during the day. Not had the SQL clusters configured with multiple virtual names im afraid. Its been a case of one SQL Instance per 2-node cluster (due to project/secure reasons). Simon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kennedy, Cameron Sent: Monday, June 16, 2008 1:59 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Windows 2-node cluster backup Hi all, hoping someone has some experience with backing up a Windows SQL cluster. I am having the below issues: Netbackup 6.5.2, AIX master + media + Windows media. 2-node Windows SQL cluster = 2 physical servers, 2 virtual servers, 2 SQL instances. Typically we have 1 virtual server + instance on each physical server and this runs fine. Each physical server has a dedicated backup NIC on 1GB LAN, and each has a static IP assigned. This works for backup fine, until a failover of the cluster happens without a failback. So we created virtual backup nics, that are tied to the real backup nics. We did this via Windows cluster administrator. Now when a cluster failover happens, the virtual backup IP's follow to the active node - good. However, if we set (in the hosts file) that the backup client is assigned the virtual NIC, when the backup starts the master server can talk to the client via the virtual backup IP, but the client responds to the master server via the real backup IP. Netbackup promptly fails the job, because of this discrepancy as seen in dbclient log. If I update the hosts file to include the real backup IP of the host, then the job runs fine. This of course would mean that everytime the cluster failed, I would have to update the hosts file which would be unacceptible. How are others doing this? thanks This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. 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. - 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] Windows 2-node cluster backup
There was a very good technote for this under NBU3.4, called something like revised setup for SQL in MSCS Regards Michael 2008/6/16, Kennedy, Cameron [EMAIL PROTECTED]: Hi all, hoping someone has some experience with backing up a Windows SQL cluster. I am having the below issues: Netbackup 6.5.2, AIX master + media + Windows media. 2-node Windows SQL cluster = 2 physical servers, 2 virtual servers, 2 SQL instances. Typically we have 1 virtual server + instance on each physical server and this runs fine. Each physical server has a dedicated backup NIC on 1GB LAN, and each has a static IP assigned. This works for backup fine, until a failover of the cluster happens without a failback. So we created virtual backup nics, that are tied to the real backup nics. We did this via Windows cluster administrator. Now when a cluster failover happens, the virtual backup IP's follow to the active node - good. However, if we set (in the hosts file) that the backup client is assigned the virtual NIC, when the backup starts the master server can talk to the client via the virtual backup IP, but the client responds to the master server via the real backup IP. Netbackup promptly fails the job, because of this discrepancy as seen in dbclient log. If I update the hosts file to include the real backup IP of the host, then the job runs fine. This of course would mean that everytime the cluster failed, I would have to update the hosts file which would be unacceptible. How are others doing this? thanks This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Windows 2-node cluster backup
Does anyone know if Netbackup passes environment variables through to the SQL backup script? In our Oracle environment we script a simple check for the NB_ORA_SCHED environment variable which tells Oracle which type of backup to do. Can I do something similar with SQL scripts or do I need to create two separate policies, one for Fulls and one for Incremental backups? -Jonathan -Original Message- From: Kennedy, Cameron [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2008 12:11 PM To: Martin, Jonathan; Michael Graff Andersen Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Windows 2-node cluster backup Thanks for the info. I have attemtpted with the No.Restrictions file (actually my doco from 6.5 calls it No.Restricton (no s) - I attempted both) and it didn't seem to make a difference. Also, The doco, appears to be geared to people that have different names for the same host. My issue is I have different IP's for the same name and, the IP that the client talks on is not always constant (depending on what node has the virtual server.). I am planning on trying the host file entry later this afternoon - let you know how I go. Thanks. -Original Message- From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2008 12:04 PM To: Michael Graff Andersen; Kennedy, Cameron Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Windows 2-node cluster backup I just looked it up. I think the HOSTS file entries will work but the supported Netbackup way is documented as follows. Establish the permissions settings as follows for a redirected restore to a different client: On the master server, either: ■ Create a file called install_path\NetBackup\db\altnames\No.Restrictions or ■ Create each of the files, install_path\NetBackup\db\altnames\NODEA, install_path\NetBackup\db\altnames\NODEB. From the Administrator's guide: To allow redirected restores of a client's files The NetBackup administrator can permit a single client to restore the backups that belong to another client. Create a peername file on the NetBackup master server of the requesting client as described here. Note: The information within this section applies to restores made using the command line, not the Backup, Archive, and Restore client interface. Create an altnamesdirectory in the following location, then place the peername file inside of the directory: Install_path\NetBackup\db\altnames\peername Where peername is the client to possess restore privileges. Add to the peernamefile the names of the client(s) whose files the requesting client wants to restore. The requesting client can restore the files that were backed up by another client if: ■ The names of the other clients appear in the peername file, and Basically the altnames\NODE files are individual No.restrictions permissions for hosts. I'm working on testing the scenario here but I think the idea is to create a NODE file in that directory for each node fo the cluster then put the SQL Resrouce name into the text file. Then your physical nodes will be allowed to backup under the cluster's identity? -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Graff Andersen Sent: Monday, June 16, 2008 10:53 AM To: Kennedy, Cameron Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Windows 2-node cluster backup There was a very good technote for this under NBU3.4, called something like revised setup for SQL in MSCS Regards Michael 2008/6/16, Kennedy, Cameron [EMAIL PROTECTED]: Hi all, hoping someone has some experience with backing up a Windows SQL cluster. I am having the below issues: Netbackup 6.5.2, AIX master + media + Windows media. 2-node Windows SQL cluster = 2 physical servers, 2 virtual servers, 2 SQL instances. Typically we have 1 virtual server + instance on each physical server and this runs fine. Each physical server has a dedicated backup NIC on 1GB LAN, and each has a static IP assigned. This works for backup fine, until a failover of the cluster happens without a failback. So we created virtual backup nics, that are tied to the real backup nics. We did this via Windows cluster administrator. Now when a cluster failover happens, the virtual backup IP's follow to the active node - good. However, if we set (in the hosts file) that the backup client is assigned the virtual NIC, when the backup starts the master server can talk to the client via the virtual backup IP, but the client responds to the master server via the real backup IP. Netbackup promptly fails the job, because of this discrepancy as seen in dbclient log. If I update the hosts file to include the real backup IP of the host, then the job runs fine. This of course would mean that everytime the cluster failed, I would have to update the hosts file which would be unacceptible. How are others doing this? thanks
Re: [Veritas-bu] Windows 2-node cluster backup
Thanks for the info. I have attemtpted with the No.Restrictions file (actually my doco from 6.5 calls it No.Restricton (no s) - I attempted both) and it didn't seem to make a difference. Also, The doco, appears to be geared to people that have different names for the same host. My issue is I have different IP's for the same name and, the IP that the client talks on is not always constant (depending on what node has the virtual server.). I am planning on trying the host file entry later this afternoon - let you know how I go. Thanks. -Original Message- From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2008 12:04 PM To: Michael Graff Andersen; Kennedy, Cameron Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Windows 2-node cluster backup I just looked it up. I think the HOSTS file entries will work but the supported Netbackup way is documented as follows. Establish the permissions settings as follows for a redirected restore to a different client: On the master server, either: ■ Create a file called install_path\NetBackup\db\altnames\No.Restrictions or ■ Create each of the files, install_path\NetBackup\db\altnames\NODEA, install_path\NetBackup\db\altnames\NODEB. From the Administrator's guide: To allow redirected restores of a client's files The NetBackup administrator can permit a single client to restore the backups that belong to another client. Create a peername file on the NetBackup master server of the requesting client as described here. Note: The information within this section applies to restores made using the command line, not the Backup, Archive, and Restore client interface. Create an altnamesdirectory in the following location, then place the peername file inside of the directory: Install_path\NetBackup\db\altnames\peername Where peername is the client to possess restore privileges. Add to the peernamefile the names of the client(s) whose files the requesting client wants to restore. The requesting client can restore the files that were backed up by another client if: ■ The names of the other clients appear in the peername file, and Basically the altnames\NODE files are individual No.restrictions permissions for hosts. I'm working on testing the scenario here but I think the idea is to create a NODE file in that directory for each node fo the cluster then put the SQL Resrouce name into the text file. Then your physical nodes will be allowed to backup under the cluster's identity? -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Graff Andersen Sent: Monday, June 16, 2008 10:53 AM To: Kennedy, Cameron Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Windows 2-node cluster backup There was a very good technote for this under NBU3.4, called something like revised setup for SQL in MSCS Regards Michael 2008/6/16, Kennedy, Cameron [EMAIL PROTECTED]: Hi all, hoping someone has some experience with backing up a Windows SQL cluster. I am having the below issues: Netbackup 6.5.2, AIX master + media + Windows media. 2-node Windows SQL cluster = 2 physical servers, 2 virtual servers, 2 SQL instances. Typically we have 1 virtual server + instance on each physical server and this runs fine. Each physical server has a dedicated backup NIC on 1GB LAN, and each has a static IP assigned. This works for backup fine, until a failover of the cluster happens without a failback. So we created virtual backup nics, that are tied to the real backup nics. We did this via Windows cluster administrator. Now when a cluster failover happens, the virtual backup IP's follow to the active node - good. However, if we set (in the hosts file) that the backup client is assigned the virtual NIC, when the backup starts the master server can talk to the client via the virtual backup IP, but the client responds to the master server via the real backup IP. Netbackup promptly fails the job, because of this discrepancy as seen in dbclient log. If I update the hosts file to include the real backup IP of the host, then the job runs fine. This of course would mean that everytime the cluster failed, I would have to update the hosts file which would be unacceptible. How are others doing this? thanks This email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may
