But if the power goes off (via power supply loss or whatever) wouldn't data being sent TO the controler/cache already be interrupted in mid stream?

I asked a question here a few weeks ago. Why do you need SSDs or RAID controllers that will continue writing after a power loss, and the answer was: in case the power supply goes.

That makes sense, but where does the progression stop?

I mean, if the power supply goes, doesn't the motherboard, etc., also go?

At what point does this all become moot as components that aren't protected by power loss circuitry get involved and fail?

@Dashrender said:

Look at what you get for the $8 E1 plan, then decide if you need those things for the extra $3/month/user.
Me personally, nope, the business I work for, perhaps (mostly the email discovery piece).

We got 90% of the way to HIPAA compliance, and might be needed that extra $3 worth of stuff in the upcoming future. But for now, we do not.

@scottalanmiller said:

I can't even on this one!!

You had an even, professional response, though.

What? No more testing? Are we that MEH about this controller?

@Dashrender said:

Do you just have O365 Small Business Essentials licenses?

yes

For some reason I feel like if I switch to SBE I am going to be missing out on something.

But it looks like the Exchange they include is the exact same I am paying $4 for. Plus you get ODfB and other stuff. Seems like a win/win to me.

They also support hybrid on the SMB lines now, which is a plus.

@Nic

The next time I have a need for business class AV I will reach out to you.

@JaredBusch

So you are saying my original theory was right? That I can spin it up only once (for less than a week in that instance) every 90 days?

@JaredBusch said:

It means you can spin up your DR site to make sure everything works. for small amounts of time not to exceed a max of one week every 90 days.

So I could spin up for an hour every day for 90 days. That's less than 1 total week.

@BRRABill said:

• For brief periods of disaster recovery testing within one week every 90 days;

And do you have a guess as to what
"• For brief periods of disaster recovery testing within one week every 90 days;"
means?

@nadnerB said:

Lock it down with a local software restriction policy... wait, this is Windows Toy Edition (home), isn't it?

Yes. On an Alienware machine.

@scottalanmiller said:

Technically only on the CALs used during the DR test.

But why would you need any CALs at all for that? Or maybe 1 if anything?

Also, does this ...

Maintain SA coverage for all CALs, External Connector licenses and Server Management Licenses under which it accesses the backup instance and manage the OSEs in which that software runs.

Mean that you need SA on the CALs as well?

So say I have a Server 2012 VL with 20 2012 CALs to access it.

I need SA on both the server AND the CALs?

Here is the rest of it...

In order to use the software under disaster recovery rights, Customer must comply with the following terms:
• The OSE on the disaster recovery Server must not be running at any other times except as above.
• The OSE on the disaster recovery Server may not be in the same cluster as the production Server.
• Other than backup instances run on Microsoft Azure Services, Windows Server License is not required for the disaster recovery Server if the following conditions are met:
o The Hyper-V role within Windows Server is used to replicate Virtual OSEs from the production Server at a primary site to a disaster recovery Server.
o The disaster recovery Server may be used only to

• run hardware virtualization software, such as Hyper-V,
• provide hardware virtualization services,
• run software agents to manage the hardware virtualization software,
• serve as a destination for replication,
• receive replicated Virtual OSEs, test failover,
• await failover of the Virtual OSEs, and
• run disaster recovery workloads as described above.
  o The disaster recovery Server may not be used as a production Server.
  • Use of the software backup Instance should comply with the License Terms for the software.
  • Once the disaster recovery process is complete and the production Server is recovered, the backup Instance must not be running at any other times except those times allowed here.
  • Maintain SA coverage for all CALs, External Connector licenses and Server Management Licenses under which it accesses the backup instance and manage the OSEs in which that software runs.
  • Customer’s right to run the backup Instances ends when Customer’s Software Assurance coverage ends.

@scottalanmiller

I found the following on the Product Use document from November of 2015.

The backup Instance can run only during the following exception periods:
• For brief periods of disaster recovery testing within one week every 90 days;
• During a disaster, while the production Server being recovered is down; and
• Around the time of a disaster, for a brief period, to assist in the transfer between the primary production server and the disaster recovery Server.

I can honestly admit I don't know what "within one week every 90 days" means.

I meant a week in how often you were able to turn it on.

I read this on a SA right explanation, not from MS though.
"The DR server must normally be turned off except for one week every 90 days for software self-testing and patch management and during disaster recovery."

@scottalanmiller

Is that was in that original thread someone said it is too late for us?

Like we could not go through you now, since we are already signed up/

@Nic said:

Do you have any more details on the case with the encryption snafu? From what I've heard we work fine alongside encryption:

The Wave software interacts with the logon part of Windows to pass the drive unlocking credentials entered at boot (which are synced to the user account) onto the OS. So the user can have a SSO if they want. Some AV programs apparently can break this. I had to go in and edit registry settings and then turn all that stuff off. Wave said to try reinstalling and it might stick. But since the user was looking for OTHER features as well, we just decided to scrap Webroot.

As I said I did hear some great things about Webroot, and was thinking of going with that as my recommended paid solution for SOHO/SMB.

I think they also set the "occasional" part of that to like a week or something.

Yet, if what you guys are saying is correct, then the Datto device should be OK if you have SA. Though I am not sure their daily screenshots would be OK.

@Chris can we get an official chime in on this?

@Dashrender

Do you just have O365 Small Business Essentials licenses?