They have more time to focus on other problems. The support team is able to restore files quickly, 24/7, and it is less work for them. The continuous file versioning has helped to fix these problems pretty quickly.Ĭontinuous file versioning also makes it easier for our operations group. We haven't had any disasters that we've had to recover from but we've had three or four hardware failures a year that we've had to deal with. For us, OR and DR are pretty much the same thing. It is a similar process to the DR, although a little bit different. We have not had a problem with ransomware but if we did, we would be able to restore the data pretty quickly by going back to an older version of the file before the ransomware took over. Certainly, at this point, we have a lot of file versions. Right now, we have them stored forever, but we're trying to reign that in a little bit and keep them only for a period of time. Nasuni provides continuous file versioning and we take snapshots on a regular basis. People were then again using their local filer to connect. Once that ESX server was fixed, we were able to repoint everything back to it in a matter of minutes. We were able to quickly repoint all of the users to a backup filer that we have at our data center, they were back up and running within minutes, and they still have read-write capabilities. For example, we lost a controller the other day and all of the drives were corrupted. If a filer goes down, or an ESX server goes down, then we can quickly recover. The biggest and most impressive thing for us is the operational recovery (OR) and disaster recovery (DR) capabilities that Nasuni has. Overall, the continuous file versioning is really helpful. We were able to do this without any issues. We've had a few people delete things, or they have become corrupted, and we were able to get that file back to them in the states that it was in about five minutes before they had a problem. There is very little chance that the data is going to be done. If a user deletes a file or a file becomes corrupted, it's easy for them to get it restored. This report is something we created on our own to keep track of things. It gives us a quick view of everything and how much total we're using within Nasuni. It also tells us if the filer has been restarted and how long ago that happened. We keep track of that to make sure nothing is getting out of hand. We have a report that comes out three times a day that gives us the amount of data that's in the queue to be uploaded to Azure on each individual filer. The Nasuni filers are easy to manage, although the process is similar to what we had before. Now, with Nasuni, we're able to pretty much keep their experience seamless, no matter how much trouble the hardware is in at the site. It used to be a lot of trouble to bring data back up and a lot of the time, it was read-only, so the people couldn't use it very well. Previously, with the solutions we had, it would have taken weeks sometimes to get things fixed and back up and running for people. The OR and DR capabilities have been a very big help for us.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |