"Setting Validation Failed" in Invoke-RestMethod

Thanks Ryan,

The header issue you mentioned is indeed something we had to deal with, though my original post may have had some conflicting information with the code as I was copying it from the Zerto document but our code had already taken the changes into account.  The exact code I’m running is:

################################################

# Starting for each VPG action of collecting ZVM VPG data

################################################

foreach ($VPGLine in $zertoprotectiongrouparray)

{

$VPGidentifier = $VPGLine.vpgidentifier

$VPGOrganization = $VPGLine.OrganizationName

$VPGVMCount = $VPGLine.VmsCount

$JSON =

“{

“”VpgIdentifier””:””$VPGidentifier“”

}”

################################################

# Posting the VPG JSON Request to the API

################################################

Try

{

$VPGSettingsIdentifier = Invoke-RestMethod -Method Post -Uri $CreateVPGURL -Body $JSON -ContentType $TypeJSON -Headers $zertoSessionHeader_json

$ValidVPGSettingsIdentifier = $true

}

Catch {

$ValidVPGSettingsIdentifier = $false

}

And to note this works for most of our VPGs, just a select few we’ve found so far that return the error I listed above.

Thanks!

Just as a follow up to this in case anyone in the future needs it –

I worked with Gijsbert a bit and at his suggestion messed around with my service profile and journal configuration settings (in the replication tab of the affected VPGs).  My service profile is set to have a 4 hour history, with the journal limit values at 35%/45%.  When I changed it to a custom profile the problem seemed to go away, even though I matched what my actual service profile had exactly.  When I changed it back, the problem came back.

So it seems like there was something going on with the service profile – further apparent by the exception that I was getting mentioning it:

Invoke-RestMethod : {“Message”:”Setting validation failed: Below fileds Warning Journal Percent[ Profile value 35 , New Value 0 ] , Hard Limit Journal Percent[ Profile value 45 , New Value 0 ] are not corresponds service profile definitions; “}

Notice how it shows the journal values I mentioned (35/45), but then mentions “New Value 0” on both.  I mentioned to Gijsbert that it seems like maybe this is the default value when it can’t actually pull the data, as a journal hard limit of 0% either means unlimited (which we don’t have it set to), or would make recovery virtually impossible if it was actually 0%.

I’m not sure why it cared about the actual profile or how the profile itself was bad, but we were luckily in the process of moving all our VPGs to a new service profile instead which also fixed the problem VPGs as we changed them.

If it’s not private, I’d love to see the actual code for the API so I can see where it defines that exception to throw and maybe run through it to see where the check failed for me.

Thanks Gijsbert for putting me in the right direction and helping me figure out it was a problem with the recovery service profile. 🙂