What to do when you don't agree with the opinion of an IT consultant
-
An RPO/RTO question is a lot more difficult to answer than one might expect. I'm sure that Alex and Scott have a linty of questions that can make it easier, but for a company that hasn't ever looked at these questions before it's likely they have no real understanding of how to answer these requests.
When I first started with my company I was told that we could live without our brand new EHR for 6 days (the downtime the vendor told us we'd suffer if we had a total server failure). The vendor at the time refused to provide installation media/files (they built then shipped the servers to us) and all we had for backups were SQL level backups.
I approached the board with a plan to provide better options, but at that near day one the board stated that 6 days of downtime considering the current setup was acceptable. Of course I nearly passed out that this consider I'd been supporting their phones for the past 4 years and they were nearly unbearable when their phones wouldn't sync for a day to their calendars.
Fast forward a year and a few minor outages later, the tune changed and we could now only afford one day of downtime, so they approved the purchase of Appasure, and we reduced our downtime to a few hours.
Back to the point at hand, if the Docs in technobabble's case haven't experienced downtime in the past they will have unrealistic expectations of either uptime or tolerable downtime.
-
Great example of how small businesses think and work. In this case, both Docs and the Billing Company that is providing the Docs the software have never seen data lose nor technical failures. I am drafting a letter to the client to get them thinking about the future of the business.
-
Or the possible lack thereof.
-
@Dashrender said:
An RPO/RTO question is a lot more difficult to answer than one might expect. I'm sure that Alex and Scott have a linty of questions that can make it easier, but for a company that hasn't ever looked at these questions before it's likely they have no real understanding of how to answer these requests.
When I first started with my company I was told that we could live without our brand new EHR for 6 days (the downtime the vendor told us we'd suffer if we had a total server failure). The vendor at the time refused to provide installation media/files (they built then shipped the servers to us) and all we had for backups were SQL level backups.
I approached the board with a plan to provide better options, but at that near day one the board stated that 6 days of downtime considering the current setup was acceptable. Of course I nearly passed out that this consider I'd been supporting their phones for the past 4 years and they were nearly unbearable when their phones wouldn't sync for a day to their calendars.
Fast forward a year and a few minor outages later, the tune changed and we could now only afford one day of downtime, so they approved the purchase of Appasure, and we reduced our downtime to a few hours.
Back to the point at hand, if the Docs in technobabble's case haven't experienced downtime in the past they will have unrealistic expectations of either uptime or tolerable downtime.
For RTO, the easiest way to ask it is, "If X fails, how long can the business be without it before it severely impairs the business?" For some folks, it's a few hours, or even more than a day. For others, it's less. For RPO, it's, "If we need to roll back to backups, how far back can we recover to in an emergency without causing undue data loss?" Most folks are ok with the previous night's backup, but not quite everyone. The longest it's ever taken me to determine RPO/RTO has been about 30 minutes.
-
let me talk to these docs/managers/directors/ whoever
-
Love the community engagement figuring this out, now I'm curious.
Grabs the popcorn
-
A quick conversation with the stakeholders all at one table usually does the trick.
-
The stakeholders are here are just the small business owner.
-
@technobabble said:
The stakeholders are here are just the small business owner.
Should be even easier then.
-
@technobabble said:
The silent partner is becoming involved.
@technobabble said:
The stakeholders are here are just the small business owner.
These two statements do not jive.
-
@JaredBusch said:
@technobabble said:
The silent partner is becoming involved.
@technobabble said:
The stakeholders are here are just the small business owner.
These two statements do not jive.
Crap...you are correct sir, he's not so silent anymore. Thanks to all of you peeps, I was able to bring something new to the table. We'll see if they are interested in protecting their business or just moving servers out of the office.
-
I am through worrying about this client.
According to the client "I understand and appreciate your thoughts I have already advised the cloud company I am interested in disaster recovery as this is one of the main reasons we are going outside of our office for server location.
I will let you know what I find."
