Issue with gateway selection when creating Deduplication Store

When trying to configure (add) a Deduplication Store device on a new server, I could create the store, but when having to select a "client" for the gateway, the machine with the store isn't listed; instead machines that still run StoreOnce are listed. I don't understand, but  I'm new to Deduplication Store. And I cannot continue creating the device unless I add at least one gateway, it seems. Is this a software bug, or a misunderstanding at my side?

This is for Data Protector 24.4, and the machine to host Deduplication Store has the Deduplication Store and the Disk Agent installed; does it need a Media Agent, too? I thought Deduplication Store is a kind of Media Agent.

Parents
  • Suggested Answer

    0  

    The B2D gateway is included in a media agent indeed. That's why you see them for your current SO gateways ... those systems do have a media agent installed. This is the same for all B2D devices.

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.

  • 0 in reply to   

    Is there some concept overview relating "Backup to disk" (StoreOnce, Deduplication Store, etc.), "Gateway",  and "Media Agent"?

    Does the media agent connect to the B2D via a gateway, or what is the relation? When configuring a backup, it seems the B2D takes the role of a library device, while the gateway teems to have the role of a "drive" inside the library, so I don't really see a media agent there..

    The other point is: When I add the "Deduplication Store" component, and the component needs a media agent, why isn't it selected automatically?

    I noticed that adding a component even reinstalled the core components even if there and current (and an upgrade always seems to replace the software, even if current (but that's another topic)).

  • 0 in reply to 

    While we are on it: I also think that it would be state of the art when using "Add component" to see which components are there already when selecting the component to add. As it is now the complete set of components is updated (or added if actually new). Most software management is much more clever than this.

Reply
  • 0 in reply to 

    While we are on it: I also think that it would be state of the art when using "Add component" to see which components are there already when selecting the component to add. As it is now the complete set of components is updated (or added if actually new). Most software management is much more clever than this.

Children
No Data