Table 20 Description of “An Example of Global Reporting” (continued)
Item Description
2Database containing the local materialized views for the management server in Tokyo.
3Management server for the SAN in New York City.
4Database for the Management Server in New York City. It contains the local materialized views for New York City, in addition to the global views containing local data from Tokyo, London, and New York.
5Management server for the SAN in London
6Database containing the local materialized views for the management server in London.
Keep in mind the following when setting up global reporting:
•Multiple Global Reporter Servers - Global reporting can be set up at multiple sites. Your associates in London and Tokyo can also set up global reporting at their site so they obtain data gathered by the management server in New York City.
•Multiple Sites - If you do have multiple Global Reporter servers, each Global Reporter server must contact each site that has the data the Global Reporter server wants to include in global reports. For example, assume you set up a Global Reporter server in Tokyo that collects data from a site in London. You also have another Global Reporter server in New York City. The Global Reporter server in New York City must contact the Global Reporter server in Tokyo and the site in London to obtain data from Tokyo and London. If the Global Reporter server in New York City contacts just the Global Reporter server in Tokyo, it does not obtain data from the site in London.
•Data Gathering - The Global Reporter server gathers data from sites as scheduled or when the Refresh Now button on the Global Reporter tab is clicked. The management server pulls data from a site's local materialized views, which are snapshots of relevant data from the site's local database. During a refresh, the Global Reporter server contacts each site and attempts to pull data from its materialized views. If a site's local view is refreshing, the Global Reporter server skips pulling the data from that view and proceeds to pull data from the remaining views. The Global Reporter server then attempts to pull data from the skipped views.
•Firewalls - If a site is behind a firewall, the port for the Oracle TNS listener must be open. For example, if the site uses port 1521 for its TNS listener, this port must be open on the firewall.
•Contact Status - The Contact Status column on the Global Reporter tab only verifies if the management server was able to contact the site. It does not specify if the refresh was successful. For example, if the Global Reporter server is able to contact the site, but the refresh fails. The Contact Status column still reports “SUCCESS” because the site was able to be contacted. If you have trouble contacting the site, try pinging it to verify the network connection is working. If ping works, verify that the management server on the site is running.
HP Storage Essentials SRM 6.0 User Guide 211