Contact Us  |  Blog  |  Account  |  Support  |  DEMO

Cloud Backup with Nasuni

When you have a continuously versioning file system that automatically stores file changes as they occur directly in cloud storage, why do you need traditional file backup? You don’t.

Video Transcript

In a traditional file environment file backup is an expensive insurance policy that customers simply have to pay. If you experience inadvertent deletion or a malware attack you need copies to be able to restore from, but it involves application servers and media servers and tape, disk to disk, even off citing to Iron Mountain. It’s a lot to babysit and manage and nobody really likes doing it. In a Nasuni environment, file data protection is wildly different. Briefly on how it works when people write data to a Nasuni device we’re always capturing just the changes to data or any new data and continuously versioning that to the cloud. We’re deduping and compressing and encrypting along the way. We’re storing a version history in the cloud of how your data has changed over time. Now when we talk to customers about not needing to back up their files anymore people say, “Well why is that? You know, what safeguards have you put in place that I don’t have to be responsible for my own backup?” Nasuni provides granular restore so you can restore data on the folder or file level from the cloud whenever you need to. You don’t have to mount volumes or do any of that stuff that you do in a traditional sense. The cloud provides redundancy. In a traditional environment you’re making lots of copies yourself. In the cloud they spread your data out over server farms and data centers, fault domains and availability zones to make sure there are plenty of copies if any data were to be deleted or compromised in the cloud. We always send data to the cloud as a new object, so what we mean by that is we’re never changing history. If you make a change to a PowerPoint file – maybe just the title – we don’t go back to the original PowerPoint title and change it we represent just the bytes that comprise that title in a brand new version. That creates a very stable file system history for us to restore from and eliminates the possibility of file system corruption since never going back in time to change something. Lastly, users and applications cannot delete data directly from the cloud. They can certainly delete data from the local file system as part of their normal workflow, but we preserve that history in the cloud if it needs to be restored at any point in time. Now if you need to purge data from the cloud or delete it you can certainly implement our retention policies to do that we just make sure the users can’t do it themselves right away, protection. So in terms of a Nasuni file environment the big takeaway is you don’t have to run a legacy backup application against a Nasuni device to protect that data, nor do you have to get involved with backup services in the cloud to protect your cloud data either. Nasuni has it covered.