AWS Veritas NBU for SAP DB2部署文档

1-环境概述​

此手册主要介绍Veritas NetBackup软件在AWS上对SAP DB2备份功能的实现，部署过程以及策略配置和数据恢复。​

2-系统架构​

本次测试环境列表：​

主机名​	用途​	EC2资源​	OS/应用部署​	IP地址​
SRC105200​	NBU备份服务器​	2vCPU／4G​Mem／300G系统盘，1块网卡​	Rhel7​	xxxx​
sc1dx3​	SAP DB2客户端​	2vCPU／4G​Mem／300G系统盘，1块网卡​	RHEL6.8 /SAP ​	xxxx​
个人PC​	NBU​Console​	Windows7​

3-部署前准备​

服务器准备：​

部署前需要提前准备好1台NBU RHEL7版本的Master服务器以及1台SAP DB2服务器，1台Windows操作系统的管理平台。​

生产系统需要按照如下配置准备NBU Master主机：​

属性​	需求​
操作系统​	RHEL6.x​ RHEL7.x​ SuSE 11.x​ SuSE 12 .x​ Windows 2008​ Windows 2008 R2​ Windows 2012​ Windows 2012 R2​
架构​	X86_64​
部署位置​	主AZ，单机部署​
CPU核数​	4​
内存​	16GB​
磁盘空间​	系统100GB，数据磁盘300GB​
网卡​	1块​
IP地址​	能够通过TCP/IP连接业务主机​

NBU服务器需要打开的端口如下：​

源主机​	目的主机​	TCP/UDP​	端口​
业务主机​	NBU主机​	TCP​	1556/13724​
NBU主机​	业务主机​	TCP​	1556/13724​

S3需要如下权限：​

S3：CreateBucket​

S3：ListAllMyBuckets​

S3：ListBucket​

S3：GetBucketLocation​

S3：GetObject的​

S3：PutObject​

S3：DeleteObject的​

S3：PutObjectTagging​

S3：PutLifecycleConfiguration​

S3: GetLifecycleConfiguration​

S3：PutObjectTagging​

账号：需要提供每台服务器的管理账号以及添加root权限。

​

4-NBU部署配置​

4.1-安装NBU Master 服务器​

创建用户：​

mkdir -p /usr/openv/wmc​

groupadd nbwebgrp​

useradd -g nbwebgrp -c 'NetBackup Web Services account' -d /usr/openv/wmc nbwebsvc​

安装NBU master server之前需要根据KB的要求调整OS内核的参数。如果不调整在安装NBU的时候也会提示您，比如：​

1-最大同步信号量调整，重启生效。​

echo "kernel.sem=300 307200 32 1024">> /etc/sysctl.conf​

sysctl -p​

2-加大OS最大打开文件数量，添加4行，重启生效。​

vim /etc/security/limits.conf​

* hard core unlimited​

* soft core unlimited​

* hard nofile 32768​

* soft nofile 32768​

3-查看SWAP内存和内核参数,如果操作系统已有SWAP内存可以忽略此步骤​

free -m 增加SWAP的内存大小到1GB​

dd if=/dev/zero of=/home/swap bs=1024 count=1024000​

mkswap /home/swap​

swapon /home/swap​

free -m​

Master服务器安装：​

1. When the following message appears press Enter to continue:

   Veritas Installation Script

   Copyright 1993 - 2016 Veritas Corporation, All Rights Reserved.

   Installing NetBackup Server Software

   Please review the VERITAS SOFTWARE LICENSE AGREEMENT located on

   the installation media before proceeding. The agreement includes

   details on the NetBackup Product Improvement Program.

   For NetBackup installation and upgrade information specific to your

   platform and to find out if your installed EEBs or hot fixes are

   contained in this release, check out the Veritas Services and

   Operations Readiness Tools (SORT) Installation and Upgrade Checklist

   and Hot fix and EEB Release Auditor, respectively

   Do you wish to continue? [y,n] (y)​

2. When the following message appears press Enter to continue:

   Is this host a master server? [y/n] (y)​

3. If you need to perform a disaster recovery of your master server, select Y when prompted. Press Enter for the default N.

   Do you want to do a disaster recovery on this master server? [y/n] (n)

   The disaster recovery process requires additional steps and information that is not covered in this manual. More information is available.

   Veritas NetBackup Troubleshooting Guide​

4. For the NetBackup installation location, enter the appropriate platform information as follows:

1. When the following question appears, press Enter to accept the default (y).

   The NetBackup and Media Manager software is built

   for use on <platform> hardware. Do you want to install

   NetBackup and Media Manager files? [y,n] (y)​

2. When the following question appears, select where to install NetBackup and Media Manager software:

   NetBackup and Media Manager are normally

   installed in /usr/openv.

   Is it OK to install in /usr/openv? [y,n] (y)

   The path displayed for Solaris is /opt/openv.

   To accept the default (y), press Enter.

   To change the installation location, type n and press Enter. Then enter the appropriate destination.

   Additional information about installation folder restrictions is available.

   See ​​Restrictions on the NetBackup installation directory​​.​

3. To accept the displayed (default) name, press Enter.​
4. To change the displayed (default) name, type n and enter the name that you want.​
5. For a clustered NetBackup server, enter the virtual name for the NetBackup server and not the actual local host name.​
6. To accept the displayed name (which is the name that you identified in the previous step), press Enter.​

7. If you entered a virtual name for the server in the previous step, the installation script presents the following question:

   Is this server part of a cluster installation?

   If the answer is yes, press y and answer the series of cluster configuration questions that appear.

   If the answer is no, press n.​

8. If there are no media servers for this master server, press Enter and proceed to the next step.​

9. If there are media servers for this master server, type y and enter the name of each media server.

   When you enter the media server names, you must enter the computer name and the domain name. For example:

   alpha.domain.com

   Where alpha is the computer name and domain.com is the domain name.

   The media server names that you enter here are added to the bp.conf file on the master server, automatically. After you install the media server software later, the master server can then communicate with the media servers immediately.​

10. To add a media server to an existing and an operational NetBackup environment, you cannot use the procedures in this guide. For complete details on how to add a media server to an existing and an operational NetBackup environment, see the NetBackup Administrator's Guide, Volume II.

    ​​http://www.veritas.com/docs/DOC5332​​​

11. If you have (or want to have) a clustered NetBackup server, type n.​

12. For non-clustered installations, press Enter to accept the default answer (y) and start the NetBackup processes and the EMM server.

    You must start these processes now because the EMM server must be running when you install any media servers later.​

1. Enter the Netbackup server or Enterprise server License.​

2. Type y, then follow the prompts to add license keys for other NetBackup options and agents.

   Although you can add licenses later, you should enter them now. If you add any licenses later through the NetBackup Administration Console, you must restart the console.​

3. After all licenses are entered, type q to quit the License Key Utility and complete the server software installation.​

