Avamar:如何在 Avamar Server 上运行proactive_check.pl运行状况检查脚本
Summary: 本文旨在阐明主动运行状况检查 (PHC) 脚本的功能,并提供有关其执行的全面指南。
Instructions
proactive_check.pl 脚本必须在 中的 Avamar 网格(单节点或实用程序节点)上运行 /home/admin/proactive_check 目录下看到一个新的 res 目录。
1.以“管理员”身份登录到 Avamar 实用程序节点。
2.检查 proactive_check 目录存在:
ls -ld proactive_check
目录存在时的输出:
admin@avamar-server:~/>: ls -ld proactive_check
drwx------ 2 admin admin 282 May 27 13:18 proactive_check
目录不存在时的输出:
admin@avamar-server:~/>: ls -ld proactive_check
ls: cannot access 'proactive_check': No such file or directory
3.如果必须恢复 proactive_check 目录,请转至步骤 4,否则创建目录。确保路径位于 /home/admin 中:
cd /home/admin
mkdir proactive_check
ls -ld proactive_check
示例:
admin@avamar-server:~/>: cd /home/admin
admin@avamar-server:~/>:
admin@avamar-server:~/>: mkdir proactive_check
admin@avamar-server:~/>:
admin@avamar-server:~/>: ls -ld proactive_check
drwx------ 2 admin admin 282 May 27 13:38 proactive_check
4.转至 proactive_check 目录并检查 proactive_check.pl 或 proactive_check.uu 文件存在:
cd /home/admin/proactive_check
ls -lh proactive_check*
当其中一个文件或两个文件存在时的输出:
admin@avamar-server:~/>: cd /home/admin/proactive_check
admin@avamar-server:~/proactive_check/>: ls -lh proactive_check*
-rwxr-xr-x 1 admin admin 399K May 27 05:04 proactive_check.pl
-rwx--x--x 1 admin admin 123K Jan 19 15:56 proactive_check.uu
文件不存在时的输出:
admin@avamar-server:~/>: cd /home/admin/proactive_check
admin@avamar-server:~/proactive_check/>: ls -lh proactive_check*
ls: cannot access 'proactive_check': No such file or directory
5.如果文件不存在,请转至步骤 6,否则重命名现有文件:
mv proactive_check.pl x-proactive_check.pl.`date -I`
mv proactive_check.uu x-proactive_check.uu.`date -I`
示例:
admin@avamar-server:~/proactive_check/>: mv proactive_check.pl x-proactive_check.pl.`date -I`
admin@avamar-server:~/proactive_check/>: mv proactive_check.uu x-proactive_check.uu.`date -I`
6.下载 proactive_check.pl 或 proactive_check.uu 从 戴尔中部站点。
proactive_check.uu“文件,小于完整”proactive_check.pl“,方法是在熟悉 vi 编辑器的情况下,将内容粘贴到 Avamar 网格上的文件中。
7.仍以管理员身份登录,转至 proactive_check 目录中,并确认文件已正确传输:
cd /home/admin/proactive_check
ls -lh proactive_check*
输出:
admin@avamar-server:~/>: cd /home/admin/proactive_check admin@avamar-server:~/proactive_check/>: ls -lh proactive_check* -rwxr-xr-x 1 admin admin 399K May 27 05:04 proactive_check.pl Or admin@avamar-server:~/>: cd /home/admin/proactive_check admin@avamar-server:~/proactive_check/>: ls -lh proactive_check* -rwx--x--x 1 admin admin 123K Jan 19 15:56 proactive_check.uu
8.如果 proactive_check.uu 传输后,转换文件:
perl proactive_check.uu
示例:
admin@avamar-server:~/proactive_check/>: perl proactive_check.uu
上面的命令会创建 proactive_check.pl, 可以通过运行以下命令进行验证:
admin@avamar-server:~/proactive_check/>: ls -lh proactive_check.*
-rw------- 1 admin admin 123K May 27 16:13 proactive_check.uu
-rwx--x--x 1 admin admin 399K May 27 16:14 proactive_check.pl
9.如果 proactive_check.pl 已传输,使其可执行:
chmod 755 proactive_check.pl
之前:
admin@avamar-server:~/proactive_check/>: ls -lh proactive_check.pl
-rw------- 1 admin admin 399K May 27 16:17 proactive_check.pl
之后:
admin@avamar-server:~/proactive_check/>: chmod 755 proactive_check.pl
admin@avamar-server:~/proactive_check/>: ls -lh proactive_check.pl
-rwxr-xr-x 1 admin admin 399K May 27 16:17 proactive_check.pl
10.确认 Avamar 版本:
gsan --version
示例输出:
admin@avamar-server:~/>: gsan --version
version: 19.10.0-135
build date: Dec 8 2023 07:01:51
msg format: 13-10
SSL: TLSv1 OpenSSL 1.0.2p-fips 14 Aug 2018 (OwB:1.5.11.0, BSAFE Micro Edition Suite:5.0.2.1)
Zlib: 1.2.11
LZO: 1.08 Jul 12 2002
platform: Linux
OS version: SLES-64
Processor: x86_64
-
如果在 Avamar 版本 19.1 及更低版本上运行脚本,则必须以管理员身份运行脚本
-
如果在 Avamar 版本 19.2 或更高版本上运行脚本,则必须以 root 用户身份运行脚本:
su -
cd /home/admin/proactive_check
脚本使用时间:
- 使用以下命令将脚本作为“主动运行状况检查”工具运行
--logoff标志(约 3 至 5 分钟) - 将脚本作为“关闭 SR 运行状况检查”工具运行(大约 1 到 3 分钟)
将脚本作为运行状况检查工具:
运行不带任何参数的脚本,以检查 Avamar 的整体运行状况:
./proactive_check.pl
在 Avamar 19.10 版本中运行脚本的示例。(以 root 用户身份):
root@avamar-server:/home/admin/proactive_check/#: ./proactive_check.pl
proactive_check.pl 8.13
Latest script version DISABLED
===== START HEALTHCHECK
Please Wait... Gathering System Info - This may take a minute or two
Avamar Hostname avamar-server.lab.com
Avamar Server Version 19.10.0-135
GSAN Version 19.10.0-135
MCS Version 19.10.0-135
avtar Version: 19.10.100-135
Hardware Manufacturer vmware
System ID 1234567890@00:AA:11:BB:22:CC
Node Type Single Node AVE .5TB
Operating System SLES12SP5-2024-R1
Avamar Hardening RPM 7.0.2-2.x86_64
Registered Media Access Nodes NONE
SWID ELMAVM123456YZ
License PASSED
AVI Installer PASSED 19.10.0.135
Datadomain dd-server Vers:7.13.0.20-1082704 S/N:AUXXXXXXXXXX7W
Datadomain dd_only_mode WARNING
ddrmaint Patches PASSED
Replication Partner Source to avamar-target.lab.com
Hardware EOSL PASSED
Remote Management PASSED
Version Supported PASSED
MC flush in past 24 hours PASSED
HFSCheck in past 36 hours PASSED
Checkpoint Status PASSED
Status.dpn PASSED
Mandatory Client Upgrades PASSED
Data Domain Version PASSED
/etc/profile PASSED
mcserver.xml PASSED
preferences.dtd permissions PASSED
MCS database size PASSED
Java symlink PASSED
Certificate Expiration PASSED
GSAN Patches PASSED
File Permissions PASSED
FIPS Status PASSED Disabled
Bonding Configuration PASSED
ascd status PASSED
Cron Running PASSED
Checkpoint Retention PASSED
Config Settings PASSED
HFSCheck overtime allowed PASSED
Swap Space PASSED
HFSCheck run time PASSED
MCS Patches INFO
Open File Settings PASSED
GSAN status PASSED
MCS status PASSED
ddrmaint service PASSED
ESE status WARNING
Backup Scheduler running PASSED
Maintenance scheduler running PASSED
Cron jobs enabled PASSED
Unattended startup PASSED
See detailed ERROR information in hc_results.txt
FINISHED
然后,可以通过查看 hc_results.txt 文件中:
cat hc_results.txt
包含更多信息的输出示例:
root@avamar-server:/home/admin/proactive_check/#: cat hc_results.txt
========================================================================
Run Date: Mon May 27 14:51:11 2024 Version 8.13
========================================================================
command line:
DISCLAIMER: The results from this script are intended for the exclusive use of EMC Support & Development Engineers to diagnose potential problems so that they can use their trained skills to see exactly how the issues might or might not affect an individual server's performance
Please review KB534454 Avamar troubleshooting hierarchy if there are any issues found
# --> Latest script version DISABLED
# --> Avamar Hostname avamar-server.lab.com
# --> Avamar Server Version 19.10.0-135
# --> GSAN Version 19.10.0-135
# --> MCS Version 19.10.0-135
# --> Java processes (10)
# --> avtar Version: 19.10.100-135
# --> Hardware Manufacturer vmware
# --> System ID 1234567890@00:AA:11:BB:22:CC
# --> Node Type Single Node AVE .5TB
# --> Operating System SLES12SP5-2024-R1
# --> Avamar Hardening RPM 7.0.2-2.x86_64
# --> Registered Media Access Nodes NONE
WARNING: License has an expiration date.
# --> SWID ELMAVM123456YZ
# --> License PASSED
# --> AVI Installer PASSED 19.10.0.135
# --> Datadomain hdd-server Vers:7.13.0.20-1082704 S/N:AUXXXXXXXXXX7W
WARNING: Backups to the Data Domain are not locked. If this Avamar system is intended to be used as a pure metadata node (no backups going to Avamar), consider locking down the backups to the Data Domain to prevent accidental backups going to the Avamar system
RESOLUTION: See KB531973 and the latest admin guide for Avamar AVE Installs and the dd_only_mode flag. Please also see KB 000047627 and set maxcompdatastripe=20971520 and checkdiratomicrefs=true
# --> Datadomain dd_only_mode WARNING
# --> ddrmaint Patches PASSED
# --> Replication Partner Source to avamar-target.lab.com
# --> Hardware EOSL PASSED
# --> Remote Management PASSED
# --> Version Supported PASSED
# --> MC flush in past 24 hours PASSED
# --> HFSCheck in past 36 hours PASSED
# --> Checkpoint Status PASSED
# --> Status.dpn PASSED
# --> Mandatory Client Upgrades PASSED
# --> Data Domain Version PASSED
# --> /etc/profile PASSED
# --> mcserver.xml PASSED
# --> preferences.dtd permissions PASSED
The MCS database size is 358 MB
# --> MCS database size PASSED
# --> Java symlink PASSED
# --> Certificate Expiration PASSED
# --> GSAN Patches PASSED
# --> File Permissions PASSED
# --> FIPS Status PASSED Disabled
# --> Bonding Configuration PASSED
# --> ascd status PASSED
# --> Cron Running PASSED
# --> Checkpoint Retention PASSED
# --> Config Settings PASSED
# --> HFSCheck overtime allowed PASSED
# --> Swap Space PASSED
# --> HFSCheck run time PASSED
INFO: System is not on TLA recommended MCS hotfix 338823
RESOLUTION: See hot fix 338823 for more information
# --> MCS Patches INFO
# --> Open File Settings PASSED
# --> GSAN status PASSED
# --> MCS status PASSED
# --> ddrmaint service PASSED
WARNING: ESE status is down
RESOLUTION: Start ESE service if required
# --> ESE status WARNING
# --> Backup Scheduler running PASSED
# --> Maintenance scheduler running PASSED
# --> Cron jobs enabled PASSED
# --> Unattended startup PASSED
脚本可以多次运行。结果将附加到hc_history.log文件中。
提示和注释:
在服务请求 (SR) 的生命周期内,脚本必须至少运行一次,且必须使用”--logoff“标记以记录正在调查的问题并将 SR 编号与服务器关联。
使用注销标志可确保未来在网格上工作的技术支持工程师 (TSE) 可以查看网格的“病史”。
- Avamar:如何使用 sched.sh 检查历史备份、复制和维护活动
- Avamar:如何使用 capacity.sh 脚本管理容量
-
replrpt(将复制信息打印到屏幕,例如replrpt.sh)
当标记 --sched开始, --capacity 或 --replrpt ,输出将发送到屏幕,而不是该单个标志的文件。如果必须恢复 --hc 标记,应用所有列出的标记,并将每个标记的输出发送到其各自的标记 hc_*.txt 文件中定义。
使用以下命令运行以下命令 --hc 标志来创建整个集合的单个 hc_*.txt 文件:
./proactive_check.pl --hcAdditional Information
有时,脚本可能会报告 Avamar Server 存在多个问题。
以下文章介绍了各种问题的互动方式以及应首先处理的问题:Avamar:如何正确应用“Avamar 故障处理层次结构”方法。
有关主动检查脚本的完整标记列表,请运行:
./proactive_check.pl --help