Infor SyteLine4 min readNetray Engineering Team

How to Set Up Database Backup Automation in SyteLine

SyteLine databases running on SQL Server require automated backup strategies to protect against data loss, corruption, and disaster scenarios. Without proper backup automation, a single hardware failure or ransomware attack can destroy years of manufacturing data including customer orders, inventory records, and financial transactions. This guide covers configuring SQL Server maintenance plans for SyteLine, managing transaction log growth, and implementing a tested disaster recovery procedure.

Configuring SQL Server Maintenance Plans for SyteLine

Create a SQL Server Maintenance Plan in SQL Server Management Studio (SSMS) targeting the SyteLine application database and the SyteLineFormsDB database. Schedule full backups nightly at a low-activity window—typically 1:00-3:00 AM—and differential backups every 4 hours during business operations. Store backups on a dedicated backup volume separate from the database drives, and configure a secondary copy to network-attached storage or cloud storage for offsite protection. The maintenance plan should also include index reorganization and statistics updates to maintain query performance.

  • Create a maintenance plan in SSMS targeting both the SyteLine application database and SyteLineFormsDB for comprehensive coverage
  • Schedule full database backups nightly with COMPRESSION and CHECKSUM options to reduce storage by 60-70% and verify integrity
  • Configure differential backups every 4 hours to minimize data loss exposure to a maximum 4-hour recovery point objective
  • Set backup retention to 14 days on local storage and 90 days on offsite storage to meet SOX and regulatory requirements

Managing Transaction Log Backups and Growth

SyteLine databases in Full Recovery mode generate transaction logs that grow continuously until backed up. Without regular transaction log backups, the log file can consume all available disk space and halt the SyteLine application server. Configure transaction log backups every 15-30 minutes to maintain a tight Recovery Point Objective (RPO) and prevent log file bloat. Monitor log file size through SQL Server Agent alerts configured to trigger when the log reaches 80% of its maximum configured size.

  • Schedule transaction log backups every 15 minutes for production databases to achieve a 15-minute RPO for disaster recovery
  • Set SQL Server Agent alerts to notify administrators when transaction log usage exceeds 80% of the configured maximum size
  • Configure auto-growth for log files in 1GB increments with a maximum size cap to prevent runaway disk consumption
  • Run DBCC SQLPERF(LOGSPACE) weekly to monitor log space utilization trends and adjust backup frequency accordingly

Disaster Recovery Testing and Restore Procedures

A backup strategy is only as reliable as its last successful restore test. Schedule quarterly disaster recovery drills that restore the SyteLine database to a separate SQL Server instance and verify application functionality. Document the restore procedure including the sequence of full backup, differential backup, and transaction log restores needed to recover to a specific point in time. Maintain a runbook accessible to all database administrators with step-by-step instructions, estimated recovery times, and escalation contacts.

  • Perform quarterly restore tests to a non-production SQL Server instance and validate SyteLine application connectivity and data integrity
  • Document point-in-time recovery procedures using RESTORE DATABASE WITH NORECOVERY followed by sequential log restores
  • Target a Recovery Time Objective (RTO) of 4 hours or less for full database restoration including application server reconfiguration
  • Store the disaster recovery runbook in a location accessible outside the SyteLine infrastructure—cloud storage or printed hard copy

Frequently Asked Questions

How large are typical SyteLine database backups?

SyteLine database sizes vary widely based on transaction volume and history retention. A mid-size manufacturer with 5 years of data typically has a 20-80 GB database. With SQL Server backup compression enabled, full backups compress to 30-40% of the original size. Expect 8-30 GB compressed backup files for most implementations, with differential backups ranging from 2-10 GB depending on daily transaction volume.

Should I back up the SyteLineFormsDB separately?

Yes, always include SyteLineFormsDB in your backup strategy. This database stores all custom form definitions, IDO extensions, and user interface modifications. Losing SyteLineFormsDB means recreating every customization from scratch, which can take weeks for heavily customized environments. Back it up on the same schedule as the main application database to ensure consistent recovery of both data and interface configurations.

Can I use Azure Backup for SyteLine databases?

Yes, SQL Server databases hosting SyteLine can use Azure Backup through the BACKUP TO URL syntax or the Azure Backup agent. Configure an Azure Storage account with a blob container for backup storage. Azure Backup provides geo-redundant storage, 99.99% availability, and automated retention management. For CloudSuite Industrial on Infor Cloud, backups are managed by Infor's cloud operations team with a standard 30-day retention policy.

Key Takeaways

  • 1Configuring SQL Server Maintenance Plans for SyteLine: Create a SQL Server Maintenance Plan in SQL Server Management Studio (SSMS) targeting the SyteLine application database and the SyteLineFormsDB database. Schedule full backups nightly at a low-activity window—typically 1:00-3:00 AM—and differential backups every 4 hours during business operations.
  • 2Managing Transaction Log Backups and Growth: SyteLine databases in Full Recovery mode generate transaction logs that grow continuously until backed up. Without regular transaction log backups, the log file can consume all available disk space and halt the SyteLine application server.
  • 3Disaster Recovery Testing and Restore Procedures: A backup strategy is only as reliable as its last successful restore test. Schedule quarterly disaster recovery drills that restore the SyteLine database to a separate SQL Server instance and verify application functionality.

Want automated backup monitoring for your SyteLine environment? Netray's infrastructure agents can configure alerts and validate your disaster recovery readiness.

Talk to an ExpertSee a Demo

Related Resources

Infor SyteLine

How to Configure the SyteLine Application Server

Configure the Infor SyteLine application server including IIS settings, IDO runtime configuration, connection pooling, and performance tuning for CloudSuite Industrial.

Infor SyteLine

How to Configure Performance Monitoring in SyteLine

Set up performance monitoring for Infor SyteLine including IDO request tracing, SQL query analysis, application server metrics, and user experience monitoring.

Infor SyteLine

How to Set Up Environment Promotion in SyteLine

Configure SyteLine environment promotion to migrate customizations, configurations, and data between development, test, and production environments safely.

Back to All Resources