Backups should not block dns propagation
-
If I understand correctly, a backup process blocks dns propagation, e.g. adding an alias to a Surfer installation.
If this can be avoided, it would be a cool improvement to efficiency of a deployed instance.
Not urgent, something for the list, if it is viable.
-
Right, when an app is being backed up, it "locks" the app. This is just a simple hack to provide consistency in the backup. Meaning, you backup the db, then you are backing up the files, and now in the middle the db is changed with new domains/locations. Now you end up in some inconsistent backup. I know this is not "technically" atomic but it is just pragmatic
But something we can look into with better backup strategies. -
Right, when an app is being backed up, it "locks" the app. This is just a simple hack to provide consistency in the backup. Meaning, you backup the db, then you are backing up the files, and now in the middle the db is changed with new domains/locations. Now you end up in some inconsistent backup. I know this is not "technically" atomic but it is just pragmatic
But something we can look into with better backup strategies.@girish thank you.
Backup reliability is key so I donβt want to suggest a hack.I think the backup process locks all apps. My alias configuration on Surfer would not go through until all apps were completed, not a question of just one app having to complete.
A back-burner change, certainly nothing urgent.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better π
Register Login