Performing Backups & Restores (part 2 of 3)

By Ashwin Venugopal -

 



To read part 1 please click here
To read part 3 please click here


SQL Server Backups

SQL Server backup to URL (Azure Storage)

If you want to implement SQL Server Backup to URL, then, you have to use the following methods:
  • Back Up Task in SQL Server Management Studio- A database can be backed up to URL via the Back Up task in SQL Server Management Studio using an SQL Server Credential.

  • SQL Server Backup to URL Using Maintenance Plan Wizard- The Maintenance Plan Wizard in SQL Server Management Studio includes URL as one of the destination options, and the other supporting objects required to backup to Windows Azure storage like the SQL Credential.

  • Transact-SQL , PowerShell or C#- These options should create a striped backup set, an SQL Server file-snapshot backup, or an SQL credential using Shared Access token.

SQL Server Automated Backup v2 for Azure VMs

The Managed Backup can be automatically configured by Automated Backup v2 to Microsoft Azure for all existing and new databases on an Azure VM running SQL Server 2016/2017 Standard, Enterprise, or Developer editions which allows you to configure regular database backups utilizing Azure blob storage.

Automated Backup v2 can easily work with SQL Server 2016 or higher while Automated Backup v1 can be used to back up your databases for SQL Server 2014.

Database Configuration:

  • The full recovery model can be easily used by Target databases.
  • It is unnecessary to use full recovery model by System databases, but while using log backups for Model or MSDB you have to use full recovery model.
  • Target databases must be on either the default SQL Server instance, or a named instance installed by the procedure described at https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-server-iaas-faq#administration   

To configure Automated Backup v2, the Azure portal or Az PowerShell can also be used during provisioning or existing SQL Server 2016/2017 VMs.

SQL Server Backup in Azure VMs (to Recovery Services Vault)

This process includes running discovery of SQL Server instances and their databases from an Azure Recovery Services vault, selecting the databases to be backed up in the discovery results as well as assigning a backup policy that determines backup settings, like frequency and retention. If the SQL Server VM isn't created with the help of Azure Marketplace image, then, you should assign the sysadmin role to NT SERVICE\AzureWLBackupPluginSvc account.

SQL Server file snapshot-based backups to Azure Storage

Azure snapshots can be used by SQL Server File-snapshot backup to provide almost instantaneous backups and quicker restores for database files stored using the Azure Blob storage service which allows you to simplify your backup as well as restore policies.

Azure PowerShell scripts and SQL queries can be used to apply SQL Server data files as Azure Blobs which will also readily help you to create a database in SQL Server running on-premises or in a VM on Azure as well as setting up dedicated storage location for your data  in Azure blob Storage. 

Whatever implementation method you use, this process involves setting up a storage account, creating SQL Server credentials as well as creating a database files stored in blobs. SQL server also requires the credentials to store the security information which can be used to write and read from the Azure blob container.  






To read part 1 please click here
To read part 3 please click here











Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more