For businesses

Cloud backup for a small business that needs to recover its work

NordenVault provides European storage, S3-compatible access and a dashboard for backup sources and files. Connect the right tool for each workload, decide how much history to keep and prove that you can restore the data your business needs.

Start with what your business must recover

List the data that keeps you operating: client documents, project files, database exports, configuration and records held on individual computers. Name an owner for each source. Identify files kept in other cloud services, and confirm whether you need a separate export or a specialist backup product for them.

For each source, agree how much recent work you could afford to lose and how long recovery could take. For example, a daily document backup may suit one team, while a transactional database may need more frequent exports or continuous recovery tooling. These are workload decisions, not promises made by buying storage.

The UK NCSC backup guidance recommends keeping copies of important business data and checking that you can restore them. Use that basic test for every source you add.

Match the backup method to the workload

WorkloadStarting pointRecovery test
Working documentsDesktop folder uploads or restic snapshots.Restore a required file and an older edit if history matters.
File server or NASA supported S3 backup tool configured on that system.Restore a representative directory and check permissions separately.
PostgreSQL or MySQLA consistent database export or native backup, then offsite storage.Import into an isolated test database and check application access.
Virtual machines or KubernetesWorkload-aware backup software using compatible storage.Rebuild the application and its dependencies in a test environment.

Use the individual guides for PostgreSQL, MySQL, file servers, Kubernetes and Veeam. Compatibility with an S3 API is only one requirement; check the backup application’s version and storage requirements too.

Set up a source with controlled credentials

Create a named backup source for each workload, then configure its credentials in your backup software. Keep a record of the machine, owner, tool, destination and expected schedule. Use separate credentials where supported so that one machine’s access can be rotated or revoked independently.

Store credentials in the operating system’s protected credential facilities or a restricted configuration file. Limit who can change backup jobs, delete stored data or change retention. Keep recovery instructions and encryption passwords available to an authorised person who can act if the usual administrator is absent.

Keep history that matches your recovery needs

A copy of the latest files and a history of previous states solve different problems. Snapshot retention, object versioning and object-lock policies are separate controls. Confirm how each one behaves in your chosen configuration, including who can delete data and what happens when a subscription or machine is removed.

Before enabling cleanup, create a test file, change it, back it up again and recover the required earlier state. If you need immutability, ask for the exact protection mode and test its behaviour. We do not claim that a standard storage subscription automatically makes every backup ransomware-proof.

Monitor completion and run recovery exercises

Record failed jobs and missed schedules, and assign someone to follow up. Check the backup tool’s result as well as the storage dashboard: seeing objects in a bucket does not establish that an application-consistent job completed successfully. Restic can create a partial snapshot when some source files are unreadable, so the exit code matters.

Run a documented recovery exercise with a sample that represents the real workload. Time the recovery, open the restored files and check dependencies such as database credentials and application configuration. Keep an independent copy or recovery route for especially important data.

Include sharing and data processing in the decision

NordenVault can also provide controlled file-sharing links for client delivery. Keep the sharing workflow separate from backup administration. A person who needs to deliver a finished file should not receive a backup repository password for that purpose.

Review the data-residency details, supporting services and data processing agreement. Select a plan for the capacity, users and sources you actually need. Begin the trial with one representative workload and a successful restore before moving the remaining sources.