4. Verify or enter the correct computer name when prompted by the following message:

   Installing NetBackup Enterprise Server version: 8.1.1

   If this machine will be using a different network interface than

   the default (name), the name of the preferred interface

   should be used as the configured server name. If this machine

   will be part of a cluster, the virtual name should be used as the

   configured server name.

   The domainname of your server appears to be "domain". You

   may choose to use this domainname in your configured NetBackup

   server name, or simply use "name" as the configured

   NetBackup server name.

   Would you like to use "name.domain" as the configured NetBackup server

   name of this machine? [y, n] (y)​

5. Identify or verify the master server by answering the following question when it appears:

   Is <name> the master server? [y, n] (y)​

6. Identify whether there are any media servers for this master server by answering the following question when it appears:

   Do you want to add any media servers now? [y, n] (n)​

7. When the following message appears, press Enter and accept the default name of the EMM server. You must configure EMM on the master server. All master servers must have their own EMM configuration. Remote EMM or shared EMM is no longer supported.

   NetBackup maintains a centralized catalog (separate from the

   image catalog) for data related to media and device

   configuration, device management, storage units, hosts and host

   aliases, media server status, NDMP credentials, and other

   information. This is managed by the Enterprise Media Manager

   server.

   Enter the name of the Enterprise Media Manager (default: <name>)​

8. Answer the following question when it appears:

   Do you want to start the NetBackup job-related processes so backups and

   restores can be initiated? [y, n] (y)​

9. You need wait until your initial installation is complete.​

4.2-安装NBU Console服务器​

1. 运行NBU Server安装程序；​

2. 

3. 通过Windows UAC；​

4. 

5. 安装欢迎界面，选择下一步；​

6. 

7. 选择接受许可协议，下一步；​

8. 

9. 输入许可号，选择媒体服务器；​

10. 

11. 输入管理账户信息：选择实现在Windows服务器创建的本地组／用户，输入密码；​

12. 

13. 选择NBU服务器（即本机）；​

14. 

15. 确认开始安装；​

16. 

17. 安装开始至止完成；​

18. 

19. 查看Windows 服务，看到NetBackup服务正确启动，确保安装成功；​

20. 

21. 登陆NBU管理控制台，登陆；​

22. 

23. 验证能成功登陆管理控制台；​

13．更新中文语言包；​

下载NBU中文语言包，解压后打开执行，选择NetBackup Chinese Language Pack Installation.​

一直点击下一步直至完成安装​

14-登陆NBU管理平台以及创建token​

输入主机名称和账号密码来进行登陆，控制台账号添加方法请参考4.4配置​

在证书管理内，右击空白地方选择新令牌创建，复制token令牌信息，用于NBU media客户端安装使用，此token用于media和master服务器的首次连接安全验证使用。​

4.3-安装NBU Media服务器​

准备工作：​

将media/client主机名及IP信息更新到master和media/client服务器上，确保网络连通。​

这里需要注意DNS解析问题是否会导致网络不通。​

客户端介质服务器安装：​

[root@nbuclient001 NetBackup_8.1.1_LinuxR_x86_64]# ./install​

Veritas Installation Script​

Copyright (c) 2018 Veritas Technologies LLC. All rights reserved.​

Installing NetBackup Server Software​

Please review the VERITAS SOFTWARE LICENSE AGREEMENT located on​

the installation media before proceeding. The agreement includes​

details on the NetBackup Product Improvement Program.​

For NetBackup installation and upgrade information specific to your​

platform and to find out if your installed EEBs or hot fixes are​

contained in this release, check the Installation and Upgrade checklists​

and the Hot Fix and EEB Release Auditor, both available on the Veritas​

Services and Operations Readiness Tools (SORT) page:​

​​https://sort.veritas.com/netbackup​​.​

ATTENTION! To help ensure a successful upgrade to NetBackup 8.1.1,​

please visit the NetBackup 8.x Upgrade Portal:​

​​https://www.veritas.com/docs/000115678​​.​

Do you wish to continue? [y,n] (y) y​

Starting NetBackup Deduplication installer​

testing: /tmp/pdde_pkg_dir_1417​

NetBackup Deduplication preinstall check passed​

Is this host the master server? [y,n] (y) n​

Checking for required system conditions...​

ok server_conf_settings_critical: Inapplicable for new NetBackup installation: skipping​

ok media_server_cluster_upgrade: NetBackup is not installed: skipping​

ok remote_emm: NetBackup is not installed: skipping​

ok wsl_account: Inapplicable for non - Master Server: skipping​

ok unsupported_platform: Passed checks for unsupported platforms.​

ok be_nb_same_host: inapplicable on linux: skipping​

ok nbdb_ntfs_dir_symlink: inapplicable on linux: skipping​

ok nbdb_maintenance_space: no NBDB maintenance required on new install: skipping​

Checking for recommended system conditions...​

ok os_update_level: inapplicable on linux: skipping​

not ok ulimit_nofiles: nofiles ulimit 1024 is too low.​

NetBackup Master and Media Server processes may run slower if they are​

limited to fewer than 8000 open file descriptors. This test runs​

'ulimit -n' and checks that the result is at least 8000 on NetBackup​

servers. See​

​​https://www.veritas.com/support/en_US/article.TECH75332​​​

for more information.​

ok hotfix_auditor: NetBackup is not installed or there is no hotfix or EEB data present. Skipping HF/EEB Auditor check.​

ok ephemeral_port_range: The ephemeral port range does not include ports used by NetBackup services.​

ok port_availability_check: Inapplicable for upgrade to non - Master Server: skipping​

ok server_conf_settings_noncritical: Inapplicable for new NetBackup installation: skipping​

not ok semaphore_limits: too low:​

Performance of NetBackup Master and Media Servers can be affected​

adversely if the system is configured with low semaphore limits. This​

test checks whether the current semaphore limits are set as​

recommended. See ​​https://www.veritas.com/support/en_US/article.TECH203066​​ for​

details.​

If this machine will be using a different network interface than the​

default (nbuclient001), the name of the preferred interface should be used​

as the configured server name. If this machine will be part of a​

cluster, the virtual name should be used as the configured server name.​

The domainname of this machine appears to be "cn-north-1.compute.internal".​

You may choose to use this domainname in your configured NetBackup server​

name, or simply use "nbuclient001" as the configured NetBackup server name.​

Would you like to use "nbuclient001.cn-north-1.compute.internal" as the configured​

NetBackup server name of this machine? [y,n] (y) n​

Enter the name of this NetBackup server: nbuclient001​

What is the fully qualified name of the master server? nbumaster100​

The NetBackup and Media Manager software is built for use on LINUX_RH_X86 hardware.​

Do you want to install NetBackup and Media Manager files? [y,n] (y) y​

NetBackup and Media Manager are normally installed in /usr/openv.​

Is it OK to install in /usr/openv? [y,n] (y) y​

