The Eclipse Systems team has certified the following tools for backups of the Eclipse infrastructure.
Supported Backup Methods
|Supported Platforms||Linux, Windows||Linux, Windows||AIX, Linux, Windows|
|Backup Type||Disk, network||Disk||Tape|
|Backup Method||Byte pattern differential||Full||Full|
|On-Site Backup||Yes, ABS Local Backup||Yes||Yes|
|Off-Site Backups||Yes, ABS Online Backup||N/A||N/A|
|Off-Site Backup Location||Epicor Data Center||N/A||N/A|
|Off-Site Failover Hosting||Yes, ABS Failover Hosting||N/A||No|
|Off-Site Data Retention||> 30 Days||N/A||N/A|
|Proactive Monitoring||Yes, ABS Monitoring||No||No|
|Average RPO||24 hours||24 hours||24 hours|
|Average RTO||4-8 hours||1 hour||4-8 hours|
|Certified by Eclipse||Yes||Yes, when using RDX type disk cartridges attached to a physical server||Yes|
Please contact your inside sales representative for more information and pricing. RTO and RPO are dependent upon a number of factors, including the amount of data being backed up and available bandwidth.
Other Backup Methods
For Eclipse customers wishing to use an alternate, non-supported backup method, here are a few guidelines:
- All backup support (i.e. installation, configuration, monitoring and file restores) will be the responsibility of the customer. All service requests related to non-supported backup software will be billable.
- The Eclipse database backup is not “valid” unless the database is suspended and/or there is absolutely no activity taking place.
- Storage-level (i.e. LVM, filesystem, SAN) snapshots can be combined with database suspension to provide a “valid” backup source for active servers.
- The backup job should include the important Eclipse data files.