Disaster Recovery

What does the word disaster mean to you? Hurricanes, cyclones, tornadoes, wildfires, floods, and more. Across the globe, these events seem to be occurring more frequently. Any of these events can affect the availability of a data center.

Note:

Oracle NetSuite decides what constitutes a disaster, at their sole discretion.

Data centers require a constant supply of electricity and continuous access to the internet. All Oracle NetSuite data centers have redundant power supplies, and multiple network paths to the internet. On rare occasions, these redundant systems are not enough.

Disaster recovery, or DR, refers to the plan and the process by which Oracle NetSuite restores your NetSuite production account in a designated disaster recovery data center.

Oracle NetSuite backs up the data in your production account multiple times each day. The backup data is replicated to a dedicated disaster recovery data center. This backup process ensures that when Oracle NetSuite enacts the disaster recovery plan, your production account can be restored in the DR data center.

The disaster recovery plan and process make your NetSuite production account available when the data has been restored from a backup archive. Exactly how long the restoration process takes for your production account varies, depending on the size and complexity of the account.

Note:

We often test our Disaster Recovery plan, or DR plan. However, declaring DR is a rare event. The DR plan is not enacted for short term service disruptions. During a service disruption event, Oracle NetSuite prioritizes data consistency. The preference is to recover the account in the existing data center whenever possible, especially when a disruption is not expected to last for long.

About Premium Disaster Recovery

Oracle NetSuite offers a Premium Disaster Recovery Cloud Service that provides enhanced Recovery Time and Recovery Point Objectives for your NetSuite production account. See Premium Disaster Recovery Cloud Service Guide.

For more information about the Premium Disaster Recovery Cloud Service, including term definitions and exclusions, go to the NetSuite Cloud Services – Service Descriptions page to access a PDF that contains detailed service descriptions for NetSuite Cloud Services.

If you choose to purchase this service, you do not need to take any special actions in your production account, other than to ensure that you are following the best practices for an account that operates in the cloud. Following the documented best practices supports the timely recovery of the information in your production account. For more information, see Best Practices for Cloud Accounts.

The Premium Disaster Recovery Cloud Service employs additional technology and processes to get your production account up and running quickly. In addition to our regular disaster recovery provisions, the Premium Disaster Recovery Cloud Service ensures that a frequently refreshed copy of your NetSuite production account exists in a remote site. In the event of a service disruption, this account is already in place and ready to take over.

Not everything is covered under the Premium Disaster Recovery Cloud Service RTO and RPO targets. For example:

Both the standard and Premium DR plans cover your NetSuite production account. Non-production accounts, such as sandboxes and development accounts, are not covered under disaster recovery plans.
The recovery process begins right away for all SuiteCommerce products, but the final service readiness depends on the configuration of the store. Factors such as item volume and site configuration complexity affect how long it may take for your store to be available.

In the rare event that Oracle NetSuite activates the Premium Disaster Recovery Cloud Service, all you need to do is log in to your NetSuite production account as usual when the promised Recovery Time Objective (RTO) has been met. You may experience some degradation in the performance of your production account during a disaster recovery event.

Note:

Oracle NetSuite decides what constitutes a disaster, at their sole discretion.

Standard DR	Premium DR Cloud Service
During normal operations: A backup archive exists at a remote site. The health of the backup archive is monitored. The backup archive is ready to restore a production account in the event that Disaster Recovery (DR) plans are enacted.	During normal operations: A backup database in a remote site is constantly updated. Transaction data is continuously synced to a backup database to support the Recovery Point Objective (RPO). The health and readiness of the backup database is constantly monitored and maintained. Any problems detected with the backup database are proactively remedied. This ensures that if recovery is needed, it can occur within the RPO and RTO. The backup database is always ready to take over in the event that Disaster Recovery plans are enacted.
During Disaster Recovery: Operations engineers follow the Cloud Event Response and Recovery Plan that corresponds to the event. Accounts are restored from backup archives, which can take several hours. As backups are not instantaneous, the transaction data in the restored account may lag behind the production account.	During Disaster Recovery: Operations engineers follow the Cloud Event Response and Recovery Plan that corresponds to the event. Production accounts are recovered by switching over to the remote backup database. The recovery occurs within the promised RTO. There is no need for Premium DR customers to wait for a restoration from a backup archive. The transaction data in the restored account is much more current, thanks to the continual updates to the backup database, enabling it to target the stated Recovery Point Objective (RPO).

Standard DR

Premium DR Cloud Service

During normal operations:

A backup archive exists at a remote site.
The health of the backup archive is monitored.
The backup archive is ready to restore a production account in the event that Disaster Recovery (DR) plans are enacted.

During normal operations:

A backup database in a remote site is constantly updated. Transaction data is continuously synced to a backup database to support the Recovery Point Objective (RPO).
The health and readiness of the backup database is constantly monitored and maintained. Any problems detected with the backup database are proactively remedied. This ensures that if recovery is needed, it can occur within the RPO and RTO.
The backup database is always ready to take over in the event that Disaster Recovery plans are enacted.

During Disaster Recovery:

Operations engineers follow the Cloud Event Response and Recovery Plan that corresponds to the event.
Accounts are restored from backup archives, which can take several hours.
As backups are not instantaneous, the transaction data in the restored account may lag behind the production account.

During Disaster Recovery:

Operations engineers follow the Cloud Event Response and Recovery Plan that corresponds to the event.
Production accounts are recovered by switching over to the remote backup database. The recovery occurs within the promised RTO. There is no need for Premium DR customers to wait for a restoration from a backup archive.
The transaction data in the restored account is much more current, thanks to the continual updates to the backup database, enabling it to target the stated Recovery Point Objective (RPO).

General Notices