The employees of Google, perhaps spurred by the Chinese, also didn't want to be looked down upon by them, making it seem as if the great Americans were not as capable as these local Chinese.
So, everyone began to work overtime frantically. After the Chinese rested for a night and slept soundly, they continued their work. Thus, both Google and Jiangnan Group worked overtime for 24 hours, completing the final debugging.
Ultimately, the installation and debugging work, which was originally estimated to take at least seven days, was completed in just three and a half days.
During the remaining five and a half days, Jiangnan's high-quality servers demonstrated their value. Due to the extremely fast storage and deletion speeds, the data transfer was much quicker than anticipated.
When only 30% of the data remained, Larry Page directly issued an order to cease any intentional traffic restrictions and transfer all their data.
The reason for issuing such a decision on the last day, despite the risk, was that Larry Page had extensive contact with Yahoo and understood the company very well.
Yahoo had already become a behemoth at this time, with thousands of employees in its US headquarters alone and dozens of different departments.
Furthermore, internal management had begun to descend into chaos. Take the server department, for instance; they didn't have a direct management channel to the top, requiring a four-tiered hierarchical oversight.
Of course, such a situation was very normal in large companies; this was the so-called "big company disease."
Companies suffering from the big company disease had extremely slow internal information reporting. A piece of information discovered at the bottom level often took days or even weeks before it had a chance to reach the eyes of the senior management.
And even then, it was only a chance; more likely, such information would be directly lost in the communication process.
Take this instance of Google's data anomaly. After Larry Page announced the full data transfer, the staff responsible for monitoring server traffic immediately discovered the abnormality.
After all, the data traffic had suddenly increased several times; even an idiot could see the problem.
But the result was that this staff member chose to ignore it.
This was not because the staff member was in league with Larry Page or had been bribed by him. On the contrary, Larry Page and this staff member didn't know each other at all.
The only reason this staff member chose to ignore it was that reporting it was too troublesome.
He would need to pull the data, then fill out a detailed form, and finally submit a report. All these tasks combined would take at least an hour or two; it was too tiring.
When he first joined the company, this staff member would have diligently written a report for such matters.
But after experiencing such situations a few times, this staff member helplessly realized that apart from his direct supervisor, no one higher up reacted to the report; he received no feedback whatsoever.
In fact, an explosion of traffic at a certain moment was quite normal. For example, it could be due to a significant news event, a trending topic, a network malfunction in a certain region, or even a hacker attack. There were various reasons, but it wasn't usually a big deal.
After trying to ignore such situations once and receiving no punishment or reprimand, this staff member habitually chose to ignore them. After all, his salary was fixed; why should he increase his workload?
As a result, for three full hours of surging traffic, Yahoo itself took no action.
It wasn't until three hours later, when the employee noticed that the traffic was still running at high speed, that he began to suspect something was amiss.
But he couldn't manage it anymore because he was about to get off work. Would he report it to his supervisor at this time, only to earn himself an opportunity for unpaid overtime?
So, he decisively chose to continue ignoring it, instead reminding the person who was about to take over his shift to pay attention to the traffic changes, and then left work directly.
The employee who took over had the same mindset. He procrastinated for four hours, giving Google seven hours of no response time, before realizing he needed to write a report to his supervisor.
He then spent an hour writing the report and sent it to his supervisor's email. However, it was already close to midnight, and the supervisor had already fallen asleep. Who would pay attention to such a report?
It wasn't until 9:00 AM the next morning when the supervisor started work that he noticed the report in his inbox. He then called the employee responsible for monitoring. The employee reported that the traffic had returned to normal levels around 8:00 AM, and the surge had subsided.
"It's just an occasional glitch, nothing to worry about!" the supervisor muttered. If he were to report it, he would have to write a two-hour report, which was too much work.
At this moment, Google was completely free from Yahoo, reborn through blood.
————————————
"How was yesterday's data? Has it returned to normal?" It was also nine o'clock the next morning when the staff member from the previous day returned to work.
He was actually quite responsible, constantly thinking about the abnormal traffic that had persisted for over three hours yesterday. So, the first thing he did upon returning was to check if the abnormal traffic was still present. To his pleasant surprise, the traffic had returned to normal, even lower than usual.
This put the staff member at ease. Coincidentally, his manager came over to inquire about the situation. Upon hearing about the anomaly report sent by the night shift staff member, he reported that the traffic was normal and there were no issues.
This normal state continued until noon.
According to the company's work guidelines, it was necessary to constantly check the detailed data of each server and compare it with the situation of the storage servers to assess the risk of data loss.
Therefore, no one truly checked the data at all times; a comparison at three points in the morning, noon, and evening was sufficient.
Thus, on this day, when the latest data intelligence appeared on the computer screen, the staff member merely glanced at it. Instantly, his entire body froze. A few seconds later, he let out a wail like a ghost crying.
The commotion was so great that it immediately drew his supervisor. Upon seeing the data, the supervisor was utterly stunned.
Because at this moment, among all the storage servers, the data on nearly 8,000 storage servers had been completely wiped, and the data on 6,000 storage servers was significantly lost, accounting for one-fourth of the total number of servers.
"Which departments do these cleared servers belong to? Can they be recovered?" the supervisor asked desperately, knowing that this data was most likely unrecoverable.
Even if it could be recovered, the time required would be measured in months. Even if it were successfully recovered in the end, their lives and futures would be ruined; he would have to resign from the company.
This was the company's most critical data! Without this data, the company had no idea how to explain itself to its users.
"This... fortunately, in this misfortune, I checked, and all the lost data belongs to Google, which we were storing on their behalf. Our company's own user data has no losses!" the staff member said.
"Really!" The supervisor's face immediately lit up with the excitement of a desperate man finding salvation. He immediately reinvestigated and confirmed that the staff member was not mistaken. The lost data had nothing to do with Yahoo; it was all Google's.
"Even so, it's still a terrible situation. The entire Google website is likely paralyzed now, and Google will come knocking on our door soon!" the staff member said despairingly.
Perhaps the supervisor could still survive this time, but he himself was certainly doomed.
"Strange, why was it only Google's data that was deleted? And when was it deleted?" the supervisor asked, suddenly turning the question when the situation seemed to have a turning point.
"It should be related to yesterday's massive data flow!" the staff member analyzed. "Hackers must have infiltrated Google's backend, seized their company's permissions, and then deleted all the data in the servers. Only this explanation makes sense!"
The staff member was correct. Currently, this was the only plausible explanation, as no one could imagine that this data would be deleted by Google itself.
"No, not necessarily. This might not have been done by hackers at all!" the supervisor shook his head. He recalled many rumors within the company, the difficult negotiations the company had with Google, the occasional rage of Madam Yang, and the fatal weakness of Google that he held in his hands.
Perhaps this was not done by hackers at all; perhaps it was done by one of their own!