X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D2514D1E9D1; Sun, 4 Apr 2004 19:10:56 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 47094-10; Sun, 4 Apr 2004 16:11:17 -0300 (ADT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id DFCD9D1E9B0; Sun, 4 Apr 2004 16:10:53 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 35B463C9E8; Sun, 4 Apr 2004 16:11:30 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 32C513C93D; Sun, 4 Apr 2004 16:11:30 -0300 (ADT) Date: Sun, 4 Apr 2004 16:11:30 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: pgsql-www@postgresql.org Cc: pgsql-core@postgresql.org Subject: Moving services to a new server / IP ... Message-ID: <20040404155944.W79409@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/9 X-Sequence-Number: 4113 In order to deal with the DDoS attacks that have been hitting one of our clients, we've just setup a US based server that offers DDoS filtering (not sure how they are doing it, but apparently they've been effective in the past) ... the server that we are moving the client to has 700GB of available bandwidth on it, and his VM uses <30GB of it ... First thing we're going to be doing is setting up redundant DNS on that machine, replicated from the main server (we use bind-dlz for DNS), so in case of problems in the future, we'll be able to relatively easily change DNS around ... Second thing is we're going to build a VM on the machine that we're going to rsync a bunch of stuff over to, to offload it from the servers in Panama ... masters will remain there, all that will be on the US server will be mirrors ... Dave and I just chatted, and came up with the following as easy things to move across: ftp.postgresql.org (which also means I'll be able to open it up a bit more for # of connections and speed) anoncvs.postgresql.org rsync.postgresql.org - this is where mirrors will connect to to update themselves, and will itself be updated hourly bt.postgresql.org Basically, those things that are not database dependent ... we had thought about www.postgresql.org, but there are just too many database dependencies on it ... *but* ... with DNS on that server also, if the Panama network goes down, its a simple update on the SQL database on the US server to change www.postgresql.org to point at rsync.postgresql.org for the duration ... Is there anything else that doesn't have any database dependencies that could be easily mirrored, that we're not thinking of? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664