December 30, 2021 at 7:57 pm
"I do have one database that is STUPID critical to the company - in order to get access to it, you must first sign a waiver saying that in the event of data loss due to my fault, I am liable for $8 million!"
Brian, that is hilarious. Surely you are jerking me around with this one. But just in case, that's where I stand up and say 'Good night, boss. See ya tomorrow."
I have my coffee cup ready at all times just to the right of my keyboard. And I've only ruined one keyboard with it too.
Rick
Disaster Recovery = Backup ( Backup ( Your Backup ) )
December 30, 2021 at 8:08 pm
@ZZartin - that makes perfect sense. I do agree that the "urgent" fixes can go live without prior approval or code review, but we DO still do a post-release code review for those. A scenario I can think of with that would be after-hours support. Application breaks due to a bug that is found while I am on-call, I will fix the bug and release the code to live without prior approval, BUT I will get it reviewed after it goes live.
@skeleton567 - I wish I was joking about that. They asked me to support it and then gave me the paperwork to sign. Any time a new person gets access or someone loses access, the access controller sends out an email to everyone who has signed the paperwork. THANKFULLY that system is on its way out as it was used solely for a product that is approaching EOL. Also, my responsibility is only to maintain the backup strategy for the system and to restore it in the event of DR. I don't look at the data and don't want to. They also know how much I get paid, and if they think I can handle $8 million, they must expect me to be working there until I am 600 years old or more! The similar system for newer products has no liability like that yet I helped set it up to be much more secure. It's weird how this company works sometimes...
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
December 30, 2021 at 8:21 pm
Ok, Brian, sorry I'm so slow on this. Now I get it. That's where they keep the porn collection.
Tell them to fund a personal liability policy for you before you touch it.
Rick
Disaster Recovery = Backup ( Backup ( Your Backup ) )
December 30, 2021 at 8:27 pm
HAHAHA... that is the running gag in the office actually! But the data in that database is critical to the company until the product goes EOL, yet it is running on one of our oldest VM's and SQL instances! Both are out of support and it is a "best effort" to restore it in the event we need to do DR. The data stored in there is written to units that we build and sell and if the data got leaked, anyone could build similar units and we would have a LOT more competition.
It's kind of like if the source code repository at Microsoft were to get leaked and all of their source code went public, it would be devastating to the company. If this database got leaked, it would be a similar thing for us.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
December 31, 2021 at 3:46 am
This was removed by the editor as SPAM
Viewing 5 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply