Dell PowerVault DL4000 Dell PowerVault DL4000 Backup To Disk Appliance - Power - Page 77

Configuring SQL Attachability Settings, SQL Server 2008 R2

Get Dell PowerVault DL4000 PDF manuals and user guides View all Dell PowerVault DL4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 77 highlights

consistency of the SQL databases and ensure that all data files (MDF and LDF files) are available in the backup snapshot. Attachability checks can be run for specific recovery points on demand or as part of a nightly job. Attachability requires the presence of a local instance of Microsoft SQL Server on the Core. This is a passive instance with no active databases or queries. Attachability supports SQL Server 2005, 2008, and 2008 R2. The account used to perform the test must be granted the sysadmin role on the SQL Server instances. NOTE: The SQL Server on-disk storage format is the same in both 64-bit and 32-bit environments and attachability works across both versions. A database that is detached from a server instance that is running in one environment can be attached on a server instance that runs in another environment. CAUTION: The version of SQL Server on the Core has to be equal to or newer than the SQL Server version on all the agents with SQL Server installed. Configuring SQL Attachability Settings Prior to running attachability checks on the protected SQL databases, you must first select a local instance of SQL Server against which the attachability checks to perform. To configure SQL attachability settings: 1. Navigate to the AppAssure 5 Core, and then click the Configuration tab. 2. From the Manage option, click Attachability. The Attachability Check Settings window is displayed. 3. Select the local SQL Server instance to use to perform attachability checks for the protected SQL databases. You can choose from: - SQL Server 2005 - SQL Server 2008 - SQL Server 2008 R2 4. Select the credential type. You can choose from: - Windows - SQL 5. Specify the credentials with administrative privileges for the Windows or SQL Server instances, as described below. Text Box Username Password Description Enter a user name for logon permissions to the SQL server. Enter a password for SQL attachability. It is used to control logon activity. 6. Click Test Connection. NOTE: If you entered the credentials incorrectly, a message is displayed to alert you that the credentials test failed. Correct the credential information and run the connection test again. 7. Click Apply. Attachability checks are now available to be run on the protected SQL Server databases. 77

  • 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
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
consistency of the SQL databases and ensure that all data files (MDF and LDF files) are available in the backup
snapshot.
Attachability checks can be run for specific recovery points on demand or as part of a nightly job. Attachability requires
the presence of a local instance of Microsoft SQL Server on the Core. This is a passive instance with no active
databases or queries. Attachability supports SQL Server 2005, 2008, and 2008 R2. The account used to perform the test
must be granted the sysadmin role on the SQL Server instances.
NOTE:
The SQL Server on-disk storage format is the same in both 64-bit and 32-bit environments and attachability
works across both versions. A database that is detached from a server instance that is running in one environment
can be attached on a server instance that runs in another environment.
CAUTION: The version of SQL Server on the Core has to be equal to or newer than the SQL Server version on all the
agents with SQL Server installed.
Configuring SQL Attachability Settings
Prior to running attachability checks on the protected SQL databases, you must first select a local instance of SQL
Server against which the attachability checks to perform.
To configure SQL attachability settings:
1.
Navigate to the AppAssure 5 Core, and then click the
Configuration
tab.
2.
From the
Manage
option, click
Attachability
.
The
Attachability Check Settings
window is displayed.
3.
Select the local SQL Server instance to use to perform attachability checks for the protected SQL databases.
You can choose from:
–
SQL Server 2005
–
SQL Server 2008
–
SQL Server 2008 R2
4.
Select the credential type.
You can choose from:
–
Windows
–
SQL
5.
Specify the credentials with administrative privileges for the Windows or SQL Server instances, as described
below.
Text Box
Description
Username
Enter a user name for logon permissions to the SQL server.
Password
Enter a password for SQL attachability. It is used to control logon activity.
6.
Click
Test Connection
.
NOTE:
If you entered the credentials incorrectly, a message is displayed to alert you that the credentials test
failed. Correct the credential information and run the connection test again.
7.
Click
Apply
.
Attachability checks are now available to be run on the protected SQL Server databases.
77