Thx so much for the update. I will relax until Monday lol! I was completely unaware about the need to have all three servers up and running. Hopefully, they can all be running by early next week. Thx again!!
Cheers
Bill

Jim

If you can keep your Network access OFF until all of the problems are finished, then the only problem will be the amount of data stored on your computer waiting to be sent. You can leave it off for a year if you like.
This applies to any models.

It will also mean that you CAN'T do an Update, because this turns on Network access for long enough to run the command, and you won't be able to download any more models either, as this also requires Network access to be on.

The trick with all of this is to not let any zips get into the Transfers tab while Network access is enabled. Once BOINC starts trying to upload, the 14 day timer will start.

I hope that everyone is regularly watching the News and Announcements thread, (or is Subscribed to it), because this is where the first news will get posted about a fix.

---

Backups: Here

1. Buy more data servers. I'm doing this at the moment but I have to deal with much bureaucracy so it is quite slow, and it takes an actual lack of space to swing things in to action. More space was requested when we started sending out hadam3p jobs but it has taken until now.

As one fellow computer engineer to another, you must request things like this [drive space] as SHOW-STOPPERS (for the new model/project) to the bureaucracy or they will never approve it until some crisis. And surely they'd prefer not to have a crisis?

The HadAM3P models should never have been released on CPDN main project until the space for all the uploaded results were appropriated/purchased. And the situation that we are all in right now is proof that this should have been done months ago. Tell that to management for the next project/model.

I'm aborting all my models until this is resolved as a protest to management.
No space for results = no space for crunching on my machine

[DJStarfox wrote:] I'm aborting all my models until this is resolved as a protest to management.
No space for results = no space for crunching on my machine

I doubt whether such a protest will be successful, for the simple reason that, except in unusual circumstances, the situation ought not to be a problem for participants. Messy and irritating, certainly. But until the hard-wired 14-day limit is reached some time next week we participants are just buffering some data until the project can accept it, and the amount of buffered data is trivial compared to the size of a running model. Quite apart from respecting our efforts, I think you can be confident that the project won't want to lose any data ...

New storage is on order, so there will be enough disk space.

For people who know their way around a computer there is no need for anything to be lost. Suspend network activity or the model before a Zip file is generated, or re-run from a backup, or check Les's post How to extend the 14 day time limit. For others, the clock is ticking, but the project knows that.