that each client system is accessible from every other client system using the same fully qualified node name.
Creating cells in the Windows environment
Due to the different possible configurations (domain versus workgroup), the various levels of support for Windows Administrators may have some impact on the setup of Data Protector during installation. An important prerequisite is to have a clean node name resolving setup, so that each client system is accessible from every other client system using the same fully qualified node name.
Windows domains
A Windows domain can easily be mapped to a Data Protector cell. In a single Windows domain, use a
Mapping a Data Protector cell into a Windows domain
Mapping a Data Protector cell into a Windows domain also eases administration within Data Protector itself. To ease administration, distribute the software such that all the client systems can be installed using a central Windows account in a domain organization. Other operations, however, are not limited to a Windows domain organization since all operations and security verifications are performed by the Data Protector internal protocol and not by the Windows Security.
In general, there are no limitations on how and where Data Protector can be installed. However, because of the structure of Windows and the most common configurations that are domain environments, some operations are easier when Data Protector is mapped to a single domain or a multiple domain model, where one of the domains is a master domain, to allow a single user to manage all the client systems within the environment (Software Distribution and User Configuration).
In a multiple cell environment with a
Concepts guide | 65 |