We are running a MS SQL server with several different databases each placed on a separate LUN. That means: there are 6 DBs, for each we have a DB-LUN and a LOG-LUN, sums up to 12 LUNs plus a single SnapInfo-LUN.
The LUNs were mounted by mountpoints.
Now all of a sudden SMSQL complains during the full backup of one DB:
[19:50:14.334] Getting SnapInfo directory info...
[19:50:14.334] Failed to get SnapInfo directory from registry, please re-run the Configuration Wizard.
'til then the structure in the SnapInfo was very clear and readable:
and underneath an entry for each DB:
Because the error message was so clear I re-run the config wizard, but now we got an additional directory in the SnapInfo:
and in this directory a subdir
Backup is working now, but the funny thing is, that now SMSQL remembers the old SnapInfo location:
[09:56:41.979] SnapManager finds an alternative snapinfo directory for database [IQSCAQ] of [ServerName] at:
[09:56:41.979] Renaming alternative snapinfo directory...
The Question is:
how do I get rid of the newly created SnapInfo directory "VDISK__MountPoint-001" and tell SMSQL to store its data in the former and proper named directory E:\snapinfo\SMSQL_SnapInfo\SQL__ServerName\DB__IQSCAQ?
Where does SMSQL stores the SnapInfo config information?
And why after all created the Configuration Wizard a new directory?
I've had the exact same issue when reconfiguring it the other day.
I resolved all my issues by going through the Reconfiguration Wizard.
I then recreated all my backup jobs with the exact same settings.
Have you tried this yet?
It shouldn't stop any services. Just make sure that when you reconfigure it, you don't move any DBs/Luns and it won't stop any services. If you do move DBs on a different Lun, it will stop only this database but not the actual SQL database engine.
Let us know!