Hi, all. Before we can roll scalr out internally, there's a few last min things that need to be taken care of. Primarily, disaster recovery
I have two questions: They both assume the following: 1. The scalr server lives in AWS. A snapshot of the system is made every 12 hours. The scalr server is scalr.mycorp.com DNS entry pointing to an EIP. 2. There was a catastrophic failure; the box is 100% unavailable, all i have is a snapshot. So my firs question: 1. Let's assume that I can bring the server up and things are working fine. What about all the nodes that were created / spun up since my last backup? E.G. I created the most recent snapshot at Noon. at 4 PM i launched 5 new instances. How can I get scalr to 'know' about those nodes? There will be no record of them on the snapshot; only in AWS. Will the scalr-agent phoning home be 'enough' to get things working agin? 2. Let's say that i have nodes that are configured to talk to 1.2.3.4 as the scalr server. What file(s) do i need to update on the clients so that they'll begin talking to the scalr server located a 6.7.8.9? Can this even work? Thanks! -K -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
