Dmaryakh wrote: ↑Sat Jan 28, 2023 7:34 pm
GaryN wrote: ↑Sat Jan 28, 2023 12:45 pm
John
Unfortunately, there have been and still are IT and other people who think nothing of making changes directly in the production system.
"It's only a "little" change." (How many times have we heard that one?)
"It's faster than going through DEV, then a QA review, then finally into PRD"
But what about backup? Even if a week-old (or even a month-old) probably still worth doing a full inventory is probably cheaper than dropped sales due to online being out for 2+ weeks
The standard that I was trained at was "Do every thing to,
not to go down at all."
The problem for many years has been that some/many of the IT staff were not trained like that. As a result, their "production" discipline is lacking or non-existent.
Backup planning is a CRITICAL IT/SysAdmin task. If this is not done properly, or at all, the IT director should be fired.
Sorry but one-week old and even worse one-month old backup is just a few steps from useless.
That last backup has to be taken with the system off-line, and NO transactions after the backup.
If you restore your system from the last backup (a week or a month ago), and IF there were transactions after that, and IF you do not have a method to capture the transactions since the last backup, THEN you lost all the transactions (sales) since the last backup. You have no idea who bought what, who paid and who still owes you money, who you shipped product to and who you still need to ship product to. And because of all the missing data, your accounting is screwed up. This kind of stuff can put a company out of business.
Quote from the CC web site:
The web store is temporarily unavailable as we are doing some maintenance.
IMHO, this is a major issue.
In this day and age, you CANNOT have your web store be down for a week.
What kind of "maintenance" takes more than a week?
What is dumb is that screen does not even give you an alternative, like "please CALL us at xxx-xxx-xxxx to place your order by phone."
I have twice seen IT "professionals" trying to fix a problem by trying many things.
But at the end, when they could not solve the problem, they could not "back out" what they did, and put the system back to a known condition. This was because they did not record what they did. They were "flying by the seat of their pants;" try this, try that, try something else . . .
At the end, we had to rebuild the servers, from the OS on up.