Proxy passes FC address to Media Agent

Proxy passes FC address to Media Agent

Brief description:

Multi-interface B2D Library (StoreOnce Catalyst or Data Domain Boost) configured using an IP address or DNS name can't be used by a client for Server-side or Source-side de-duplication in case it can only access the FC interface of the device. The client fails to retrieve the FC address due to missing IP communication.

This request is to add a "proxy mechanism" to fetch the FC address by a different client system (e.g. Cell Manager or different gateway configured) and send it to the FC-only client.

Benefit:

Client systems in an isolated network environment (e.g. DMZ, hosted customer LAN) unable to access the Backup System IP address (FC connectivity is available) would be able to use a Multi-interface B2D Library (StoreOnce Catalyst or Data Domain Boost).

Workaround:

Configure an additional B2D Library with a FC address to be used by the isolated clients. This adds additional complexity to the environment and should be avoided if possible.

2 Comments
Micro Focus Contributor
Micro Focus Contributor
Status changed to: Waiting for Votes
 
Super Contributor.. Aleksandr_Sviridov Super Contributor..
Super Contributor..

Great idea!

Or maby MF should add two different parameters into the library preferences:

1. DNS-name

2. FC-name

And then user will configure device to use one of this names. 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.