What is the difference between POS and VSC? Which should I use?

Hello

Turns out we have a multitude of backup running for our virtual machine environment. We lack vCenter 6.0, 6.1 VDP, VSC 6.2P1, SnapManager for SQL and SnapMirror jobs put in place in OnCommand 3.1.2.

I go crazy trying to pierce the need to have all these products running of backups and snapmirroring data. Bottom line, our SnapMirrors for one or two Volumes take f o r e v e r... And that impacts my tests of SRM (when you use the replication of data).

I'm trying to clean up, he perfected down, consolidation, re-scheduling and friction on all these solutions. And in the middle of my panic, I thought that "these all do essentially the same thing? Taking snapshots and SnapMirroring data? »

So, my question to the community is, what is the difference between these solutions, or are they all essentially do the same thing? They confront each other, vying for the band width and stumbling on them to achieve the same thing? Right now my plan is to suspend all work of everything except VSC and SnapManager for SQL and do all this from VSC. This means suspend jobs in NetApp services.

I'm not the admin for POS, it is my co-worker, so he who installed independently of my work. Is it still necessary?

What brought me to all of this, besides the failure of MRS to transfer data (SnapMirror on request within a reasonable time) was noting the deltas for our work of snapshot is always huge at certain times of the day. For example, our biggest pork of data has a light snapshot at midnight, and he is constantly 71GB. This leads me to believe that this is a job, because it is predictable. The net effect is SnapMirror jobs take days, latency are several days and transfers has never really stop.

We plan to upgrade our pipe between our protected Site (HQ) and our DR Site (branch) of 50mbps at 100 Mbps. We have 100 out of our headquarters and 50 in our satellite TV right now, so we want to both be 100. Maybe that would solve the issue, but I still would be pretty effective.

If you need more information, let me know and I will fill you, or less make up something so I look like I know what I'm talking about.

TIA!

Steve

The reason why you do SnapMirror replication is DR. It is not a backup solution. If you stop all your SnapMirrors in OnCommand Unified Manager and your storage array, the production goes down, you no longer have a DR.

What does VSC is, it creates snapshots of your NetApp volumes, you can use for short term backup/recovery. The snapshots are not a real backup solution, however. If someone deletes a volume on the NetApp snapshots of this volume will not save you because they no longer exist. But they are still useful in many scenarios, such as Previous Versions of Microsoft CIFS options.

SnapManager aims to make consistent snapshots of demand for software such as MS SQL in your case. Instant database do not give you this ability, as they do not trigger the VSS suspension. More SnapManager for SQL gives you point in the ability to recover in time for your databases to SQL transaction logs, which provide none of the solutions above. However, as SnapManager creates snapshots, you must make sure that you have dedicated LUN for you SQL VM, otherwise you will be taking snapshots of the same volumes twice.

And now VDP makes backups of your environment. It supports long-term retention, as snapshots in general are not kept for more than one week or one month. Make sure that the data are stored on a separate volume from where are your virtual machines. Or ideally to a destination that is external to your storage group.

Hope that clears things up a bit. The result is, what you have is perfectly fine.

Tags: VMware

Similar Questions

Maybe you are looking for