Loadmysocial327

-->

This article describes how to restore Azure VM data from the recovery points stored in Azure Backup Recovery Services vaults.

Oct 20, 2015 Restart your computer in the Recovery Partition, erase the drive, reinstall the OS, and then when asked if you want to restore data from another computer or TimeMachine backup say yes. Make sure your TimeMachine drive is connected and select it. Select both the Applications folder and your personal folder. Jun 01, 2011 I had my MBP SSD corrupted a week back, and had to reformat and re-install OSX. I then used my Time Machine backup to restore all my data and programs. But now, MS Office 2011 is asking for me re-enter my Authentication Key. While I have the Office disk; here is my issue. The disk is a family pack (3 licenses). But it had only 1 Auth Key (alpha.

Restore options

Azure Backup provides several ways to restore a VM.

Note

You can also recover specific files and folders on an Azure VM. Learn more.

Storage accounts

Some details about storage accounts:

• Create VM: When you create a new VM, the VM will be placed in the storage account you specify.
• Restore disk: When you restore a disk, the disk is copied to the storage account you specify. The restore job generates a template that you can download and use to specify custom VM settings. This template is placed in the specified storage account.
• Replace disk: When you replace a disk in an existing VM, Azure Backup takes a snapshot of the existing VM before replacing the disk. The snapshot is also copied to the Recovery Services vault through data transfer, as a background process. However, once the snapshot phase is completed, the replace disks operation is triggered. After the replace disk operation, the disks of the source Azure VM are left in the specified Resource group for your operation and the VHDs are stored in the specified storage account. You can choose to delete or retain these VHDs and disks.
• Storage account location: The storage account must be in the same region as the vault. Only these accounts are displayed. If there are no storage accounts in the location, you need to create one.
• Storage type: Blob storage isn't supported.
• Storage redundancy: Zone redundant storage (ZRS) isn't supported. The replication and redundancy information for the account is shown in parentheses after the account name.
• Premium storage:
  • When restoring non-premium VMs, premium storage accounts aren't supported.
  • When restoring managed VMs, premium storage accounts configured with network rules aren't supported.

Before you start

To restore a VM (create a new VM), make sure you have the correct Azure role-based access control (Azure RBAC) permissions for the Restore VM operation.

If you don't have permissions, you can restore a disk, and then after the disk is restored, you can use the template that was generated as part of the restore operation to create a new VM.

Note

The functionality described in the following sections can also be accessed via Backup center. Backup center is a single unified management experience in Azure. It enables enterprises to govern, monitor, operate, and analyze backups at scale. With this solution, you can perform most of the key backup management operations without being limited to the scope of an individual vault.

Select a restore point

1. Navigate to Backup center in the Azure portal and click Restore from the Overview tab.

2. Select Azure Virtual machines as the Datasource type, and then select a Backup instance.

3. Select a VM and click Continue.

4. In the next screen that appears, select a restore point to use for the recovery.

Choose a VM restore configuration

1. In Restore Virtual Machine, select a restore option:

   • Create new: Use this option if you want to create a new VM. You can create a VM with simple settings, or restore a disk and create a customized VM.

   • Replace existing: Use this option if you want to replace disks on an existing VM.

2. Specify settings for your selected restore option.

Create a VM

As one of the restore options, you can create a VM quickly with basic settings from a restore point.

1. In Restore Virtual Machine > Create new > Restore Type, select Create a virtual machine.

2. In Virtual machine name, specify a VM that doesn't exist in the subscription.

3. In Resource group, select an existing resource group for the new VM, or create a new one with a globally unique name. If you assign a name that already exists, Azure assigns the group the same name as the VM.

4. In Virtual network, select the VNet in which the VM will be placed. All VNets associated with the subscription are displayed. Select the subnet. The first subnet is selected by default.

5. In Staging Location, specify the storage account for the VM. Learn more.

6. Select Restore to trigger the restore operation.

Restore disks

As one of the restore options, you can create a disk from a restore point. Then with the disk, you can do one of the following actions:

• Use the template that's generated during the restore operation to customize settings, and trigger VM deployment. You edit the default template settings, and submit the template for VM deployment.
• Attach restored disks to an existing VM.
• Create a new VM from the restored disks using PowerShell.

1. In Restore configuration > Create new > Restore Type, select Restore disks.

2. In Resource group, select an existing resource group for the restored disks, or create a new one with a globally unique name.

3. In Staging location, specify the storage account to which to copy the VHDs. Learn more.

4. Select Restore to trigger the restore operation.

When your virtual machine uses managed disks and you select the Create virtual machine option, Azure Backup doesn't use the specified storage account. In the case of Restore disks and Instant Restore, the storage account is used only for storing the template. Managed disks are created in the specified resource group.When your virtual machine uses unmanaged disks, they're restored as blobs to the storage account.

Use templates to customize a restored VM

After the disk is restored, use the template that was generated as part of the restore operation to customize and create a new VM:

1. In Backup Jobs, select the relevant restore job.

2. In Restore, select Deploy Template to initiate template deployment.

   Note

   For a shared access signature (SAS) that has Allow storage account key access set to disabled, the template won't deploy when you select Deploy Template.

3. To customize the VM setting provided in the template, select Edit template. If you want to add more customizations, select Edit parameters.

   • Learn more about deploying resources from a custom template.
   • Learn more about authoring templates.

4. Enter the custom values for the VM, accept the Terms and Conditions and select Purchase.

Replace existing disks

As one of the restore options, you can replace an existing VM disk with the selected restore point. Review all restore options.

1. In Restore configuration, select Replace existing.

2. In Restore Type, select Replace disk/s. This is the restore point that will be used replace existing VM disks.

3. In Staging Location, specify where snapshots of the current managed disks should be saved during the restore process. Learn more.

Cross Region Restore

As one of the restore options, Cross Region Restore (CRR) allows you to restore Azure VMs in a secondary region, which is an Azure paired region.

To begin using the feature, read the Before You Begin section.

To see if CRR is enabled, follow the instructions in Configure Cross Region Restore.

View backup items in secondary region

If CRR is enabled, you can view the backup items in the secondary region.

1. From the portal, go to Recovery Services vault > Backup items.
2. Select Secondary Region to view the items in the secondary region.

Note

Only Backup Management Types supporting the CRR feature will be shown in the list. Currently, only support for restoring secondary region data to a secondary region is allowed.
CRR for Azure VMs is supported for Azure Managed VMs (including encrypted Azure VMs).

Restore in secondary region

The secondary region restore user experience will be similar to the primary region restore user experience. When configuring details in the Restore Configuration pane to configure your restore, you'll be prompted to provide only secondary region parameters.

Currently, secondary region RPO is up to 12 hours from the primary region, even though read-access geo-redundant storage (RA-GRS) replication is 15 minutes.

• To restore and create a VM, refer to Create a VM.
• To restore as a disk, refer to Restore disks.

Note

• After the restore is triggered and in the data transfer phase, the restore job can't be cancelled.
• The Cross Region Restore feature restores CMK (customer-managed keys) enabled Azure VMs, which aren't backed-up in a CMK enabled Recovery Services vault, as non-CMK enabled VMs in the secondary region.
• The Azure roles needed to restore in the secondary region are the same as those in the primary region.
• While restoring an Azure VM, Azure Backup configures the virtual network settings in the secondary region automatically. If you are restoring disks while deploying the template, ensure to provide the virtual network settings, corresponding to the secondary region.

Azure zone pinned VMs can be restored in any availability zones of the same region.

Restore Microsoft Office From Time Machine Download

In the restore process, you'll see the option Availability Zone. You'll see your default zone first. To choose a different zone, choose the number of the zone of your choice. If the pinned zone is unavailable, you won't be able to restore the data to another zone because the backed-up data isn't zonally replicated. The restore in availability zones is possible from recovery points in vault tier only.

Monitoring secondary region restore jobs

1. From the portal, go to Recovery Services vault > Backup Jobs

2. Select Secondary Region to view the items in the secondary region.

Restoring unmanaged VMs and disks as managed

You're provided with an option to restore unmanaged disks as managed disks during restore. By default, the unmanaged VMs / disks are restored as unmanaged VMs / disks. However, if you choose to restore as managed VMs / disks, it's now possible to do so. These restores aren't triggered from the snapshot phase but only from the vault phase. This feature isn't available for unmanaged encrypted VMs.

Restore Microsoft Office From Time Machine Using

Restore VMs with special configurations

There are many common scenarios in which you might need to restore VMs.

Restore domain controller VMs

For more information, see Back up and restore Active Directory domain controllers.

Restore VMs with managed identities

Managed identities eliminate the need for the user to maintain the credentials. Managed identities provide an identity for applications to use when connecting to resources that support Azure Active Directory (Azure AD) authentication.

Azure Backup offers the flexibility to restore the managed Azure VM with managed identities. You can choose to select system-managed identities or user-managed identities as shown in the figure below. This is introduced as one of the input parameters in the Restore configuration blade of Azure VM. Managed identities used as one of the input parameter is only used for accessing the storage accounts, which is used as staging location during restore and not for any other Azure resource controlling. These managed identities have to be associated to the vault.

If you choose to select system-assigned or user-assigned managed identities, check for the below actions for managed identity on the target staging Storage Account.

Or, add the role assignment on the staging location (Storage Account) to have Storage account Backup Contributor and Storage Blob data Contributor for the successful restore operation.

You can also select the user-managed identity by providing the input as their MSI Resource ID as provided in the figure below.

Note

The support is available for only managed VMs, and not supported for classic VMs and unmanaged VMs. For the storage accounts that are restricted with firewalls, system MSI is only supported.

Cross Region Restore isn't supported with managed identities.

Currently, this is available in all Azure public and national cloud regions.

Track the restore operation

After you trigger the restore operation, the backup service creates a job for tracking. Azure Backup displays notifications about the job in the portal. If they aren't visible, select the Notifications symbol, and then select More events in the activity log to see the Restore Process Status.

Track restore as follows:

1. To view operations for the job, select the notifications hyperlink. Alternatively, in the vault, select Backup jobs, and then select the relevant VM.

2. To monitor restore progress, select any restore job with a status of In-progress. This displays the progress bar, which displays information about the restore progress:

   • Estimated time of restore: Initially provides the time taken to complete the restore operation. As the operation progresses, the time taken reduces and reaches zero when the restore operation finishes.
   • Percentage of restore. Shows the percentage of restore operation that's done.
   • Number of bytes transferred: If you're restoring by creating a new VM, it shows the bytes that were transferred against the total number of bytes to be transferred.

Post-restore steps

There are a few things to note after restoring a VM:

• Extensions present during the backup configuration are installed, but not enabled. If you see an issue, reinstall the extensions.

• If the backed-up VM had a static IP address, the restored VM will have a dynamic IP address to avoid conflict. You can add a static IP address to the restored VM.

• A restored VM doesn't have an availability set. If you use the restore disk option, then you can specify an availability set when you create a VM from the disk using the provided template or PowerShell.

• If you use a cloud-init-based Linux distribution, such as Ubuntu, for security reasons the password is blocked after the restore. Use the VMAccess extension on the restored VM to reset the password. We recommend using SSH keys on these distributions, so you don't need to reset the password after the restore.

• If you're unable to access a VM once restored because the VM has a broken relationship with the domain controller, then follow the steps below to bring up the VM:

  • Attach OS disk as a data disk to a recovered VM.
  • Manually install VM agent if Azure Agent is found to be unresponsive by following this link.
  • Enable Serial Console access on VM to allow command-line access to VM

  • When the VM is rebuilt use Azure portal to reset local administrator account and password

  • Use Serial console access and CMD to disjoin VM from domain

• Once the VM is disjoined and restarted, you'll be able to successfully RDP to the VM with local admin credentials and rejoin VM back to domain successfully.

Backing up restored VMs

• If you restored a VM to the same resource group with the same name as the originally backed-up VM, backup continues on the VM after restore.
• If you restored the VM to a different resource group or you specified a different name for the restored VM, you need to set up backup for the restored VM.

Next steps

Restore Microsoft Office From Time Machine Free

• If you experience difficulties during the restore process, review common issues and errors.
• After the VM is restored, learn about managing virtual machines

My guess would be that Office is seeing the change as a new system, and is requiring the key as an anti-piracy measure. Of course, that doesn't help you recover the key. You may want to try posting over on the Microsoft Office for Mac forums. Someone over there is more likely to know how to extract that data. If it were Mail, I could tell you exactly where to start looking in the Finder, but I have no idea about Outlook.

In the future, you would be wise to keep a plain text file somewhere with all your product keys listed in it. Keep that file backed up, and you also might want to print it out and file it away somewhere any time it changes. That way, you shouldn't find yourself in this situation again.

Jun 19, 2012 6:19 AM