Restore PostgreSQL database

[VirtualTehnofille]

Hi,

How to perform Linux PostgreSQL instance restore in multi-tenant environment in following cases:
1) PostgreSQL instance is backed up with VMware vSphere option "WAL Files PostgreSQL Backup Jobs" as mentioned here https://helpcenter.veeam.com/docs/backu ... ml?ver=120
2) PostgreSQL instance is backed up with Veeam Linux Agent - as mentioned here https://helpcenter.veeam.com/docs/agent ... tml?ver=60

?

[PetrM]

Hello,

You can restore a PostgreSQL instance from a backup of a physical or virtual machine created in Veeam Backup & Replication, please refer to this page to obtain more information about the required job settings. The instructions to restore an instance can be found in this section of the user guide.

Thanks!

[VirtualTehnofille]

Hi,
Thank you for reply.
We have enabled required application aware processing for PostgreSQL. Except application-aware processing, and some PostgreSQL configs I don't see much of additional requirements for Backup operation, since backups can be performed over vSphere VIX or Backup Agent.

However, I found this requirement for restore that is confusing to me https://helpcenter.veeam.com/docs/backu ... ml?ver=120 and port requirement: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

In documentation is mentioned:
"Veeam Explorer for PostgreSQL does not support recovery operations over VIX API or vSphere Automation API."
"You can recover PostgreSQL data over SSH only, restore using Linux Management Agent is not supported."

While we can use vSphere VIX or Backup Agent for backup seams that the same technologies cannot be used for Restore.

Is it expected that in multi-tenant and network segmented environment, Veeam Backup Server or Veeam Cloud Connect server has network SSH and other multiple ports access to every backed-up PostgreSQL Linux VM in order for restore to be performed?

[PetrM]

Hello,

UPD 11/10/2024: there is no 2500-3300 port range requirement for the provider repository
I guess the main concern here is the requirement of the 2500 to 3300 port range from the repository to the source VM? I will consider possible workarounds, but I'd like to make sure first that my understanding of the problem is correct.

Thanks!

[PetrM]

@VirtualTehnofille
Well, it looks like I misunderstood your question when I was reading it yesterday.

You don't need to provide network access from the provider infrastructure to the source workloads. All communication, including data transfer from repositories, is performed through the gateway server. Only the tenant backup server must be able to connect to the PostgreSQL server over SSH, as it plays the role of the mount server.

Thanks!

[VirtualTehnofille]

1) In Veeam provider Multi-tenant Cloud Director case, tenants do not have their own private VBRs. Company has Veeam Backup Server that is connected to vSphere vCenter and Cloud Director. Tenants only have access to the Veeam Backup Enterprise manager for backup/restore operations.

In mentioned multi-tenant case that means that additional VBR Server needs to be deployed per tenant who wants PostgreSQL, and service should be over Agents? (since obviously tenants cannot have access to vSphere).

2) In Veeam Cloud Connect Case. That also means tenants need VBR Server to deployed locally and cannot just relay on VSPC portal?

[PetrM]

Hello,

1) In this case, you will need to meet the requirements outlined on this page. However, I agree that there is still room for improvement, such as teaching our guest interaction proxy to redirect restore traffic from a repository to the guest workloads, but ETA is yet to be determined.

2) I'm not sure if I understand this question correctly. In the case of Cloud Connect, tenants have their Veeam Backup & Replication server, which acts as the mount server (SSH to the guest is required, pls refer to my previous post) during restore by Explorer.

Thanks!

[VirtualTehnofille]

Thank you for provided insight.

1) For VBR multi-tenant case, its not very viable option to open direct network connections to every tenant, since they are network segregated. Since we need to meet requirement of page you mentioned, the only other workaround i can think of is to, create one way connection over external network by NAT-ing SSH, and other ports from VM. Another challenge is that 2500-3300 whole range needs to be NAT-ed.
Restore over VIX and Agent, would be so much simpler for providers.

2) Many tenants don't have their own Veeam Backup & Replication server, they only use Veeam Agent's connected to Veeam Service Provider Portal in order to use Veeam Cloud Connect Repository for off-site backup.

If I understand you correctly, requirement for Cloud Connect Restore is that Veeam Backup & Replication server needs to be deployed on tenant side. VBR server will than have connection to VCC and perform orchestration of PostgreSQL restore.

Is there a plan to add PostgreSQL restore to the VCSP Portal ?

[PetrM]

1) I fully agree that it is a pain point, and I believe we should address it in future releases by teaching our guest interaction proxy to redirect restore traffic. The workaround you are considering seems reasonable, but you don't need to NAT SSH. Instead, you can deploy a mount server on the tenant side.

2) In the case of Cloud Connect, you need to run Explorer on the tenant backup server. Regarding VCSP, there are no plans to add application-item restore there, but we have noted your request.

Thanks!