Skip to main content
Question

Backup and Restore for IFS Cloud Build Place

  • Nov 6, 2026 7:18 AM UTC
  • 2 replies
  • 26 views

Forum|alt.badge.img+1

Hello,

I would like to confirm the backup and restore mechanism for IFS Cloud Build Place.

・Is backup available for Build Place?
・If so, how are the databases and master data in Build Place environments backed up?

・In case of data loss, data corruption, or accidental deletion, how can the Build Place environment and its data be restored?
 

My understanding is that backup and restore operations for Build Place environments are managed by IFS, and customers are not required to perform these operations themselves.

 

Thank you.

2 replies

Forum|alt.badge.img+3
  • Do Gooder (Employee)
  • Nov 6, 2026 7:29 AM UTC

Build Place environments (DEV, QAS, TOP, DEL, BAS) are temporary environments provisioned on demand from your Customer Solution repository, with a defined lifespan (7–30 days by default, extendable to 45). They are deleted automatically when they expire. As a result, there is no customer-facing backup and restore for Build Place environment databases. If an environment is lost, corrupted or deleted, simply order a new one from the Lifecycle Experience Center based on the last successful build. Your code and configuration are safe in the repository.

Build Place should not contain production data. Master and basic data should be kept in the Use Place (e.g. your CFG/UAT environments) or in reusable data packages, so it can be reloaded into any new Build Place environment. Use Place environments are operated and backed up by IFS. If you need a restore there, raise a case with IFS Support.


Forum|alt.badge.img+7
  • Sidekick (Partner)
  • Nov 6, 2026 9:05 AM UTC

Hello ​@AyakaFujita,

As Arif mentioned, there is currently no backup mechanism for Build Place environments. If an environment expires or becomes corrupted, the basic test data imported into that environment would be lost.

I understand how frustrating it can be to lose test data from a temporary environment and then have to recreate or reimport it each time a new environment is created.

From our side, we normally export the required data while the environment is still available and then reimport it when a new environment is created. You could also consider creating your own script to automate this process.

I believe IFS should provide a standard functionality for this, as it would be useful for all IFS Cloud customers working with temporary Build Place environments.