User Tools

Site Tools


public:module:microsoft_sql_database:requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
public:module:microsoft_sql_database:requirements [2019/09/19 17:53]
ronnie.chan
public:module:microsoft_sql_database:requirements [2021/04/19 11:32]
ronnie.chan
Line 1: Line 1:
 ====== Requirements ====== ====== Requirements ======
-----+
 You are strongly recommended to configure or check all the requirements below before you proceed with the MS SQL server backup and restoration. You are strongly recommended to configure or check all the requirements below before you proceed with the MS SQL server backup and restoration.
  
-CloudBacko Pro supports 2 backup modes when creating a backup set for MS SQL server, VSS mode and ODBC mode.+===== Hardware Requirement =====
  
-{{INLINETOC}} \\+Refer to the here for the list of hardware requirements:​ [[public:​edition:​cloudbacko_pro:​hardware_requirement]] 
 + 
 +===== Software Requirement ===== 
 + 
 +Refer to the [[public:​edition:​cloudbacko_pro:​supported_platforms|list of compatible operating systems]] and [[public:​edition:​cloudbacko_pro:​supported_applications|application versions]]. 
 + 
 +===== CloudBacko Pro Installation ===== 
 + 
 +Make sure the latest version of CloudBacko Pro is installed directly on the machine where the MSSQL Server database(s) are hosted. 
 + 
 +<WRAP indent>​ 
 +Backup and restore of MS SQL Server database(s) running on a remote machine is not supported. 
 +</​WRAP>​ 
 + 
 +===== Java Heap Size ===== 
 + 
 +The default Java heap size setting on CloudBacko Pro is 2048MB. For MS SQL Server backup it is highly recommended to increase the Java heap size setting to be at least 4096MB to improve backup and restore performance. The actual heap size is dependent on the amount of free memory available on your MS SQL server. See: [[public:​edition:​cloudbacko_pro:​faq:​how_to_increase_java_heap_size]] 
 + 
 +===== MS SQL Server Registry ===== 
 + 
 +Make sure the MS SQL entry is present in the registry key "​HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL"​. 
 +To access this path, type “regedit” in the command prompt to launch the Registry Editor.  
 + 
 +{{public:​module:​microsoft_sql_database:​cloudbacko_module_sql_005.png?​800}} 
 + 
 +<WRAP info> 
 +Pay extra attention when you are checking configuration in Registry Editor. Any unauthorized changes could cause interruption to the Windows operation.  
 +</​WRAP>​ 
 + 
 +===== SQL Server Services =====  
 + 
 +Ensure that the following SQL Server Services have been enabled in the Windows Services menu. Launch Services in Windows by clicking Start then typing “Services” in the search box. All MS SQL server related services should be started by default. If in case it is not, turn it on by right clicking the item then selecting Start. 
 + 
 +{{public:​module:​microsoft_sql_database:​cloudbacko_module_sql_003.png?​800}} 
 + 
 +===== Transport Layer Security(TLS) =====  
 + 
 +For MS SQL Server 2005, 2008, 2012, and 2014 VSS and ODBC backup modes, TLS version 1.0 must be enabled as only TLS version 1.0 is supported. 
 + 
 +To check if TLS 1.0 is enabled on the MS SQL machine, launch the registry editor and locate the following path: 
 + 
 +“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client” 
 + 
 +The value of registry key should be “1” to indicate that TLS 1.0 is enabled. 
 + 
 +| {{public:​module:​microsoft_sql_database:​image1019.png?​800}} | 
 + 
 +Meanwhile, for MS SQL Server 2016, 2017 and 2019 VSS and ODBC backup modes, TLS version 1.2 must be enabled as only TLS version 1.2 is supported. 
 + 
 +To check if TLS 1.2 is enabled on the MS SQL machine, launch the registry editor and locate the following path: 
 + 
 +“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client” 
 + 
 +The value of registry key should be “1” to indicate that TLS 1.2 is enabled. 
 + 
 +| {{public:​module:​microsoft_sql_database:​image1023.png?​800}} | 
 + 
 +===== Upgrade VMware Tools Requirement ===== 
 + 
 +To avoid unexpected java crash, if the Windows machine is a guest VM hosted on a VMware Host then it is highly recommended that the VMware tools version installed on the guest VM must be 10.0.5 or above. Below is the warning message that will be displayed if the version of the VMware Tools is less than 10.0.5. 
 + 
 +| {{public:​module:​microsoft_sql_database:​image1025.png?​800}} | 
 + 
 + 
 +CloudBacko Pro supports 2 backup modes when creating a backup set for MS SQL server, VSS mode and ODBC mode.
  
 ===== VSS Backup Mode ===== ===== VSS Backup Mode =====
Line 131: Line 195:
  
 {{public:​module:​microsoft_sql_database:​cloudbacko_module_sql_002.png?​800}} {{public:​module:​microsoft_sql_database:​cloudbacko_module_sql_002.png?​800}}
-  
-2. SQL Server Services 
  
-{{public:​module:​microsoft_sql_database:​cloudbacko_module_sql_003.png?​800}} 
    
 3. Volume Shadow Copy 3. Volume Shadow Copy
Line 141: Line 202:
 </​WRAP>​ </​WRAP>​
  
-=== MS SQL Server Registry === 
----- 
-Make sure the MS SQL entry is present in the registry key "​HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL"​. 
-To access this path, type “regedit” in the command prompt to launch the Registry Editor. ​ 
- 
-{{public:​module:​microsoft_sql_database:​cloudbacko_module_sql_005.png?​800}} 
- 
-<WRAP info> 
-Pay extra attention when you are checking configuration in Registry Editor. Any unauthorized changes could cause interruption to the Windows operation. ​ 
-</​WRAP>​ 
  
 === MS SQL Recovery Model === === MS SQL Recovery Model ===
public/module/microsoft_sql_database/requirements.txt · Last modified: 2021/04/19 11:41 by ronnie.chan