Cloud Backup Instance Feasability (Azure)

KazuyaDarklight

Dabbler
Joined
May 8, 2019
Messages
36
Not sure if this belongs here or in build help.

Why?:
We have a 45 drives chassis and its great and at the very least we do have cloud backup enabled with B2. But I can't think of a good way to link up with that as a live pool, we'd need to download it all to a new/rebuilt system. I've been pondering what it might cost/what our options might be in terms of more active or responsive DR. So obviously there is always the option of building out a new chassis and colocating it of course and that will have its costs, but there is a lot of fuss in regards to making it the right size, upgrades etc. So I'm wondering for cost/benefit comparison's sake, what I could get away with

Main Questions:
  • Other posts indicate I should be able to run an instance in Azure fine, any hurdles I should be aware of? I'm admittedly an Azure noob for the most part, it would just be nice to keep things in MS' cloud since we have pre-existing connections to it via O365 etc.
  • Are the minimum specs (8GB RAM etc) still the minimum for a unit if its only doing replication? I saw one post where the guy was running ultra-low specs successfully but there wasn't much conversation in that thread so I'd like the community's input. The idea being to run it at the lowest stable specs 99% of the time and then reset it to higher RAM and CPU if we every actually have a DR scenario and are using it for legitimate access. (Not trying to risk data integrity just don't want to pay more than needed.)
  • Given that the objective is to have a user accessible instance of our files in the cloud that can sit dormant and low cost most of the time and be spun up and accessible in relatively short order. (ie- Under a day.) Is there a better way? (That doesn't cost way more.)
Thanks for your time.
 
Top