- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Application Integration
- >
- [Rest API] - Enable Protection Group Sync
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2016 10:23 AM
03-18-2016 10:23 AM
During some recent testing I was getting fed up of Veeam crashing into nimble synchronised snapshots. My solution to this would have been to add a pre & post script to the Veeam job to suspend synchronisation upon job start and re-enable at job end...
According to the API documentation you call
/v1/volume_collections/{id}
e.g.
$data = @{
app_sync = "vmware"
vcenter_hostname = "xxx"
vcenter_username = "xxx\xxx"
vcenter_password = "xxxv"
}
$body = convertto-json (@{ data = $data })
$result=Invoke-RestMethod -Uri $apiurl -Method PUT -Header $header -Body $body
However I'm getting a 400 error...
My request to suspend works fine - the only difference being:
$data = @{
app_sync = "none"
}
Can anyone confirm if this is allowed through the API?? We're running firmware 2.3.9.2-303808-opt on a CS300
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2016 02:10 AM
03-20-2016 02:10 AM
SolutionBackslash is almost always used as an escape character, converto-json is escaping your single backslash:
PS D:\powershellserver> $data = @{
>> app_sync = "vmware"
>> vcenter_hostname = "xxx"
>> vcenter_username = "xxx\xxx"
>> vcenter_password = "xxxv"
>> }
>>
PS D:\powershellserver>
PS D:\powershellserver> $body = convertto-json (@{ data = $data })
PS D:\powershellserver> echo $body
{
"data": {
"vcenter_password": "xxxv",
"vcenter_hostname": "xxx",
"vcenter_username": "xxx\\xxx",
"app_sync": "vmware"
}
}
I imagine this is why you are getting the 400 error (the API endpoint may not be interpreting the escaped backslash properly).
I would suggest instead of DOMAIN\USER, you use USER@DOMAIN (better to use FQDN), vcenter doesn't care which version of the username you use.
- Casey Crawford