The current prototype implementation of Space is hosted on instances in two Cloud-VPS projects (T225081, T225082). The Cloud VPS environment does not provide any automated backup system for instances (virtual machines) or the data contained inside them. The best effort data protection currently provided to all Cloud VPS projects includes usage of RAID in the storage layer which provides basic protection against catastrophic data loss caused by a single hard drive failure, but no further data protection is in place. A failure of multiple drives on the underlying hypervisor (host computer) for any instance can result in data corruption or complete loss of the instance's virtual hard drive. A failure of the entire hypervisor due to hardware malfunction is also possible and could lead to all instances hosted on a failed hypervisor being unavailable for hours to days to weeks if they can be recovered at all. The cloud-services-team is currently working on a multi-quarter project to increase the redundancy of instance storage and detach that storage from a single hypervisor (T90364), but this project is months away from active use.
As the usage of the Space prototype increases, it becomes more and more urgent for a well documented and tested backup and recovery plan to be implemented. Promotion at events like Wikimania and WikiArabia did not seem to include prominent notices that Space is currently only at the prototype/experiment phase of hosting which creates the worrying assumption that a product which has stickers and posters can be relied on to preserve important communications.
The cloud-services-team would be happy to consult with @Qgil and other the maintainers of the Discourse and WordPress instances that power https://space.wmflabs.org and https://discuss-space.wmflabs.org on their backup and recovery plans.