Veritas Flex Appliance 3.x 初始化与管理指南

需积分: 5 74 浏览量更新于2024-06-22 收藏 1.64MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Flex Appliance 是一款由 Veritas Technologies LLC 开发的硬件设备，主要用于数据保护和存储管理。本指南是 Flex Appliance 的 'Getting Started and Administration Guide'，适用于3.x版本，旨在帮助用户了解如何启动和管理Flex Appliance。文档在2023年7月13日进行了最后更新，包含法律声明、版权信息以及第三方软件的使用条款。" Veritas Flex Appliance 是一个集成的数据保护解决方案，它结合了硬件和Veritas的软件技术，如NetBackup，为用户提供了一站式的备份和恢复服务。该设备的设计目的是简化数据中心的操作，提供高效、可靠的灾备策略，并确保企业符合法规遵从性要求。本指南的核心内容可能包括以下几个方面： 1. **初始设置与部署**：指导用户如何进行物理安装、网络配置以及设备的初步启动，确保Flex Appliance能够正确地融入现有的IT环境中。 2. **系统管理**：详细阐述如何管理Flex Appliance的硬件资源、监控性能、更新固件和应用补丁，以及执行日常维护任务。 3. **Veritas NetBackup集成**：解释如何配置和使用NetBackup功能，进行数据备份、恢复和策略设定，以保护关键业务数据。 4. **用户界面和CLI操作**：介绍Web界面和命令行界面（CLI）的使用方法，让用户能通过这两种方式对设备进行操作和监控。 5. **安全性和权限管理**：讨论如何设置访问控制、认证和加密，以保护设备和数据免受未经授权的访问。 6. **故障排查和维护**：提供故障诊断步骤、常见问题解答以及如何联系技术支持以获取帮助。 7. **第三方软件和开源许可**：由于Flex Appliance可能包含第三方软件，文档会提及这些组件的开源或免费软件许可证信息，并指明用户可以查阅的详细法律文件。 8. **合规性与许可证协议**：强调产品使用、复制、分发和反编译的限制，提醒用户遵循相关法律法规。 "Flex Appliance Getting Started and Administration Guide" 是一个全面的指导文档，旨在帮助IT专业人员有效地管理和利用Veritas Flex Appliance，实现高效的数据保护和存储管理。对于初次接触Flex Appliance或者需要深入理解其操作和管理的用户来说，这是一份非常有价值的参考资料。

资源详情

资源推荐

instances section of the System topology page and click the instance name,

then click Live firewall settings.

Supported upgrade and update paths to this

release

The following describes the supported upgrade and update paths to Flex Appliance

version 3.x:

For upgrades to 3.0:

■ Direct upgrade path

You can upgrade directly from version 2.1 or 2.1.x to version 3.0.

■ Multi-step upgrade path

Any appliance running an earlier version must first be upgraded to version 2.1.

If you have a multi-node appliance, upgrade both nodes to version 2.1 before

you upgrade to version 3.0.

For updates to 3.1:

■ Direct update path

You can update directly from version 3.0 to version 3.1.

■ Multi-step update path

Any appliance running an earlier version must first be upgraded to version 3.0.

If you have a multi-node appliance, upgrade both nodes to version 3.0 before

you update to version 3.1.

For upgrades or updates to 3.2:

■ Direct upgrade or update path

You can upgrade or update directly from versions 2.1, 2.1.x, 3.0, or 3.1 to version

3.2.

■ Multi-step upgrade path

Any appliance running an earlier version must first be upgraded to version 2.1.

If you have a multi-node appliance, upgrade both nodes to version 2.1 before

you upgrade to version 3.2.

Operational notes

This topic explains important aspects of Flex Appliance 3.x operations that may not

be documented elsewhere in the documentation.

The following list contains the notes and the known issues that apply for the Flex

Appliance 3.x software:

16Release notes

Supported upgrade and update paths to this release

■ Once you upgrade to version 3.x, SAN client (Fibre Transport Media Server)

backups no longer work on NetBackup application instances earlier than version

10.1. To use SAN client on earlier versions, you must install an EEB on versions

10.0.0.1 and 9.1.0.1. Versions other than 10.0.0.1 and 9.1.0.1 do not have an

EEB and must be upgraded before you can install the EEB.

You can find the EEBs at the following locations:

■ Version 10.0.0.1

■ Version 9.1.0.1

Veritas recommends that you install the EEB before you upgrade the appliance

to version 3.x so that scheduled backups are not interrupted.

■ Once you upgrade to version 3.x, universal shares no longer work on NetBackup

application instances earlier than version 10.1.1. To use universal shares on

earlier versions, you must install an EEB on versions 10.1, 10.0.0.1, and 9.1.0.1.

Versions other than 10.1, 10.0.0.1, and 9.1.0.1 do not have an EEB and must

be upgraded before you can install the EEB.

You can find the EEBs at the following locations:

■ Version 10.1

■ Version 10.0.0.1

■ Version 9.1.0.1

Veritas recommends that you install the EEB before you upgrade the appliance

to version 3.x so that scheduled backups are not interrupted.

■ When you access the Flex Appliance Shell through the Veritas Remote

Management Interface, do not enter alt+PrtScn while a command is running.

If you do, the command fails, and it still may not work when you try to rerun it.

■ When you create an instance, if you change the unit for a volume in the Storage

section but do not enter a new size, the unit does not update. To work around

this issue, you must also enter a new size. Once the unit has updated, you can

change the size back to the previous value if needed.

■ For this release, the audit log may include incorrect username or group name

values for user identifiers (for example, UID and GUID). The log shows the

values for the user IDs or group IDs on the appliance instead of the user IDs or

group IDs on the application instance.

■ For this release, if you configure or change the configuration of a Call Home

proxy server, the event does not display correctly in System Health Insights.

The Severity column on the Events page shows as Unknown. You can ignore

this status.

17Release notes

Operational notes

■ If you generate a Data Collect log package and stay on the Activity Monitor

page for more than 15 minutes, you may see a new task appear on the monitor

page. The new task stops immediately with the following message:

“A Data Collect operation is already in progress. Retry after the task is

completed.”

This task displays in error and can be ignored. It has no impact on the generation

of the log package.

■ The Linux Ispci utility shows an incorrect model number for the SAS storage

controller. You can see the correct model number with the hardware-health

commands in the Flex Appliance Shell.

■ If you make configuration changes on the appliance while an update is in

progress, the update may fail. To avoid this issue, do not make configuration

changes or run the system restart command until the update is fully complete.

If you were not aware of this issue and have encountered it, rerun the update

to resolve it.

■ For this release, the Alt + s shortcut in the Flex Appliance Shell is not enabled.

■ When you add a node to the appliance either during initial configuration or after,

the system self-test command fails on the new node if you run it before you

run setup add-node. The following error appears:

"Hostagent must not be active on unconfigured appliance"

If you see this error in this scenario, it can be ignored. Run setup add-node to

finish adding the node and then run system self-test again.

■ For this release, the Performance graphs on the Flex Appliance Console Home

page show data only in the UTC time zone.

■ On a multi-node appliance, an issue can occur if you remove a node while that

node is powered off. If the node comes back online before you have restarted

the appliance, the removed node is added back to the appliance. If you

experience this issue, remove the node again and then immediately restart the

appliance.

■ When you run the following commands, messages that include the text avc:

denied and comm=’iptables’ or comm=’ip6tables’ may appear in the logs at

/var/log/audit/audit.log:

■ setup configure-console

■ system restart

■ system appliance-recover

■ systemctl restart system-hostnamed

■ hostnamectl

18Release notes

Operational notes

The messages look similar to the following:

node=localhost.localdomain type=AVC

msg=audit(1668166429.323:16048): avc: denied { ioctl } for

pid=612229 comm="iptables"

These messages can be ignored.

■ Alerts are not currently sent for the metrics that can be set with the set alerts

hardware-threshold command.

■ The support data-collect command may show the following error:

"*** Error in `qaucli': double free or corruption"

This error can be safely disregarded. The command still generates a DataCollect

package.

■ During a firmware update, an issue can occur with the storage shelf controller

