Enable the Infrastructure Backup Service through the administration portal so that Azure Stack can generate backups. You can use these backups to restore your environment using cloud recovery in the event of a catastrophic failure. The purpose of cloud recovery is to ensure that your operators and users can log back into the portal after recovery is complete. Users will have their subscriptions restored including role-based access permissions and roles, original plans, offers, and previously defined compute, storage, and network quotas.
However, the Infrastructure Backup Service does not backup IaaS VMs, network configurations, and storage resources such as storage accounts, blobs, tables, and so on, so users logging in after cloud recovery completes will not see any of their previously existing resources. Platform as a Service (PaaS) resources and data are also not backed up by the service.
Enable or reconfigure backup
- Open the Azure Stack administration portal.
- Select All services, and then under the ADMINISTRATION category select Infrastructure backup. Choose Configuration in the Infrastructure backup blade.
- Type the path to the Backup storage location. Use a Universal Naming Convention (UNC) string for the path to a file share hosted on a separate device. A UNC string specifies the location of resources such as shared files or devices. For the service, you can use an IP address. To ensure availability of the backup data after a disaster, the device should be in a separate location.
Note: – If your environment supports name resolution from the Azure Stack infrastructure network to your enterprise environment, you can use an FQDN rather than the IP.
- Type the Username using the domain and username with sufficient access to read and write files. For example,
- Type the Password for the user.
- Type the password again to Confirm Password.
- The frequency in hours determines how often backups are created. The default value is 12. Scheduler supports a maximum of 12 and a minimum of 4.
- The retention period in days determines how many days of backups are preserved on the external location. The default value is 7. Scheduler supports a maximum of 14 and a minimum of 2. Backups older than the retention period are automatically deleted from the external location.
Note – If you want to archive backups older than the retention period, make sure to backup the files before the scheduler deletes the backups. If you reduce the backup retention period (e.g. from 7 days to 5 days), the scheduler will delete all backups older than the new retention period. Make sure you are ok with the backups getting deleted before you update this value.
- Provide a pre-shared key in the Encryption Key box. Backup files are encrypted using this key. Make sure to store this key in a secure location. Once you set this key for the first time or rotate the key in the future, you cannot view the key from this interface. To create the key, run the following Azure Stack PowerShell commands:
10. Select OK to save your backup controller settings.
To start a backup, click on Backup now to start an on-demand backup. An on-demand backup will not modify the time for the next scheduled backup. After the task completes, you can confirm the settings in Essentials:
You can also run the PowerShell cmdlet Start-AzsBackup on your Azure Stack administration computer.
Enable or disable automatic backups
Backups are automatically scheduled when you enable backup. You can check the next schedule backup time in Essentials.
If you need to disable future scheduled backups, click on Disable Automatic Backups. Disabling automatic backups will keep backup settings configured and will retain the backup schedule. This action simply tells the scheduler to skip future backups.
Confirm that future scheduled backups have been disabled in Essentials:
Click on Enable Automatic Backups to inform the scheduler to start future backups at the scheduled time.
Note – If you configured infrastructure backup before updating to 1807, automatic backups will be disabled. This way the backups started by Azure Stack do not conflict with backups started by an external task scheduling engine. Once you disable any external task scheduler, click on Enable Automatic Backups.
Start Azure Stack backup
Start a new backup without job progress tracking
Use Start-AzSBackup to start a new backup immediately with no job progress tracking.
Start Azure Stack backup with job progress tracking
Use Start-AzSBackup to start a new backup with the -AsJob parameter and save it as a variable to track backup job progress.
Note – Backup job will appear as successfully completed in the portal about 10-15 minutes before the job will finish. Therefore, the actual status is better observed via the code below.
Important – The initial 1 millisecond delay is introduced because the code is too quick to register the job correctly and it comes back with no PSBeginTime and in turn with no State of the job.
Confirm backup has completed
Confirm backup has completed using PowerShell
Use the following PowerShell commands to ensure that backup has completed successfully: