The node to be backed up from will be based on the backup priorities for each of the nodes. Backups can happen from any readable replica i. If any replica is excluded from backup, for example Exclude Replica is enabled or is marked as not readable, then that replica will not be selected for backup under any of the options. If multiple replicas are available and readable then the node with the highest backup priority will be selected for backup.
DPM cannot be used to protect this configuration. There are some known issues with Prefer secondary backup preference for the SQL AlwaysOn option, DPM always takes a backup from secondary; if no secondary can be found then the backup fails. If you haven't see:. What can DPM back up? What's supported and what isn't for DPM? Set up storage - You can store backed up data on disk, on tape, and in the cloud with Azure. Read more in Prepare data storage.
Read Deploy the DPM protection agent. Learn more in Deploy protection groups. Note that:. You have the option of selecting protection at the instance level or protection of individual databases.
When you are protecting at the instance level, any database that is added to that instance of SQL Server will automatically be added to DPM protection. If you are using SQL Server AlwaysOn availability groups, you can create a protection group that contains the availability groups. DPM detects the availability groups and will displays them under Cluster Group. Select the whole group to protect it so that any databases that you add to the group are protected automatically, or select individual databases.
For each instance of SQL Server, you can also run a system state backup or full bare metal backup. This in useful if you want to be able to recover your whole server and not just data.
In Select data protection method , specify how you want to handle short and long-term backup. Short-term back up is always to disk first, with the option of backing up from the disk to the Azure cloud with Azure backup for short or long-term.
As an alternative to long-term backup to the cloud you can also configure long-term back up to a standalone tape device or tape library connected to the DPM server. In Select short-term goals , specify how you want to back up to short-term storage on disk.
In Retention range , you specify how long you want to keep the data on disk. In Synchronization frequency , you specify how often you want to run an incremental backup to disk.
If you don't want to set a back up interval, you can select Just before a recovery point so that DPM will run an express full backup just before each recovery point is scheduled.
SQL Server databases that are log-shipped, in read-only mode, or that use the simple recovery model do not support incremental backup. Recovery points are created for each express full backup only. For all other SQL Server databases, synchronization transfers a transaction log backup, and recovery points are created for each incremental synchronization and express full backup. The transaction log is a serial record of all the transactions that have been performed against the database since the transaction log was last backed up.
If you want to store data on tape for long-term storage, in Specify long-term goals , indicate how long you want to keep tape data years. In Frequency of backup specify how often backups to tape should run. The frequency is based on the retention range you've specified:.
When the retention range is years, you can select backups to occur daily, weekly, bi-weekly, monthly, quarterly, half-yearly, or yearly. When the retention range is months, you can select backups to occur daily, weekly, bi-weekly, or monthly. On a stand-alone tape drive, for a single protection group, DPM uses the same tape for daily backups until there is insufficient space on the tape.
You can also colocate data from different protection groups on tape. In the Review disk allocation page review the storage pool disk space allocated for the protection group. Total Data size is the size of the data you want to back up, and Disk space to be provisioned on DPM is the space that DPM recommends for the protection group. DPM chooses the ideal backup volume, based on the settings.
However, you can edit the backup volume choices in the Disk allocation details. For the workloads, select the preferred storage in the dropdown menu. Underprovisioned space is the amount of storage DPM suggests you add to the volume, to continue with backups smoothly in the future. In Choose replica creation method , select how you want to handle the initial full data replication. If you select to replicate over the network we recommended you choose an off-peak time. For large amounts of data or less than optimal network conditions, consider replicating the data offline using removable media.
In Choose consistency check options , select how you want to automate consistency checks. You can enable a check to run only when replica data becomes inconsistent, or according to a schedule. If you don't want to configure automatic consistency checking, you can run a manual check at any time by right-clicking the protection group in the Protection area of the DPM console, and selecting Perform Consistency Check.
If you've selected to back up to the cloud with Azure Backup, on the Specify online protection data page make sure the workloads you want to back up to Azure are selected.
In Specify online backup schedule , specify how often incremental backups to Azure should occur. Backups can occur up to twice a day. Each time a back up runs a data recovery point is created in Azure from the copy of the backed up data stored on the DPM disk.
In Choose online replication , specify how the initial full replication of data will occur. You can replicate over the network, or do an offline backup offline seeding. Offline backup uses the Azure Import feature. For more information, see Offline seeding using Azure Data Box. On the Summary page, review your settings. After you click Create Group initial replication of the data occurs.
When it finishes the protection group status will show as OK on the Status page. Backup then takes place in line with the protection group settings. DPM monitors the initial synchronization and subsequent backups. You can monitor the SQL Server data in a couple of ways:.
Using default DPM monitoring can set up notifications for proactive monitoring. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. Friday, October 15, PM. I would first verify that you can recover the instances using the DPM recovery method. It could be that for some reason either they are not being backed up or they are backed up but not even the DPM server can recover them for some reason.
I would look to see if there are any consistencies in which instances are not showing up in the SSRT. Maybe long names or special characters?
0コメント