that causes an update failure message to appear. If you see a failure message,

it may have appeared in error, and the update may still have worked. Run the

following command to confirm the firmware version:

show hardware-health primaryshelf component=controller

■ For this release, while an update is in progress, do not perform any other

operations in the Flex Appliance Shell or the Flex Appliance Console.

■ When you install application add-ons on an instance, the Flex Appliance Console

lets you select different versions of the same OST plug-in. However, this

configuration is not supported, and if you select more than one version of the

same plug-in, the Install add-ons page shows duplicate entries. Only install

one version of each OST plug-in on an instance. If you need to change the

version of an OST plug-in that is already installed, first uninstall it, and then

install the new version.

■ If the host0 or host1 port is not connected to the appliance node during initial

configuration, the following error message appears that does not provide

complete information:

“Network card for <interface name> is missing. Make sure that all network

interfaces are connected to the appliance.”

If you encounter this message, verify that all ports are connected according to

the initial configuration guidelines. See “Initial configuration guidelines and

checklist” on page 24. Then restart the node to continue the configuration.

■ When you create a new application instance, the Application instances section

of the System topology page may show the instance status as Partially Deleted

while the creation is in progress. The Partially Deleted status displays in error

and can be safely ignored. You can track the instance creation progress from

the Activity Monitor, and the instance status changes to Online when the instance

creation has completed successfully.

19Release notes

Operational notes

■ A known issue can occur when you try to delete an application instance on a

multi-node appliance. The following error message displays in the Activity

Monitor:

"Failed to delete instance. Check /var/log/nodeworker/worker.log and VCS logs

for more details."

This issue is fixed in version 3.2. To avoid this issue on earlier releases, relocate

the instance to the other node before you delete it.

If you were not aware of this issue and encounter it, contact Veritas Technical

Support for assistance and ask your representative to reference article

100054665.

■ Performing a power cycle from the Veritas Remote Management Interface can

cause system downtime.

This issue is fixed in version 3.2. If you need to restart the appliance on earlier

releases, run the system restart command from the Flex Appliance Shell.

■ For versions 3.0 and 3.1, if you add a node to the appliance and do not use

DNS, you must perform the following steps after you add the hostname resolution

information for the new node to the appliance Hosts file:

■ Log in to the Flex Appliance Shell from the preexisting node that was already

part of the appliance.

■ Run the following command:

system ha-service restart service=infra_svc node=<node hostname>

Where <node hostname> is the hostname of the node that you are logged

in to.

Perform these steps after you run the system add-host command and before

you run the setup add-node command. You do not need to perform these steps

on version 3.2 and later.

■ If you do not use DNS and you configure email alerts or configure Call Home

with a proxy server, the alert tests fail, and alerts are not sent.

This issue is fixed in version 3.2. To resolve this issue on earlier releases,

perform the following steps after you configure the alerts:

■ Log in to the Flex Appliance Shell and run the following command:

system add-host

■ Enter the required information for the SMTP server or the Call Home proxy

server.

■ Run the following commands:

system os-service restart service=autosupport

system ha-server restart service=infra_svc node=<node hostname>

20Release notes

Operational notes

剩余128页未读，继续阅读

weixin_40191861_zj

粉丝: 77
资源: 1万+

Veritas Flex Appliance 3.x 初始化与管理指南

getting start with Flex

Flex Appliance Getting Started and Administration Guide

Getting Started with Flex 4

descibe an AI-based appliance for office scenario and analyse its advantages and disadvantages for the development of society

appliance classification using vi trajectories and convolutional neural netw

使用vcenter appliance自带证书系统更新证书

vmware vcenter server appliance 7.0u3l 密钥

self.models[appliance_name].load_state_dict(torch.load("./"+appliance_name+"_seq2point_best_state_dict.pt"))

在centos7.8中使用docker方式安装zabbix5 基于zabbix-appliance

使用 vimtop 命令监控 vCenter Server Appliance 的服务详细步骤

oracle database appliance x9-2-ha

VMware vCenter Server Appliance的安装硬件和软件需求

vcenter server appliance

写一段7个用电器通过检测到的电能参数去智能识别的代码

最新资源