-
- Influencer
- Posts: 20
- Liked: 5 times
- Joined: Aug 09, 2010 7:58 pm
- Full Name: Justin Giardina
- Contact:
Type="VmRestorePoint"
With vCD integration, it looks like the API returns "Type="VmRestorePoint" " to any restore point, whenther it be a VM or vApp. Is this by design?
Also, the only difference I see is in the name (which has a partial uuid for VM). Do you plan to do the same for a vApp?
Also, the only difference I see is in the name (which has a partial uuid for VM). Do you plan to do the same for a vApp?
-
- Product Manager
- Posts: 20414
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Type="VmRestorePoint"
Yes, it is. Probably, you can use RestoreSpec parameter in order to distinguish between VM and vApp restore points. In the latter case, the said parameter is named vCloudVAppRestoreSpec.Is this by design?
Thanks.
-
- Influencer
- Posts: 20
- Liked: 5 times
- Joined: Aug 09, 2010 7:58 pm
- Full Name: Justin Giardina
- Contact:
Re: Type="VmRestorePoint"
Thanks for the info, we will have a look.
-
- Influencer
- Posts: 20
- Liked: 5 times
- Joined: Aug 09, 2010 7:58 pm
- Full Name: Justin Giardina
- Contact:
Re: Type="VmRestorePoint"
Just looking at it quick, I don't think that helps, according to documentation you can't add query params to those requests and there is still no way to figure out which vApp it belongs to. It would have to have the uuid somewhere to be useful. Are we incorrect here?
-
- Influencer
- Posts: 20
- Liked: 5 times
- Joined: Aug 09, 2010 7:58 pm
- Full Name: Justin Giardina
- Contact:
Re: Type="VmRestorePoint"
Here is an example of the data returned for a VM (which includes vCD UUID):
Here is an example of a vApp (No UUID):
Even if the vApp returned a UUID, we would still need to parse for parenthesis which is also not great. We would prefer if we could use something other than "VmDisplayName" to designate a vApp.
It seems like the RestoreSpec you mentioned is just useful on the actual restoration of the vApp, not finding it from a list of available backups.
Code: Select all
<?xml version="1.0" ?>
<VmRestorePoint Href="https://x.x.x.x:9398/api/vmRestorePoints/e2ecda6a-0a8e-4caf-bd66-00e22f70848d?format=Entity" Name="Resource Test Linux (6e3f88e1-5f31-42f4-9f05-1c904db0ce85)@2014-04-04 15:54:58" Type="VmRestorePoint" UID="urn:veeam:VmRestorePoint:e2ecda6a-0a8e-4caf-bd66-00e22f70848d" VmDisplayName="Resource Test Linux" xmlns="http://www.veeam.com/ent/v1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Code: Select all
<?xml version="1.0" ?>
<VmRestorePoint Href="https://x.x.x.x:9398/api/vmRestorePoints/53e69fcc-b644-4864-9bb3-006a10d7f756?format=Entity" Name="Test Disk Rollui@2014-04-05 23:02:49" Type="VmRestorePoint" UID="urn:veeam:VmRestorePoint:53e69fcc-b644-4864-9bb3-006a10d7f756" VmDisplayName="Test Disk Rollup" xmlns="http://www.veeam.com/ent/v1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
It seems like the RestoreSpec you mentioned is just useful on the actual restoration of the vApp, not finding it from a list of available backups.
Who is online
Users browsing this forum: No registered users and 2 guests