Successfully unpacked /tmp/NetBackup_8.1.1_LinuxR_x86_64/linuxR_x86/catalog/anb/certcmdTool_for_UNIX.tar.gz.​

Checking for local CA certificate​

Local CA certificate is not found on host. Proceeding with installation.​

Getting CA certificate details.​

NOTE: Depending on the network, this action may take a few minutes.​

To continue without setting up secure communication, press Ctrl+C.​

CA Certificate received successfully from server nbumaster100.​

Subject Name : /CN=nbatd/OU=root@nbu001/O=vx​

Start Date : Apr 12 08:50:26 2018 GMT​

Expiry Date : Apr 07 10:05:26 2038 GMT​

SHA1 Fingerprint : D0:1C:4B:18:24:0A:1F:4A:60:9F:32:B1:B8:1B:4D:F5:7D:FC:65:B4​

CA Certificate State : Not Trusted​

Master server [nbumaster100] reports CA Certificate fingerprint​

[D0:1C:4B:18:24:0A:1F:4A:60:9F:32:B1:B8:1B:4D:F5:7D:FC:65:B4].​

Is this correct? [y,n] y​

Storing CA certificate.​

NOTE: Depending on the network, this action may take a few minutes.​

To continue without setting up secure communication, press Ctrl+C.​

The validation of root certificate fingerprint is successful.​

CA certificate stored successfully from server nbumaster100.​

Getting host certificate for hostname nbuclient001.​

NOTE: Depending on the network, this action may take a few minutes.​

To continue without setting up secure communication, press Ctrl+C.​

An authorization token is required in order to get the host certificate for this​

host. At the prompt, enter the authorization token or q to skip the question.​

NOTE: The answer entered will not be displayed to the terminal.​

Enter the authorization token for nbumaster100 or q to skip:​

Getting host certificate with token for hostname nbuclient001.​

NOTE: Depending on the network, this action may take a few minutes.​

To continue without setting up secure communication, press Ctrl+C.​

Host certificate and certificate revocation list received successfully from server nbumaster100.​

Saving server binaries for LINUX_RH_X86.​

Reading NetBackup files from /tmp/NetBackup_8.1.1_LinuxR_x86_64/linuxR_x86/anb​

Checking for pre-existing SYMCnetbp package.​

package SYMCnetbp is not installed​

Checking for pre-existing VRTSnetbp package.​

Installing VRTSnetbp package.​

Installation of VRTSnetbp was successful.​

More details regarding VRTSnetbp can be found in file​

/tmp/install_netbppkg_trace.1562 on nbuclient001.​

x openv/netbackup/client/Linux/​

x openv/netbackup/client/Linux/Debian2.6.18/​

x openv/netbackup/client/Linux/Debian2.6.18/client_bin.tar.gz​

x openv/netbackup/client/Linux/Debian2.6.18/certcmdTool_for_UNIX.tar.gz​

x openv/netbackup/client/Linux/Debian2.6.18/ssh_to_client​

x openv/netbackup/client/Linux/Debian2.6.18/extract_java​

x openv/netbackup/client/Linux/Debian2.6.18/cp_to_client​

x openv/netbackup/client/Linux/Debian2.6.18/nbcheck​

x openv/netbackup/client/Linux/Debian2.6.18/pddeagent.tar.gz​

x openv/netbackup/client/Linux/Debian2.6.18/.sizes_JRE​

x openv/netbackup/client/Linux/Debian2.6.18/nb_init_cfg​

x openv/netbackup/client/Linux/Debian2.6.18/.sizes_NB-Java​

x openv/netbackup/client/Linux/Debian2.6.18/nbbsdtar​

x openv/netbackup/client/Linux/Debian2.6.18/client_config​

x openv/netbackup/client/Linux/Debian2.6.18/.sizes_client_bin​

x openv/netbackup/client/Linux/Debian2.6.18/PBX.tar.gz​

x openv/netbackup/client/Linux/Debian2.6.18/nbj.conf​

x openv/netbackup/client/Linux/Debian2.6.18/sftp_to_client​

x openv/netbackup/client/Linux/Debian2.6.18/pdinstall​

x openv/netbackup/client/Linux/Debian2.6.18/.sizes​

x openv/netbackup/client/Linux/Debian2.6.18/installpbx​

x openv/netbackup/client/Linux/Debian2.6.18/JRE.tar.gz​

x openv/netbackup/client/Linux/Debian2.6.18/version​

x openv/netbackup/client/Linux/Debian2.6.18/NB-Java.tar.gz​

x openv/netbackup/client/Linux/SuSE3.0.76/​

x openv/netbackup/client/Linux/SuSE3.0.76/VRTSpddea.rpm​

x openv/netbackup/client/Linux/SuSE3.0.76/VRTSnbpck.rpm​

x openv/netbackup/client/Linux/SuSE3.0.76/certcmdTool_for_UNIX.tar.gz​

x openv/netbackup/client/Linux/SuSE3.0.76/ssh_to_client​

x openv/netbackup/client/Linux/SuSE3.0.76/VRTSnbjre.rpm​

x openv/netbackup/client/Linux/SuSE3.0.76/extract_java​

x openv/netbackup/client/Linux/SuSE3.0.76/cp_to_client​

x openv/netbackup/client/Linux/SuSE3.0.76/nbcheck​

x openv/netbackup/client/Linux/SuSE3.0.76/nb_init_cfg​

x openv/netbackup/client/Linux/SuSE3.0.76/VRTSnbjava.rpm​

x openv/netbackup/client/Linux/SuSE3.0.76/VRTSnbcfg.rpm​

x openv/netbackup/client/Linux/SuSE3.0.76/nbbsdtar​

x openv/netbackup/client/Linux/SuSE3.0.76/VRTSpbx.rpm​

x openv/netbackup/client/Linux/SuSE3.0.76/client_config​

x openv/netbackup/client/Linux/SuSE3.0.76/VRTSnbclt.rpm​

x openv/netbackup/client/Linux/SuSE3.0.76/nbj.conf​

x openv/netbackup/client/Linux/SuSE3.0.76/sftp_to_client​

x openv/netbackup/client/Linux/SuSE3.0.76/pdinstall​

x openv/netbackup/client/Linux/SuSE3.0.76/.sizes​

x openv/netbackup/client/Linux/SuSE3.0.76/version​

x openv/netbackup/client/Linux/RedHat2.6.18/​

x openv/netbackup/client/Linux/RedHat2.6.18/VRTSpddea.rpm​

x openv/netbackup/client/Linux/RedHat2.6.18/VRTSnbpck.rpm​

x openv/netbackup/client/Linux/RedHat2.6.18/certcmdTool_for_UNIX.tar.gz​

x openv/netbackup/client/Linux/RedHat2.6.18/ssh_to_client​

x openv/netbackup/client/Linux/RedHat2.6.18/VRTSnbjre.rpm​

x openv/netbackup/client/Linux/RedHat2.6.18/extract_java​

