I am looking for some help with figuring out a way to take a Redis Docker image and then do near real time replication of the data to another server maybe over an SSH tunnnel. I need this to be able to go onto a Ubuntu 16.04 LTS VM/docker host, reason for this is OS limit is that the Redis Docker container is only a small part of our setup/application and the other major parts are not tested on anything else. I was doing some reading and Redis itself has replication, but I am not sure if this is the best way to go about doing it. We do have an SSH tunnel set up for another database sync. How could I do this properly? The whole point/idea of this is that we need a DR plan and this factors into it. My best idea so far has been a rsync between the two servers I need the data on, though I know that is not a good solution and want something a bit better.

I'm connected to a cluster which has a release, from a chart, but it was installed by someone else who I think used a tweaked, locally-stored chart. I don't have access to their original chart/repo. Is there a way I can retrieve it from the cluster, so I can tweak/amend, and re-install it? Or, can I find the URL of the original repo that was used? The chart name is `wordpress-0.6.0`, but that's of no use, since it's the same as the "official"/original one.

I would like to know how everyone is making external backups of S3 buckets and best practices/recommendations for this. Regardless of how good AWS is it is still a single point of failure. Especially on a more corporate scale, vast amounts of buckets that are very large. The S3 buckets functionality seems to be very limited. My resolution was the following: The way I'm looking at doing this now is by downloading the data to an external server (bare-metal as EC2 instance is a lot more expensive) and then pushing that to my backups provider.

Have a look at what's described in the question about "Brief outage planned for Wed, May 3, 2017 at 0:00 UTC, 8pm US/Eastern (like a fire drill for computers)", which is about testing of the existing "Disaster Recovery Planning" (= DRP) of the entire family of SE sites. If you were in charge of this, what would be your recommendations to improve these kinds of DRP-testing in production?