HPE Store once Catalyst replication for Airgap solution

[AnandK1]

Hello Team,

Just want check, we have two store once devices, one is primary backup and another is secondary copy.

For secondary store once planning to configure airgap solution.

Please advise, shall we replicate one catalyst to another catalyst in between two devices with out Commvault aux copy. In this case will restore data any time from secondary copy.

The secondary store once is connected another media agent server which is in different site.

[Mohammed_I]

Hi AnandK1, Good day this is new set and i can share you best practices however i would recommend you to Contact HPE Storage Consultant Team to get the more details, StoreOnce Catalyst Best Practices 
  · Wherever possible, use low-bandwidth StoreOnce Catalyst for optimal backup performance and network usage.
  · When performing low-bandwidth StoreOnce Catalyst backups, spread the number of backup sessions across multiple media servers to reduce the possibility of a media server becoming a performance bottleneck.
  · When using ProLiant media servers and database servers for low-bandwidth StoreOnce Catalyst, enable “HPE Static High-Performance Mode” through the ProLiant “Power Management” settings for the best backup performance. This setting is not the default.
  · For optimum performance, set StoreOnce Catalyst client log levels to the default ERROR log level.
  · When performing backups over Fibre Channel or Ethernet, StoreOnce Catalyst compression and checksums can be set to DISABLED through the backup application configuration file. When performing StoreOnce Catalyst Ethernet backups over WAN, StoreOnce Catalyst compression and checksums must be ENABLED (default) through the backup application (plug-in) configuration file.
  · When configuring a backup application to use a Fully Qualified Domain Name (FQDN) address for a StoreOnce System, be sure that the FQDN is fully registered with a Domain Name Server. Do not use local host file entries. This step is important when using StoreOnce Catalyst Copy jobs because the source StoreOnce System will use the FQDN to communicate directly with the target StoreOnce System. Using local client host file entries will result in the source StoreOnce System not being able to resolve the target FQDN address.
  · To reduce the chance of connection failures on busy Windows clients when using Catalyst over Ethernet, decrease the TIMED_WAIT Windows TCP parameter.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.