Getting last backup instant for Discovered Entity in Protection Group?

[eric.staats]

On v13 of the API, I am trying to associate each VM that Veeam B&R is aware of with its last backup instant. For many of the VMs, this is possible by getting the VM name, then looking through the list of RestorePoints and finding the latest one for the VM name.

However, for Protection Groups, this method doesn't seem to be working. I am getting the list of Protection Groups:
`/api/v1/agents/protectionGroups`

And then for each `id` there, I look up the details of their discovered entities:
`/api/v1/agents/protectionGroups/{id}/discoveredEntities`

That gives me a list of VMs, including `name` and `ipAddresses`.

The `name`s of those VMs don't appear to be in the results from `/api/v1/restorePoints`. Does anyone know if those VM names should appear in `restorePoints` if they have been backed up? I am running against a test instance of Veeam that may not be the most data-rich, so I'm also not sure if it's just something in my setup and none of those VMs are actually backed up in my instance.

[david.domask]

Hi eric.staats,

You're trying to get restore points for Veeam Agent for Windows backups?

Doesn't api/v1/restorePoints?limit=200&platformNameFilter=WindowsPhysical work for you? You will need to have done a backup naturally (managed by backup server I believe), and you should get result like this:

Code: Select all

{
  "data": [
    {
      "platformName": "WindowsPhysical",
      "type": "Increment",
      "malwareStatus": "Clean",
      "guestOsFamily": "Windows",
      "id": "fc59bfab-a44b-42c2-96bb-2aab91d7bcc7",
      "name": "HK-mgnt-Win11.lab.intern",
      "platformId": "00000000-0000-0000-0000-000000000000",
      "creationTime": "2026-06-09T22:05:19+02:00",
      "backupId": "de50b96e-aee2-44c7-ae40-d13c881ce7c4",
      "parentBackupId": "9bec96ba-7185-4fbc-8052-eaa2eff26efa",
      "sessionId": "00000000-0000-0000-0000-000000000000",
      "allowedOperations": [
        "StartFlrRestore"
      ],
      "backupFileId": "2635f639-854c-44f4-b841-2d1dc0b31dab",
      "originalSize": 102692388864
    },

Can you explain a bit more on your setup? Have you actually run any Veeam Agent for Windows backups yet?

[eric.staats]

I'm working on an application that uses the Veeam API to get data, so I'm less familiar with the day to day operation of Veeam itself and don't actually manage the server I'm testing against personally. My ultimate goal is associate a "last backup time" with a MAC address or IP address for the machines that Veeam is backing up. The restorePoint endpoint has the backup creation time, but it doesn't have a MAC/IP address, which is why I'm going through the protectionGroups endpoint too.

I'll see if I can actually get this scenario replicated in the test environment I'm using, but someone else on my team who looked at this earlier didn't think the "name" property on the discoveredEntities results was matching up with any of the "name" properties on the restorePoints results, so I was just wondering if that was expected or not.

[david.domask]

If you can share some examples (redacting confidential info as needed), we can better advise, as I do not see such a discrepancy in my lab regarding names. IP / MAC is not returned by the restorePoint endpoints, so this is expected.

[eric.staats]

So for example, here's one of the discoveredEntities that is coming back via the "/api/v1/agents/protectionGroups/{id}/discoveredEntities" endpoint:

Code: Select all

    {
        'state': 'Online',
        'agentStatus': 'Installed',
        'driverStatus': 'NotInstalled',
        'operatingSystem': 'Windows10',
        'operatingSystemPlatform': 'X64',
        'agentVersion': '13.0.1.120',
        'rebootRequired': False,
        'ipAddresses': ['IP Address A'],
        'lastConnected': '2026-06-05T02:00:42.922004',
        'operatingSystemVersion': 'Microsoft Windows 10 (1809, 64-bit)',
        'operatingSystemUpdateVersion': 1809,
        'objectId': '88f960b4-e0e9-48e1-856e-5e05e2399c30',
        'biosUuid': 'cef4fa71-beec-4107-a2c1-11a24db71254',
        'plugins': [
            { 'type': 'MSSQL', 'status': 'NotInstalled' },
            { 'type': 'OracleRMAN', 'status': 'NotInstalled' },
            { 'type': 'SAPHANA', 'status': 'NotInstalled' },
            { 'type': 'SAPOnOracle', 'status': 'NotInstalled' },
        ],
        'isTrusted': True,
        'type': 'Computer',
        'id': '6b38d43c-9420-4db7-8a60-2923f497799a',
        'name': 'HOSTNAME 1',
        'parentId': '5a5c91ba-f98c-44e6-88c5-704e6c8f4dee',
        'protectionGroupId': '730dc485-84c2-4a9d-86e7-2e35d1d5a0be',
    }
  

I've also got the entire list of "restorePoints" in back from the API. There are no entries in the restorePoints where the "name" matches the "name" of the discoveredEntity, but I can find some where the "ipAddress" of the discoveredEntity matches the "name" field on the restorePoint.

restorePoint:

Code: Select all

    {
        'platformName': 'WindowsPhysical',
        'type': 'Increment',
        'malwareStatus': 'Clean',
        'guestOsFamily': 'Windows',
        'id': '1fcfeb1e-2443-477c-9400-c0407af7c18d',
        'name': 'IP Address A',
        'platformId': '00000000-0000-0000-0000-000000000000',
        'creationTime': '2026-06-03T10:06:14-04:00',
        'backupId': 'c61a412c-dc42-4b61-86de-2d12dc0d9975',
        'sessionId': '00000000-0000-0000-0000-000000000000',
        'allowedOperations': ['StartFlrRestore'],
        'backupFileId': '4472e9a9-57bb-4bd0-8147-db5e7e330243',
        'originalSize': 59863134208,
    }

Do you think that is a reliable way to associate a backup instant with the discoveredEntity?

The reason I'm asking is because the other computers we're able to discover via various other API endpoints seem to match to restorePoints based on "name", so I want to check the validity of assuming that discoveredEntities' "ipAddresses" will show up as the "name" in the restorePoints.

[david.domask]

Got it, please ask the persons administering the backup server how these machines were added to Veeam, by IP or by their hostname

'name': '26.164.232.140',

This is probably where you're seeing confusion, looks like this machine was added with IP as the name or for some reason Veeam wasn't able to get the hostname correctly for some reason.

If they cannot figure that part out, open a Support Case and let Veeam Support review the situation.

Basically I don't think this is about the endpoints, it's about how the computer's info is stored in Veeam and needs to be checked.