Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
LLAMS348020dJust say you were running a test of the failover systems 😬
AtuM237920dDon't feel bad. Accidents happen and most of the times you learn from them. You had backup, everything is fine.
Oktokolo304019dI always do a manual backup and test my SQL script against a copy of that backup on my dev system before doing anything on the live DB.
It costs time but already prevented the dirtying of quite some pants in the past...
IntrusionCM631519dImportant question: Have you learned from your mistakes?
If not, let me spank that wet butt till you remember what you did wrong.
myss457419dFrom your arrogance it's obvious you've never handled db larger then 100 gigs, good luck and lemme know on how creating a "manual backup" to your localhost will go and how many things will be on fire after/during your first attempt 😉
And creating manual backups of prod on your local is nowhere near doing it right.
devphobe811718dMore important question? How’d you do it!? I once took down an entire hospitals network for 2 hours.
There are DBs that aren't too big to copy - and there are DBs not containing usefull data.
If you have backups, the database can be copied. If you don't have backups, testing on the live system is indeed fine as the data obviously is disposable...
I don't say, that copying databases over 100GiB is fun - only, that you better do it and test stuff somewhere else before throwing it at the production servers.
It may of course also be the staging server instead of your dev system (i just happen to have it all locally too).
You need to test restoring a backup from time to time anyways...