Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Respected Contributor.. brits Respected Contributor..
Respected Contributor..
659 views

DP 9.09 & storeonce 6500 catalyst store over FC

Hi Team,

I have a plan to configure DP 9.09 with Storeonce 6500 catalyst store via FC & take the agent based backup of client servers. Kindly suggest if the below mentioned dataflow from client to store is correct or needs any correction. 

DP client backup IP  -> media agent backup IP -> media agent HBA -> storeonce catalyst store.

After zoning MA with storeonce & creating store in 6500, below steps to configure stores in DP devices. Please correct if I am missing something.

- In deduplication system, mention "identifier" name showing in storeonce 6500 serviceset in FC setting tab 

- in store, mention the same store name which is created in storeonce 6500

- in Gateway, select the specific media server & add.

0 Likes
3 Replies
Jason_Mac
Frequent Visitor.

Re: DP 9.09 & storeonce 6500 catalyst store over FC

Yes, this looks good. After adding the gateway, just hit check to make sure you don't get the lovely 'StoreOnce Devices is offline' error... :) I am not sure of your full envirnment, but you might want to consider zoning your CM as well -- it can act as a MA if you ever need to offload some jobs from your current media agents. But yes, what you listed looks good.

0 Likes
Respected Contributor.. brits Respected Contributor..
Respected Contributor..

Re: DP 9.09 & storeonce 6500 catalyst store over FC

Thnx Jason for answer.  

I will hit the check option to verify the configuration. 

CM is on VM and we have dedicated physical MA servers for backup load.

One more question :- when data travels from client to MA via ethernet , which method translates the data from ethernet to FC on MA server?

0 Likes
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: DP 9.09 & storeonce 6500 catalyst store over FC

Hi brits,


@britswrote:

One more question :- when data travels from client to MA via ethernet , which method translates the data from ethernet to FC on MA server?


Data is received from Disk Agent on the Media Agent via IP (when on different systems or Shared Memory if DA/MA are on the same system). As you know the Media Agent is doing the work of writing to the backup device. This is basic functionality and as long as the device is supported this "translation" happens transparent to the user in the background and you don't need to worry about it.

Since you're running an up-to-date version of 9.x you could also use the IP of the Service Set and allow FC-fallback to find the right way to the device. If the CoFC device is available on the Media Agent it will be used, if not it will fallback to IP.

This offers a great flexibility and reduces load on the Media Agent, but needs a little bit preparation. In this case you should use Source-side deduplication which requires the Media Agent installed on all relevant clients. You can zone them to the Service Set (Source-side dedupe FC-enabled client) or leave it (Source-side dedupe IP-only client) based on what the infrastructure allows.

Source-side dedupe FC-enabled client:
Disk Agent/Media Agent (Shared Memory) -> Media Agent HBA (FC) -> StoreOnce Catalyst store

Source-side dedupe IP-only client:
Disk Agent/Media Agent (Shared Memory) -> Media Agent NIC (IP) -> StoreOnce Catalyst store

Server-side dedupe CoFC Media Agent:
Disk Agent (IP) -> Media Agent (Shared Memory) -> Media Agent HBA (FC) -> StoreOnce Catalyst store

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
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.