请输入搜索词进行查询
搜索 <book_title>...
NetBackup™ for OpenStack 管理指南
Last Published:
2024-11-11
Product(s):
NetBackup (10.5)
- 简介
- 部署 NetBackup for OpenStack
- 要求
- NetBackup for OpenStack 网络注意事项
- 准备安装
- 启动 NetBackup for OpenStack 虚拟机
- 关于 NetBackup for OpenStack 备份目标类型
- 安装 NetBackup for OpenStack 组件
- 在 RHOSP 上安装
- 在 Ansible OpenStack Ussuri 上安装
- 在 Kolla 上安装
- 更改 NetBackup for OpenStack 节点上的 Nova 用户 ID
- 复制 NetBackup for OpenStack 部署脚本
- 将 NetBackup for OpenStack 部署脚本复制到 Kolla-ansible 部署脚本
- 将 NetBackup for OpenStack 映像推送到本地注册表
- 编辑 globals.yml 以设置 NetBackup for OpenStack 参数
- 启用 NetBackup for OpenStack 备份装入功能
- 提取 NetBackup for OpenStack 容器映像
- 部署 NetBackup for OpenStack 组件
- 验证 NetBackup for OpenStack 部署
- 配置 NetBackup for OpenStack
- NetBackup for OpenStack 资源限制
- 安装后运行状况检查
- 卸载 NetBackup for OpenStack
- 从 RHOSP 卸载
- 从 Ansible OpenStack 卸载
- 卸载 NetBackup for OpenStack 服务
- 销毁 NetBackup for OpenStack datamover API 容器
- 清理 openstack_user_config.yml
- 在 user_variables.yml 中删除 NetBackup for OpenStack haproxy 设置
- 删除 NetBackup for OpenStack datamover API 清单文件
- 删除 NetBackup for OpenStack datamover API 服务端点
- 删除 NetBackup for OpenStack datamover API 数据库和用户
- 从 rabbitmq 容器中删除 nbosdmapi rabbitmq 用户
- 清理 haproxy
- 从计算节点中删除证书
- 销毁 NetBackup for OpenStack 虚拟机群集
- 从 Kolla OpenStack 卸载
- 安装 nbosjm CLI 客户端
- 关于 NetBackup for OpenStack 中的日志轮换
- 配置 NetBackup OpenStack 设备
- 配置 NetBackup 主服务器
- NetBackup for OpenStack 保护
- 执行 OpenStack 快照、备份和还原
- 执行备份管理任务
- 灾难恢复
- 故障排除
- 常规故障排除提示
- 在 NetBackup for OpenStack 设备上使用 nbosjm CLI 工具
- NetBackup for OpenStack 的运行状况检查
- 重要日志文件
- 对由于装入点不可用而处于脱机状态的 NBOSDM 容器进行故障排除
- 还原 Windows 实例后,磁盘处于脱机状态
- 从快照副本进行选择性还原失败
- 由于通用共享路径中的旧 nova ID,备份失败
- 使用 NetBackup for OpenStack 中的 NetBackup 支持实用程序
- 如果物理卷和卷组的元数据大小较小,则无法创建卷
- 如果 DNS 服务器无法解析 IP 地址,或 IP 地址有误,NBOSVM 配置将失败
- 使用多个存储服务器创建存储单元时出错
- 如果 OpenStack 用户无法访问 OpenStack 映像,则快照作业失败
- 如果 OpenStack 用户无法访问挂接到实例的子网,一键式还原将失败
- NBOSVM 配置器 UI 未检测到主服务器
- 索引
在 NetBackup for OpenStack 群集上
nbosjm-policies
此服务在每个 NetBackup for OpenStack 节点上运行并处于活动状态。
[root@Upstream ~]# systemctl status nbosjm-policies
● nbosjm-policies.service - nbosjm policies service
Loaded: loaded (/etc/systemd/system/nbosjm-policies.service; enabled;
vendor preset: disabled)
Active: active (running) since Wed 2020-06-10 13:42:42 UTC; 1 weeks
4 days ago
Main PID: 12779 (nbosjm-wor)
Tasks: 17
CGroup: /system.slice/nbosjm-policies.service
├─12779 /home/stack/myansible/bin/python
/home/stack/myansible/bin/nbosjm-policies
--config-file=/etc/nbosjm/nbosjm.conf
├─12982 /home/stack/myansible/bin/python
/home/stack/myansible/bin/nbosjm-policies
--config-file=/etc/nbosjm/nbosjm.conf
├─12983 /home/stack/myansible/bin/python
/home/stack/myansible/bin/nbosjm-policies
--config-file=/etc/nbosjm/nbosjm.conf
├─12984 /home/stack/myansible/bin/python
/home/stack/myansible/bin/nbosjm-policies
--config-file=/etc/nbosjm/nbosjm.conf
[...]
nbosjm-api
此服务在每个 NetBackup for OpenStack 节点上运行并处于活动状态。
[root@Upstream ~]# systemctl status nbosjm-api
● nbosjm-api.service - nbosjm api service
Loaded: loaded (/etc/systemd/system/nbosjm-api.service; disabled;
vendor preset: disabled)
Drop-In: /run/systemd/system/nbosjm-api.service.d
└─50-pacemaker.conf
Active: active (running) since Thu 2020-04-16 22:30:11 UTC;
2 months 5 days ago
Main PID: 11815 (nbosjm-api)
Tasks: 1
CGroup: /system.slice/nbosjm-api.service
└─11815 /home/stack/myansible/bin/python /home/stack/
myansible/bin/nbosjm-api --config-file=/etc/
nbosjm/nbosjm.conf
nbosjm-scheduler
此服务在每个 NetBackup for OpenStack 节点上运行并处于活动状态。
[root@Upstream ~]# systemctl status nbosjm-scheduler
● nbosjm-scheduler.service - nbosjm scheduler service
Loaded: loaded (/etc/systemd/system/nbosjm-scheduler.service; disabled;
vendor preset: disabled)
Drop-In: /run/systemd/system/nbosjm-scheduler.service.d
└─50-pacemaker.conf
Active: active (running) since Thu 2020-04-02 13:49:22 UTC; 2 months
20 days ago
Main PID: 29439 (nbosjm-sch)
Tasks: 1
CGroup: /system.slice/nbosjm-scheduler.service
└─29439 /home/stack/myansible/bin/python /home/stack/myansible
/bin/nbosjm-scheduler --config-file=/etc/nbosjm/
nbosjm.conf
nbosjm-cron
此服务由 Pacemaker 控制,仅在主节点上运行。
[root@Upstream ~]# systemctl status nbosjm-cron
● nbosjm-cron.service - Cluster Controlled nbosjm-cron
Loaded: loaded (/etc/systemd/system/nbosjm-cron.service; disabled;
vendor preset: disabled)
Drop-In: /run/systemd/system/nbosjm-cron.service.d
└─50-pacemaker.conf
Active: active (running) since Wed 2021-01-27 19:59:26 UTC; 6 days ago
Main PID: 23071 (nbosjm-cro)
CGroup: /system.slice/nbosjm-cron.service
├─23071 /home/stack/myansible/bin/python3 /home/stack/
myansible/bin/nbosjm-cron --config-file=/etc/nbosjm
/nbosjm.conf
└─23248 /home/stack/myansible/bin/python3 /home/stack/
myansible/bin/nbosjm-cron --config-file=/etc/nbosjm/
nbosjm.conf
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: ● nbosjm-cron.service - Cluster Controlled nbosjm-cron
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Loaded: loaded (/etc/systemd/system/nbosjm-cron.service; disabled;
vendor preset: disabled)
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Drop-In: /run/systemd/system/nbosjm-cron.service.d
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: └─50-pacemaker.conf
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Active: active (running) since Wed 2021-01-27 19:59:26 UTC;
6 days ago
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Main PID: 23071 (nbosjm-cro)
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: CGroup: /system.slice/nbosjm-cron.service
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: ├─23071 /home/stack/myansible/bin/python3 /home/stack/myansible/
bin/nbosjm-cron --config-file=/etc/nbosjm/nbosjm.conf
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: ├─23248 /home/stack/myansible/bin/python3 /home/stack/myansible/
bin/nbosjm-cron --config-file=/etc/nbosjm/nbosjm.conf
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: └─27145 /usr/bin/systemctl status nbosjm-cron
Pacemaker 群集状态
Pacemaker 群集控制并监视 NetBackup for OpenStack 群集中的 VIP。它还控制 nbosjm-api 和 nbosjm-scheduler 服务在哪个节点上运行。
[root@Upstream ~]# pcs status
Cluster name: NetBackup for OpenStack
WARNINGS:
Corosync and pacemaker node names do not match (IPs used in setup?)
Stack: corosync
Current DC: nbosvm1-ansible-ussuri-ubuntu18-vagrant (version
1.1.23-1.el7_9.1-9acf116022) - chapterition with quorum
Last updated: Wed Feb 3 19:20:02 2021
Last change: Wed Jan 27 20:00:12 2021 by root via crm_resource on
nbosvm1-ansible-ussuri-ubuntu18-vagrant
1 node configured
6 resource instances configured
Online: [ nbosvm1-ansible-ussuri-ubuntu18-vagrant ]
Full list of resources:
virtual_ip (ocf::heartbeat:IPaddr2): Started nbosvm1-ansible-
ussuri-ubuntu18-vagrant
virtual_ip_public (ocf::heartbeat:IPaddr2): Started nbosvm1-
ansible-ussuri-ubuntu18-vagrant
virtual_ip_admin (ocf::heartbeat:IPaddr2): Started nbosvm1-
ansible-ussuri-ubuntu18-vagrant
virtual_ip_internal (ocf::heartbeat:IPaddr2): Started nbosvm1-
ansible-ussuri-ubuntu18-vagrant
nbosjm-cron (systemd:nbosjm-cron): Started nbosvm1-ansible-
ussuri-ubuntu18-vagrant
Clone Set: lb_nginx-clone [lb_nginx]
Started: [ nbosvm1-ansible-ussuri-ubuntu18-vagrant ]
Daemon Status:
corosync: active/enabled
pacemaker: active/enabled
pcsd: active/enabled
装入可用性
NetBackup for OpenStack 群集需要访问备份目标,并且应始终具有正确的装入。
[root@Upstream ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.8G 38M 3.8G 1% /dev/shm
tmpfs 3.8G 427M 3.4G 12% /run
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/vda1 40G 8.8G 32G 22% /
tmpfs 773M 0 773M 0% /run/user/996
tmpfs 773M 0 773M 0% /run/user/0
10.10.2.20:/upstream 1008G 704G 254G 74% /var/NetBackupOpenStack-mounts/
MTAuMTAuMi4yMDovdXBzdHJlYW0=
10.10.2.20:/upstream2 483G 22G 462G 5% /var/NetBackupOpenStack-mounts/
MTAuMTAuMi4yMDovdXBzdHJlYW0y