x openv/netbackup/client/Linux/RedHat2.6.18/cp_to_client​

x openv/netbackup/client/Linux/RedHat2.6.18/nbcheck​

x openv/netbackup/client/Linux/RedHat2.6.18/nb_init_cfg​

x openv/netbackup/client/Linux/RedHat2.6.18/VRTSnbjava.rpm​

x openv/netbackup/client/Linux/RedHat2.6.18/VRTSnbcfg.rpm​

x openv/netbackup/client/Linux/RedHat2.6.18/nbbsdtar​

x openv/netbackup/client/Linux/RedHat2.6.18/VRTSpbx.rpm​

x openv/netbackup/client/Linux/RedHat2.6.18/client_config​

x openv/netbackup/client/Linux/RedHat2.6.18/VRTSnbclt.rpm​

x openv/netbackup/client/Linux/RedHat2.6.18/nbj.conf​

x openv/netbackup/client/Linux/RedHat2.6.18/sftp_to_client​

x openv/netbackup/client/Linux/RedHat2.6.18/pdinstall​

x openv/netbackup/client/Linux/RedHat2.6.18/.sizes​

x openv/netbackup/client/Linux/RedHat2.6.18/version​

Copying RedHat2.6.18 Client Binaries​

Installing VRTSnbpck ...​

Installation of VRTSnbpck was successful. Check /tmp/install_VRTSnbpck.rpm_trace.2163 for details.​

Installing VRTSpbx ...​

Installation of VRTSpbx was successful. Check /tmp/install_VRTSpbx.rpm_trace.2163 for details.​

Installing VRTSnbclt ...​

Installation of VRTSnbclt was successful. Check /tmp/install_VRTSnbclt.rpm_trace.2163 for details.​

Terminating NetBackup and/or Media Manager processes.​

Installing NB-Java.​

Installing VRTSnbjre ...​

Installation of VRTSnbjre was successful.​

More details regarding VRTSnbjre can be found in file​

/tmp/install_VRTSnbjre.rpm_trace.2523 on nbuclient001.​

Installing VRTSnbjava ...​

Installation of VRTSnbjava was successful.​

More details regarding VRTSnbjava can be found in file​

/tmp/install_VRTSnbjava.rpm_trace.2523 on nbuclient001.​

Migrating log files in /usr/openv/logs​

Migration of log files complete.​

No [x]inetd process found.​

Installing VRTSpddea.rpm ...​

Installation of VRTSpddea.rpm was successful. Check /tmp/install_VRTSpddea.rpm_trace.2163 for details.​

Starting NetBackup Deduplication installer​

testing: /tmp/pdde_pkg_dir_3133​

Checking for SYMCpddea package...​

Checking for VRTSpddea package...​

Package VRTSpddea found.​

NetBackup Deduplication software is installed.​

NetBackup Deduplication is not yet configured.​

Checking for SYMCpddes package...​

Checking for VRTSpddes package...​

Checking for SYMCpddea package...​

Installing NetBackup Deduplication server package (/usr/openv/pddeserver.tar.gz)...​

Extracting package VRTSpddes in /tmp/pdde_pkg_dir_3133.​

Package VRTSpddes extracted to /tmp/pdde_pkg_dir_3133.​

Installing package VRTSpddes.​

Package VRTSpddes installed.​

Installing NetBackup Extendable Storage File System Service (VxESFS) ...​

Running install_esfs script ...​

Successfully installed NetBackup Extendable Storage File System Service (VxESFS)​

Running NetBackup Deduplication upgrade script (server mode)...​

NetBackup Deduplication install finished successfully.​

Version now installed: 11.0101.0018.0202​

Full NetBackup Deduplication installation log saved to: /var/log/puredisk/2018-04-12_12:26-pdde-install.log​

Installing VRTSnbcfg.rpm ...​

Installation of VRTSnbcfg.rpm was successful. Check /tmp/install_VRTSnbcfg.rpm_trace.2163 for details.​

Done executing NB.inst.​

If you ran NB.inst instead of <cdrom_path>/install, you must​

run /usr/openv/netbackup/bin/install_bp to initiate NetBackup.​

Running /usr/openv/netbackup/bin/install_bp​

A NetBackup Server or Enterprise Server license key is needed​

for installation to continue.​

Enter license key: KJNW-P8BN-DBW4-4HCR-CRPR-NWO4-F4K4-V7GG-VECP-P​

Evaluation NetBackup Enterprise Server with Apr 30, 2018 expiration date will be registered.​

Is this OK? [y,n] (y) n​

KJNW-P8BN-DBW4-4HCR-CRPR-NWO4-F4K4-V7GG-VECP-P:​

Evaluation NetBackup Enterprise Server Base product with the following features enabled:​

Virtual Appliance​

Replication Director​

Accelerator​

PureDisk Remote Office​

PureDisk Option​

SAN Client​

PureDisk MS Exchange Agent​

Enterprise Vault Agent​

PureDisk MS SQL Server Agent​

Flexible Disk Option​

OpenStorage Disk Option​

Virtual Tape Option​

Bare Metal Restore​

Encryption​

Open File Backup​

BigData​

Remote Client Support​

Robotic Library Sharing Support​

Remote Media Server Support​

Microsoft RSM Robotic Libraries​

ADIC DAS/SDLC Robotic Libraries​

IBM ATL Robotic Libraries​

Fujitsu LMF Robotic Libraries​

StorageTek ACS Robotic Libraries​

Snapshot Client​

MS SharePoint Agent​

Inline Tape Copy​

Vault​

Library Based Tape Drives​

DataStore​

Encryption (Legacy DES 56-bit)​

Encryption (Legacy DES 40-bit)​

SAP extension​

Sybase extension​

Informix extension​

Oracle extension​

Lotus Notes extension​

DB2 extension​

MS SQL Server extension​

MS Exchange extension​

Shared Storage Option​

NDMP​

Additional clients​

has been registered.​

All additional keys should be added at this time.​

Do you want to add additional license keys now? [y,n] (y) n​

Use /usr/openv/netbackup/bin/admincmd/get_license_key​

to add, delete or list license keys at a later time.​

Installing NetBackup Enterprise Server version: 8.1.1​

Resolved Master Server name [nbumaster100] from /tmp/nb_servers_tmp.​

Checking network connections.​

bp.conf: IP_ADDRESS_FAMILY = AF_INET: default value, no update needed​

Successfully cleared host cache​

Successfully cleared peer validation cache​

Machine nbuclient001 is a media server, and it is not the EMMSERVER.​

Successfully updated the session cache parameters.​

Creating /usr/openv/tmp/sqlany​

Installed SQL Anywhere Version 16.0.0.2322​

Installation completed successfully ​

This is not a EMM and Master server, exiting​

Starting the NetBackup Authentication daemon.​

Starting the NetBackup network daemon.​

Starting the NetBackup client daemon.​

Starting the NetBackup SAN Client Fibre Transport daemon.​

