How Does the vpgSettings API Work

How Does the vpgSettings API Work The definition of a VPG can be described by the set of values. The vpgSettings API enables managing this set of values. All the VPG settings are managed in a VPG settings object, which is saved in memory. This object is managed during a session and used to either

How Does the vpgSettings API Work

How Does the vpgSettings API Work

The definition of a VPG can be described by the set of values. The vpgSettings API enables managing this set of values. All the VPG settings are managed in a VPG settings object, which is saved in memory. This object is managed during a session and used to either create a VPG or update an existing VPG.

Managing a VPG using the vpgSettings API involves the following steps:

1.Create a VPG settings object.

2.Manipulate the VPG settings object to include the values you want.

3.Commit the VPG settings object to update the VPG definition in the Zerto Virtual Manager using the values from the VPG settings object in the memory.

The VPG settings object uses an identifier, the vpgSettingsIdentifier. This identifier is not the same as the VPG identifier used to identify an existing VPG.

To ensure uniqueness, you supply identifiers to the vpgSettings API and not names. To retrieve identifiers to use in the vpgSettings API, use other Zerto Virtual Replication RESTful APIs. For example, to retrieve the recovery network identifiers for failover and failover test networks, use the virtualizationsites/{SITEIDENTIFIER}/networks API to return both the network names and identifiers. In the vpgSettings API, you use the network identifier and not the name. In the same way, use the virtualizationsites/{SITEIDENTIFIER}/vms API to return the identifiers of all unprotected virtual machines in a site, and use these identifiers in the vpgSettings API to specify the virtual machines to add to a VPG or to protect in a new VPG.

Note: For details about using all the Zerto Virtual Replication APIs, refer to the Zerto Virtual Replication RESTful API Reference Guide documentation.

Back to top

ncG1vJloZqxrXpa6osbOp5iwq16YvK572Z6praeUpMSvuM6am5icn5jAcIKNbpaFmaSawLV7uZ6pradVZ32XtdGtrJqkVWd9k7HPpaCcmaSevK9xkWmRnqqkpHJzfLWiqa2tkaFyc3ysmqWan5WncnN8hGtvk459Wn96cZFpZF5qYHaklHGRaYanpJmjsmZ%2Bj4Gcpahfh7K0wMWuo3qIeah8gpyorICnrKKke3N6lGefraWc

 Share!