I think it could handle it, I haven't checked how much BitcoinD uses but can't imagine much more than smaller spikes as it holds blockchain in ram to process. Apache and SQL can be installed pretty lightweight. I was about to say traffic would probably be the biggest issue but 2TB is a plentiful amount until you start hitting deepbit size (even then that's probably only gigs).
Actually btcguild use ~4,5TB of traffic per month and they do around 150 gigs per day, but that is for ~2TH. At 60 gh/s i think it would not be that much, and in the event it might not be enough i will try to add more quota.
And i am not much worried about ram, as i am about CPU time. I have no idea what kind of CPU time all the stuff will take up and what lags i might expect.