I did a lot of hosting (of well over a million sites and clients) and this is simply not good practice. Not even looking at the amount paid by edublogs to host. If a warning is ignored you automatically dispatch another mail (and/or sms as some do which is even better). Then you block web traffic in the firewall, leaving :22 open so the client can repair if they missed the 2 warnings.
Depending on the prior cases for that client (or; is this client a notorious spreader of illegal materials or someone who didn't paid in time on numerous occasions) you send automated warnings for a few days if the content remains in place and THEN you can decide to (manually) switch of the server. Unfortunately bigger companies forget about client support / contact and that client is king; Pearson is not your client, edublogs is; you are supposed to defend them, especially lacking prior cases over a larger period of time.
If edublogs called serverbeach to explain the case, telling them they removed the content (from varnish as well) through the open ssh connection, the support person can immediately check and switch it back on. That's normal practice to me and any host who doesn't do that is not worth paying more than $1.99 for some experimental landing page/site which doesn't mean much to you anyway if closed down.
Sorry to say if this is how Serverbeach or Site5.com treat paying customers, I will never bring my business there and I hope others do not either to show that we expect better from you in this day and age. There are clear ways to treat DMCA's and most can be done automated without actually removing anything yourself on the server; there are plenty of filtering rules to block outside the actual server while keeping the rest of the system up and giving the client ample opportunity to remove the offending content.
Depending on the prior cases for that client (or; is this client a notorious spreader of illegal materials or someone who didn't paid in time on numerous occasions) you send automated warnings for a few days if the content remains in place and THEN you can decide to (manually) switch of the server. Unfortunately bigger companies forget about client support / contact and that client is king; Pearson is not your client, edublogs is; you are supposed to defend them, especially lacking prior cases over a larger period of time.
If edublogs called serverbeach to explain the case, telling them they removed the content (from varnish as well) through the open ssh connection, the support person can immediately check and switch it back on. That's normal practice to me and any host who doesn't do that is not worth paying more than $1.99 for some experimental landing page/site which doesn't mean much to you anyway if closed down.
Sorry to say if this is how Serverbeach or Site5.com treat paying customers, I will never bring my business there and I hope others do not either to show that we expect better from you in this day and age. There are clear ways to treat DMCA's and most can be done automated without actually removing anything yourself on the server; there are plenty of filtering rules to block outside the actual server while keeping the rest of the system up and giving the client ample opportunity to remove the offending content.