# Sage X3 Maintenance Checklist: Schedule and Plan for Admins

> Source: https://netray.co/tools/sage-x3-maintenance-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A tick-box routine maintenance plan for Sage X3: database, batch server, Syracuse, backups, patches, security and testing.

## Category

other-erp

## Erp

Sage X3

## Audience

- X3 administrator
- IT manager
- ERP support

## Tool

**Kind:** checklist

**Scoring Note:** Tick tasks that are done and documented on your schedule. Critical items protect data and recovery. If any critical item is missing, fix it before spending time on the rest.

**Groups:**

#### Daily

**Items:**

**Text:** Confirm full or incremental database backup completed and the job log shows success

**Critical:** true

**Text:** Check that the X3 batch server and its task queue are running and no tasks are stuck

**Critical:** true

Review failed or aborted batch tasks and imports and restart or assign them

Check Syracuse web server and runtime services are up on every node

**Text:** Check free disk space on database, application, log and backup volumes

**Critical:** true

Review SQL Server or Oracle error logs for new errors

Scan the X3 trace and audit log for repeated errors

#### Weekly

**Items:**

**Text:** Run a test restore of the latest backup to a non-production server

**Critical:** true

Rebuild or reorganize fragmented indexes and update statistics on large tables

Review long-running queries and blocking sessions

Clear or archive old log, trace and temp files

Check locked users, orphan sessions and stuck locks on the application server

Review scheduled jobs for printing, interfaces and EDI

#### Monthly

**Items:**

**Text:** Review user accounts and remove or disable leavers and unused logins

**Critical:** true

Review roles and profiles for segregation-of-duties conflicts

Capacity check: database size growth, transaction log size, memory and CPU trend

**Text:** Verify backup retention meets policy and offsite or immutable copies exist

**Critical:** true

Review operating system and database security updates and plan installation

Check certificate expiry dates for Syracuse and integrations

Run period-end close checks with finance before month-end

#### Quarterly and yearly

**Items:**

**Text:** Review available Sage X3 patches and release notes against your version and support status

**Critical:** true

Apply patches in a test folder first, retest key processes, then schedule production

**Text:** Document and rehearse the disaster recovery restore, with timings

**Critical:** true

Review customizations and custom screens for upgrade impact

Archive or purge old transactional data per retention policy

Verify license and user counts against what is in use

Review the support contract and escalation contacts

#### Before and after any change

**Items:**

**Text:** Take a verified backup of the database and X3 folders immediately before the change

**Critical:** true

Record who changed what, when and why in a change log

Test in a non-production folder that mirrors production

Prepare a rollback plan and an agreed maintenance window

**Text:** Smoke test sales order, purchase receipt, work order and stock posting after the change

**Critical:** true

Notify users of the window and the result

## Content

**Intro:** A Sage X3 maintenance plan is mostly discipline: backups that restore, a batch server that keeps running, users that are cleaned up and patches that are tested before they reach production. This checklist turns that into a daily to yearly schedule you can print or export.

**Sections:**

#### How to use the checklist

**Body:** Work down the groups at the interval shown, ticking items you have done and documented. Export it to PDF or Excel to hand to whoever covers administration, and keep a dated copy as evidence for auditors. Items marked critical protect your ability to recover, so start there if you have limited time. Adjust frequency to your size: a single-site company may run weekly checks monthly, while a multi-site manufacturer should keep them as listed.

#### What a Sage X3 maintenance plan must cover

**Body:** An X3 platform has several layers: the relational database (SQL Server or Oracle), the application and runtime server, the batch server that processes queued tasks, the Syracuse web server with its supporting services, and the interfaces around it. Maintenance means watching each layer, keeping the database healthy, cleaning up access and testing recovery. Version support also matters, since older X3 versions leave mainstream support, so a yearly review of your version against the vendor's support status belongs in the plan.

#### Backup and recovery come first

**Body:** A backup you have never restored is a hope, not a control. Test a restore regularly to a separate server and time it, then compare the time to what the business can tolerate. Back up the database and the X3 folders on the application server, including custom code and configuration. Keep at least one copy offsite or immutable, since ransomware targets backup shares. Document which order to restore database, folders and services in your recovery runbook.

#### Patching, support and common mistakes

**Body:** Apply patches to a copy of production first, run your key business processes through it, then schedule production with a rollback plan. Common mistakes include patching production first, ignoring disk space until a batch stops, never removing leavers' accounts, tuning nothing until users complain, and relying on one person who knows how the system is run. If you outsource support, make sure the contract covers response times, who owns the schedule above and what is excluded.

**Cta:** If admin time goes into watching logs and answering routine data questions, we can add a private AI layer that summarizes system health and answers read-only X3 questions on your own infrastructure.

**Faq:**

#### How often should Sage X3 be maintained?

**Answer:** Check backups, batch server and disk space daily, restore tests and index upkeep weekly, user reviews and capacity monthly, and patching and disaster recovery drills quarterly or yearly. The checklist groups tasks by that rhythm so you can run it as a schedule.

#### What is the Sage X3 batch server?

**Answer:** It is the component that runs queued background tasks such as imports, scheduled jobs, printing and long processes. If it stops, those tasks queue up silently, so checking its status daily is a core maintenance task.

#### Should I patch Sage X3 as soon as a patch is released?

**Answer:** No. Read the release notes, apply the patch to a test folder that mirrors production, run your key business processes, and only then schedule production with a rollback plan. Urgent security fixes can be fast-tracked but still need a backup and a smoke test.

#### Do I need outside Sage X3 support?

**Answer:** It depends on your skills and size. In-house administrators can run this checklist, while smaller teams often use a partner for patching and troubleshooting. Whichever you choose, make sure someone owns the schedule and backups are tested.

## Search terms

sage x3 maintenance checklist, sage x3 maintenance schedule, sage x3 maintenance tips, sage x3 maintenance plan, sage x3 maintenance support, sage x3 administration checklist, sage x3 backup, sage x3 patch process

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json