Skip to main content

Massive data loss incident in a hosting service provider

Here is another report on an incident in Japan.
First Server is one of the major hosting providers of rental servers in Japan.
On June 20th, when one of their engineers tried to apply a security fix to their customer's OS environment,
he/she mistakenly erased more than five thousand disk images of their customers,
as well as the corresponding backup disk images.
After three days of recovery work they given up recovering all of them.

Tragically the compensation will be at most the total price which the customer has been paid for the service, the spokesman of the company explained.
This incident seems to be an alarm bell on the service management depending on the hosting service of third-parties.

You can make a contract with them, but they do what they can do at most.

Comments

Popular posts from this blog

Configuring Network Manager for PPPoE connection

When I'm home, I use fiber-optic line with a dedicated old small router (YAMAHA RT107e) for access to the Internet. But I recently became anxious about the router. If it fails, how can I survive until I get another one? So, I tried to connect my Debian desktop PC to the fiber-optic line without the router. The PC have to talk to the other side of the line with PPPoE but I did not know how. In my PC, the Network Manager manages network configuration. So, I had to configure the Network Manager to utilize the pppoe like : nmcli connection add ifname eth0 connection.type pppoe username USERNAME password PASSWORD

Xen on Squeeze failed to start up the X server with an Intel graphics controller

I recently tried to set up Xen on my Squeeze box, with intel 945GM graphics controller. I followed the instruction on Xen - Debian Wiki . I installed the Xen hypervisor, kernel, xen-tools and other stuff, then created a domU image of Ubuntu natty. After that, I rebooted the system. But when X server was about to be launched, the screen became black out,  both keyboard and mouse don't work anymore. I reread the article on the wiki, and figured out the Xorg driver for Intel graphics controller  is suspicious. So, I changed the Xorg driver 'intel' to 'fbdev' wrting /etc/X11/xorg.conf , and rebooted.  This workaround works out! The drawback of the workaround is, 'intel' driver specific features, including DRI and XvMC, are disabled.

Sharing one home directory between the Linux machines with the different display resolutions and different pointing devices, keeping $HOME/.config data for each machine

 Back in 1990's, it was common practice to share one home directory between many UNIX servers using NFS. But it is not in these days. But I have become to want to share my home directory between two different Linux machines: One is  a Debian GNU/Linux installed as a primary OS of a dual boot machine,  and the other is a virtualized Linux box within the Virtualbox running under the Windows 10, a secondary OS of the dual-boot. They have different display resolutions and pointing devices. These differences led me to an annoying problem: if you open GNOME desktop environment, display and pointing device setting became broken. Today's GNOME desktop environment stores most of the settings to the files under $HOME/.config directory. But if you share $HOME/.config between two machines, the stored configuration for a particular machine may become incompatible with other machines with different display resolutions and pointing devices. Indeed, my GNOME desktop has become unusable. To ove