3 site backup plan

[Convergo]

Hi there,

having two sites and a stretched vmware cluster, my plan is to place a store once on each site as a catalyst back-up repository. Having site 1 receiving a backup of the complete environment and storing it on store-site1 with Veeam, and having a catalyst copy job to copy all the backedup vms to a catalyst store on site 2 named store-site2. Site 2 subsequently creates a copy of catalyst store-site2 to catalyst store-site3 on the third site.

What would be a good practice to continue the backup jobs and copies to site-3 when site 1 or site 2 is unavailable ?

[Mohammed_I · Accepted solution]

Hi Convergo, 

Good day i enclosing 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.

And if needed, also increase the ephemeral port range. Ephemeral ports are range of ports that Windows Server uses for outbound communications over TCP/IP. 

When an outbound connection is finished, the port associated to the connection is temporarily put into a TIMED_WAIT state in which time it is temporarily unavailable for reuse.

For more information you can contact HPE Consultant Team . 

Thank you.

[support_s]

Hello,

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

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

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