Skip to main content

Backup Strategy Overview

A comprehensive backup strategy ensures business continuity, data integrity, and rapid recovery in case of system failures, data corruption, or cyber threats.

ServiceOps provides a robust backup management solution that helps organizations safeguard critical applications and databases against data loss, corruption, and cyber threats. With automated backup scheduling, secure storage options, and quick recovery procedures, businesses can minimize downtime and maintain operational efficiency.

This overview covers the essential components of a comprehensive backup strategy for ServiceOps deployments, including what to backup, when to backup, where to store backups, and how to ensure your backup strategy aligns with your business continuity requirements.

What to Backup​

Application Components

Your ServiceOps backup strategy should cover all critical application components:

  • Main Server: Core application files, libraries, configurations, and databases
  • Analytics Server: Analytics data, configurations, and filedb
  • File Server: File storage, configurations, and uploaded content
  • Chat Server: Chat service configurations and data
  • Plugin Server: Plugin configurations and customizations
  • Discovery Service: Discovery configurations and filedb
  • Frontend Application: Web interface files and configurations
  • Nginx: Web server configurations and SSL certificates
  • PostgreSQL Database: Complete database with all ITSM data
  • Configuration Files: System configurations, SSL certificates, and security settings

Critical Data Types

  • ITSM Data: Incidents, requests, changes, problems, releases, assets, projects
  • Configuration Data: Workflows, templates, custom fields, SLA policies
  • User Data: User accounts, permissions, authentication settings
  • Integration Data: API configurations, webhook settings, third-party connections
  • Audit Logs: System activity, security events, configuration changes

Backup Types and Frequency​

Database Backups

  • Frequency: Daily (recommended minimum)
  • Retention: 10-30 days (configurable 5-99 backups)
  • Storage Options: Local storage or FTP server
  • Format: PostgreSQL dump files (.sql or custom format)
note

Database backups are critical as they contain all your ITSM data, configurations, and user information.

Application Backups

  • Frequency: Weekly (or before major changes)
  • Retention: 4-12 weeks
  • Storage Options: Local storage or network storage
  • Components: All server directories, configurations, and application files

Configuration Backups

  • Frequency: Before any configuration changes
  • Retention: 6-12 months
  • Storage Options: Version control system or secure storage
  • Components: Configuration files, SSL certificates, custom scripts

Storage Strategy​

Local Storage

  • Pros: Fast access, no network dependency, immediate availability
  • Cons: Vulnerable to local disasters, limited redundancy
  • Best For: Short-term backups, development environments

Network Storage (FTP/SFTP)

  • Pros: Off-site protection, centralized management, scalable
  • Cons: Network dependency, potential bandwidth limitations
  • Best For: Production environments, disaster recovery

Cloud Storage

  • Pros: High availability, geographic redundancy, managed security
  • Cons: Ongoing costs, internet dependency
  • Best For: Enterprise deployments, compliance requirements

Backup Scheduling​

Automated Scheduling

ServiceOps supports automated backup scheduling with flexible options:

  • Once: Single backup at specified date/time
  • Daily: Automated daily backups at specified time
  • Weekly: Weekly backups on specified day and time
  • Monthly: Monthly backups on specified date and time

Recommended Schedule

For production environments:

  • Database: Daily at 2:00 AM
  • Application: Weekly on Sunday at 1:00 AM
  • Configuration: Before any system changes

Security Considerations​

Backup Encryption

  • Encrypt sensitive backup files
  • Use strong encryption algorithms
  • Secure encryption key management

Access Control

  • Limit backup access to authorized personnel
  • Implement role-based access controls
  • Audit backup access and modifications

Network Security

  • Use secure protocols (SFTP, HTTPS) for remote backups
  • Implement network segmentation for backup storage
  • Regular security assessments of backup systems

Testing and Validation​

Backup Verification

  • Regularly test backup restoration procedures
  • Verify backup file integrity and completeness
  • Document restoration procedures and timeframes

Recovery Testing

  • Perform full system recovery tests quarterly
  • Test partial data recovery scenarios
  • Validate recovery time objectives (RTO)

Monitoring and Maintenance​

Backup Monitoring

  • Monitor backup job success/failure rates
  • Track backup storage utilization
  • Alert on backup failures or storage issues

Maintenance Tasks

  • Regularly review and update backup retention policies
  • Clean up old backup files
  • Update backup procedures as system evolves

Disaster Recovery Planning​

Recovery Time Objectives (RTO)

  • Critical Systems: 4-8 hours
  • Non-Critical Systems: 24-48 hours
  • Data Recovery: 1-4 hours

Recovery Point Objectives (RPO)

  • Database: 24 hours maximum
  • Configuration: 1 week maximum
  • Application: 1 week maximum

Compliance and Governance​

Data Retention

  • Align backup retention with business requirements
  • Consider regulatory compliance needs
  • Document retention policies and procedures

Audit Requirements

  • Maintain backup audit logs
  • Document backup and recovery procedures
  • Regular compliance assessments

Best Practices​

Before Implementation

  1. Assess Requirements: Understand your business continuity needs
  2. Plan Storage: Design scalable backup storage architecture
  3. Test Procedures: Validate backup and recovery procedures
  4. Train Personnel: Ensure staff can execute backup procedures

Ongoing Operations

  1. Monitor Regularly: Check backup job status and storage usage
  2. Test Periodically: Validate backup integrity and recovery procedures
  3. Update Procedures: Keep backup procedures current with system changes
  4. Review Performance: Optimize backup schedules and storage usage

Documentation

  1. Maintain Procedures: Keep backup and recovery procedures current
  2. Update Contacts: Maintain current contact information for key personnel
  3. Review Annually: Annual review of backup strategy and procedures