Thursday 2 April 2020
Found performance issues at our service provider. Reduced performance and/or inability to log in.
11:15 - Solved - No more peculiarities observed in the monitoring. vPlan performance is stable again.
10:15 - Update - Chronicle is fully running again so events in vPlan are shown again. The performance is closely monitored.
09:40 - Update - vPlan can be used again. Attention: There is still a disturbance with Chronicle at the moment, so logging of events will not be shown.
09:11 - Investigation -Start investigation for cause and solution.
09:08 - Report - Check performance issues with our service provider.
Wednesday 15 January 2020
We experience a problem with Cluster 1. Customers who are in this cluster experience problems with login and performance.
19:55 - Solved - vPlan is fully available again.
19:23 - Update - Backups are read again.
17:23 - Update - vPlan is completely down. Backup is now running and will be restored.
16:22 - Update - The situation is still unchanged. We are still working on repairs for cluster 1.
15:18 - Update - We are still working on repairs for cluster 1.
14:15 - Update - From now on there will be an hourly update every hour.
14:10 - Update - A plan of action has been made. All clusters will go down around 17:00. vPlan will not be available at that time. At that time a full backup will be made and the problem will be solved. Cluster 1 stays down for now.
13:40 - Update - A backup will be made of Cluster 1.
13:30 - Identified - The problem is known. One cluster (out of a total of 3 clusters) has a problem
13:12 - Research - Problem is inventoried and investigated
13:10 - Notification - The first notification comes in of problems with logging in.
Tuesday 10 September 2019 and Wednesday 11 September 2019
There are performance and login problems. After lengthy research, it appears that there is a broken server layer in our data center. After acting quickly, we were able to solve the problem at 05.15 on Wednesday. More info will follow.
05:15 - Solved - Everything has been tested and is working properly again.
04:50 - Update - vPlan is back at the right speed.
04:37 - Update - vPlan is back on the air, but with a delay which was also expected.
24:00 - Update -
23:28 - Update - We make steps. The recovery action is running according to schedule. This is the last update for today. We will continue working tonight to make sure everything is up and running tomorrow morning.
21:40 - Update - We are still experiencing some inconvenience, but we are busy rolling out the solution.
20:33 - Update - The copy action will last a bit longer. We still assume to be up and running tomorrow morning.
18:03 - Update - The recovery action is still on schedule.
16:26 - Update - The recovery action continues tonight and tonight. We assume we will be up and running tomorrow morning. The next update will be at 18:00.
16:00 - Update - As expected the copy action is still running. After this the server will be redesigned.
15:19 - Update - The copy action is still running and is expected to take another 1.5 hours.
14:47 - Update - We are currently working on a copy action to a new environment.
14:09 - Update - The situation has not changed yet. We are currently implementing a new solution.
13:27 - Update - We are still working on repairs.
13:01 - Update - The restoration work is still ongoing. Unfortunately we are not able to specify a new turnaround time yet.
12:28 - Update - Unfortunately we are still working on repairs. We hope to come up with new information about lead times soon.
11:58 - Update - We are still trying to work with manpower on the solution. The turnaround time of the repairs is taking longer than expected. We will keep you informed every half hour.
11:39 - Update - We are still working on repairs.
11:05 - Update - We are currently repairing our servers.
10:31 - Update - Unfortunately vPlan is not yet available. As expected this will take all morning.
10:01 - Update - The expectation is unchanged. We are in the process of excluding causes, which brings us to the actual problem. That is why vPlan is currently not available.
09:28 - Update - There is a failure in our data center. Together with our hosting provider we are conducting further investigation. The expectation is that the failure will unfortunately continue throughout the morning.
08:56 - Update - vPlan is still experiencing problems. We are in the process of finding out what the problem is. We will keep you informed every half hour.
08:24 - Update - We are currently investigating the cause.
08:16 - Monitoring - There are performance issues. vPlan is available but can react slowly to actions.
Monday 09 September 2019
vPlan has had limited availability. Users have problems logging in and performance.
18:56 - Solved - The problem is solved. Users can login again. Any messages in the queue will be processed.
17:51 - Identified - The problem has been found and is now being resolved.
16:04 - Research - vPlan is hard to reach. Users experience problems logging in.