In
PowerProtect Data Manager, assets are the basic units that
PowerProtect Data Manager protects. Asset sources are the mechanism that
PowerProtect Data Manager uses to manage assets and communicate with the
protection storage where backup copies of the assets are stored.
PowerProtect Data Manager supports
PowerProtect
DD Management Center (DDMC) as the storage and programmatic interface for controlling
protection storage systems.
Supported asset sources
Asset sources can be a vCenter server, Kubernetes cluster, Network Attached Storage (NAS) appliance or share, application host, SMIS server, storage array, or Cloud Snapshot Manager tenant. Assets can be virtual machines, Kubernetes namespaces and persistent volume claims (PVCs), NAS appliance or share assets,Microsoft Exchange Server databases, Microsoft SQL Server databases, Oracle databases, SAP HANA databases, file systems, storage groups, or PowerStore block volumes.
Supported asset languages
PowerProtect Data Manager supports the protection of data hosted on operating systems in multiple languages. For more information, see the
E-Lab Navigator.
Prerequisite to adding an asset source
Before you can add an asset source, you must enable the source within the
PowerProtect Data Manager user interface.
In the
Assets window, you can export asset records by using the
Export All functionality.
IPv6 information not displayed by the
Asset Sources window
The
Asset Sources window does not display IPv6 information. If an asset only uses IPv6, the
IPV4 column displays a blank entry. To select an IPv6-only asset, refer to the
Name column.
Maximum supported number of characters in an asset or storage name is 25
PowerProtect Data Manager does not support more than 25 characters in an asset or storage name.
CAUTION:If this maximum is exceeded, protection policy configuration fails.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\