# Can't restore a snapshot instance
**URL:** https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089
**Category:** Support
**Created:** [May 20, 2020, 4:23pm UTC](https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089 "2020-05-20T16:23:56Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@eextra](https://meta.discourse.org/u/eextra)
#### Post date: [May 20, 2020, 4:23pm UTC](https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089/1 "2020-05-20T16:23:56Z")
I can’t restore a snapshot instance.
I’m testing in different ways. Installation, forum backup works well, but I’m concerned about restoring a snapshot instance from lightsail.
I restore the image and everything works on the old domain but I can’t connect a new one. When assigning a different address there is a mistake that you cannot connect to the port (blocked) even though the port is unlocked (443 and also 80) ./discourse-setup and rebuild app dont work. . I check for 3 different providers and domains in a row and there is always the same problem. Ports and A record on ip are definitely well set.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [May 20, 2020, 5:10pm UTC](https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089/2 "2020-05-20T17:10:09Z")
Snapshots aren’t really supported, there are too many variables which could lead to an inconsistent state. You’re going to need to use the built-in backup mechanism.
---
### Author:  [@eextra](https://meta.discourse.org/u/eextra)
#### Post date: [May 20, 2020, 7:52pm UTC](https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089/3 "2020-05-20T19:52:20Z")
What are these variables? why is this not a problem in comparable systems like node bb and others ?
Can you clarify that further?
---
### Author:  [@eextra](https://meta.discourse.org/u/eextra)
#### Post date: [May 20, 2020, 7:59pm UTC](https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089/4 "2020-05-20T19:59:39Z")
**So, basically, paying for backup on the aws/azure is completely useless ?**
it is not a small problem because in principle, the very strong and robust side of the host provider becomes useless and this largely limits repair after a major failure
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [May 20, 2020, 8:03pm UTC](https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089/5 "2020-05-20T20:03:08Z")
If you can get it to work, more power to you!
---
### Author:  [@md-misko](https://meta.discourse.org/u/md-misko)
#### Post date: [May 23, 2020, 9:01pm UTC](https://meta.discourse.org/t/cant-restore-a-snapshot-instance/152089/6 "2020-05-23T21:01:17Z")
> [@eextra](#):
>
> So, basically, paying for backup on the aws/azure is completely useless ?
Not quite, you can set up [Configure Application-Consistent Backup for Azure Linux VMs by Using Azure Backup - Azure Backup | Microsoft Learn](https://docs.microsoft.com/en-us/azure/backup/backup-azure-linux-app-consistent) using a pre and post script that puts Discourse into read only mode just prior to VM backup:
```plaintext
docker exec -i app discourse enable_readonly
```
```plaintext
docker exec -i app discourse disable_readonly
```
which ensures database consistency on restore (proven to work with both backup and restore of full VM).