A customer is planning HPE Storence integration with HPE SimpliVity.

According to the HPE SimpliVity Administration Guide1, one of the major considerations for integrating HPE Storence with HPE SimpliVity is the physical location of the HPE Storence system. The guide recommends that the HPE Storence system should be located in a third site that is independent from the two HPE SimpliVity sites, and that the network latency between the sites should be less than 10 ms. This ensures that the HPE Storence system can act as a reliable backup target for the HPE SimpliVity federation, and that the backup and restore operations can be performed efficiently and securely. The other options are not correct because:

The number of HPE Storence/SimpliVity integration licenses is not a major consideration for this integration. The HPE SimpliVity federation does not require any additional licenses to integrate with HPE Storence1.

The number of the stores configured with HPE SimpliVity is not a major consideration for this integration. The HPE SimpliVity federation can integrate with any number of HPE Storence stores, as long as they are configured with the HPE Storence Catalyst protocol1.

The limited support from software-optimized HPE SimpliVity models is not a major consideration for this integration. The HPE SimpliVity federation can integrate with HPE Storence regardless of the hardware model of the HPE SimpliVity nodes, as long as they are running the same software version1. References: 1: HPE SimpliVity Administration Guide (A00019350ENW), pages 105-107.