@nerdydad said in 3 steps to maintain the 3-2-1 backup rule:

@scottalanmiller said in 3 steps to maintain the 3-2-1 backup rule:

@nerdydad said in 3 steps to maintain the 3-2-1 backup rule:

@oksana Is there a way of pointing Starwind VTL to a private cloud provider instead of Microsoft blob, Azure AWS, or Backblaze?

It's not that easy. What API is that private provider using?

¯＼(ツ)/¯

Then how would they point to it? It's like asking "can I use a thing"? I don't know, depends what that thing is.

@jaredbusch said in Microsoft buys GitHub for $7.5 billion:

@obsolesce The only reason I’m not moving my projects to githhub is because I cannot get private repository without paying for it. Gitlab offers that.

Yeah that's why I have everything on GitLab as well.

@scottalanmiller said in What Is Expected of Microsoft Server Support?:

Did they fix something broken with the OS that IT could not have fixed?

There are some quirky poorly documented things that are sometimes need to be done with ESEUTIL, and repairing from corruption, or failed log replays on Exchange and SQL. In theory it's not always Microsofts fault (caused by storage layer issues).

The other issue is driver issues for IO devices. In theory this should be transative (supported by teh OEM who agree's to support your OS). That said OEM's often don't support the free OS's because they don't have joint engineering commitements to fix issues on them.

RedHat has hard commitments from Avago/Broadcom to fix a driver HBA issue if they find it. Having a Server that has a supported OS means they have Avago's commitment to spend hundreds of thousands of engineering time to fix an issue. Redhat will possibly work to mitigate it from their side if possible. Missing the OS vendor in this conversation/effort can make things move slower or stall. Avago and other component manufactoreres will refuse support calls from a customer who bought the device through an OEM so without the OEM listing your OS as supported you are kinda screwed.

(A long time ago) I saw a case where a I/O device had outright buggy silicon, and a driver and OS side workaround was needed to resolve it. This is all the more fun as how the I/O device engineering teams work is they generally refuse to work with a customer directly and require the OS vendor escalate the issue to them.

Where was this when we started our o365 migration!!!

I wouldn't like to see the end of 365, but I would always like to see good competition to Microsoft, a leopard never changes its spots in my eyes and Microsoft have history with all the previous court cases in some of their dodgy practices and monopolisation..they slagged off Linux to high heaven in the older days and now their embracing it? Might be something to do with Microsoft using it as part of their azure backend.

You can't doubt they make some excellent products but they have always ripped people off and most of their licencing models are complete shit...I think in a few years people will be moaning to high hell once all their subscription models have been increased through the roof and Microsoft know you won't go over to Google now as their Google apps/g suite has been left in the dust.

Microsoft are far from a perfect company and it does iritate me when people di*k ride and never see any fault with them and a lot and most are Linux haters I find as well...