.svg)
AcroBackup for NetSuite: Enterprise-Level Continuous Off-Site Oracle NetSuite Backups
Many of the finance teams we talk to already have a backup process. It is usually someone exporting saved searches to spreadsheets on a schedule that slips. AcroBackup for NetSuite, our continuous backup service, replaces that with a daily, automated, off-site copy of your business records, held on the DBVault platform in relational format with the relationships between them intact, so a deleted invoice or a mass update gone wrong can be found and recovered rather than reconstructed. It also means your organisation holds an independent, off-site copy of its own records that it owns, can query and can export, and that does not depend on its access to the account.
How continuous NetSuite backup works
Implementation begins with account mapping and one full backup, which together take two to three weeks depending on the size of the account. From that point the service runs on incremental capture: each day it identifies what changed in NetSuite and writes only those changes to the off-site copy. Capturing deltas rather than repeating a full export is what allows the backup to run daily, without the long extraction windows that make manual backups slip.
The copy is a relational database, not a folder of files, and every record is indexed. That indexing is what makes recovery selective: your team can locate an individual customer, invoice or custom record as it stood on a given day and export it, instead of restoring a bulk archive and searching it afterwards.
.png)
Record-Level Recovery
Encryption In Transit & At Rest
.png)
Encrypted AWS Infrastructure
Daily Incremental Capture
Data Retention & Compliance
Vendor Independence
What the daily copy protects you from
The events that cost finance teams time are rarely dramatic. A mass update writes the wrong value across thousands of records. A user with
delete permission removes a transaction that closed a period. An integration reposts and duplicates a month of activity. In each case the
question is the same: what did this record look like before, and can we prove it? A daily off-site copy answers that from your own data
rather than from a support ticket, and it does so for records, sublists, custom fields and File Cabinet content alike.
Your continuity does not rest on a single system, either. If access to the account itself is interrupted, whether by a lapsed
subscription, a change of administrator, a lockout or an incident on the platform, your finance team is not paralysed. It can still
query, export and prove its financial position from the independent copy held for it on DBVault, on AWS.
Where your backup is held
The backup is held on the DBVault platform, which runs on Amazon Web Services with network isolation and encryption in transit and at rest. There is no on-premises installation. Where data residency is a requirement, the backup can be provisioned in a nominated AWS region so that records stay within a jurisdiction your legal or compliance team has approved. If your policy requires the data to sit on hardware you operate, this service is not the right fit.
DBVault Supports
.webp)
.png)
What is captured, and what is not
The backup covers transactional, entity and accounting records, together with File Cabinet content, sublists, custom records and custom fields. It does not capture metadata objects such as scripts, and workflows locked in the NetSuite interface cannot be backed up. Coverage is scoped to your production account. These boundaries are stated up front so that your team knows what the backup holds, and what it does not, before any request arrives.
Business records in full: customers, contacts, sales orders, invoices, leads and the custom records your account has accumulated over the years.
Hundreds of record relationships are preserved, including customers to contacts, invoices to customers and bill payments to vendors. A flat export loses the answer to any question that depends on how two records connect; a relational copy keeps it.
Your data stays portable. Snapshots are available to your own users, and records can be exported to CSV or taken as a MySQL database, so the copy remains useful whether or not you continue the subscription.
Sublists are kept intact, including addresses, line items, contacts and user notes, alongside File Cabinet content and the custom fields attached to standard records.
Why Choose Blueacrobat?
Experience with the difficult account
We have extracted and archived ERP data, most of it Oracle NetSuite, for HPE, Kimberly-Clark, Dropbox, Snapchat, NetApp and many others: long-lived instances, heavily customised accounts, multi-book and multi-subsidiary structures, and document stores that had to keep their folder structure. The case studies describe engagements of that kind in the reviewer's own words.
Verified against the source
A plausible row count is not treated as proof. Every extraction is compared with the source: record counts by type, financial totals,
referential integrity and field-level checks, then acceptance by your own users before sign-off. If people kept working in ERP during
the project, the delta is captured and verified again.
A fixed order of work
Map the account, extract, verify, user acceptance, then a delta where required. The sequence is the same on every engagement, which is
what lets a fixed shutdown date be planned against it, and what the service does not do is stated before the work starts: we do not
load data into a successor ERP, and the archive is read-only access to history, not a replacement for the application.
Assurance you can check
Blueacrobat is ISO/IEC 27001:2022 certified and SOC 2 Type II audited; the
Trust Centre describes the controls and how to obtain the certificate and the report. Every
engagement has a written scope and a named contact, and extraction runs with your own credentials, used read-only.
What recovery looks like, stated plainly
Two different things get called a restore, and it is worth settling which one you need before you buy.
Recovering records is what the service is built for. Because every record is indexed, an authorised user can search the off-site copy for the customer, invoice, journal or custom record in question, see it as it stood on a given day, and export it as CSV for re-entry or for handing to auditors. This is the case that comes up in practice.
Rebuilding an entire NetSuite account is a project, not a button. Full system restoration requires re-implementation of the account and manual re-importing of records. The service holds your data and hands it back in a usable form; it does not stand your instance back up for you. If your disaster recovery plan assumes a one-click restore of the whole environment, test that assumption against your NetSuite service agreement and your own recovery plan before you rely on it.
Questions we are usually asked
How often does the backup run?
.webp)
Daily. Implementation performs one full backup, and from then on the service captures the day's changes incrementally. The practical consequence is that the most recent day of activity is the exposure to plan around, which is the figure your continuity policy should be written against.
Can you restore our NetSuite account back to how it was?
Not as a single operation. Recovering individual records, sublists and files is what the service does well, and it does it selectively. Restoring a whole account is a re-implementation followed by manual re-import of records. We state this before an engagement rather than after, because it is the one expectation that most often goes unchecked internally.
Isn't our NetSuite data already protected by Oracle?
Oracle operates the NetSuite service, and the commitments that come with it are set out in your own service agreement; that document is the place to check what it covers. The distinction worth drawing is a different one. Platform resilience protects the service. It is not the same as your organisation holding an independent copy of its own records that you control, can query and can export. Most of what finance teams actually deal with are changes made inside the account by authorised users, such as a mass update, a deletion or a duplicated integration run.
What is not included in the backup?
Metadata objects such as scripts are not captured, and workflows locked in the NetSuite interface cannot be backed up. Coverage is scoped to your production account rather than sandboxes. File Cabinet content is backed up, but it is not hosted locally on your own infrastructure.
Where is our data held, and can we choose the region?
On Amazon Web Services, encrypted in transit and at rest, with network isolation. Where residency is a requirement, the backup can be provisioned in a nominated AWS region so records stay inside a jurisdiction your compliance team has approved. DBVault is cloud-only; there is no on-premises installation.
How is access controlled?
Single sign-on and multi-factor authentication are supported, with role-based permissions so that administrators and read-only viewers see different things, and IP-based restrictions where you want access limited to known networks. Blueacrobat is ISO/IEC 27001:2022 certified and undergoes an annual SOC 2 Type II examination; security and procurement teams can review the controls in our Trust Centre.
How long does implementation take, and what do you need from us?
Two to three weeks for account mapping and the initial full backup, depending on the size of the account. From you we need authorised access to the NetSuite account using credentials you control and can revoke, a named administrator for the vault, and a decision on which record types are in scope. The technical work is ours.
What determines the price?
Three things: the size of the NetSuite database, the size of the File Cabinet, and the number of users who need access. It is an annual subscription rather than a one-time purchase. Those figures come from a short sizing form, and a quote follows from it rather than from a list price, because accounts of the same nominal size differ widely once customisation is taken into account.
If we stop the subscription, do we lose the data?
Not if you take it with you. Snapshots are accessible to your own users throughout the subscription, and the records can be exported to CSV or taken as a MySQL database at any point. The hosted copy is not kept indefinitely after termination; our terms provide a window to download it, so plan the export before the end date.
We are switching NetSuite off rather than keeping it running. Is this the right service?
No, and the difference matters. Continuous backup protects a live account. If the account is being retired, migrated away from or allowed to lapse, the work is a one-time extraction into a permanent read-only archive. That is our AcroXtract service, and the resulting archive is hosted on the same DBVault platform. Archival is the larger part of what we do, and the two are often confused, so it is worth being sure which one your situation calls for.
Review your NetSuite backup position
Tell us the size of your NetSuite account, your File Cabinet, and how many people would need access. We will show you the vault working against data like yours, confirm what a recovery would involve in your situation, and return a quote.
.svg)
.svg)
.png)
.png)
