![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 16%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECS%3C/text%3E%3C/svg%3E)
Azure Database para PostgreSQL
Servicio de base de datos PostgreSQL administrado por Azure para el desarrollo y la implementación de aplicaciones.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 24%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Hi Contact RyC Services,
The flaw is related to the temporary restore server called temp-recovery-point-7. This name already exists in the background due to a previous failed restore, so the platform returns a conflict and the deployment cannot continue. Please try to restore again using a new server name (e.g. temp-recovery-point-8). If you want to reuse the same name, the locked resource must first be deleted. This is the fastest way to make restoration successful.
Even though you've tried different target server names, restores still fail because there are multiple previous restore attempts stuck in a "Delete" state. When these ghost servers are not fully cleaned up, Azure blocks the new restore operations and returns the same conflict error. This isn't a problem with the name you choose, but because the platform still has incomplete deletion workflows from previous restore attempts.