Sydney Wide Downtime [September 14th]

We just want to make an announcement concerning the service connection issues over the past few hours.

Firstly we want to say it was not an attack against us (as thought earlier). Connectivity issues were caused by one of the main internet providers (Pacific Internet) for EpicServers and our Sydney datacenter (GlobalSwitch). Pacific Internet were experiencing router hardware difficulties which resulted in routing issues. We were then notified that "A restart of both routers rectified the issue." All EpicServers should now be running as usual prior to the down time.

We just want to make the situation clear and avoid any hesitation one may see with our services, operations or providers (which are now back and running as normal).

We apologise for any inconvenience this may have caused and we thank you for understanding and being patient during this period.
If you find anything out of place or that may have gone missing please contact the support and we'll help restore any issues.

Thank you.
Ron, I don't think this is mainly about disk crash and more about the evesrr file system has not been cleaned in a while, and because of this there is lots of directories and files.And as the machines prob. hasn't been rebooted in a while, the file system needs some cleaning, which takes a lots of time. Large evesrrs like this might take some days just doing this. It's not your home computer rebooting But, the major problem is that we are not reciving information about what happens. They could have warned us about this with a message from the Nabaztag before statrting the move. And posted information here and on other places where we are constantly updated about the situation. That is something they can do. Even if the other isn't working that well. Maybe set up an simple evesrr with some information while the original one is booting?
If it wasn't for the Darwin Awards, there would be no way we could find an excuse to laugh at other ppl's mersiy. One day there will be an excuse to steal things oh wait there already are sport riots
PepsiMonster- That is exactly my point! I would think in times like this you would want new bnssueis, more bnssueis but that email response definitely doesn't show that. And of course your servers are going to tell you a different story!catty- you are right it situations as horrible as this it is best to just laugh, i did more of the get angry when we left than laughed but next time =).LAEasyMeals- yeah the power of the internet is underestimated by some bnssueises. She would have been smart to consider that I wrote to her rather than Yelped but now I yelped and tweeted and blogged! I hope word gets out that Xiomara is no place to spend your money!
A few things we've itonced with this. First, we use this in order to segregate our large reports to a single server. This lets us restrict most of our report servers to 10MB, which handles 95% of the traffic just fine. The other 5% is segregated to a specific server which is set with a 300MB limit.1) The Report Scheduler in InfoView allows you to specify a server group to run the report against.2) When the report is opened in DocumentViewer, it passes through the report server again. The schedule settings do not kick in at this point, only the Process tab settings. So, if your users are opening the report and attempting to use the Save to my computer as function, you'd better have the server group specified on the Process tab.3) If you open an instance of the report, whether the latest instance using View Latest Instance or a previous instance from History, even the Process tab settings are ignored. It just uses a random server. If you can tell me how to fix this behavior, I'd be most grateful.4) You cannot specify a server group for Xcelsius dashboards running through BOXI.
Great paper with really good ihnigst. It takes a lot of planning to decide what configurations to go with for even for the most basic servers. is definitely some advice that I wish I had had before setting up The tables had good information, but I wonder how a uniform look for them would affect the presentation. I think that the money saved is a fair argument to run Linux over MS, but I'm curious exactly what you mean by efficiency . Are you speaking to the software efficiency and its need for less resources or the efficiency of command line over GUI? I could spot you the software efficiency, but I'd have to argue the efficiency of a command line vs GUI.Some misspellings/grammar issues:5th line, 1st para: very should be vary 1st line, 4th para: bellow should be below 1st line, 5th para: fare should be fair 3rd line, 5th para: effieciency should be efficiency4th line, 7 para: it's should be its (no apostrophe to show possession for it )There should be a colon instead of a period after the first sentence of your last paragraph.
I like how your paper is written. It is clean and well pnreeetsd. Good tables although I’m not sure if they were the right one’s that the teacher was asking for although the instructions were pretty hard to understand.I don’t know if it’s just the GUI that makes Windows so bloated, because Linux desktop has a GUI and it does pretty well with the resources it’s just Microsoft attempting to dumb down the O.S so more people can effectively use it. I also wouldn’t say that Linux is well worth the money saved… It’d be worth that money spent again. But I do think that linux is very misunderstood and because of that people are afraid of it. If an organization gets the right person to administrate their Linux servers they will be able to do anything a windows server can do without the MS crap do deal withAbout that NAS system, I wouldn’t even think about using one of those except for the fact that it would be running Linux because at a previous employer they had a NAS that they waiting WAY to long to get off of. It was a cheap solution to a problem they had at the time but it didn’t scale well at all. It got to the point where if we copied a file larger than 75 Mb it would bring the network down to a crawl. It was awesome. It was running Windows but I really don’t think it was a Windows problem we believed it was more of a hardware issue.
1 ; 2 ; 3 ; 4 ; 5 ; 6 ; 7 ; 8 ; 9 ; 10 ; 11 ; 12 ; 13

Email: (Kept private)
Post your comment here!

:) :O ;) :( 8-) :$ :P :@ (6) :| :'( 8) :S :D
Enter Verification Code: