Application agent and File System agent coexistence
PowerProtect Data Manager supports the following application agent and File System agent coexistence:
Coexistence of the Oracle RMAN agent or SAP HANA agent with the File System agent on Linux.
Coexistence of the Oracle RMAN agent with the File System agent on AIX.
Coexistence of the Microsoft SQL Server or
Microsoft Exchange Server application agent with the File System agent on Windows.
NOTE When the
Microsoft Exchange Server application agent and the File System agent coexist and both agents are installed and registered to the same PowerProtect Data Manager instance, the following workflows are supported.
For File Systems:
Use File-based backup (FBB) instead of Block-based backup, and provide a dummy exclusion filter in the protection policy.
In the File System protection policy backup, do not include
Microsoft Exchange Server.edb and log file assets.
For
Microsoft Exchange Server:
Run
Microsoft Exchange Server full backups only.
The coexistence of these agents enables you to protect the Microsoft SQL Server,
Microsoft Exchange Server, Oracle, or SAP HANA database with the host file system. The following configurations are supported for agent coexistence:
Both agents in managed mode (registered to
PowerProtect Data Manager)
The Microsoft SQL Server,
Microsoft Exchange Server, Oracle, or SAP HANA agent in stand-alone mode, with the File System agent registered to
PowerProtect Data Manager
NOTE The latest version of each agent must be installed if the agents are registered to
PowerProtect Data Manager. The File System agent is supported in managed mode only.
The steps for installation and usage for each agent are the same.
The table below lists the supported use cases and limitations.
Table 1. Supported cases
Category
Supported cases
Current limitations
Agent installation and uninstallation
New installation of both agents is supported with:
Microsoft SQL Server agent,
Microsoft Exchange Server agent, Oracle RMAN agent, or SAP HANA agent in stand-alone or managed mode.
File System agent in managed mode.
New installation of an agent is supported in managed mode with an existing agent in stand-alone mode.
New installation of an agent is supported in stand-alone mode with an existing agent in managed mode.
Repair of an existing agent installation is supported.
Uninstallation of agents is supported.
Uninstalling the last agent that is installed on the host unregisters the host from
PowerProtect Data Manager. Any new agent installation that occurs after the uninstall must be newly registered to the
PowerProtect Data Manager server.
Similar to the agent installations, uninstallation of each agent is performed separately.
Host registration and unregistration
Registration of an installed agent to the
PowerProtect Data Manager server is supported.
Unregistration of agents from the
PowerProtect Data Manager server is supported.
Both agents, if operating in managed mode, should be registered to the same
PowerProtect Data Manager server only. There is no option to register each agent to a different
PowerProtect Data Manager server.
Unregistering a host unregisters all the managed agents that are installed on that host. Stand-alone agents are not affected.
After unregistering a host, the host's assets still appear in the UI in order to support the restore of these assets to a different host. However, backups are not initiated on these assets as the protection policies are disabled.
Backup and restore features
Protection policy creation is supported on all registered agents.
All scheduled protection policy backups are supported on both agents as per individual protection policies.
Self-service backups are supported on both agents.
Compliance is supported on both agents as per the individual service-level agreements (SLAs).
Manual backups are supported at the protection policy level and individual asset level through the centralized protection policy workflow.
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: <>()\