Starting the NetBackup Discovery Framework.​

testing: /tmp/pdde_pkg_dir_1417​

NetBackup Deduplication preinstall check passed​

Is this host the master server? [y,n] (y) n​

Checking for required system conditions...​

ok server_conf_settings_critical: Inapplicable for new NetBackup installation: skipping​

ok media_server_cluster_upgrade: NetBackup is not installed: skipping​

ok remote_emm: NetBackup is not installed: skipping​

ok wsl_account: Inapplicable for non - Master Server: skipping​

ok unsupported_platform: Passed checks for unsupported platforms.​

ok be_nb_same_host: inapplicable on linux: skipping​

ok nbdb_ntfs_dir_symlink: inapplicable on linux: skipping​

ok nbdb_maintenance_space: no NBDB maintenance required on new install: skipping​

Checking for recommended system conditions...​

ok os_update_level: inapplicable on linux: skipping​

not ok ulimit_nofiles: nofiles ulimit 1024 is too low.​

NetBackup Master and Media Server processes may run slower if they are​

limited to fewer than 8000 open file descriptors. This test runs​

'ulimit -n' and checks that the result is at least 8000 on NetBackup​

This is not a EMM and Master server, exiting​

Starting the NetBackup Authentication daemon.​

Starting the NetBackup network daemon.​

Starting the NetBackup client daemon.​

Starting the NetBackup SAN Client Fibre Transport daemon.​

Starting the NetBackup Discovery Framework.​

Starting the NetBackup Event Manager.​

Starting the NetBackup Deduplication Manager.​

Starting the NetBackup Deduplication Engine.​

Starting the NetBackup compatibility daemon.​

Starting the Media Manager device daemon processes.​

Starting the NetBackup Remote Monitoring Management System.​

Starting the NetBackup Key Management daemon.​

Starting the NetBackup Service Layer.​

Starting the NetBackup CloudStore Service Container.​

Starting the NetBackup Service Monitor.​

Starting the NetBackup Bare Metal Restore Boot Server daemon.​

NetBackup server installation complete.​

4.4-配置NBU Master/Media连接​

1-配置NBU Console登陆用户：​

NBU Console管理平台默认只能root用户进行登陆，如需要使用其它用户进行登陆，需要添加账号配置到NBU Master服务器上，具体配置方法如下：​

Vim /usr/openv/java/auth.conf ​

复制root配置的信息，修改添加新的用户名保存退出即可。​

2-部署基于主机名的安全证书​

/ usr / openv / netbackup / bin / admincmd / bpnbaz -ProvisionCert host_name （在master上分别对master和media服务器进行执行）​

在netbackup管理主机属性—master上附加服务器添加client IP​

重启client netbackup服务​

/etc/init.d/netbackup stop​

/etc/init.d/netbakcup start​

4-配置每个客户端的最大作业​

以下过程显示如何设置每个客户端的最大作业数属性。​

为每个客户端配置最大作业​

在NetBackup管理控制台的左侧窗格中，展开“ NetBackup管理”>“主机属性”。​

选择主服务器。​

在右侧窗格中，双击服务器图标。​

点击全局属性。​

将每个客户端的最大作业数更改为99。​

每个客户端的最大作业数指定每个客户端允许的最大并发备份数，默认值是1。​

4.5-配置AWS S3存储​

准备工作：​

1、配置云存储服务（默认不需要配置，如nbcssc服务不能起来需要在master和media分别）​

/usr/openv/netbackup/bin/nbcssc -t -a NetBackup

/usr/openv/netbackup/bin/nbcssc -s -a NetBackup -m cloud_master_host -f ​

注：Cloud_master_host修改为master主机名称​

2、检查iptables服状态，需要停止或者添加单独的防火墙策略，放开NBU通信​

service iptables stop​

3、​

在进行云存储服务器之前，需要在“主机属性”下面选择“介质服务器”，然后双机右侧的机器名称，将其连接到NBU console，否则后面创建磁盘池会报错。​

1. 在管理控制台中，选择“配置云存储服务器”选项；​

2. 

3. 选择下一步；​

4. 

5. 在云存储下来列表中，选择Amazon（S3）选项；​

6. 

7. 配置AWS中国区S3存储的域名，并输入账号及验证信息；​

8. 

9. 选择相应的压缩、加密选项，选择下一步；​

10. 

11. 确认配置信息，选择下一步；​

12. 

13. 完成配置；​

14. 

15. 选择存储池中相应的卷；​

16. 

17. 在额外的卷选项界面中，选择默认选项，下一步；​

18. 

19. 确认卷选项，选择下一步；​

20. 

21. 成功为NBU配置云存储资源； ​

22. 

23. 这里如果无法勾选上一步骤的“使用刚创建的磁盘池创建存储单元”则需要手工在NBU console里选择存储单元选项卡进行创建。​
24. 为新建的存储资源命名，并行作业数根据实际配置，建议配置为99。​

25. 

26. 注意这里的“最大并发作业数”​
27. 完成操作；​

28. 

29. 回到NBU管理控制台，验证S3资源创建成功；​

4.6-配置NBU Catalog策略​

NBU Catalog内记录了NBU策略的备份信息以及Master的连接认证和信息，需要定期对其进行备份，如果遇到主机宕机，可以通过Catalog来进行还原，确保原备份可以正常恢复。​

配置方法：​

1-首先登陆NBU Console控制平台，在全局安全设置内选择灾难恢复，根据密码规则设置灾难恢复密码，此密码需要妥善保存，如丢失遗忘后不能通过历史Catalog进行还原。​

2-密码设置成功后，创建存储单元用于存放Catalog日志，存储单元路径需要提前创建完成以及挂载在非操作系统磁盘上，避免操作系统故障影响丢失所有Catalog数据。​

输入存储单元名称，选择目录的绝对路径，点击确定进行创建。​

3-选择配置目录库备份​

点击下一步​

输入Catalog策略名称，选中新建目录库备份策略，点击下一步

输入策略名称

选择备份类型，建议使用默认，点击下一步

定义备份周期和保留周期，根据实际需要设置

选择执行的时间​

输入之前创建的catalog存储单元路径以及登陆名和密码，登陆名和密码可以为NBU控制台登陆账号，确保此账号有权限对存储单元路径有读写执行的权限，点击下一步​

选择是否需要邮件发送，选择否，可以根据客户需要设置

点击完成，配置完成Catalog备份策略。

4.7-配置SAP DB2客户端​

1-将DB2 配置为与 NetBackup 一起工作：​

使用​

# cd /usr/openv/netbackup/bin​

运行db2_config:​

./db2_config​

将出现以下消息：​

Please specify the DB2 instance home path name:​

提供适当的主路径名称，然后按​

/home/db2inst1​

将出现以下消息：​

Do you have other DB2 instances? (y/n) [n] ​

根据需要添加其他​

注：instance home 等信息可以通过more /home/db2inst1/sqllib/db2profile 查看。​

