Off-Site Backup Storage
Forge can copy supported database backups to protected off-site object storage. The available destination is shown in each database service’s backup settings.
Customers do not need Forge Cloud’s platform storage credentials. Do not place platform R2 or S3 credentials in workspace, project or service variables.
Backup Destinations
Section titled “Backup Destinations”Depending on the service and plan, Forge may offer:
disk: retain the backup on the service’s VPS;r2: retain the verified encrypted object off-site;disk+r2: retain both the local backup and an off-site copy.
Local-only backups do not protect against complete VPS loss. Use an available off-site destination for production data.
What Verification Means
Section titled “What Verification Means”Forge records whether the backup was encrypted, checksummed and found in the configured object store. This proves that the recorded bytes can be retrieved and authenticated. It does not by itself prove that the database, roles, permissions and application login can be recreated on a clean server.
Review restore-test status separately. A failed or missing restore test must not be treated as a recoverable production backup.
Availability
Section titled “Availability”If off-site storage is unavailable, Forge reports the backup error and preserves a valid local artifact when the selected destination permits it. A local artifact does not turn a failed required off-site backup into success.
Contact Forge support when the off-site option is unavailable for a workspace that should have it. Do not work around the restriction by copying platform credentials into a service.