We know only we'll be failing over to BCP for a very long period around the 4th of July weekend because of whatever happened there.
17 replies (most recent on top)
Well, the company could have said that, instead of giving us the mushroom treatment.
Post ID: @6wbk+1bmMH5AG
Secrecy? It's material information that could be used by hackers to gain access to our systems. If you needed to know, you'd know.
Yeah, when organizations rule by secrecy, backchannels fill the resulting information vaccuum.
If the company were actually, you know, TRANSPARENT, team members wouldn't resort to using the layoff boards.
BTW, the BCP away from Silas was canceled late last week, without an explanation.
This is 1) not layoff related, 2) not public information, and 3) exposes topology information for no good reason.
The data lake flooded it :/
All stems back to the fire that occurred at Oxmoor. They keep trying to get items moved from the BCP location at Silas back to Oxmoor through failover events. Thus far they've all "failed". And, whoever said CPG was involved is probably right. They had to redesign some post-fire. I've learned to glance over the emails when I receive them. But, our area is working fine on the BCP server.
Structural issue? Finally a real answer!
Correct, apps need to failover to their bcp location between this upcoming weekend and the following weekend so they can address the situation.
There's a structural issue with the second floor.
"current skills" strike again!
LOL @ this site
That is backwards. Applications already failed away from Silas. Not all apps use Oxmoor as a backup to Silas.
I know, I was on an EACO line all day putting out fires. Some applications failed back after testing. Others were on an extended stay. Now they are moving back to Silas.
You can now clearly see that none of the posters so far have any idea about what they are talking about. Why provide information then, if this is not accurate? The failover event from Silas to Oxmoor will begin next weekend. Applications will stay in Oxmoor for at least 3 months.
Curious. We were told it was related to a "CPG renovation."
Nothing. The Silas BCP event has been ongoing for a while now. Apps primary out of Silas were failed to their BCP connectivity. Some were failed over just for a few hours testing, then moved back to Silas that weekend.
Other apps continues to run at their BCP sites and soon be going back to their primary site in Silas.
The last exec was fired because their disaster recovery plan was a disaster and never worked.