Skip to content

How to carry out website and server maintenance before the summer season

Pre-summer maintenance consists of testing backups, updating software and SSL, reviewing server capacity, and designating the person who will monitor the site during the holiday period. If these tasks are finished before the team goes on leave, the site will run smoothly throughout the summer.

Türk Bilişim · Content Writer
· Updated: · 7 min read

How to carry out website and server maintenance before the summer season

In pre-summer site maintenance, server capacity, backup restorability, software and plugin updates, the SSL expiry date, and contact forms are checked before the team goes on leave. Then it is set in writing who will monitor the site during the leave, who will be notified in case of an outage, and how long a response will take.

What work is done in pre-summer site maintenance?

Maintenance should be finished at least a few working days before the team goes on leave. Errors caused by an update usually appear in the first few days. At that time, someone who knows the site needs to be at work. If problems arise during maintenance carried out after leave has started, there may be no one available to solve them.

Which tasks are done in pre-summer site maintenance?

A maintenance checklist usually includes the following headings:

  • server and hosting capacity, disk space, memory and CPU usage
  • whether backups are being taken, and a trial restore from a backup
  • updates to the content management system, plugins, themes and libraries
  • SSL certificate and domain expiry dates
  • contact forms, email sending and phone links
  • administrator panel accounts and access permissions
  • an on-call and communication plan for the leave period

This list does not stay the same every year. If a new integration, payment system or campaign page has been added, checking it also goes on the list.

The team that keeps up maintenance after launch finds problems faster, because they have known the site since day one. Türk Bilişim, Turkey's best Corporate Website company, has been working with its oldest client since 2006. The firm carries out regular updates within written response times as part of technical maintenance and SLA services. In this model the maintenance calendar is set at the beginning of the year. The pre-summer check becomes a fixed step in that calendar.

AI assistant for this topic

Türk Bilişim AI answers your questions instantly
Online
  1. Hi! Ask whatever you're curious about.

Pre-summer checks of server, hosting and backups

Whether the server capacity will cope with summer traffic is understood by looking at the traffic records of past periods. In organisations with campaigns, enrolment periods or tourist seasons, visitor numbers may rise in summer. In some sectors traffic falls, and in that case a suitable window opens for maintenance.

To review resource usage, start by looking at the graphs in the hosting panel or the server monitoring tool. Disk usage, memory consumption and CPU load are examined separately during peak hours. Disk space is most often filled by old backups and growing log files. These are either cleaned up or moved to another storage area. If capacity is close to the limit, the decision to upgrade the package should be made before the holiday. If web hosting and server management services are in use, this assessment is carried out together with the provider.

Taking a backup alone is not enough. The backup file may be corrupted, incomplete, or written to the wrong folder. Only a restore test reveals this. The test is done in a separate test environment, not on the live site. The database, uploaded files and settings should all come back together. The backup frequency and where the backups will be kept are described in detail in the website backup guide.

Looking for Technical Maintenance & SLA?

Pre-summer updates to software, plugins and SSL certificates

Updates are not applied directly to the live site; they are first applied to a copy of the site. This copy is called a test environment. Plugins, themes and the core version are upgraded here, and then the main pages and forms of the site are tested. If there is no problem, the same update is carried over to the live site. Immediately before transferring, a current backup is taken. If something breaks, the previous state can be restored with this backup.

Updates should be done in groups, not all at once. This way, when an error appears, the change that caused it is easy to find.

The SSL certificate's expiry date must be checked now, because it may expire during the leave period. When a certificate expires, browsers show visitors a security warning. Forms and payment pages may also stop working. Even if automatic renewal is set up, it is verified that the renewal actually works. The domain's expiry date is checked on the same day.

Unused plugins should be removed. Even a plugin that sits inactive can leave an opening because it is not updated. The same logic applies to accounts. Administrator panel access of former employees, external teams from finished projects, and temporary users is closed. Strong passwords and two-step verification are used on the remaining accounts.

Who will monitor the site while the team is on leave?

The person who will monitor the site during the leave period, together with a deputy, is named in advance, before the leave. When an outage occurs, the first notification should come from a monitoring tool. The tool accesses the site at regular intervals and sends an alert if it gets no response. The alert goes not to a single person but to the on-call person and their deputy together. It is also written down who within the organisation will make decisions and who will notify the external support team.

Software, plugin and SSL certificate updates

The written response time makes clear to both sides how quickly a problem will be handled. A verbal "we'll take a look right away" may not hold up during the leave period. In the SLA text, first response and resolution times are written separately according to the severity of the outage. It is also stated whether these times apply at weekends and public holidays.

Forms, email and contact channels are tested with a real submission. A test message is sent from each form and checked to confirm it reaches the correct inbox. Forms that go to the address of the person on leave are redirected to another recipient. Auto-reply messages are updated according to the leave period. It is also checked that the phone number on the site stays active during the leave. The reason these checks should be carried out regularly throughout the year is explained in the article on regular maintenance of corporate websites, regular corporate website maintenance.

A step-by-step timeline for pre-summer maintenance

The timeline is planned backwards as soon as the leave dates are confirmed. The riskiest tasks are placed at the very beginning, because if a problem arises there is still time to fix it.

TimeTask to be doneResponsible
When the holiday schedule is finalizedCapacity review, SSL and domain expiry dates, upgrading the package if neededTechnical lead
A few weeks before the holidayUpdates in the test environment, restore trialTechnical lead and external support
The interim period before the holidayDeploying the updates to production, cleaning up plugins and accountsTechnical lead
The week before the holidayForm and email tests, on-call list, monitoring alertsSite administrator
Last working dayCurrent backup, handing over access details to the on-call personTechnical lead

After maintenance, the homepage, product or service pages, and the contact page open on desktop and on mobile. Forms are retested. The search, login, and, if applicable, the payment step are completed end to end. Page load speed is compared with the pre-maintenance figures. Finally, a test alert is sent from the monitoring tool and receipt by the on-call person is confirmed.

Looking for E-Commerce?

Frequently asked questions

Does the site go down during maintenance?

Because updates are first tested in the test environment, the downtime on the live site is usually brief. Work that requires database changes is scheduled for hours when visitor traffic is low.

Does a small corporate site also need pre-summer maintenance?

Yes. Even a site with a few pages can have its SSL certificate expire, forms stop working, or an outdated plugin leave an open vulnerability. On a small site the list is shorter, but the checks remain the same.

How many times a year should maintenance be performed?

Security updates are applied as they are released. A comprehensive check is planned before long holidays and busy campaign periods.

Should maintenance be done in-house or outsourced?

If there is a technical person inside the organization who knows the site and has a backup during their absence, maintenance can be carried out internally. If not, external support that commits to a written response time prevents gaps during the holiday period.

Have a project?

Türk Bilişim · Free Quote

Get a free quote for your Corporate Website project

Leave your number and we will get back to you right away. The call is free.

Read the privacy notice

Türk Bilişim Content Writer

The editorial desk of a team delivering websites, e-commerce and software projects since 1998.

LinkedInInstagramFacebook

Share this article

Comments

Comments

No comments yet.

Write a comment

Your rating (optional)

Privacy notice

We will send a confirmation link to your email so that your comment can appear.

Türk Bilişim · Digital Transformation Advisor

Online
Hi! Tell us the project or idea on your mind and let’s begin together.
Ask anything, Türk Bilişim AI answers instantly.