I have survived years without getting an account on the boards but now out of blind hope that someone at Jolt will read it Here goes.
With many long years in the IT business i know that there is nothing that pisses a customer off more then setting a deadline and then resetting it.
This is what you at Jolt have done over 50 times now. doing it once is bad doing it 5 times and you would seriously compromise your reputation with that client doing it 50 times and you just wouldn't find anyone who would employ you as long as that incident is remembered.
This has nothing to do with skills and everything to do with experience. it is my deduction that you lack it and there is no shame in that. No one starts out experienced but it is something you pickup along the road.
So my suggestion would be have your developers gather and have them write a number on a paper on how long they think it would take to get it all up and running again. Then take the highest number and triple it. that is your deadline. That is the date you divulge to your consumers when they can expect services to resume.If you finish early then you have bonus time to run extra tests allow the users to stress the servers properly everything you should have done before taking it live. Another option is to resume services and inform the consumers that there will be a rollback/restart occurring at the date set for the deadline. This will allow you to get all the test time you need and the customers will know what is going on, they may not approve it but the alternative of constantly disappointing your customers on a semi hourly basis is worse.
Best Regards
/Rev