例：​

2-配置DB2备份脚步​

创建一个新的目录用于存放DB2每个实例的执行脚步，生产环境可以规划完成后进行创建配置。​

mkdir /db2/nbu/LSY/ （根据每个实例名称创建一个文件夹避免混淆）​

复制/usr/openv/netbackup/ext/db_ext/db2/scripts/db2_backup到创建好的脚步路径下。​

使用chmod命令将文件属性改为775，使用chown命令将文件所属组改为实例的用户名​

修改脚步信息如下，只需要修改绿色字体部分，每个数据库均需要一个脚步。​

注意：​

1. db2.conf里的缺省的schedule不能修改​
2. policy名称需要和NBU console里创建的policy名称一致​
3. db2.conf里“DB2 User Exit Program”部分全部注释掉​
4. 在db2_backup备份脚本中，对应的db2 backup database命令中添加上online参数，放在$MY_DB2和$MY_SCHED之间​

多db2实例配置示例​

这里需要注意db2_backup备份脚本和db2.conf配置文件都是和实例一一对应的，每个db2实例都对应有各自的这两个文件。​

==============================================================​

##配置db2客户端​

[root@sc1dx4 netbackup]# cd bin/​

[root@sc1dx4 bin]# ./db2_config​

Please specify the DB2 instance home path name:​

/db2/db2qnh​

Do you have other DB2 instances? (y/n) [n]​

y​

Please specify the DB2 instance home path name:​

/db2/db2qsy​

Do you have other DB2 instances? (y/n) [n]​

y​

Please specify the DB2 instance home path name:​

/db2/db2dnh​

Do you have other DB2 instances? (y/n) [n]​

y​

Please specify the DB2 instance home path name:​

/db2/db2dsy​

Do you have other DB2 instances? (y/n) [n]​

n​

Linking /db2/db2qnh/sqllib/adm/db2uext2 to /usr/openv/netbackup/bin/db2uext2.64.​

Copying /usr/openv/netbackup/ext/db_ext/db2/scripts/db2.conf to /db2/db2qnh/db2.conf.​

Linking /db2/db2qsy/sqllib/adm/db2uext2 to /usr/openv/netbackup/bin/db2uext2.64.​

Copying /usr/openv/netbackup/ext/db_ext/db2/scripts/db2.conf to /db2/db2qsy/db2.conf.​

Linking /db2/db2dnh/sqllib/adm/db2uext2 to /usr/openv/netbackup/bin/db2uext2.64.​

Copying /usr/openv/netbackup/ext/db_ext/db2/scripts/db2.conf to /db2/db2dnh/db2.conf.​

Linking /db2/db2dsy/sqllib/adm/db2uext2 to /usr/openv/netbackup/bin/db2uext2.64.​

Copying /usr/openv/netbackup/ext/db_ext/db2/scripts/db2.conf to /db2/db2dsy/db2.conf.​

[root@sc1dx4 bin]#​

[root@sc1dx4 bin]# ls -l /db2/*/db2.conf​

-rw-rw-rw-. 1 root root 2474 Jul 13 14:37 /db2/db2dnh/db2.conf​

-rw-rw-rw-. 1 root root 2474 Jul 13 14:37 /db2/db2dsy/db2.conf​

-rw-rw-rw-. 1 root root 2474 Jul 13 14:37 /db2/db2qnh/db2.conf​

-rw-rw-rw-. 1 root root 2474 Jul 13 14:37 /db2/db2qsy/db2.conf​

[root@sc1dx4 bin]#​

[root@sc1dx4 bin]# ls -l /db2/db2*/sqllib/adm/db2uext2​

lrwxrwxrwx. 1 root dbdnhadm 36 Jul 13 14:37 /db2/db2dnh/sqllib/adm/db2uext2 -> /usr/openv/netbackup/bin/db2uext2.64​

lrwxrwxrwx. 1 root dbdsyadm 36 Jul 13 14:37 /db2/db2dsy/sqllib/adm/db2uext2 -> /usr/openv/netbackup/bin/db2uext2.64​

lrwxrwxrwx. 1 root dbqnhadm 36 Jul 13 14:37 /db2/db2qnh/sqllib/adm/db2uext2 -> /usr/openv/netbackup/bin/db2uext2.64​

lrwxrwxrwx. 1 root dbqsyadm 36 Jul 13 14:37 /db2/db2qsy/sqllib/adm/db2uext2 -> /usr/openv/netbackup/bin/db2uext2.64​

[root@sc1dx4 bin]#​

======================​

[root@sc1dx4 db2]# cd /db2/script/​

[root@sc1dx4 script]# mkdir -p dnh qnh dsy qsy​

[root@sc1dx4 ~]# cp /usr/openv/netbackup/ext/db_ext/db2/scripts/db2_backup /db2/script/qnh/​

[root@sc1dx4 ~]# cp /usr/openv/netbackup/ext/db_ext/db2/scripts/db2_backup /db2/script/qsy/​

[root@sc1dx4 ~]# cp /usr/openv/netbackup/ext/db_ext/db2/scripts/db2_backup /db2/script/dnh/​

[root@sc1dx4 ~]# cp /usr/openv/netbackup/ext/db_ext/db2/scripts/db2_backup /db2/script/dsy/​

[root@sc1dx4 ~]#​

[root@sc1dx4 script]# chmod 775 */*​

[root@sc1dx4 script]# ls -l */*​

-rwxr-xr-x. 1 root root 1733 Jul 13 14:44 dnh/db2_backup​

-rwxr-xr-x. 1 root root 1733 Jul 13 14:44 dsy/db2_backup​

-rwxr-xr-x. 1 root root 1733 Jul 13 14:44 qnh/db2_backup​

-rwxr-xr-x. 1 root root 1733 Jul 13 14:44 qsy/db2_backup​

[root@sc1dx4 script]# id db2qnh​

uid=530(db2qnh) gid=538(dbqnhadm) groups=538(dbqnhadm),500(sapinst)​

[root@sc1dx4 script]# id db2qsy​

uid=515(db2qsy) gid=518(dbqsyadm) groups=518(dbqsyadm),500(sapinst)​

[root@sc1dx4 script]# id db2dnh​

uid=527(db2dnh) gid=534(dbdnhadm) groups=534(dbdnhadm),500(sapinst)​

[root@sc1dx4 script]# id db2dsy​

uid=509(db2dsy) gid=510(dbdsyadm) groups=510(dbdsyadm),500(sapinst)​

[root@sc1dx4 script]#​

chown db2qnh:dbqnhadm /db2/script/qnh/db2_backup​

chown db2qsy:dbqsyadm /db2/script/qsy/db2_backup​

chown db2dnh:dbdnhadm /db2/script/dnh/db2_backup​

chown db2dsy:dbdsyadm /db2/script/dsy/db2_backup​

[root@sc1dx4 script]# ls -l */*​

