What is your primary use case for NetApp SnapCenter?

The major use case for NetApp SnapCenter is that our customer previously used Commvault. For huge VMs with sizes of five TB or 10 TB, taking the file level backup in Commvault took a long time, often two or three days to complete that job. The customer migrated to NetApp SnapCenter with the same workload, and now those jobs are getting completed immediately. The positive impact from NetApp SnapCenter is significant. While Commvault took two to three days to complete jobs, especially with VM sizes above 8 TB or 10 TB, the same workload configured for NetApp SnapCenter completes in a few seconds. This process utilizes the basic NetApp feature called Snapshot, which takes a snapshot with specific schedules and creates a backup job. While Commvault works at the file level, NetApp SnapCenter works at the block level, which accounts for its speed.

I help my customers to install and integrate NetApp SnapCenter ( /products/netapp-snapcenter-reviews ). The solution is used for central consolidation of NetApp ( /products/netapp-41749-reviews ) devices and for snapshots and restore.

SnapCenter is a product for customers who want centralized management of their backup and recovery processes. Customers need application-aware backups, like Oracle Database and Microsoft SQL Server, or any application designed on the NetApp storage volume. So, if a customer uses VMware, this tool or software is centralized and installed on a separate system, server, or virtual machine. It connects to the NetApp service system on one side and to the application on the other. This gives customers the ease of managing everything from a central command and control, instead of using multiple tools to do the same job.

Our partner firm, an IT firm, was using NetApp SnapCenter for training and educational purposes. They were partnering with an organization to train staff.

We primarily use the solution for snapshots and for backups.

It's for storage. We sell a call center and voicemail solution and we store the recordings there. We also store the configuration file there. We use it for redundancy. We are using an HA proxy for redundancy so if one fails we can use another node.

Primary use case is covering fast backup and restore for customers, mostly for SQL databases, some Oracle database systems in servers, and some file share backups with Snapshots with the possibility of restore. SnapCenter is usually an additional software, which is not the main backup software. Most companies have already found a backup solution and are using SnapCenter to be able to do a fast restoration of their data. Therefore, they are using two solutions at once, side-by-side. Companies will have their primary backup solution and SnapCenter as a redundancy because the primary solution isn't favored to recover data so quickly.

Backing up SQL and Exchange is our primary use case.

We use it in our managed services for customers. We back up customer data from systems that we manage for them.

We are a NetApp partner. For our systems, we are using SnapCenter only for testing purposes. For customers, we started to install when it was SnapManager, quite some years ago. We have many installations with SnapManager and some installations with SnapCenter. We're at the stage of migrating from SnapManager to SnapCenter. Our customers primarily use SnapCenter for SQL Server and VMware.

We back up Microsoft SQL and Microsoft Exchange 2016.

We use it for VMware. We haven't integrated any of our SQL or Exchange solutions with SnapCenter. We haven't tested that yet. I think there is a plugin for Oracle but we haven't tested that either. The primary thing we have been using in SnapCenter is the ability to integrate with our ESXi environment. We have about 300 virtual machines, including virtual desktops. That's going to be increased to about 400 or 500, once the projects in the pipeline are rolled out.

Our primary use case is VM backup and our secondary use case is backup from all databases like SQL.

We're using it for Oracle and SQL, and we use it for backups and cloning.

It's used for backup and restoring of virtual machines from VMware. I have some experience with SnapCenter but only on the installation. I don't work directly with the end customers.

Our clients use it for backup and restore.

It is used for VMware and Microsoft SQL databases. We use it for ordinary backups. Nothing special.

We have a handful of customers constantly using it, mostly for SQL databases, while one of them uses it for VMware.

We use it for backup and for restore, primarily. It's really just for VMs. You can use it for other things, but we don't have other things to work with.

We use it as a backup solution.

We use SnapCenter for our VMware, SQL, and Oracle environments providing application-consistent and centralized backup and recovery from disasters, and cloning. It maximizes NetApp Snapshot, SnapMirror, SnapVault and cloning technology.

It's used as a backup and recovery software. Some of our clients are using the solution for private cloud primary backup.

The primary use case is for our backup strategy. We run almost all our backups over SnapCenter and we are migrating the rest.

We use it for Oracle, on the client side. In our company, we are mostly using SnapCenter software in our test environment. There are many customers using NetApp products, but most of them don't use SnapCenter software in their production environment. So we do not have a lot of experience with it in production systems. We are testing it in our data core environment and our test environment. We check the software's features and new features, and sometimes we do troubleshooting as well. We test VMware Snapshot, Hyper-V Snapshot, database Snapshots, for example, MS SQL and Oracle.

We use HANA Database for SMB. This is where we are using SnapCenter to manage all our Snapshots, backups, etc.

Our ERP structure is on the SnapCenter. We also keep on it SQL Servers, VMware products, etc.