Backup
Protect your data from outages and ransomware, and recover in minutes
Bring back a deleted folder or a broken server from the same cloud portal you run your servers in, without opening a ticket. Your backups stay in Türkiye and are shielded from unauthorized deletion with locks and verified deletes.
Why now
- Tuesday morning, the files on the accounting server have new extensions and there is a ransom note on screen. Attackers go after backups first; if the backup itself can be deleted, you have nowhere to return to. Here, deleting a copy needs an emailed code, and nobody on the tenant side can touch a locked copy.
- Backups run every night, but nobody has ever tested a restore. When every test depends on a ticket and someone else's calendar, it simply doesn't happen, and a restore tried for the first time on the bad day rarely goes to plan. Here, opening a copy as a new server next to production takes a few clicks.
- An overnight patch left the application server unable to boot, and the contact center needs it at 8:30. The fastest way back is the last known good copy: pick the moment on the calendar and restore the server in place.
- Someone deleted a shared project folder by mistake, and nobody noticed for three days. Restoring the whole server would stop everyone else working; you only need that one folder back.
- The warranty on your backup server is ending, the disk array is full and the backup license is up for renewal. Taking backup as a service instead of buying the stack again turns that capital line into a monthly usage line.
What changes
| Today | With Nesnet |
|---|---|
| You open a ticket for a restore and wait in the queue. | You pick the copy, start the restore yourself and follow it in the portal's task list. |
| One lost file means restoring the whole server and stopping everyone. | Only the file or folder you need comes back; the server stays up and everyone keeps working. |
| A compromised admin account can wipe your backups too. | Deleting a copy needs a code sent to a verified address, deleted copies are held for a while, and locked copies can't be deleted at all. |
| You find out a backup has been failing for months on the day you need it. | Failed and overdue backups are flagged in red, and the status lands in your inbox with a daily report. |
| Backup server, storage, license and warranty renew on separate schedules. | Your invoice shows protected servers and backup storage used; maintaining the stack is Nesnet's job. |
From today to live: how it works
- 1
Discovery call
You and the Nesnet team agree which servers need protection, which need application-consistent backup and how far back you need to go. By the end of the call you have a class recommendation and the items that set the price.
- 2
Service enabled in your organization
Nesnet allocates your backup storage, binds the classes and enables restore rights; there is nothing for you to install. The backup menu then appears in your cloud portal.
- 3
Protect your servers
The first-run wizard verifies your notification address, then you pick a class and tick the servers to protect. You can add an auto-protect rule here so new servers are covered from day one.
- 4
First backup and a test restore
The wizard starts the first backup straight away. Once the copy is ready, you open it as a new server next to production and see exactly how a restore behaves in your environment.
- 5
Monitor and rehearse
The overview screen, email notifications and the daily report keep backup status in front of you. Repeating a test restore every so often makes the bad day feel like a routine.
What you get
Restore without a ticket
Restore rights are switched on when your organization is set up, so you pick the copy and start the restore yourself. Recovery time stops depending on the length of a support queue and starts depending on how quickly you click.
Protect servers in a few clicks
To protect a server you assign it to a backup class, and you can select many servers and assign them in one go. Changing class is a single action, and if the new assignment fails the server falls back to its previous class instead of going unprotected.
No server left unprotected
Define your own auto-protect rules and matching servers join the right class without waiting for a manual assignment. Whether a colleague's new server gets backed up no longer depends on someone remembering.
Back up on demand before risky changes
Right before a major update or configuration change, start a backup of a single server without waiting for the schedule. The server keeps running throughout, with only a very brief pause while the snapshot is taken.
Recover a single file or folder
Bring back just the files and folders you need from the chosen copy without restoring the whole server. The server stays up and users keep working; the only requirement is that guest tools were running when the backup was taken.
Test alongside production, then swap in
Open a copy as a brand-new server instead of overwriting the live one, and check the application works. Once you're sure, restore the original server in place from the same copy and remove the test server.
Roll a broken server back to its last good state
An in-place restore shuts the server down and replaces its disks with the copy you choose, and the interface warns you before it does. Instead of rebuilding a system that won't boot, you get back to yesterday's working state in a few steps.
Deleted servers keep their backups
Even if you delete a server in the portal, its backups stay listed for the full retention period. When a retired project's server is needed months later, you bring the right copy back as a new server.
Pick the right moment from a calendar
Copies are laid out on a calendar showing when each was taken, its size, its type and its lock status. Finding the copy from just before a problem started doesn't mean digging through log files.
Consistent backups for databases
In an application-consistent class, guest tools inside the server quiesce the application before the backup is taken (VSS on Windows). Systems like SQL Server and mail servers come back in a consistent state, not halfway through a transaction.
Lock important copies against deletion
Put a retention lock on a specific copy for a set number of days, and nobody on the tenant side can delete it while the lock holds. A copy needed for a year-end audit or a legal matter stays put even if the class's normal retention runs out.
Immutable retention
When you need a stricter rule, Nesnet enables an immutable retention lock on a class template on request. Once that lock is in place, the backup system refuses to lift it, and the copy stays exactly as it is until it expires.
Two layers against accidental and malicious deletes
Deleting a backup copy has to be confirmed with a short-lived code sent to your verified email address. Even a confirmed delete isn't applied immediately: the copy is held for a while and can be recovered from the recently deleted list.
See backup health at a glance
The overview screen shows how many servers you have, which are protected, which need attention and how much space is used, together with a seven-day backup health chart. When management asks whether the backups are sound, the answer is on one screen.
Per-server RPO history
The reports section summarizes each server's recovery point (RPO) over the last thirty days and highlights any row that missed its target in red. The evidence an auditor or your board asks for is ready without installing another tool.
Hear about problems first
You receive email notifications for completed backups, failed backups and quota warnings, and every tenant also gets a daily backup report. You can see backup status over your morning coffee without logging in.
See why it failed and retry from there
The workflow tab separates running, finished and failed jobs and refreshes on its own. A failed job shows its reason in the details, and you retry or cancel it right there without raising a ticket.
Know your backup space at all times
How much of your organization's backup quota is in use is always visible in the portal. When space runs low, the quota grows without touching existing backups or interrupting the service, and the storage line on your invoice matches the same gauge.
Protection follows moved servers
Move a server to another application unit inside the same resource area and its protection carries on. Reorganizing your environment doesn't mean checking server by server whether a backup fell off.
Backups scoped to your organization
Every screen and every action in the portal covers only your organization's servers and copies. Restores stay inside your own resource area, so a copy can never be opened in another organization's environment by mistake.
Why Nesnet
Backup lives next to your servers, in the same portal
Backup isn't a separate console; it sits inside the cloud portal where you create your servers. Nesnet wrote and runs the extension that makes this possible, so there is no second account, second password or extra backup screen to learn.
Your data stays in Türkiye
Your backups and the system that manages them never leave the country. Nesnet's infrastructure runs in the Equinix Istanbul (Dudullu) and Türk Telekom Ankara facilities, so the question of where your data sits has a clear answer.
Tenant isolation is tested, not assumed
No organization can list another organization's servers, copies or jobs, and every operation that changes something has a test that proves it. Tenants have no direct network path to the backup server; every request goes through Nesnet's broker service.
Nothing turns green without proof
The extension never shows a job as successful until it has seen it finish, and it never hides an error. When the backup system responds slowly, the screen tells you data is missing instead of quietly showing a partial picture.
Run by Nesnet, supported locally
The same Nesnet team builds and runs the backup software, the backup storage and the self-service extension. If something goes wrong, Nesnet’s support team helps you in Turkish or English.
A monthly invoice instead of upfront spend
Invoices are issued as e-invoices or e-archive invoices. The upfront spend on backup hardware turns into items on your monthly invoice.
Example scenarios
Back to a clean copy after ransomware
Situation
At a logistics company, documents on the file server were encrypted overnight. The attacker had taken over an admin password and also tried to delete the backups.
Outcome
The delete request went nowhere without the code sent to the verified email address, and the locked monthly copies couldn't be deleted anyway. The team first opened the pre-attack copy as a new server to confirm it was clean, then restored the file server from it.
Project files deleted from a shared folder
Situation
At an architecture practice, someone deleted a project folder on the file server by mistake, and it went unnoticed for three days. The rest of the server is fine and nobody wants it taken offline.
Outcome
The admin picked the copy from before the deletion on the calendar and restored just that folder at file level. The server never went down, everyone else kept working, and the job was followed in the portal's task list.
An application server that won't boot after patching
Situation
After an overnight OS update, a contact center's application server hangs at startup. The team isn't sure whether the update or another change is to blame.
Outcome
The team opened the pre-update copy as a new server and confirmed the application ran correctly. They then restored the original server in place from the same copy and removed the test server, with the system ready before the shift began.
A server retired months ago is needed again
Situation
A closed project's server had been deleted from the portal. A customer dispute means someone has to look at the records on it again.
Outcome
Because retention hadn't expired, the deleted server's copies were still listed. The admin brought the right copy back as a new server and removed it again once the records had been reviewed.
A locked copy for the year-end audit
Situation
Finance wants the December close copy kept until the external audit is finished. The class's normal retention period would expire before that.
Outcome
The admin placed a retention lock on that copy for the required number of days, so no tenant action can delete it. The auditor received a screenshot of the locked copy on the calendar along with the thirty-day RPO report.
Who does what
| Nesnet | You |
|---|---|
| Builds, runs, updates and expands the backup software and backup storage infrastructure. | Decide which server goes in which class and manage assignments and auto-protect rules. |
| Develops the self-service extension and maintains tenant isolation and cross-tenant access tests. | Verify and maintain the email address used for notifications and delete codes. |
| Defines backup classes and binds frequency, retention and consistency mode to each class. | Keep guest tools running on your servers for application-consistent backup and file-level restore. |
| Allocates backup storage, binds classes and enables restore rights when your organization is set up. | Follow up on failed and at-risk backups and test restores on a spare server from time to time. |
| Enables an immutable retention class on request and grows your quota without interrupting the service. | Decide which critical copies get a retention lock. |
Who it is for
IT teams running servers on Nesnet's cloud
Teams whose virtual servers already live on Nesnet's cloud and who want to manage backup from their own portal account. Protecting a server, starting a backup and restoring it all happen on one screen, with no one to wait for.
Organizations running databases and mail servers
Companies with write-heavy systems such as SQL Server, a mail server or an ERP database. These servers go into an application-consistent class, so a restored copy opens in a cleanly quiesced state.
Regulated and audited organizations
Finance, healthcare and public-sector suppliers that must keep a specific month-end or incident-day copy untouched. You lock the copy for a set number of days, and the lock status shows on the calendar.
Teams retiring their own backup stack
Small IT teams tired of backup servers, disk arrays, license renewals and tape rotation. Nesnet runs the backup software, the backup storage and their updates; your team only decides what gets protected and how.
Software teams with test environments
Teams that want fast-changing test servers protected too. Non-critical servers go into a less frequent class and production servers into a more frequent one, so cost tracks the value of what you protect.
May not be the right fit
If you need a different backup time and retention period for every single server, this service will feel narrow: frequency and retention come with classes Nesnet defines, and at most three classes are active per organization. In that case, running backup software on your own servers is the better fit.
If you want an up-to-date, ready-to-run copy of your on-premises servers waiting in Nesnet's cloud, look at Business Continuity; Backup keeps copies from past days.
Under the hood
An enterprise backup application takes and manages the backups; policies and the copy catalogue live in that software, while backup blocks are stored on the backup storage system it writes to. Backups use the virtualisation platform's standard snapshot mechanism, with guest tools inside the server quiescing the application in application-consistent classes (VSS on Windows). On top of that Nesnet added its own software: a plug-in installed in the cloud portal, which shows each tenant only its own VMs and copies, writes jobs into the portal's Recent Tasks and imports restored VMs into the tenant's inventory. Nesnet also operates a second backup platform; this page covers the self-service backup.
Building blocks
- Backup application
- backup policies, schedules and the copy catalogue
- Backup storage system
- storage that holds the backup blocks
- Cloud portal and API
- the tenant portal where the plug-in runs
- Nesnet backup plug-in
- the multi-tenant self-service layer: interface, broker service, portal extension
- Guest tools
- quiescing for application-consistent backups (VSS on Windows)
How it compares
| Option | When it is the right choice |
|---|---|
| Run backup software on your own servers | If you need a separate schedule or retention per VM, or an agent-based setup for a particular application, and you have a team to run it, this route is more flexible. Licences, storage, monitoring and restore testing then stay with your team. |
| Nesnet's second backup platform | Alongside the self-service backup on this page, Nesnet operates a separate backup platform with its own management console and its own operating model. If your current backup design is built on different backup software, talk to Nesnet about which of the two fits you. |
| Business Continuity | If the goal is not to keep past copies but to hold a continuously updated replica of your on-premises virtual servers in Nesnet's cloud, that is the right service. The two do not replace each other; in a quote each VM gets backup and continuity selected separately. |
Technical specifications
| Backup software | Enterprise backup software, tenant layer by Nesnet |
|---|---|
| Backup storage | Deduplicating backup storage (backup blocks); policies and catalogue in the backup software |
| Where you manage it | Plug-in installed in the cloud portal |
| Self-service layer | Plug-in written by Nesnet: portal UI, Go broker, service extension |
| Backup method | The virtualization platform's standard snapshot |
| Consistency mode | Crash-consistent or application-consistent (VSS / QGA via guest tools) |
|---|---|
| Class model | Frequency, retention and consistency set per class; tenant picks the class |
| Class limit | Up to 3 active classes per tenant; each VM in one class |
| During backup | VM keeps running; brief pause of under a second to a few seconds at snapshot |
| Moved VMs | Protection continues when a VM moves to another application unit in the same allocation |
| Scope | In place, as a new VM, file / folder level |
|---|---|
| File-level requirement | Guest tools running at backup time; file browsing may not work for encrypted VMs |
| Boundary | Within the same VDC; no restore to another VDC or tenant |
| Deleted VMs | Copies stay listed for the retention period; restored as a new VM |
| Expected duration | Up to 50 GB minutes, 50–500 GB tens of minutes, over 1 TB hours (depends on bandwidth; not a commitment) |
| Delete confirmation | 6-digit code to verified e-mail, valid 10 minutes |
|---|---|
| Deletion hold | 24 hours by default; recoverable from "Recently deleted" |
| GOVERNANCE lock | Set by the tenant for a number of days; locked copy cannot be deleted by tenant actions |
| COMPLIANCE lock | On a class template, enabled only by Nesnet; cannot be reverted |
| Backup quota | Per-tenant quota; "Used X / Y GB"; increases without interruption |
|---|---|
| Notifications | Quota warning, backup completed, backup failed |
| Daily report | Daily backup report e-mail per tenant |
| Data location | Türkiye; single region |
If something breaks
If a backup fails
The row turns red with a Failed status and the detail view shows the reason. You can retry from the same screen, and a backup-failed e-mail is sent as well.
If the last good backup gets too old
When a VM's last successful backup is older than one and a half times its class interval, the VM is flagged "At risk". Missed backups therefore do not pile up quietly; they show up under "needs attention" on the overview.
If backup storage fills up
Once the quota is full, new backups are refused and Nesnet is alerted, and you receive a quota warning by e-mail. The quota can be increased without affecting existing backups or interrupting the service.
If the backup server responds slowly
The panel does not wait forever. It opens with the data it has and says clearly which information is incomplete.
Frequently asked questions
Pricing and first steps
Pricing
Backup is billed monthly on usage, in two parts: a license for every protected server and a per-GB charge for the space used in backup storage. The price is set by the servers you protect and the items you choose, and Nesnet’s team prepares your quote.
What the price depends on
- Number of protected VMs: the licence is counted for every VM under protection.
- Space used in backup storage (GB): the "Used X / Y GB" gauge in the portal shows this figure at any time.
- Retention of the chosen class: the longer copies are kept, the more space they take.
- Retention locks: a locked copy cannot be deleted before its lock expires, so it keeps using space until then.
How to get started
- 1.Fill in the form or call 0800 606 1071.
- 2.We agree on servers and classes in one call and prepare a price.
- 3.The service goes live; you start the first backup and test a restore.
See your backup actually come back, today
Tell the Nesnet team which servers you want protected and in which class, and you'll hear back within the same business day. Once the service is on, you open your first copy next to production and watch the restore work for yourself.