Disaster Recovery

What comes to mind when you think of a disaster? Think hurricanes, cyclones, tornadoes, wildfires, floods -the list goes on. Globally, we're seeing more of these events happen all the time. Any of these events can impact a data center's availability, so you're not immune to potential disruptions.

Note:

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

Data centers need a steady power supply and constant internet connection. Oracle NetSuite data centers have backup power and multiple internet connections. Even with these backups, they're not always enough in rare cases.

Disaster recovery (DR) is the plan for restoring your NetSuite account in a special data center.

Oracle NetSuite backs up your production account data multiple times daily. This backup process means that when disaster strikes, Oracle NetSuite can restore your account in the DR 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 DR plan and process get your NetSuite account up and running after it's been restored from a backup. Restoration time varies depending on your account's size and complexity.

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 purchase this service, you don't need to take any special actions in your production account -make sure you're following cloud best practices. By following these best practices, you'll be able to recover your account info quickly if needed. For more information, see Best Practices for Cloud Accounts.

The Premium Disaster Recovery Cloud Service uses extra tech and processes to quickly get your account back online. On top of our standard disaster recovery, the Premium service keeps a fresh copy of your account in a remote location. If a disruption happens, this account is ready to take over, so you're back up and running quickly.

There are some limits to what's covered by the Premium Disaster Recovery Cloud Service's RTO and RPO targets. For example:

Both plans cover your production account, but they don't cover other types of accounts. Accounts like sandboxes and development accounts aren't covered by disaster recovery plans.
Recovery starts immediately for all SuiteCommerce products, but the store's configuration affects how long it takes to be fully ready. Things like the number of items and site complexity impact how long it takes for your store to be available.

If Oracle NetSuite activates the Premium Disaster Recovery Cloud Service, you're all set -simply log in as usual when the RTO is met. Your account's performance might be slower than usual 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).

Note:

Custom maintenance domains are not supported during a disaster recovery event. In such cases, the standard NetSuite maintenance pages will be displayed to the shoppers.

General Notices