SnapManager for SQL databases already on LUNs

GRIMSTONER — Wed, 04 Jun 2025 21:46:58 GMT

We've never used SnapManager before, but have setup our SQL server's LUNs as per NetApp best practice. So, all our databases and transaction logs currently reside on LUNs.

During the SnapManager for SQL install, we're prompted to link databases with LUNs in order to be migrated. When I got to this step, I didn't need to configure anything, and it seems that SnapManager automatically picked up this mapping.

As part of the last step, I had to specify whether the SnapManager for SQL configuration wizard will delete the databases where it was moved from. I've disabled this option.

What is going to happen if I continue with the configuration wizard? Will copies of the DB's be made in it's current location (on the LUN)? Or will SnapManager just start managing these databases?

Re: SnapManager for SQL databases already on LUNs

GRIMSTONER — Fri, 18 Mar 2016 23:32:56 GMT

FYI...

Simulated this, and this is one of the lines in the report:

[DB] There is no change for SQL Server user database.
[DB] There is no change for SQL Server system database.

So its safe to run.

topic SnapManager for SQL databases already on LUNs in Data Protection

SnapManager for SQL databases already on LUNs

Re: SnapManager for SQL databases already on LUNs