请教各位高手帮做一个策略

Question

NBU6.5、HACMP 群集 oracle  SAN备份。 master在windows上，客户端是 AIX HACMP 如何做一个策略，这样系统切换时，备份正常。不用设置2个策略。

Answer 1

指向VIP备份不就行了。

Answer 2

这问题有难度  看高手怎么解决

Answer 3

还真都没有想到过这个问题，如果在备份过程中出现切换的话，这个备份是怎样的！我是这样想的，一般我们都是先备份数据文件，然后再备份log文件，你是这么做的吧！如果数据文件备份完成后，没有备份archivelog文件，备份中断的话，另外一台机器应该是再继续备份一遍数据文件，然后再备份archivelog文件，然后删除。我想应该是这样的！但是不是特别的确认。现在的备份策略跟你是否是双机没有太大的关系，在Policy里面配置Client端的时候，你把两个节点就加入进去就好啦！如果要是配置成备份虚拟的主机名和IP地址的话，哪么就相当于备份一台机器是一样的！

Answer 4

如果双机互备，如何实现A机宕机 切到B机以后  备份自动切换过去且不中断备份？以前是建2个策略太被动了。如何实现自由切换不影响备份。双机需要安装2个客户端和 DB AGENT 吗？ 如何设置一个NBU策略 实现 ORACLE 双机的 备份 切换后备份仍然正常。

Answer 5

vip=`ifconfig -a | grep "XXX.XXX.XXX.XXX" | grep -v grep | wc -l`if [ $vip = 0 ]
then
  echo "The Virtual IP is not this host, skip backup......"&
  exit 0;
fiXXX.XXX.XXX.XXX代表的就是你都主机虚拟出来都IP地址，这样也可以实现！做客户端选择的时候需要填写两个物理的主机节点！还有就是你的是一个instance吧？我现在做的是2个instance，如果是2个instance的话，哪么还是需要2个policy的！

Answer 6

配置集群Media Server,做LAN-FREE备份，如何配置集群Media Server见官方文档

Answer 7

看这文档后，想理清的思路。
================================================================================To configure NBU to backup oracle cluster, pls refer to the following documents:
------------------------------------------------------------
When backing up Oracle in a VERITAS Cluster Server (tm) environment using a virtual node name, Recovery Manager exits with an ORA-27206 error.
--------------------------------------------------------------------------------
Exact Error Message
RMAN-10035: exception raised in RPC: ORA-27206: requested file not found in media management catalog
Details:
Additional Problem Descripqion:
The dbclient log shows that the backup completes successfully, but the dbc_GetMediaListByName request during sbtinfo2 fails to verify the media ID to which the backup image was written.
Problem Resolution:
Note: This solution is only valid on active/passive clusters.
Note: This solution is for VERITAS NetBackup (tm) 3.4 installations earlier than patch level 34_3.  If using NetBackup 34_3 or later, or NetBackup 4.5, then please refer to the procedure documented in TechNote 262915 in the Related Documents section of this TechNote.
Sample Configuration:
vnode = Virtual node name of Oracle cluster
node1 = Host name of the first database client
node2 = Host name of the second database client
1. In the client list of the Oracle class on the master server, specify the virtual name of the cluster (vnode).
   Refer to the VERITAS NetBackup for Oracle System Administrator's Guide - UNIX, Version 3.4 for instructions on how to create an Oracle class.
2. In the /usr/openv/netbackup/bp.conf file on each database host in the cluster (node1 and node2), also specify the virtual name of the cluster.
CLIENT_NAME = vnode
Note: A bp.conf file may have only one CLIENT_NAME entry.
3. If it has not been done already, create the following directory and files on the master server to permit the client hosts to access images for the virtual name.
mkdir /usr/openv/netbackup/db/altnames
echo "vnode" >> /usr/openv/netbackup/db/altnames/node1
echo "vnode" >> /usr/openv/netbackup/db/altnames/node2
4. Note that future restores from these backup images may have to follow alternate client restore procedures.
------------------------------------------------------------
How to configure Oracle recovery manager backups in a cluster to use the "virtual name" of the cluster, using the VERITAS NetBackup (tm) for Oracle database agent
--------------------------------------------------------------------------------
Details:
Here are the necessary steps to follow that will allow you to back up your Oracle database using the virtual name of the cluster or floating IP address:
1. Change the Oracle policy to use the "virtual name" of the cluster as the client
2. Modify the /usr/openv/netbackup/bp.conf file on the two clients in the cluster so that the CLIENT_NAME variable is set to the actual host name of the server. This will allow the normal standard file system level backups to continue using the host name of the client instead of the virtual name.
3. Within your backup scripq you will need to pass the NB_ORA_CLIENT name set to the virtual name of the cluster using either the "parms" or the "send" parameters in the RCV scripq. See page 94 of the VERITAS NetBackup 4.5 for Oracle on UNIX Administrator's Guide for further examples.
For example:
PARMS="ENV=(NB_ORA_CLIENT=<virtual name of cluster>)";
send 'NB_ORA_CLIENT=<virtual name of cluster>';
4. This will allow backups to take place using the virtual name of the cluster as the client.