Dell EqualLogic PS6210XV EqualLogic Auto-Snapshot Manager/Microsoft Edition Ve - Page 74

Using ASM/ME with SQL Server, SQL Server Version Compatibility, Create and Schedule SQL Smart Copies

Page 74 highlights

7 Using ASM/ME with SQL Server ASM/ME supports SQL Server 2014, 2016 and 2017. See the Dell EqualLogic Host Integration Tools for Microsoft Release Notes for specific release versions. Certain ASM/ME operations are specific to SQL Server and some operations behave differently when Smart Copy sets include SQL Server components. ASM/ME operations that are not specific to SQL Server are described in General ASM/ME Operations. NOTE: ASM/ME does not support creating Smart Copies of SQL Availability Groups. Topics: • SQL Server Version Compatibility • Create and Schedule SQL Smart Copies • Restore Options for SQL Server Smart Copies SQL Server Version Compatibility Although it is not detected during installation, ASM/ME verifies the compatibility of the installed version of SQL Server. If ASM/ME detects an unsupported version of SQL Server, a red arrow displays next to the application in the ASM/ME console. The SqlServerWriter node (under the Applications node) is disabled if the installed version and service pack level of SQL Server are unsupported. See the product requirements in the Host Integration Tools for Microsoft Installation and User's Guide. See Using ASM/ME with Hyper-V if you intend to run SQL Server with a Hyper-V virtual machine. In some configurations, certain ASM/ME operations are constrained. Create and Schedule SQL Smart Copies • If you use ASM/ME to create a Smart Copy set or a schedule that includes multiple SQL Server components (multiple databases sharing similar volumes), ASM/ME warns you that during restore operations, all components are set offline even if you need to restore only one component. • Limit the number of databases in a Smart Copy collection to 34 or fewer. If you have more than 34 databases, spread them among multiple hosts. For more information, see Knowledge Base article: support.microsoft.com/kb/943471. • The procedures for creating and scheduling Smart Copies are the same as the general operations described in General ASM/ME Operations. • As a best practice, do not put system databases (Master, Model, MSDB, and TempDB) on the same volumes as user databases. Keeping these databases separate allows for independent recovery of the user content or the system. It also prevents problems caused by changes to the system databases while restoring user content. Restore Options for SQL Server Smart Copies The following table summarizes available SQL Server restore options and Backup Types according to the Smart Copy Type. Table 27. SQL Server Data Restore Options by Smart Copy Type Smart Copy Type Backup Type Snapshot copy or full Restore Options • Mount • Restore selected databases. (Apply logs option also available for the full backup type.) • Restore all • Restore as new Clone copy or full • Mount 74 Using ASM/ME with SQL Server

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134

Using ASM/ME with SQL Server
ASM/ME supports SQL Server 2014, 2016 and 2017. See the
Dell EqualLogic Host Integration Tools for Microsoft Release Notes
for
specific release versions.
Certain ASM/ME operations are specific to SQL Server and some operations behave differently when Smart Copy sets include SQL
Server components. ASM/ME operations that are not specific to SQL Server are described in
General ASM/ME Operations
.
NOTE:
ASM/ME does not support creating Smart Copies of SQL Availability Groups.
Topics:
SQL Server Version Compatibility
Create and Schedule SQL Smart Copies
Restore Options for SQL Server Smart Copies
SQL Server Version Compatibility
Although it is not detected during installation, ASM/ME verifies the compatibility of the installed version of SQL Server. If ASM/ME
detects an unsupported version of SQL Server, a red arrow displays next to the application in the ASM/ME console. The SqlServerWriter
node (under the Applications node) is disabled if the installed version and service pack level of SQL Server are unsupported.
See the product requirements in the
Host Integration Tools for Microsoft Installation and User’s Guide
.
See
Using ASM/ME with Hyper-V
if you intend to run SQL Server with a Hyper-V virtual machine. In some configurations, certain
ASM/ME operations are constrained.
Create and Schedule SQL Smart Copies
If you use ASM/ME to create a Smart Copy set or a schedule that includes multiple SQL Server components (multiple databases
sharing similar volumes), ASM/ME warns you that during restore operations, all components are set offline even if you need to restore
only one component.
Limit the number of databases in a Smart Copy collection to 34 or fewer. If you have more than 34 databases, spread them among
multiple hosts. For more information, see Knowledge Base article:
support.microsoft.com/kb/943471
.
The procedures for creating and scheduling Smart Copies are the same as the general operations described in
General ASM/ME
Operations
.
As a best practice, do not put system databases (Master, Model, MSDB, and TempDB) on the same volumes as user databases.
Keeping these databases separate allows for independent recovery of the user content or the system. It also prevents problems
caused by changes to the system databases while restoring user content.
Restore Options for SQL Server Smart Copies
The following table summarizes available SQL Server restore options and Backup Types according to the Smart Copy Type.
Table 27. SQL Server Data Restore Options by Smart Copy Type
Smart Copy Type
Backup Type
Restore Options
Snapshot
copy or full
Mount
Restore selected databases. (Apply logs option also
available for the full backup type.)
Restore all
Restore as new
Clone
copy or full
Mount
7
74
Using ASM/ME with SQL Server