-rwxrwxr-x. 1 db2dnh dbdnhadm 1733 Jul 13 14:44 dnh/db2_backup​

-rwxrwxr-x. 1 db2dsy dbdsyadm 1733 Jul 13 14:44 dsy/db2_backup​

-rwxrwxr-x. 1 db2qnh dbqnhadm 1733 Jul 13 14:44 qnh/db2_backup​

-rwxrwxr-x. 1 db2qsy dbqsyadm 1733 Jul 13 14:44 qsy/db2_backup​

[root@sc1dx4 script]#​

##添加授权位置(client上执行)​

cd /usr/openv/netbackup/bin/​

./nbsetconfig​

DB_SCRIPT_PATH=/db2/script/qnh/db2_backup​

DB_SCRIPT_PATH=/db2/script/qsy/db2_backup​

DB_SCRIPT_PATH=/db2/script/dnh/db2_backup​

DB_SCRIPT_PATH=/db2/script/dsy/db2_backup​

==================​

db2_backup文件示例​

#!/bin/sh​

#bcpyrght​

#***************************************************************************​

# $Copyright: Copyright (c) 2018 Veritas Technologies LLC. All rights reserved $​

#***************************************************************************​

#ecpyrght​

#​

# These environment variables are initialized by Netbackup (bphdb)​

#​

echo "DB2_CLIENT = $DB2_CLIENT"​

echo "DB2_SERVER = $DB2_SERVER"​

echo "DB2_POLICY = $DB2_POLICY"​

echo "DB2_SCHED = $DB2_SCHED"​

echo "DB2_FULL = $DB2_FULL" # Is 1 if Full backup scheduled​

echo "DB2_CINC = $DB2_CINC" # Is 1 if Cumulative incremental scheduled​

echo "DB2_INCR = $DB2_INCR" # Is 1 if Differential incremental scheduled​

#​

# Change MY_LIB to the correct NetBackup library name for your host:​

# Solaris or Linux 32-bit = nbdb2.so​

# Solaris 64-bit = nbdb2.so64​

# HPUX (ia64) = nbdb2.so​

# AIX or HPUX = nbdb2.sl​

# AIX or HPUX = nbdb2.sl64​

#​

MY_LIB=/usr/openv/netbackup/bin/nbdb2.so64​

#根据实际需要进行修改，Linux默认不用修改​

#​

# Change MY_DB2 to the correct DB2 instance name for your database.​

#​

MY_DB2=SSY​

#修改DB2的数据库名称​

#​

# Use the NetBackup schedule type to set DB2 full or incremental options.​

#​

if [ "$DB2_FULL" = "1" ] ; then​

MY_SCHED=""​

elif [ "$DB2_CINC" = "1" ] ; then​

MY_SCHED="INCREMENTAL"​

elif [ "$DB2_INCR" = "1" ] ; then​

MY_SCHED="INCREMENTAL DELTA"​

else​

MY_SCHED=""​

fi​

#​

# Initialize the backup command line.​

# Customize the number of sessions and buffer options for your environment.​

#​

CMD_LINE="db2 BACKUP DATABASE $MY_DB2 online $MY_SCHED LOAD $MY_LIB OPEN 4 SESSIONS BUFFER 1024"​

#​

# Change MY_USER to the proper DB2 user for performing backups​

#​

MY_USER=db2ssy​

#修改DB2实例用户名称​

echo "Executing: $CMD_LINE"​

su - $MY_USER -c "$CMD_LINE" >/db2/nbulog 2>&1​

RETURN_STATUS=$?​

# Return 0 for success, non-zero for errors​

exit $RETURN_STATUS​

3-添加授权位置​

使用nbsetconfig输入授权位置的值。客户端需要使用root运行这些命令,使用适合您的代理的路径,每个脚本均需要设置授权路径，否则备份会失败。​

cd /usr/openv/netbackup/bin

[root @ client26 bin]＃./nbsetconfig

nbsetconfig> DB_SCRIPT_PATH = /db2/nbu/TESTING-script/TESTING-script

nbsetconfig> DB_SCRIPT_PATH =/db2/nbu/

nbsetconfig>

<CTRL-d>​

4-配置DB2参数​

db2 update db cfg for TESTING using logarchmeth1 VENDOR:/usr/openv/netbackup/bin/nbdb2.so64 //修改为Vendor模式备份​

db2 update db cfg for TESTING using TRACKMOD YES​

停止应用使所有更改参数生效​

db2 force application all​

做离线备份，否则数据是backup pending状态的,无法联结​

db2 backup db TESTING to /tmp //离线全备需要提前准备好空间​

再次查看当前的数据库状态​

db2 get db cfg​

5-修改db2.conf文件​

配置/db2/db2ssy/db2.conf文件，为DB2备份指定备份策略的配置信息。内容如下：​

DATABASE TESTING​

OBJECTTYPE DATABASE​

POLICY DB2_DB_TESTING​

SCHEDULE Default-Application-Backup​

ENDOPER​

DATABASE TESTING​

OBJECTTYPE ARCHIVE​

POLICY DB2_ARCH_TESTING​

SCHEDULE Default-Application-Backup​

ENDOPER​

注：每个实例均需要配置一个db2.conf文件，对于策略名称可以根据实际需要设定​

4.8-配置备份策略​

1-创建数据库备份策略：​

登陆NBUConsole控制台，在策略内右击新建策略​

输入策略名称​

选择文件系统数据库，下一步​

输入策略名称，策略类型选择DB2​

点击添加客户端，输入需要备份的SAP操作系统主机名​

选择完全备份，下一步​

根据实际需要修改保留策略和备份间隔

选择备份开始的时间段

点击完成

双击创建完成的备份策略，策略存储选择之前创建好的S3存储

在备份选择页面，输入配置DB2客户端时准备的脚本路径（包含脚本文件名）​

选择日程表，将全备份的计划名称改为DB2_FULL后点击确认，备份策略创建完成。​

2-Archive Log策略创建，​

在NBU控制台内选择创建备份策略，输入策略名称，不选择向导进行创建。​

策略类型选择DB2， 策略存储选择配置好的S3存储单元，点击客户端页面​

输入客户端名称后，点击确认，此策略不需要添加备份选择，添加完成客户端后点击完成，日志备份策略创建成功。​

注：备份数据库以及日志的策略名称要和db2.conf内添加的信息一致。​

4.9-DB2数据库备份测试​

登陆NBU控制台进行全备测试，选中备份策略右击选择手动进行备份点击确定后开始进行备份，日志备份策略会在做全备时自动执行。​

点击确定​

查看备份完成的状态​

4.10-DB2日志归档测试​

在DB2服务器上，手工切日志db2 archive log for db TESTING，每次切换后都产生一次日志备份，从控制台可以看到日志归档策略会自动执行备份。​

4.11-DB2恢复验证​

查看历史备份记录​

/user/openv/netbackup/bin/bplist -C sc1dx3 -S SRC105200 -t 18 -R /​

