Unitrends and Office365
-
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
-
@Dashrender said in Unitrends and Office365:
@Dashrender said in Unitrends and Office365:
We need a new thread to ask the same question that Willard has been asking for a year or more.
Scott - Should companies that are buying O365 services backup their O365 instances?
The answer to this question should NOT BE yes or no - it should be a question - What is your RPO?
Even that is far too simplistic. There is a reason that we never use those RPO / RTO terms with disaster recovery planning, they are super misleading. For example...
What's your recovery point for a file if lost because of user deletion, if lost because of cryptoware that is really advanced or because of hardware failure or filesystem corruption are totally different things. It's all RPO, true, but it's not something that you can just answer with "five hours", it's complex.
-
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
You are right in that MS does have backups. But what good are they to me if I cannot restore from them when I need them? Same point we're back to again, lol.
The issue is that I simply refuse to accept someone else's backups that I (or my IT Department) cannot use to restore end-user files as a usable backup. Because it is not usable.
In the case of Microsoft's Backup... Is it usable? Yeah, sure. Is it usable to me and my team? Nope.
It's my semantics issue, and you'll likely not get me to change
-
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
Right, so you are saying it is not a backup. That goes against your statement that you agreed that it was a backup.
-
@dafyre said in Unitrends and Office365:
You are right in that MS does have backups. But what good are they to me if I cannot restore from them when I need them? Same point we're back to again, lol.
Sort of, but one leads you to discuss what is and isn't a backup, the other leads to discussing how to get the data protect that you need
-
@dafyre said in Unitrends and Office365:
It's my semantics issue, and you'll likely not get me to change
The problem is, you've said both that it is and that it is not a backup. Which I understand, can be the cat in the box, is it a backup? We only know when it gets restored? I suppose.
-
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
Right, so you are saying it is not a backup. That goes against your statement that you agreed that it was a backup.
Perhaps a better way to say it: It is a backup, but I don't count on it, because I can't use it. lol.
-
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
It's my semantics issue, and you'll likely not get me to change
The problem is, you've said both that it is and that it is not a backup. Which I understand, can be the cat in the box, is it a backup? We only know when it gets restored? I suppose.
Which is why I default to make sure you have a backup that you and your team can access.
-
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
Right, so you are saying it is not a backup. That goes against your statement that you agreed that it was a backup.
Perhaps a better way to say it: It is a backup, but I don't count it, lol.
That would be better. Or even better... it's a backup, but not useful as I need it to be.
-
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
It's my semantics issue, and you'll likely not get me to change
The problem is, you've said both that it is and that it is not a backup. Which I understand, can be the cat in the box, is it a backup? We only know when it gets restored? I suppose.
Which is why I default to make sure you have a backup that you and your team can access.
I don't think that that's a good way to look at it, because that triggers the "backup based on perspective" problem again. I don't believe that "perspective" should be included. Otherwise it's all "who you ask." And that's not useful.
-
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
Right, so you are saying it is not a backup. That goes against your statement that you agreed that it was a backup.
Perhaps a better way to say it: It is a backup, but I don't count it, lol.
That would be better. Or even better... it's a backup, but not useful as I need it to be.
Frankly - it's not useful to you at all. It's only useful to MS in the situation where MS has a failure they need to recover from. And what's worse, we have no idea how old their backups are.
-
@scottalanmiller said in Unitrends and Office365:
What's your recovery point for a file if lost because of user deletion, if lost because of cryptoware that is really advanced or because of hardware failure or filesystem corruption are totally different things. It's all RPO, true, but it's not something that you can just answer with "five hours", it's complex.
Why would those how things happened matter? You have a point in time that you as a company want to be able to recover to... so you plan for that.
-
Example... CEO wants to know if there are backups.
CEO asks IT Manager: "Manager needs someone else to restore so says no backups."
CEO asks Backup Manager: "Backup manager says yes, there are backups"
CEO asks end users: "End users have no control and say No, our data is not backed up."
CEO asks senior admin: "Senior Admin has backup access and says Yes, we have backups."
CEO asks junior admin: "No, no backups for me."
CEO asks janitor: "Jantor says no backups." -
@Dashrender said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
Right, so you are saying it is not a backup. That goes against your statement that you agreed that it was a backup.
Perhaps a better way to say it: It is a backup, but I don't count it, lol.
That would be better. Or even better... it's a backup, but not useful as I need it to be.
Frankly - it's not useful to you at all. It's only useful to MS in the situation where MS has a failure they need to recover from. And what's worse, we have no idea how old their backups are.
You can't really say that Microsoft's continuity doesn't matter to you.
-
@Dashrender said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
What's your recovery point for a file if lost because of user deletion, if lost because of cryptoware that is really advanced or because of hardware failure or filesystem corruption are totally different things. It's all RPO, true, but it's not something that you can just answer with "five hours", it's complex.
Why would those how things happened matter? You have a point in time that you as a company want to be able to recover to... so you plan for that.
Because how it happens matters, it just does. Each of those things create different recovery scenarios. Ask it the opposite way... how can they not matter?
-
@scottalanmiller said in Unitrends and Office365:
Example... CEO wants to know if there are backups.
CEO asks IT Manager: "Manager needs someone else to restore so says no backups."
CEO asks Backup Manager: "Backup manager says yes, there are backups"
CEO asks end users: "End users have no control and say No, our data is not backed up."
CEO asks senior admin: "Senior Admin has backup access and says Yes, we have backups."
CEO asks junior admin: "No, no backups for me."
CEO asks janitor: "Jantor says no backups."That is why the backup team sends out emails a time or two per year reminding folks that Yes, we do have backups, and they are taken at such and such a time every night.
Everybody's on the same page (yes, we did this at my last job for a while).
-
@scottalanmiller said in Unitrends and Office365:
@Dashrender said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
Right, so you are saying it is not a backup. That goes against your statement that you agreed that it was a backup.
Perhaps a better way to say it: It is a backup, but I don't count it, lol.
That would be better. Or even better... it's a backup, but not useful as I need it to be.
Frankly - it's not useful to you at all. It's only useful to MS in the situation where MS has a failure they need to recover from. And what's worse, we have no idea how old their backups are.
You can't really say that Microsoft's continuity doesn't matter to you.
Considering that most people have recovery times that far exceed the lack of recovery of what is available in MS's system, MS's ability to restore their failed system might not be as valuable you think. it might just be better for them to spin up a whole new whatever and we just start restoring our own data continuity plan. Maybe, maybe not.
-
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
Example... CEO wants to know if there are backups.
CEO asks IT Manager: "Manager needs someone else to restore so says no backups."
CEO asks Backup Manager: "Backup manager says yes, there are backups"
CEO asks end users: "End users have no control and say No, our data is not backed up."
CEO asks senior admin: "Senior Admin has backup access and says Yes, we have backups."
CEO asks junior admin: "No, no backups for me."
CEO asks janitor: "Jantor says no backups."That is why the backup team sends out emails a time or two per year reminding folks that Yes,
That makes no difference as long as perspective exists. If "I have access to do the restore" is a requirement for "are there backups" that email is just lies. Because it is sent to people to whom there are no backups.
-
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
Example... CEO wants to know if there are backups.
CEO asks IT Manager: "Manager needs someone else to restore so says no backups."
CEO asks Backup Manager: "Backup manager says yes, there are backups"
CEO asks end users: "End users have no control and say No, our data is not backed up."
CEO asks senior admin: "Senior Admin has backup access and says Yes, we have backups."
CEO asks junior admin: "No, no backups for me."
CEO asks janitor: "Jantor says no backups."That is why the backup team sends out emails a time or two per year reminding folks that Yes, we do have backups, and they are taken at such and such a time every night.
Everybody's on the same page (yes, we did this at my last job for a while).
Remember, Microsoft could remind you every day that you HAVE backups.
-
@Dashrender said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@Dashrender said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
@scottalanmiller said in Unitrends and Office365:
@dafyre said in Unitrends and Office365:
The Short, Short version: If I or my users cannot restore from it, I cannot consider it a backup.
If this isn't saying that there isn't a backup, what were you saying?
That I cannot consider it a backup.
Right, so you are saying it is not a backup. That goes against your statement that you agreed that it was a backup.
Perhaps a better way to say it: It is a backup, but I don't count it, lol.
That would be better. Or even better... it's a backup, but not useful as I need it to be.
Frankly - it's not useful to you at all. It's only useful to MS in the situation where MS has a failure they need to recover from. And what's worse, we have no idea how old their backups are.
You can't really say that Microsoft's continuity doesn't matter to you.
Considering that most people have recovery times that far exceed the lack of recovery of what is available in MS's system, MS's ability to restore their failed system might not be as valuable you think. it might just be better for them to spin up a whole new whatever and we just start restoring our own data continuity plan. Maybe, maybe not.
I don't have details but I'm unsure what you are saying. MS can likely recover very quickly. LTO restores are quite fast, and don't congest the WAN link like customer restores would.
