commvault.com commvault.com
Solved

MS SQL Integrity check

  • 4 February 2021
  • 5 replies
  • 294 views
Henke
Rank
Userlevel 4
Badge +13

We do Intellisnap backups of some of our SQL databases. Once a week we do a integrity check on a snapshot also and it works fine.

My question is what SQL versions can we use as proxies, does it have to be the exactly same SQL version or can it be a later version of SQL? I’ve not found that documented.

BR

Henke

icon

Best answer by Edd Rimmer 8 February 2021, 15:51

View original

5 replies

Edd Rimmer
Rank
Userlevel 4
Badge +7

Hey Henke,

As long as the SQL Version on the proxy is the same as the backup or newer, it will be fine.

For example - SQL 2012 attaching to SQL 2019 is fine. Attaching a SQL 2019 DB to a SQL 2014 instance NOT fine :)

Regards
Edd

Of all the things I've lost, I miss my mind the most
Henke
Rank
Userlevel 4
Badge +13

@Edd Rimmer I argued, though being a SQL noobie, that I thought that it would be the case.

The argument against was that if a SQL database is attached to a later version of SQL the database would be updated hence not usable on the original location.

 

BR

Henke

Edd Rimmer
Rank
Userlevel 4
Badge +7

Hey Henke,

We clone the snapshot and mount this to the proxy - the original snapshot should be left in the same condition as it was when created :grin:.

For peace of mind you can check in the CVMA.log on the proxy being used for the integrity check and you should see the snap being cloned.

For example, in my lab I am using a NetApp and use a Windows 2016 server / SQL Server 2019  to perform integrity check of a SQL Server 2017 database from a Windows 2012 server:

CVMA.log:
508   116c  02/08 14:43:41 2467 CVSnapEngineNetApp::cvso_mapSnaps  sFSSnapName [SP_2_2467_32_1612795403] sFSPath [/vol/Win2012SQL/Win2012SQL] sCloneName [SP_2_2467_32_1612795403_Win2012SQL_0]
508   116c  02/08 14:43:41 2467 CVSnapEngineNetApp::cvso_mapSnaps  sCloneName [SP_2_2467_32_1612795403_Win2012SQL_0] sClonePath [/vol/Win2012SQL/SP_2_2467_32_1612795403_Win2012SQL_0]
508   116c  02/08 14:43:41 2467 CVSnapEngineNetApp::cvso_mapSnaps Cloning LUN to path:[/vol/Win2012SQL/SP_2_2467_32_1612795403_Win2012SQL_0]
508   116c  02/08 14:43:41 2467 Cloning LUN from snapshot. FileServer:[10.10.10.104] Volume:[Win2012SQL] SnapShot:[SP_2_2467_32_1612795403] Path:[/vol/Win2012SQL/Win2012SQL] Clone:[/vol/Win2012SQL/SP_2_2467_32_1612795403_Win2012SQL_0]
508   116c  02/08 14:43:41 2467 Cloned LUN from snapshot. FileServer:[10.10.10.104] Volume:[Win2012SQL] SnapShot:[SP_2_2467_32_1612795403] AlreadyExisted:[false] Path:[/vol/Win2012SQL/Win2012SQL] Clone:[/vol/Win2012SQL/SP_2_2467_32_1612795403_Win2012SQL_0]
508   116c  02/08 14:43:41 2467 * Relative source path[Win2012SQL], Relative destination path[SP_2_2467_32_1612795403_Win2012SQL_0]
508   116c  02/08 14:43:41 2467 CVSnapEngineNetApp::cvso_mapSnaps Successfully cloned the lun. Already existed:[false].

Of all the things I've lost, I miss my mind the most
Damian Andre
Rank
Userlevel 7
Badge +23

To echo what Edd said, regardless of agent or data type, mounts never impact the original copy of the snapshot. All snapshots are cloned or mounted in such a way that changes are discarded so that the original snap is kept in-tact - this is our golden rule so to speak.

This is also why some features like live mount from snap, are only allowed for specific arrays and snap engines.

 

Henke
Rank
Userlevel 4
Badge +13

Thank you @Damian Andre  and @Edd Rimmer for the clearification!

BR

Henke

Reply


Terms & ConditionsCookie settings