eClips Scheduled Maintenance: Thursday May 15

What is being done?

Changes to the way that the MyArchive service works are being deployed to the eClips database.  These changes will mean that archives are created based on organisations within the database rather than the current method of users.

Implementing these changes requires an update to the database structure, therefore a short outage of the eClips system will occur during this maintenance work.

When will this happen?

Maintenance work will commence at 7PM on Thursday May 15. 

What is the impact on the service?

eClips will be unavailable for aproximately 10 minutes from 7PM

Note: A reminder will be sent to clients on Thursday May 15.

Emergency eClips Maintenance

Due to recent performance issues, emergency maintenance is required on the eClips IT infrastructure.

The eClips Service will be unavailable to clients for up to 30 minutes from 19:00.

FTP access for PCAs will be unavailable for approximately 10 minutes between 19:00 and 19:30.

All services will resume normal operation by 19:45.

Further notification will be sent when this maintenance has been completed.

Update on Wednesday, April 30, 2008 at 20:01 by Incident Management Team

The maintenance work has now been completed successfully.  All services are now operating normally.

NLA eClips Service Incident - Report

Problem:

The eClips Service experienced performance issues starting at 09:28 this morning.  The incident caused sporadic issues for some eClips users trying to view clippings until resolution occurred at 10:10.

Cause:

A corrupt PDF file was found to be the cause of the issue.  Clients attempting to access the file in question caused queuing of requests and therefore slowed down the service.

Solution:

A change to how PDF size is monitored is currently being implemented and also some changes to production processes will be put in place to ensure this issue does not occur again.

NLA eClips Service Incident - Report

Problem:

The primary eClips database became unavailable for approximately 20 minutes from 14:10 on 2nd April 2008. End users were unable to access cuttings during this time and were receiving a timeout message.

Cause:

An automated database growth operation took longer than expected. The growth operation is dynamic in nature and takes place when the database server requires more space to populate the database.

Solution:

To mitigate the risk of this happening again, a process will be put in place to ensure that database expansion is scheduled to occur only within the scheduled maintenance window.