Netbox usage in different regions #16160
-
Hello! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
If you're running a single Netbox instance then you must have a single database as your "source of truth". Netbox doesn't support multiple disconnected instances with eventual-consistency. Your best bet would be to build a postgres database in a place where it's always available. AWS RDS would be an example of that. It can run replicas between multiple availability zones in a region, so you get extremely high availability. Pick a region which has good connectivity to both locations of interest. If you want disconnected operation: site A can use site A's database while site B can use site B's database, even if site A can't see site B - then you need two separate Netbox instances with their own data. |
Beta Was this translation helpful? Give feedback.
-
Sir candlerb, I apologize if I don’t understand something, that if changes were made to Netbox B, but the connection with the database was lost, then these changes will no longer arrive in the database, and Netbox A will not know that Item_1 no longer exists ( even if the connection with the database is restored later) and in this case the Slave will no longer help us, right? |
Beta Was this translation helpful? Give feedback.
If Netbox A and Netbox B connect to the same Postgres instance, then they will see exactly the same data.
If, as in the second part of your diagram, Netbox B loses connection to this postgres database, then it will stop working. The user will see an error for any attempted read or update operation. Their attempt to delete Item 1 will fail, and they will see it fail. It's then up to the user to retry the request later when the database connection is back up. (While the database is unreachable, they won't even be able to see that item 1 exists, so there will be no button to click to delete it anyway, unless they browsed to it while the database connection was up)
I'd suggest you simplify th…