IBM DS8800, Introduction And Planning Manual, Page: 88 / 256

When managing a single-tenant installation, the partitioning capability of resource
groups can be used to isolate various subsets of an environment as if they were
separate tenants. For example, to separate mainframes from distributed system
servers, Windows from UNIX, or accounting departments from telemarketing.
Using resource groups to limit Copy Service operations
Figure 15 illustrates one possible implementation of an exemplary environment
that uses resource groups to limit Copy Services operations. Figure 15 shows two
tenants (Client A and Client B) that are concurrently operating on shared hosts and
storage systems.
Each tenant has its own assigned LPARs on these hosts and its own assigned
volumes on the storage systems. For example, a user cannot copy a Client A
volume to a Client B volume.
Resource groups are configured to ensure that one tenant cannot cause any Copy
Services relationships to be initiated between its volumes and the volumes of
another tenant. These controls must be set by an administrator as part of the
configuration of the user accounts or access settings for the storage unit.
Resource groups functions provide additional policy-based limitations to DS8000
users, which in conjunction with the inherent volume addressing limitations
support secure partitioning of Copy Services resources between user-defined
partitions. The process of specifying the appropriate limitations is performed by an
administrator using resource groups functions.
Note: User and administrator roles for resource groups are the same user and
administrator roles used for accessing the DS8000. For example, those roles
include storage administrator, Copy Services operator, and physical operator.
Site 1
Hosts with LPARs
Switches
Site 2
Switches
Hosts with LPARs
f2c01638
Client A Client A
Client B Client B
Client A Client A
Client B Client B
Figure 15. Implementation of multiple-client volume administration
66
Introduction and Planning Guide