可以查看到历史全备和日志备份的记录​

执行恢复命令​

Db2 restore database TESTING load /usr/openv/netbackup/bin/nbdb2.so64​

登陆控制台可以看到数据还原已经完成​

等待直至数据库恢复成功；​

执行回滚日志操作（db2 rollforward db TAT to end of logs and complete)；​

登陆NBU控制台，查看日志恢复状成功（状态为Done）：​

连接上DB2 TESTING数据库实例,查看表内数据，数据一致。​

常用DB2命令:​

根据时间戳来进行还原​

db2 restore db sample load /usr/openv/netbackup/bin/nbdb2.so64 taken at 20110222164246​

db2 rollforward db testdb to end of logs and complete​

db2 list history​

5-NBU容灾功能测试​

NBU容灾功能可以采用CPM对NBU Master主机生成快照的方式来实现，根据客户对于实际使用的需求，可以自定义设置更新快照的频率。​

当NBU Master主机发生宕机并且不可恢复时，可以通过快照来对NBU主机进行还原，新的主机可以采用新的IP地址，但是主机名称不能进行修改，主机创建完成后需要更新NBU 新Master主机以及客户端主机的DNS解析，更新完成DNS解析后在新Master主机上执行如下命令清除缓存并重启Master后，新主机可以和客户端正常联通，备份恢复工作可以继续进行。​

/usr/openv/netbackup/bin/bpclntcmd -clear_host_cache​

6-HA DB2 NBU部署​

涉及HA DB2的NBU部署和不同的单实例DB2部署主要过程类似，请参考前面章节的内容。需要关注的地方，在下面已经列出，供参考。​

环境说明：DB2配置了HA方案，当主节点DB2出现故障时会切换到备节点，正常生产过程中使用虚拟IP/虚拟主机进行对外服务。​

配置目标：部署NBU，使其能够在主节点和备节点进行正常的备份和恢复。​

注意点01：在主备两端的NBU client设置路径授权​

比如类似如下命令，在主备节点均执行：​

cd /usr/openv/netbackup/bin/​

./nbsetconfig​

DB_SCRIPT_PATH=/db2/db2pnr/script/db2_backup​

注意点02：主机属性调整​

需要在“主机属性”的“介质服务器”页面，在主备节点对应的两个介质服务器中，将主备节点的主机名都附加进去。参见下图​

注意点03：备份策略调整​

两个方面：​

1. 对于数据库备份策略，需要在客户端页面添加虚拟主机名​
2. 对于归档日志备份策略，需要在客户端页面添加主备节点主机名以及虚拟主机名​

注意点04：在主节点配置bp.conf文件​

[root@sc1pxg db2pnr]# cat /db2/db2pnr/bp.conf​

CLIENT_NAME = sc1erpvdbin​

[root@sc1pxg db2pnr]#​

7-问题处理与诊断​

问题01：创建云存储服务器无法获取到S3 bucket信息​

症状：创建云存储服务器过程中无法获取到S3 bucket信息，最后会出现如下图示的报错：​

分析及解决：​

NBU工程师在生成的log文件里发现有sts相关报错，参见下面的vxlog.230文件内容，怀疑是sts相关的配置存在异常，因此就尝试将当前的sts从nbu中删除，在重启NBU media/client服务，之后再次尝试配置云存储服务器，可以正常进行，至此，问题解决。​

下面是相关的操作记录。​

vxlogview -p 51216 -o 230 -d all > /tmp/vxlog.230​

07/16/2018 18:30:54.311 [Application] NB 51216 rdsm 230 PID:4748 TID:140198089262848 File​

ID:222 [No context] [Error] V-230-22 RDSM has encountered an issue with STS where the serv​

er was not found: getDiskVolumeInfoList():1277​

07/16/2018 18:30:54.311 [Application] NB 51216 rdsm 230 PID:4748 TID:140198089262848 File​

ID:222 [No context] [Error] V-230-1 RDSM has encountered a service exception: Error Locati​

on: getDiskVolumeInfoList():1277, Error Text: getDiskVolumeInfoList, Error Domain: 3, Erro​

r Code 2,055,011​

07/16/2018 18:50:22.650 [Application] NB 51216 rdsm 230 PID:4748 TID:140198103971584 File​

ID:222 [No context] [Error] V-230-22 RDSM has encountered an issue with STS where the serv​

er was not found: getDiskVolumeInfoList():1277​

07/16/2018 18:50:22.650 [Application] NB 51216 rdsm 230 PID:4748 TID:140198103971584 File​

ID:222 [No context] [Error] V-230-1 RDSM has encountered a service exception: Error Locati​

on: getDiskVolumeInfoList():1277, Error Text: getDiskVolumeInfoList, Error Domain: 3, Erro​

r Code 2,055,011​

nbemmcmd -listhosts​

nbemmcmd -deletehost -machinename sc1dx5 -machinetype ndmp;​

nbemmcmd -deletehost -machinename sc1dx5 -machinetype media​

netbackup stop​

netbackup start​

nbemmcmd -listhosts​

nbemmcmd -listhosts |grep x5​

问题02：如何删除media server/client记录？​

##过期磁盘池上的备份​

[root@SRC016004 admincmd]# ./bpexpdate -stype amazon_raw -dp sc1pxg​

Are you SURE you want to delete all backup copies on sc1pxg y/n (n)? y​

从磁盘卷中删除已删除的片段​

[root@SRC016004 ~]# nbdelete -allvolumes -force​

删除磁盘池​

[root@SRC016004 ~]# nbdevconfig -deletedp -stype amazon_raw -dp sc1pxg​

Disk pool sc1pxg has been deleted successfully​

删除存储服务器​

[root@SRC016004 ~]# nbdevconfig -deletests -storage_server sc1pxg -stype amazon_raw​

Storage server sc1pxg has been successfully deleted​

列出EMM中的主机​

[root@SRC016004 ~]# nbemmcmd -listhosts​

NBEMMCMD, Version: 8.1.1​

The following hosts were found:​

server SRC016004​

master SRC016004​

media sc1pxg​

ndmp sc1pxg​

ndmp SRC016004​

ndmp sc1pxg003​

Command completed successfully.​

删除ndmp和media记录​

[root@SRC016004 ~]# nbemmcmd -deletehost -machinename sc1pxg -machinetype ndmp​

NBEMMCMD, Version: 8.1.1​

Command completed successfully.​

[root@SRC016004 ~]# nbemmcmd -deletehost -machinename sc1pxg -machinetype media​

NBEMMCMD, Version: 8.1.1​

Command completed successfully.​

确认已经删除​

[root@SRC016004 ~]# nbemmcmd -listhosts​

NBEMMCMD, Version: 8.1.1​

The following hosts were found:​

server SRC016004​

master SRC016004​

ndmp SRC016004​

ndmp sc1pxg003​

Command completed successfully.​

[root@SRC016004 ~]#​