public:microsoft_sql_database
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
public:microsoft_sql_database [2019/08/19 15:03] ronnie.chan [Best Practice and Recommendation] |
public:microsoft_sql_database [2019/08/19 15:06] ronnie.chan |
||
|---|---|---|---|
| Line 291: | Line 291: | ||
| - Perform test restores periodically to ensure your backup is set up and performed properly. Performing recovery test can also help identify potential issues or gaps in your recovery plan. It is important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test and it is important to identify those flaws. \\ \\ | - Perform test restores periodically to ensure your backup is set up and performed properly. Performing recovery test can also help identify potential issues or gaps in your recovery plan. It is important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test and it is important to identify those flaws. \\ \\ | ||
| - The Restore Raw File option is for advanced MS SQL Server administrator and should only be used if you have in-depth knowledge and understanding of your MS SQL Server, otherwise, it is not recommended to use this option as there are additional MS SQL techniques required to perform the manual restore. | - The Restore Raw File option is for advanced MS SQL Server administrator and should only be used if you have in-depth knowledge and understanding of your MS SQL Server, otherwise, it is not recommended to use this option as there are additional MS SQL techniques required to perform the manual restore. | ||
| + | |||
| + | ===== Limitation ===== | ||
| + | |||
| + | ==== Standalone Environment Only ==== | ||
| + | AhsayOBM does not support backup of MS SQL server in cluster environment, only standalone environment is supported. | ||
| + | |||
| + | ==== VSS Backup Mode ==== | ||
| + | - Only support backup of database on local drive. Database on network drive is not supported. \\ \\ | ||
| + | - VSS backup mode does not support transaction log backup, therefore, transaction log backup will have to be done manually. Or you can choose ODBC backup mode for transaction log backup. \\ \\ | ||
| + | - In order to truncate transaction logs, you have to perform a manual log truncation, which could be time consuming. | ||
| + | |||
| + | ==== File System for Database Snapshot ==== | ||
| + | You cannot create database snapshots on FAT32 file system or RAW partitions. The sparse files used by database snapshots are provided by the NTFS file system. | ||
| + | |||
| + | ==== SQL Server Version ==== | ||
| + | <WRAP indent> | ||
| + | === Automated Restore Option ==== | ||
| + | If you have chosen the automated restoration to the Original SQL server or Alternate SQL server of your selection, the restoration can only be done in a SQL server version that is the same as the one used for performing the backup. | ||
| + | |||
| + | === Manual Raw-file Restore Option === | ||
| + | If you have chosen to restore the raw file, the raw database file(s) can be manually restored to the same or newer SQL server version that you used to perform the backup. | ||
| + | </WRAP> | ||
| + | |||
| + | ==== Restoration to Other SQL Server ==== | ||
| + | - If you would like to restore database to an alternate SQL server, you can only choose to restore one database to restore at a time.\\ \\ | ||
| + | - If you would like to restore database to an alternate SQL server, make sure you choose to restore raw file by enabling the checkbox Restore raw file. | ||
public/microsoft_sql_database.txt · Last modified: 2022/11/28 11:06 by kirk.lim