備份 DPM 伺服器Back up the DPM server

重要

已不再支援此版本的 Data Protection Manager (DPM),建議升級至 DPM 2019This version of Data Protection Manager (DPM) has reached the end of support, we recommend you to upgrade to DPM 2019.

如果 System Center Data Protection Manager (DPM) 失敗,為確保可復原資料,您需要有 DPM 伺服器備份策略。To ensure that data can be recovered if System Center Data Protection Manager (DPM) fails, you'll need a strategy for backing up the DPM server. 如不備份,您就必須在失敗後手動重建,且無法復原磁碟型復原點。If it isn't backed up you'll need to rebuild it manually after a failure, and disk-based recovery points won't be recoverable. 您可以使用幾種方法來備份 DPM 伺服器:You can back up DPM servers using a couple of methods:

  • 備份 DPM 伺服器 :您可以使用次要 DPM 伺服器來備份主要 DPM 伺服器。Back up the DPM server - You can back up a primary DPM server with a secondary DPM server. 次要伺服器會保護主要伺服器資料庫,和儲存在主要伺服器上的資料來源複本。The secondary server will protect the primary server database and the data source replicas stored on the primary server. 當主要伺服器失敗時,次要伺服器將可繼續保護主要伺服器所保護的工作負載,直到主要伺服器恢復可用性為止。If the primary server fails, the secondary server can continue to protect workloads that are protected by the primary server, until the primary server is available again. 如果您需要重新建置主要伺服器,您可以從次要伺服器來還原資料庫及其複本。If you need to rebuild the primary server you can restore the databases and replicas to it from the secondary server. 在主要伺服器無法使用時,您也可從次要伺服器直接將資料還原至受保護的電腦。You can also restore data to protected computers directly from the secondary server when the primary server isn't available. 您可以設定兩部伺服器 (一個主要,一個次要),或將兩伺服器設定為彼此的主要伺服器。You can set up two servers, one as primary and the another as secondary, or configure each server to act as the primary for the other. 您也可以設定 DPM 伺服器鏈結,以根據鏈結順序相互保護。You can also configure a chain of DPM servers that protect each other according to the chain order.

  • 備份 DPM 資料庫 :您可以設定 DPM 伺服器將自已的資料庫備份到其磁帶媒體櫃,或者您也可以使用非 Microsoft 的軟體將資料庫備份到磁帶或卸除式媒體。Back up the DPM database - You can configure a DPM server to back up its own databases to its tape library, or you can use non-Microsoft software to back up the databases to tape or removable media.

  • 使用協力廠商軟體備份 DPM :您可以使用支援 DPM 和 VSS 的協力廠商軟體來備份 DPM 伺服器。Back up DPM using third-party software - You can back up DPM servers using third-party software that supports DPM and VSS.

使用次要 DPM 伺服器備份Back up with a secondary DPM server

下列任一設定的 DPM 伺服器皆可備份及保護其他 DPM 伺服器的資料:Information on a DPM server can be backed up and protected by another DPM server in any of the following configurations:

  • 主要至次要保護 :儲存在主要 DPM 伺服器上的資料庫和複本,可以備份至次要 DPM 伺服器。Primary to secondary protection - The database and replicas stored on a primary DPM server can be backed up to a secondary DPM server. 如果主要伺服器失敗,次要伺服器將會繼續備份受保護的工作負載。If the primary server fails the secondary server continues to back up protected workloads. 如果主要伺服器失敗,您可以執行下列其中一項:重新建置主要伺服器,並從次要伺服器還原其資料庫和複本。If the primary server fails you can do either of the following: Rebuild the primary server and restore its database and replicas from the secondary server. 接著,在重新建置後,將受保護的工作負載移回主要伺服器。Then move the protected workloads back to the primary server after the rebuild. 選擇將保護切換至次要 DPM 伺服器。Select to switch protection to the secondary DPM server. 使用此設定時,您可以在必要時直接從次要伺服器還原至受保護的電腦。With this setting you then restore to the protected computer directly from the secondary server when the need arises. 如需相關指示,請參閱 Set up secondary serversFor instructions, see Set up secondary servers.

  • DPM 鏈結 :以 DPM 伺服器鏈結提供保護,且每一部伺服器會保護鏈結中的下一部伺服器。DPM chaining - A chain of DPM servers provide protection, and each server protects the next one in in the chain. 例如:DPM1 受到 DPM2 的保護 (DPM1 是主要伺服器,DPM2 是次要伺服器)。For example: DPM1 is protected by DPM2 (DPM1 is the primary and DPM2 is the secondary). DPM2 受到 DPM3 保護 (DPM2 是主要伺服器,DPM3 是次要伺服器)。如需相關指示,請參閱<設定鏈結>。DPM2 is protected by DPM3 (DPM2 is the primary and DPM3 is the secondary) For instructions, see Set up chaining.

  • 循環保護 :一部 DPM 伺服器由另一部 DPM 伺服器備份,反之亦然。Cyclic protection - One DPM server is backed up by another DPM server, and vice versa. 因此,DPM1 會保護 DPM2,而 DPM2 也同樣會保護 DPM1。So that DPM1 protects DPM2, and likewise DPM2 protects DPM1. 這適用於小型環境。This is useful for small environments.

設定主要和次要保護Set up primary and secondary protection

使用次要 DPM 伺服器備份主要 DPM 伺服器:Back up a primary DPM server using a secondary DPM server:

  1. 主要 DPM 伺服器已安裝保護代理程式。The Primary DPM server has the protection agent already installed. 您需要將此保護代理程式連結到次要 DPM 伺服器。You need to attach this protection agent to the secondary DPM server.

    重要

    主要與次要 DPM 伺服器的主要和次要版本必須相符。Major and minor versions of the Primary and Secondary DPM servers must match.

    請遵循下列步驟來連結代理程式:Follow these steps to attach the agent:

    1. 在次要 DPM 伺服器的 [DPM 管理主控台] 中,按一下巡覽列上的 [管理] > [代理程式]。In DPM Administrator Console of secondary DPM server, on the navigation bar, click Management > Agents . [動作] 窗格中,按一下 [安裝]In the Actions pane, click Install .
    2. [選擇代理程式部署方法] 頁面上,選取 [連接代理程式] > [受信任之網域中的電腦] > [下一步]On the Select Agent Deployment Method page, select Attach agents > Computer on a trusted domain > Next . 隨即會開啟 [保護代理程式安裝精靈]。The Protection Agent Installation Wizard opens.
    3. 在 [選取電腦] 頁面上,DPM 會顯示可用電腦清單。On the Select Computers page, DPM displays a list of available computers. 從 [電腦名稱] 清單選取主要 DPM 伺服器的名稱 > [新增] > [下一步]。Select the name of the Primary DPM server from the Computer name list > Add > Next .
    4. 在 [輸入認證] 頁面上,輸入屬於主要 DPM 伺服器上本機 Administrators 群組成員之網域帳戶的使用者名稱與密碼。On the Enter Credentials page, type the user name and password for a domain account that is a member of the local Administrators group on the Primary DPM server.
    5. 在 [摘要] 頁面上,按一下 [連接] 。On the Summary page, click Attach .
  2. 將主要 DPM 伺服器新增至現有的保護群組,或建立新的群組。Add the primary DPM server to an existing protection group, or create a new one. 選擇保護下列資料來源:Select to protect the following data sources:

    • 為主要伺服器設定的 SQL Server 資料庫。The SQL Server databases configured for the primary server.

    • 位於主要 DPM 伺服器上的所有磁碟區 (不會個別顯示共用)All volumes on the primary DPM server (Shares will not be visible separately)

    • 位於主要 DPM 伺服器上的所有複本。All replicas on the primary DPM server.

    • 您至少應選取資料庫:\Program Files\Microsoft System Center\DPM\DPM\Config 資料夾與 \Program Files\Microsoft System Center\DPM\Scripting 資料夾。At a minimum, you should select the databases, the \Program Files\Microsoft System Center\DPM\DPM\Config folder, and the \Program Files\Microsoft System Center\DPM\Scripting folder.

請注意,複本保護無法排除檔案名稱。Note that you can't exclude file names from protection for a replica. 此外,所有的 DPM 伺服器都必須執行相同的版本、更新等等。設定同步處理時,建議每 24 小時執行一次同步處理。In addition, all DPM servers must be running the same version, updates etc. When setting up synchronization we recommend you synchronize every 24 hours.

設定 DPM 鏈結Set up DPM chaining

考慮鏈結之前,請注意這些限制︰Before you consider chaining note these limitations:

  • 每一部 DPM 伺服器在鏈結中只能受到一次保護,因此請確認它們只受到一部伺服器的保護。Each DPM server can only be protected once in the chain so verify that they're not protected by more than one server.

  • 主要和次要伺服器由鏈結所建立。Primary and secondary servers are established by the chain. 因此,在上例中,雖然伺服器 DPM3 因為是 DPM2 的次要伺服器而實際上保護了 DPM1,但它無法直接作為 DPM1 的次要伺服器。So, for example if server DPM3 is actually protecting server DPM1 because it's acting as the secondary server for DPM2, it can't act directly as a secondary server for DPM1.

  • 如果有 DPM 伺服器設定成保護本身的資料來源,鏈結將會中斷。If a DPM server is configured to protect its own data source the chain will be broken. 例如,如果 DPM1 保護本身的資料庫或系統狀態,DPM2 就無法保護 DPM1。For example, if DPM1 protects its own database or system state, DPM2 can't protect DPM1.

  • 您必須先啟動主要伺服器上的 SQL Server VSS 寫入器服務,才可以保護主要 DPM 伺服器的資料庫。Before you can protect the database of a primary DPM server you need to start the SQL Server VSS Writer service on the primary server.

鏈結範例 1Chaining example 1

案例 1:鏈結式保護Scenario 1: Chained protection

案例 1 顯示鏈結四部 DPM 伺服器的案例:Scenario 1 shows a scenario in which four DPM servers are chained:

伺服器Server 保護Protecting 受下列項目保護Protected by
DS1 (主要)DS1 (primary) PS1、PS2PS1, PS2 DS3DS3
DS2 (主要)DS2 (primary) PS3、PS4PS3, PS4 DS3DS3
DS3 (次要)DS3 (secondary) DS1、DS2DS1, DS2 DS4DS4
DS4 (次要)DS4 (secondary) DS3DS3 -

四部 DPM 伺服器的鏈結案例

鏈結範例 2Chaining example 2

案例 2:鏈結式保護Scenario 2: Chained protection

案例 2 顯示鏈結四部 DPM 伺服器的案例:Scenario 2 shows a scenario in which four DPM servers are chained:

伺服器Server 保護Protecting 受下列項目保護Protected by
DS1 (主要)DS1 (primary) PS1、PS2PS1, PS2 DS2DS2
DS2 (主要)DS2 (primary) PS3PS3 DS3DS3
DS2 (次要)DS2 (secondary) DS1DS1 DS3DS3
DS3 (主要)DS3 (primary) PS4PS4 DS4DS4
DS3 (次要)DS3 (secondary) DS2DS2 DS4DS4
DS4DS4 DS3DS3 -

四部 DPM 伺服器的鏈結替代案例

循環保護Cyclic protection

如果您不要使用次要伺服器,您可以讓兩部 DPM 伺服器彼此保護。If you don't want to use a secondary server then two DPM servers can protect each other.

案例 3:循環保護Scenario 3: Cyclic protection

案例 3 顯示使用循環保護的案例Scenario 3 shows a scenario using cyclic protection

伺服器Server 保護Protecting 受下列項目保護Protected by
DS1 (主要)DS1 (primary) PS1、PS2PS1, PS2 DS2DS2
DS2 (主要)DS2 (primary) PS3PS3 DS3DS3
DS2 (次要)DS2 (secondary) DS1、DS3DS1, DS3 DS3DS3
DS3 (主要)DS3 (primary) PS4PS4 DS2DS2
DS3 (次要)DS3 (secondary) DS2DS2 DS2DS2

循環保護案例範例

設定鏈結Configure chaining

設定鏈結,如下所示:Set up chaining as follows:

  1. 在要保護的 DPM 伺服器上安裝 DPM 保護代理程式 (從您要用來保護前述伺服器的 DPM 伺服器安裝)。Install the DPM protection agent on the DPM server that you want to protect from the DPM server you want to protect it from.

  2. 針對由您保護之 DPM 伺服器所保護的資料來源,設定次要保護。Configure secondary protection for the data sources protected by the DPM server you are protecting. 請注意,在 DPM 主控台中,針對已受代理程式保護的資料來源,您將無法設定保護。Note in the DPM console you won't be able to configure protection for data sources that are already protected by the agent. 這可防止重複保護資料。This prevents you from repeatedly protecting data.

  3. 例如,如果您有 DPM1 和 DPM2,要將 DPM1 的 DPM 保護代理程式安裝到 DPM2,反之亦然。As an example, if you have DPM1 and DPM2 you'd install the DPM protection agent from DPM1 to DPM2 and vice versa. 然後在 DPM1 所保護之伺服器的 DPM2 上設定次要保護,且在 DPM2 所保護之伺服器的 DPM1 上設定次要保護。Then configure secondary protection on DPM2 for servers that DPM1 protects, and configure secondary protection on DPM1 for servers that DPM2 protects.

復原伺服器Recover the server

若主要伺服器失敗,您可以將保護切換到次要伺服器。If a primary server fails, you can switch protection to the secondary server. 在切換之後,您可以從次要伺服器執行復原功能。After switching, you can perform recovery functions from the secondary server.

將保護切換至次要伺服器Switch protection to the secondary server

使用下列步驟:Use the following steps:

  1. 在次要 DPM 伺服器上,在 DPM 管理主控台的 [保護] 區域,移至 [保護] 工作區、以滑鼠右鍵按一下您想要切換保護的 [資料來源]。On the secondary DPM server, in the Protection area of the DPM Administrator console, go to the Protection work area, right-click the data source for which, you want to switch protection.
  2. 從內容功能表中選取 [切換嚴重損壞狀況保護] 。Select Switch Disaster Protection from the context menu.
  3. 執行一致性檢查。Run a consistency check.

在切換保護之後,複本會顯示為不一致的狀態,直到檢查執行為止。After switching protection, the replica appears as inconsistent, until the check runs.

範例: 切換保護Example: Switch protection

注意

  • 若要將保護切換回主要伺服器,請執行與上面相同的步驟。To switch the protection back to the primary server, do the same steps as above.
  • 您也可以使用 Start –DPMSwitchProtection PowerShell Cmdlet,將保護切換至次要 DPM 服務器。You can also switch protection to the secondary DPM server by using the Start –DPMSwitchProtection PowerShell cmdlet.

復原主要 DPM 伺服器Recover a primary DPM server

當您復原主要 DPM 伺服器時,必須為主要 DPM 伺服器先前所保護的電腦重新建立保護。When you recover a primary DPM server, you’ll need to re-establish the protection for the computers that were previously protected by the primary DPM server. 請注意:Note that:

  • 您無法為主要 DPM 伺服器所保護的資料來源還原復原點。You can’t restore recovery points for data sources protected by the primary DPM server.
  • 當您復原資料庫檔案時,請確保主要 DPM 伺服器上的還原位置是安全的。When you recover the database files, ensure that the restore location on the primary DPM server is secure.

使用主要 DPM 服務器重新建立保護Re-establish protection with primary DPM server

  1. 在受保護的電腦上,從命令提示字元執行命令 Setdpmserver.exe <primary DPM server name>On the protected computer, from the command prompt, run the command Setdpmserver.exe <primary DPM server name> .

  2. 開啟 [電腦管理],並執行下列動作:Open Computer Management and do the following:

    • 選取 [本機使用者和群組] 。Select Local Users and Groups . 確認主要伺服器 (格式為網域/名稱) 是下列群組的成員:Verify that the primary server, in the format of Domain/Name, is a member of the following groups:
      • 散發 COM 使用者Distribute COM Users
      • DPMRADCOMTrustedMachinesDPMRADCOMTrustedMachines
      • DPMRADmTrustedMachinesDPMRADmTrustedMachines
    • 如果主要伺服器未列在任何群組中,請手動新增網域/名稱格式的伺服器。If the primary server isn’t not listed in any of the groups, manually add the server in the format of Domain/Name.

如果保護在完成上面的步驟後失敗,請執行下列動作:If protection fails after completing the above steps, do the following:

  1. 在 [系統管理工具] 中,開啟 [元件服務]。In Administrative Tools , open Component Services . 依序展開 [電腦] 、[我的電腦] ,然後按一下 [DCOM 設定] 。Expand Computers , expand My Computer , and then click DCOM Config .
  2. 在 [結果] 窗格中,以滑鼠右鍵按一下 [DPM RA 服務] 。In the results pane, right-click DPM RA Service . 按一下警示中的 [取得擁有權] > 。Click Properties > Security .
  3. 在 [啟動和啟用權限] 區域中,按一下 [編輯]。In the Launch and Activation Permissions area, click Edit .
    • 如果主要伺服器列出,表示存取控制清單 (ACL) 項目可能不正確。If the primary server is listed, the Access Control List (ACL) entry might be incorrect. 請移除該項目,然後新增具有完整權限的主要伺服器。Remove the entry, and then add the primary server with full permissions.
    • 如果主要伺服器未列出,請新增具有完整權限的主要伺服器。If the primary server is not listed, add the primary server with full permissions.

備份 DPM 資料庫Back up the DPM database

依據您的 DPM 備份策略,您必須備份 DPM 資料庫。As part of your DPM backup strategy, you'll have to back up the DPM database. DPM 資料庫名為 DPMDB。The DPM database is named DPMDB. 此資料庫包含 DPM 設定以及 DPM 備份的相關資料。This database contains the DPM configuration together with data about DPM's backups. 萬一嚴重損壞,您可以使用資料庫的最新備份來重建 DPM 伺服器的大部分功能。In case of disaster, you can rebuild most of the functionality of a DPM server by using a recent backup of the database. 假設您能夠還原資料庫,就可存取磁帶式備份,而此備份會維護所有保護群組設定以及備份排程。Assuming you can restore the database, tape- based backups are accessible, and they maintain all protection group settings and backup schedules. 如果 DPM 儲存集區磁碟並未受中斷影響,則重建後也可使用磁碟式備份。If the DPM storage pool disks were not affected by the outage, disk-based backups are also usable after a rebuild. 您可以使用不同的方法來備份資料庫。You can back up the database by using different methods.

資料庫備份方法Database backup method 優點Advantages 缺點Disadvantages
備份至 AzureBack up to Azure 在 DPM 中輕鬆設定及監視。Easily configured and monitored in DPM.

備份資料庫檔案位於多處。Multiple locations of the backup database files.

雲端儲存體提供強固的災害復原解決方案。Cloud storage provides a robust solution for disaster recovery.

資料庫的儲存體非常安全。Very secure storage for the database.

支援 120 個線上復原點。Supports 120 online recovery points.
只適用於 DPM 2012 SP1 或更新版本。Only available on DPM 2012 SP1 or later.

需要 Azure 帳戶和其他 DPM 組態。Requires Azure account and additional DPM configuration. 會產生一些 Azure 儲存體成本。Incurs some cost for Azure storage.

- 需要具有 Azure 代理程式的 Windows Server 系統支援版本,以便存取存放在 Azure 備份保存庫中的 DPM 備份。- Requires a supported version of Windows Server based system with the Azure agent to gain access to DPM backups stored in the Azure backup vault. 這不能是另一部 DPM 伺服器。This can't be another DPM server.

如果資料庫裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the database is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載資料庫。A workaround would be to use a remote SQL Server to host the database.

會產生一些額外的準備和復原時間。Some extra preparation and recovery time is incurred.
藉由備份 DPM 存放集區來備份資料庫Back up the database by backing up the DPM storage pool 容易設定和監視。Simple to configure and monitor.

備份會保留在 DPM 存放集區磁碟上,而且可輕易在本機存取。The backup is kept on the DPM storage pool disks and is easy to access locally.

DPM 排程的備份可支援 512 次快速完整備份。DPM scheduled backups support 512 express full backups. 如果您每小時進行備份,您將會有 21 天的完整保護。If you back up hourly you'll have 21 days of full protection.
不是很適合用於災害復原。Not a good option for disaster recovery. 它已上線,而如果 DPM 伺服器或存放集區磁碟故障,復原可能無法如預期般運作。It's online and recovery might not work as expected if the DPM server or storage pool disk fails.

如果資料庫裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the database is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載資料庫。A workaround would be to use a remote SQL Server to host the database.

需要進行一些準備和特殊步驟,才能在 DPM 服務或主控台未執行或沒作用時存取復原點。Some preparation and special steps are required to gain access to the recovery points if the DPM service or console isn't running or working.
備份至次要 DPM 伺服器Back up to a secondary DPM server 在 DPM 中輕鬆設定及監視。Easily configured and monitored in DPM.

DPM 排程的備份可支援 512 次快速完整備份。DPM scheduled backups support 512 express full backups. 如果每小時進行,這會提供 21 天的短期保護。If done hourly, this provides 21 days of short term protection. 如果每 30 分鐘完成一次,則會提供 10 天的保護。If done every 30 minutes, it provides 10 days of protection.

備份會保留在可在本機存取的次要 DPM 伺服器存放集區磁碟上。The backup is kept on the secondary DPM server storage pool disks which are locally accessible.

如果次要 DPM 伺服器在異地,則提供理想的災害復原解決方案。Provides a good disaster recovery solution if secondary DPM server is offsite.
需要其他 DPM 伺服器和儲存體。Additional DPM server and storage are required. 這兩部 DPM 伺服器都必須執行相同的 DPM 版本和更新彙總套件。Both DPM servers must to be running the same DPM version and update rollups.
備份至磁帶Back up to tape 在 DPM 中輕鬆設定及監視。Easily configured and monitored in DPM.

DPM 排程的磁帶備份可支援長達 99 年的保留時間。DPM scheduled tape backups support retention up to 99 years.

磁帶備份可在異地進行,以供災害復原。Tape backup can be taken offsite for disaster recovery.

您可以從任何其他已連接磁帶機/媒體櫃並使用相同磁帶媒體類型的 DPM 伺服器還原磁帶備份。Tape backup can be restored from any other DPM server that has a tape drive/library attached that uses the same tape media type.

磁帶可以進行加密以提供安全的儲存。Tape can be encrypted for secure storage.
如果資料庫裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the database is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載資料庫。A workaround would be to use a remote SQL Server to host the database.

每天只能安排一次磁帶備份。Only one tape backup per day can be scheduled.

您需要具有磁帶媒體櫃的運作中 DPM 伺服器,才能夠讀取包含您要還原之資料庫副本的 DPM 備份磁帶。You need a working DPM server with a tape library to be able to read a DPM backup tape that contains the copy of the database you want to restore.

需要進行一些準備和特殊步驟,才能存取以磁帶為基礎的復原點。Some preparation and special steps are required to gain access to the tape based recovery points.
利用原生 SQL Server 備份來備份到本機磁碟Back up with native SQL Server backup to a local disk 內建到 SQL Server 中。Built-in to SQL Server.

備份會保留在本機磁碟,以便輕易存取。The backup is kept on a local disk which is easily accessible.

可以依您要的執行頻率排程。It can be scheduled to run as often as you like.

與 DPM 完全無關。Totally independent of DPM.

您可以排程備份檔案清理。You can schedule a backup file cleanup.
除非將備份複製到遠端位置,否則不是很適合用於災害復原。Not a good option for disaster recovery unless the backups are copied to a remote location.

可能會限制保留時間和頻率的備份需要本機儲存體。Requires local storage for backups which may limit retention and frequency.
利用原生 SQL 備份與 DPM 保護備份至 DPM 保護的共用Back up with native SQL backup and DPM protection to a share protected by DPM 在 DPM 中輕鬆監視。Easily monitored in DPM.

備份資料庫檔案位於多處。Multiple locations of the backup database files.

可輕易地從網路上的任何 Windows 電腦存取。Easily accessible from any Windows machine on the network.

可能是最快的復原方法。Potentially the fastest recovery method.
僅支援 64 個復原點。Only supports 64 recovery points.

不是很適合用於網站災害復原。Not a good option for site disaster recovery. DPM 伺服器或 DPM 存放集區磁碟故障可能會妨礙復原工作。DPM server or DPM storage pool disk failure may hinder recovery efforts.

如果 DPM DB 裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the DPM DB is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載 DPMDB。A workaround would be to use a remote SQL Server to host the DPMDB.

需要進行一些額外的準備工作,才能加以設定和測試。Some extra preparation is needed to get it configured and tested.

如果 DPM 伺服器本身已關閉,但 DPM 存放集區磁碟是正常的,則需要一些額外的準備和復原時間。Some extra preparation and recovery time is needed should the DPM server itself be down but DPM storage pool disks are fine.
資料庫備份方法Database backup method 優點Advantages 缺點Disadvantages
備份至 AzureBack up to Azure 在 DPM 中輕鬆設定及監視。Easily configured and monitored in DPM.

備份資料庫檔案位於多處。Multiple locations of the backup database files.

雲端儲存體提供強固的災害復原解決方案。Cloud storage provides a robust solution for disaster recovery.

資料庫的儲存體非常安全。Very secure storage for the database.

支援 120 個線上復原點。Supports 120 online recovery points.
只適用於 DPM 2012 SP1 或更新版本。Only available on DPM 2012 SP1 or later.

需要 Azure 帳戶和其他 DPM 組態。Requires Azure account and additional DPM configuration. 會產生一些 Azure 儲存體成本。Incurs some cost for Azure storage.

- 需要具有 Azure 代理程式的 Windows Server 系統支援版本,以便存取存放在 Azure 備份保存庫中的 DPM 備份。- Requires a supported version of Windows Server based system with the Azure agent to gain access to DPM backups stored in the Azure backup vault. 這不能是另一部 DPM 伺服器。This can't be another DPM server.

如果資料庫裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the database is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載資料庫。A workaround would be to use a remote SQL Server to host the database.

會產生一些額外的準備和復原時間。Some extra preparation and recovery time is incurred.
藉由備份 DPM 存放集區來備份資料庫Back up the database by backing up the DPM storage pool 容易設定和監視。Simple to configure and monitor.

備份會保留在 DPM 存放集區磁碟上,而且可輕易在本機存取。The backup is kept on the DPM storage pool disks and is easy to access locally.

DPM 排程的備份可支援 512 次快速完整備份。DPM scheduled backups support 512 express full backups. 如果您每小時進行備份,您將會有 21 天的完整保護。If you back up hourly you'll have 21 days of full protection.
不是很適合用於災害復原。Not a good option for disaster recovery. 它已上線,而如果 DPM 伺服器或存放集區磁碟故障,復原可能無法如預期般運作。It's online and recovery might not work as expected if the DPM server or storage pool disk fails.

如果資料庫裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the database is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載資料庫。A workaround would be to use a remote SQL Server to host the database.

需要進行一些準備和特殊步驟,才能在 DPM 服務或主控台未執行或沒作用時存取復原點。Some preparation and special steps are required to gain access to the recovery points if the DPM service or console isn't running or working.
備份至次要 DPM 伺服器Back up to a secondary DPM server 在 DPM 中輕鬆設定及監視。Easily configured and monitored in DPM.

DPM 排程的備份可支援 512 次快速完整備份。DPM scheduled backups support 512 express full backups. 如果每小時進行,這會提供 21 天的短期保護。If done hourly, this provides 21 days of short term protection. 如果每 30 分鐘完成一次,則會提供 10 天的保護。If done every 30 minutes, it provides 10 days of protection.

備份會保留在可在本機存取的次要 DPM 伺服器存放集區磁碟上。The backup is kept on the secondary DPM server storage pool disks which are locally accessible.

如果次要 DPM 伺服器在異地,則提供理想的災害復原解決方案。Provides a good disaster recovery solution if secondary DPM server is offsite.
需要其他 DPM 伺服器和儲存體。Additional DPM server and storage are required. 這兩部 DPM 伺服器都必須執行相同的 DPM 版本和更新彙總套件。Both DPM servers must to be running the same DPM version and update rollups.
備份至磁帶Back up to tape 在 DPM 中輕鬆設定及監視。Easily configured and monitored in DPM.

DPM 排程的磁帶備份可支援長達 99 年的保留時間。DPM scheduled tape backups support retention up to 99 years.

磁帶備份可在異地進行,以供災害復原。Tape backup can be taken offsite for disaster recovery.

您可以從任何其他已連接磁帶機/媒體櫃並使用相同磁帶媒體類型的 DPM 伺服器還原磁帶備份。Tape backup can be restored from any other DPM server that has a tape drive/library attached that uses the same tape media type.

磁帶可以進行加密以提供安全的儲存。Tape can be encrypted for secure storage.
如果資料庫裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the database is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載資料庫。A workaround would be to use a remote SQL Server to host the database.

每天只能安排一次磁帶備份。Only one tape backup per day can be scheduled.

您需要具有磁帶媒體櫃的運作中 DPM 伺服器,才能夠讀取包含您要還原之資料庫副本的 DPM 備份磁帶。You need a working DPM server with a tape library to be able to read a DPM backup tape that contains the copy of the database you want to restore.

需要進行一些準備和特殊步驟,才能存取以磁帶為基礎的復原點。Some preparation and special steps are required to gain access to the tape based recovery points.
利用原生 SQL Server 備份來備份到本機磁碟Back up with native SQL Server backup to a local disk 內建到 SQL Server 中。Built-in to SQL Server.

備份會保留在本機磁碟,以便輕易存取。The backup is kept on a local disk which is easily accessible.

可以依您要的執行頻率排程。It can be scheduled to run as often as you like.

與 DPM 完全無關。Totally independent of DPM.

您可以排程備份檔案清理。You can schedule a backup file cleanup.
除非將備份複製到遠端位置,否則不是很適合用於災害復原。Not a good option for disaster recovery unless the backups are copied to a remote location.

可能會限制保留時間和頻率的備份需要本機儲存體。Requires local storage for backups which may limit retention and frequency.
利用原生 SQL 備份與 DPM 保護備份至 DPM 保護的共用Back up with native SQL backup and DPM protection to a share protected by DPM 在 DPM 中輕鬆監視。Easily monitored in DPM.

備份資料庫檔案位於多處。Multiple locations of the backup database files.

可輕易地從網路上的任何 Windows 電腦存取。Easily accessible from any Windows machine on the network.

可能是最快的復原方法。Potentially the fastest recovery method.
僅支援 64 個復原點。Only supports 64 recovery points.

不是很適合用於網站災害復原。Not a good option for site disaster recovery. DPM 伺服器或 DPM 存放集區磁碟故障可能會妨礙復原工作。DPM server or DPM storage pool disk failure may hinder recovery efforts.

如果 DPM DB 裝載在本機,而且您想要啟用次要保護,則不適用這個選項。Not an option if the DPM DB is hosted locally and you want to enable secondary protection. 因應措施就是使用遠端 SQL Server 來裝載 DPMDB。A workaround would be to use a remote SQL Server to host the DPMDB.

需要進行一些額外的準備工作,才能加以設定和測試。Some extra preparation is needed to get it configured and tested.

如果 DPM 伺服器本身已關閉,但 DPM 存放集區磁碟是正常的,則需要一些額外的準備和復原時間。Some extra preparation and recovery time is needed should the DPM server itself be down but DPM storage pool disks are fine.
  • 如果您使用 DPM 保護群組進行備份,建議您針對資料庫使用唯一的保護群組。If you back up by using a DPM protection group, we recommend that you use a unique protection group for the database.

  • 如果您備份到磁帶,最佳做法是為備份磁帶建立至少兩份複本,並將每個備份磁帶存放在不同的遠端位置。As a best practice, if you're backing up to tape, make at least two copies of the backup tapes, and store each of the backup tapes in a different remote location. 這個新增的保護會防護備份磁帶,避免發生實體損壞或遺失。This added protection guards against physical damage or loss of the backup tape.

  • 如果 DPM SQL Server 執行個體並未在 DPM 伺服器上執行,請先在 SQL Server 電腦上安裝 DPM 保護代理程式,您才可以保護該伺服器上的 DPM 資料庫。If the DPM SQL Server instance isn't running on the DPM server, install the DPM protection agent on the SQL Server computer before you can protect the DPM databases on that server.

    注意

    為了進行還原,您要使用 DPM 資料庫還原的 DPM 安裝必須符合 DPM 資料庫本身的版本。For restore purposes, the DPM installation you want to restore with the DPM database must match the version of the DPM database itself. 例如,如果您要復原的資料庫是安裝自 DPM 2016 含更新彙總套件 4,則 DPM 伺服器必須執行含更新彙總套件 4 的相同版本。For example, if the database you want to recover is from a DPM 2016 with Update Rollup 4 installation, the DPM server must be running the same version with Update Rollup 4. 這表示您可能必須先解除安裝再重新安裝版本相容的 DPM,才能還原資料庫。This means that you might have to uninstall and reinstall DPM with a compatible version before you restore the database. 若要檢查資料庫版本,您可能需要手動將其裝載到暫存資料庫名稱,然後針對資料庫執行 SQL 查詢,根據主要與次要版本檢查最新安裝的更新彙總套件。To check the database version you might have to mount it manually to a temporary database name and then run a SQL query against the database to check the last installed rollup, based on the major and minor versions.

  • 若要檢查 DPM 資料庫版本,請遵循下列步驟:To check the DPM database version, follow these steps:

    1. 若要執行查詢,請開啟 SQL Management Studio,並連接到執行 DPM 資料庫的 SQL 執行個體。To run the query, open SQL Management Studio, and then connect to the SQL instance that's running the DPM database.

    2. 選取 DPM 資料庫,然後開始新的查詢。Select the DPM database, and then start a new query.

    3. 將下列 SQL 查詢貼入查詢窗格中執行:Paste the following SQL query into the query pane and run it:

      從 dbo.tbl_AM_AgentPatch 順序中,依 MajorVersionNumber、MinorVersionNumber、BuildNumber 選取不同的 MajorVersionNumber、MinorVersionNumber、BuildNumber、FileNameSelect distinct MajorVersionNumber,MinorVersionNumber ,BuildNumber, FileName FROM dbo.tbl_AM_AgentPatch order byMajorVersionNumber,MinorVersionNumber,BuildNumber

    查詢結果若未傳回任何內容,或若 DPM 伺服器已從舊版升級,但其後即未安裝任何新的更新彙總套件,則不會有主要、次要的 DPM 基底安裝項目。If nothing is returned in the query results, or if the DPM server was upgraded from previous versions but no new update rollup was installed since then, there won't be an entry for the major, minor for a base installation of DPM. 若要檢查與更新彙總套件的相關聯 DPM 版本,請參閱 System Center Data Protection Manager: List of Build Numbers (System Center Data Protection Manager 的組建編號清單)。To check the DPM versions associated with update rollups see List of Build Numbers for System Center Data Protection Manager (DPM).

備份至 AzureBack up to Azure

  1. 開始前,您需要執行擷取 DPM 複本磁碟區掛接點路徑的指令碼,才能知道哪個復原點包含 DPM 備份。Before you start you'll need to run a script to retrieve the DPM replica volume mount point path so that you know which recovery point contains the DPM backup. 請在 Azure 備份完成初始複寫後執行這項操作。Do this after initial replication with Azure Backup. 將指令碼的 dplsqlservername% 替換成裝載 DPM 資料庫的 SQL Server 執行個體名稱。In the script replace dplsqlservername% with the name of the SQL Server instance hosting the DPM database.

    Select ag.NetbiosName as ServerName,ds.DataSourceName,vol.MountPointPath
    from tbl_IM_DataSource as ds
    join tbl_PRM_LogicalReplica as lr on ds.DataSourceId=lr.DataSourceId
    join tbl_AM_Server as ag on ds.ServerId=ag.ServerId
    join tbl_SPM_Volume as vol on lr.PhysicalReplicaId=vol.VolumeSetID
    and vol.Usage =1
    and lr.Validity in (1,2)
    where ds.datasourcename like '%dpmdb%'
    and servername like '%dpmsqlservername%' --netbios name of server hosting DPMDB
    

    確定您有在安裝 Azure Recovery Services 代理程式時所指定的密碼,而且已在 Azure 備份保存庫中註冊 DPM 伺服器。Make sure you have the passcode that was specified when the Azure Recovery Services Agent was installed and the DPM server was registered in the Azure Backup vault. 您將需有此密碼,才能還原備份。You'll need this passcode to restore the backup.

  2. 建立 Azure 備份保存庫,下載 Azure 備份代理程式安裝檔案和保存庫認證。Create an Azure Backup vault, download the Azure Backup Agent installation file and vault credentials. 執行安裝檔案以在 DPM 伺服器上安裝代理程式,然後使用保存庫認證在保存庫中註冊伺服器。Run the installation file to install the agent on the DPM server and use the vault credentials to register the DPM server in the vault. 深入了解Learn more.

  3. 設定保存庫後,請設定包含 DPM 資料庫的 DPM 保護群組,然後選擇將它備份到磁碟和 Azure。After the vault is configured set up a DPM protection group that contains the DPM database, and select to back it up to disk and to Azure.

從 Azure 復原 DPM 資料庫Recover the DPM database from Azure

您可以使用任何已向 Azure 備份保存庫註冊的 DPM 伺服器 (至少必須執行 DPM 2012 R2 與更新彙總套件 7),從 Azure 復原資料庫,如下所示︰You can recover the database from Azure using any DPM server (must be running at least DPM 2012 R2 with update rollup 7) that's registered in the Azure Backup vault, as follows:

  1. 在 DPM 主控台中,按一下 [復原] > [新增外部 DPM] 。in the DPM console click Recovery > Add External DPM .

  2. 提供保存庫認證 (從 Azure 備份保存庫下載)。Provide the vault credentials (download from the Azure Backup vault). 請注意,認證的有效期僅有兩天。Note that the credentials are only valid for two days.

  3. 在 [選取外部 DPM 進行復原] 中選取您要復原資料庫的 DPM 伺服器,輸入加密複雜密碼,然後按一下 [確定] 。In Select External DPM for Recovery select the DPM server for which you want to recover the database, type in the encryption passphrase, and click OK.

  4. 從可用復原點清單中選取您要使用的復原點。Select the recovery point you want to use from the list of available points. 若要回到本機 DPM 檢視,請按一下 [清除外部 DPM] 。Click Clear External DPM to return to the local DPM view.

將 DPM 資料庫備份到 DPM 存放集區Back up the DPM database to DPM storage pool

注意

此選項適用於搭配 Modern Backup Storage 的 DPM。This option is applicable for DPM with Modern Backup Storage.

  1. 在 DPM 主控台中,按一下 [保護] > [建立保護群組] 。In DPM console, click Protection > Create protection group .
  2. 在 [選擇保護群組類型] 頁面上,選取 [伺服器] 。On the Select Protection Group Type page, select Servers .
  3. 在 [選取群組成員] 頁面中,選取 [DPM 資料庫] 。On the Select group members page, select DPM database . 如果您從遠端執行 SQL Server,請選取已安裝的遠端 SQL Server,然後選取 [DPM 資料庫]。If you're running SQL Server remotely, select the remote SQL Server installed and select DPM database. 如果 SQL Server 正在 DPM 伺服器上執行,請展開 DPM 伺服器,然後選取 [DPMDB]。If SQL Server is running on the DPM server, expand the DPM server and select DPMDB.
  4. 在 [選擇資料保護方式] 頁面上,選取 [我想要使用磁碟短期保護] 。On the Select Data Protection Method page, select I want short-term protection using disk . 指定短期保護原則選項。Specify the short-term protection policy options.
  5. 初始複寫 DPM 資料庫之後,執行下列 SQL 指令碼:After initial replication of DPM database, run the following SQL script:
select AG.NetbiosName, DS.DatasourceName, V.AccessPath, LR.PhysicalReplicaId from tbl_IM_DataSource DS
join tbl_PRM_LogicalReplica as LR
on DS.DataSourceId = LR.DataSourceId
join tbl_AM_Server as AG
on DS.ServerId=AG.ServerId
join tbl_PRM_ReplicaVolume RV
on RV.ReplicaId = LR.PhysicalReplicaId
join tbl_STM_Volume V
on RV.StorageId = V.StorageId
where datasourcename like N'%dpmdb%' and ds.ProtectedGroupId is not null
and LR.Validity in (1,2)
and AG.ServerName like N'%<dpmsqlservername>%' -- <dpmsqlservername> is a placeholder, put netbios name of server hosting DPMDB

復原 DPM 資料庫Recover DPM database

若要使用相同 DB 重新建構 DPM,您需要先復原 DPM 資料庫,並使用全新安裝的 DPM 同步。To reconstruct your DPM with the same DB, you need to first recover the DPM database and sync it with the freshly installed DPM.

請使用下列步驟Use the following steps

  1. 開啟系統管理命令提示字元並執行 psexec.exe -s powershell.exe ,在系統內容中啟動 PowerShell 視窗。Open an administrative command prompt and run psexec.exe -s powershell.exe to start a PowerShell window in system context.
  2. 依您要復原的資料庫決定位置:Decide the location from where you want to recover the database:

若要從最後一次備份中複製資料庫To copy the database from the last backup

  1. 瀏覽至複本 VHD 路徑 <DPMServer FQDN><PhysicalReplicaId><PhysicalReplicaId>Navigate to replica VHD path <DPMServer FQDN><PhysicalReplicaId><PhysicalReplicaId>
  2. 使用 mount-vhd disk0.vhdx 命令裝載出現的 disk0.vhdx。Mount the disk0.vhdx present in it using mount-vhd disk0.vhdx command.
  3. 裝載複本 VHD 之後,透過 mountvol.exe 使用來自 SQL 指令碼輸出的實體複本識別碼,將磁碟機代號指派給複本磁碟區。Once replica VHD is mounted, use mountvol.exe to assign a drive letter to the replica volume using the Physical replica ID from the SQL script output. 例如:mountvol X: ?\Volume{}For example: mountvol X: ?\Volume{}\

若要從先前的復原點複製資料庫To copy the database from a previous recovery point

  1. 瀏覽至 DPMDB 的容器目錄 <DPMServer FQDN><PhysicalReplicaId> ,您會在其下看到多個具備某些唯一 GUID 識別碼的目錄,這些目錄均分別對應至 DPM DB 使用的各個復原點。Navigate to DPMDB container directory <DPMServer FQDN><PhysicalReplicaId> , you will see multiple directories with some unique GUID identifiers under it corresponding recovery points taken for DPM DB. 其他目錄則表示 PIT/復原點。Directories other than represents a PIT/recovery point.

  2. 瀏覽至任何 PIT VHD 路徑,例如 <DPMServer FQDN><PhysicalReplicaId><PITId> ,並使用 mount-vhd disk0.vhdx 命令裝載出現的 disk0.vhdx。Navigate to any PIT vhd path i.e. <DPMServer FQDN><PhysicalReplicaId><PITId> and mount the disk0.vhdx present in it using mount-vhd disk0.vhdx command.

  3. 裝載複本 VHD 之後,透過 mountvol.exe 使用來自 SQL 指令碼輸出的實體複本識別碼,將磁碟機代號指派給複本磁碟區。Once replica VHD is mounted, use mountvol.exe to assign a drive letter to the replica volume, using the Physical replica ID from the SQL script output. 例如:mountvol X: ?\Volume{}For example: mountvol X: ?\Volume{}\

    在上述步驟中所有以大括號括起來的文字均為預留位置,請以適當的值取代。All of the following text with angular braces in the above steps are place holders, replace them with appropriate values.

    • ReFSVolume - SQL 指令碼輸出中的存取路徑ReFSVolume - Access path from the SQL script output
    • DPMServer FQDN - DPM 伺服器的完整名稱DPMServer FQDN - Fully qualified name of DPM server
    • PhysicalReplicaId - SQL 指令碼輸出中的實體複本識別碼PhysicalReplicaId - Physical replica ID from the SQL script out
    • PITId - 不同於容器目錄中實體複本識別碼的 GUID 識別碼。PITId - GUID identifier other than physical replica ID in the container directory.
  4. 開啟另一個系統管理命令提示字元並執行 psexec.exe -s cmd.exe ,在系統內容中啟動命令提示字元。Open another administrative command prompt and run psexec.exe -s cmd.exe to start a command prompt in system context.

  5. 將目錄變更為 X: 磁碟機,並瀏覽到 DPM 資料庫檔案的位置。Change directory to the X: drive and navigate to the location of the DPM database files.

  6. 請將它們複製到可輕鬆執行還原的位置。Copy them to a location that's easy to restore from. 複製之後,結束 psexec cmd 視窗。Exit the psexec cmd window after you copy.

  7. 前往在步驟 1 中開啟的 psexec PowerShell 視窗,瀏覽至 VHDX 路徑,並使用 dismount-vhd disk0.vhdx 命令卸載 VHDX。Go to the psexec PowerShell window opened in step one, navigate to the VHDX path, and dismount the VHDX by using the command dismount-vhd disk0.vhdx .

  8. 重新安裝 DPM 伺服器之後,您可以執行 DPMSYNC-RESTOREDB 命令,使用還原的 DPMDB 連結至 DPM 伺服器。After reinstalling the DPM server, you can use the restored DPMDB to attach to the DPM server by running DPMSYNC-RESTOREDB command.

  9. DPMSYNC-RESTOREDB 完成之後,請執行 DPMSYNC-SYNCRun DPMSYNC-SYNC once DPMSYNC-RESTOREDB is complete.

藉由備份 DPM 存放集區來備份資料庫Back up the database by backing up the DPM storage pool

注意

此選項適用於搭配舊版儲存體的 DPM。This option is applicable for DPM with legacy storage.

開始前,您需要執行擷取 DPM 複本磁碟區掛接點路徑的指令碼,才能知道哪個復原點包含 DPM 備份。Before you start you'll need to run a script to retrieve the DPM replica volume mount point path so that you know which recovery point contains the DPM backup. 請在 Azure 備份完成初始複寫後執行這項操作。Do this after initial replication with Azure Backup. 將指令碼的 dplsqlservername% 替換成裝載 DPM 資料庫的 SQL Server 執行個體名稱。In the script replace dplsqlservername% with the name of the SQL Server instance hosting the DPM database.

Select ag.NetbiosName as ServerName,ds.DataSourceName,vol.MountPointPath
from tbl_IM_DataSource as ds
join tbl_PRM_LogicalReplica as lr on ds.DataSourceId=lr.DataSourceId
join tbl_AM_Server as ag on ds.ServerId=ag.ServerId
join tbl_SPM_Volume as vol on lr.PhysicalReplicaId=vol.VolumeSetID
and vol.Usage =1
and lr.Validity in (1,2)
where ds.datasourcename like '%dpmdb%'
and servername like '%dpmsqlservername%' --netbios name of server hosting DPMDB
  1. 在 DPM 主控台中,依序按一下 [保護] > [建立保護群組] In DPM console, click Protection > Create protection group

  2. 在 [選擇保護群組類型] 頁面上,選取 [伺服器] 。On the Select Protection Group Type page, select Servers .

  3. 在 [選取群組成員] 頁面上,選取 DPM 資料庫。On the Select group members page, select the DPM database. 如果您從遠端執行 SQL Server,請選取已安裝的遠端 SQL Server,然後選取 [DPM 資料庫]。If you're running SQL Server remotely select the remote SQL Server installed and select DPM database. 如果 SQL Server 正在 DPM 伺服器上執行,請展開 DPM 伺服器項目,然後選取 [DPMDB] 。If SQL Server is running on the DPM server expand the DPM server item and select DPMDB .

  4. 在 [選擇資料保護方式] 頁面上,選取 [我想要以磁碟短期保護] 。On the Select Data Protection Method page, select I want short-term protection using disk . 指定短期保護原則選項。Specify the short-term protection policy options. DPM 資料庫的保留範圍建議為 2 週。We recommend a retention range of two weeks for DPM databases.

復原資料庫Recover the database

假設 DPM 伺服器本身仍可運作且存放集區保持不變 (但 DPM 服務或主控台有問題),請從複本磁碟區或陰影複製來複製資料庫,如下所示:If the DPM server is still operational and the storage pool is intact (problems with the DPM service or console) then copy the database from the replica volume or a shadow copy as follows:

  1. 決定您要復原資料庫的時間。Decide from when you want to recover the database.

    • 如果您想要從直接取自 DPM 複本磁碟區的上次備份中複製資料庫,請使用 mountvol.exe 將磁碟機代號指派給使用 SQL 指令碼輸出中 GUID 的複本磁碟區。If you want to copy the database from the last backup taken directly from the DPM replica volume, use mountvol.exe to assign a drive letter to the replica volume using the GUID from the SQL script output. 例如:C:\Mountvol X: \\?\Volume{d7a4fd76-a0a8-11e2-8fd3-001c23cb7375}For example: C:\Mountvol X: \\?\Volume{d7a4fd76-a0a8-11e2-8fd3-001c23cb7375}\

    • 如果您想要從先前的復原點 (陰影複製) 複製資料庫,則必須針對使用 SQL 指令碼輸出中磁碟區 GUID 的複本列出所有的陰影複製。If you want to copy the database from a previous recovery point (shadow copy) then you need to list all the shadow copies for the replica using the volume GUID from the SQL script output. 此命令會列出該磁碟區的陰影複製:C:\>Vssadmin list shadows /for=\\?\Volume{d7a4fd76-a0a8-11e2-8fd3-001c23cb7375}\。This command lists shadow copies for that volume: C:\>Vssadmin list shadows /for=\\?\Volume{d7a4fd76-a0a8-11e2-8fd3-001c23cb7375}\. 請記下您想要復原的 [建立時間] 和 [陰影複製識別碼]。Note the creation time and the shadow copy ID you want to recover from.

  2. 然後使用陰影複製識別碼,以 diskshadow.exe 來將陰影複製裝載到未使用的磁碟機代號 X:,以便您複製資料庫檔案。Then use diskshadow.exe to mount the shadow copy to an unused drive letter X: using the shadow copy ID so that you can copy the database files.

  3. 開啟系統管理命令提示字元並執行 psexec.exe -s cmd.exe ,在系統內容中啟動命令提示字元,您便可擁有巡覽複本磁碟區 (X:) 的權限以複製檔案。Open an administrative command prompt and run psexec.exe -s cmd.exe to start a command prompt in system context so that you have permission to navigate to the replica volume (X:) and copy the files.

  4. CD 到 X: 磁碟機,並巡覽到 DPM 資料庫檔案的位置。CD to the X: drive and navigate to the location of the DPM database files. 請將它們複製到可輕鬆執行還原的位置。Copy them to a location that's easy to restore from. 複製完成之後,結束 psexec cmd 視窗,並執行 diskshadow.exe 且取消公開 X: 磁碟區。After the copy is complete exist the psexec cmd window, and run diskshadow.exe and unexpose the X: volume.

  5. 現在使用 SQL Management Studio 或執行 DPMSYNC-RESTOREDB,即可還原資料庫檔案。Now you can restore the database files by using SQL Management Studio or by running DPMSYNC-RESTOREDB.

將資料庫備份至次要伺服器Back up the database to a secondary server

  1. 在次要 DPM 伺服器上,將保護代理程式推送至 DPM 資料庫安裝所在的伺服器 – 在主要 DPM 伺服器上或在遠端 SQL Server 伺服器上。On the secondary DPM server push the protection agent to the server on which the DPM database is installed - either on the primary DPM server or on a remote SQL Server. 安裝之後,伺服器將出現在 [具有保護代理程式的未受保護伺服器] 中,並在重新整理後顯示 [確定] 狀態。After installation the server will appear in Unprotected server with protection agents and should show status OK when refreshed.

  2. 建立新的保護群組。Create a new protection group. 在 [選取群組成員] ,選擇裝載 DPM 資料庫的伺服器。In Select group member choose the server hosting the DPM database. 在 [所有 SQL Server] 中,選取您要保護的資料庫。In All SQL Servers select the database you want to protect. 在 [選擇資料保護方式] 頁面上,視需要選取使用磁碟短期保護及上線。In the Select Data Protection Method page select to use short-term protection to disk and online if required. 在 [指定短期目標] 頁面上,選取您要如何設定備份到短期儲存體。On the Specify Short-Term Goals page select how to you want configure backups to short-term storage. 對於磁碟儲存體,您每隔 30 分鐘可以有 512 個快速完整備份。For disk storage you can have 512 express full backups as often as every 30 minutes. 完成精靈。Finish the wizard. 建立初始復原點之後,將會開始提供保護。Protection will start after the initial recovery point is created

復原資料庫Recover the database

  1. 必要時,將主要伺服器重建為 DPM 伺服器。Rebuild the primary server as a DPM server if required.

  2. 若要還原資料庫,請在次要伺服器的 DPM 主控台中,按一下 [復原] 並找到受保護的資料庫。To restore the database, in the DPM console on the secondary server, click Recovery and locate the protected database.

  3. 選取要復原之復原點的日期。Select the date for the recovery point you want to recover. 將資料庫復原到原始位置。Recover the database to the original location. 復原資料庫之後,請執行 DPMSync 工具。After recovering the database run the DPMSync tool.

將資料庫備份到磁帶Back up the database to tape

您必須知道含有一份 DPM 資料庫複本之磁帶的條碼或磁帶標籤。You'll need to know the barcode or tape labels of the tapes that contain a copy of the DPM database. 若要執行這項操作,最好是安排在 DPM 資料庫進行備份的同一天郵寄「狀態報表」。The best way to do this is to schedule a Status Report to be mailed on the same day that the DPM database is backed up. 此報表將包含上次備份日期/時間、磁帶標籤和條碼,以便您可找到備份進行復原。The report will include the last backup date/time, the tape label and the barcode so that you can locate it for recovery. 此外,您可以使用這個 SQL 指令碼來擷取目前資料庫中的資訊,如此即可在發生災害時分開存放資訊。Alternatively you can use this SQL script to extract the information from the current database so you can to store it separately in case of disaster.

Select Path,ro.FileSpec,media.Label,media.BarcodeValue,pd.CreationDate,
pd.ExpiryDate,pd.LifeStatus as "1=valid, 2=expired"
from dbo.tbl_MM_MediaMap mm
join dbo.tbl_MM_PhysicalDataset pd on pd.datasetid = mm.datasetid
join dbo.tbl_MM_Media media on media.MediaId = mm.MediaId
join dbo.tbl_RM_RecoverableObjectFileSpec ro on ro.DatasetId = mm.DatasetId
where ro.filespec like '%DPMDB%'
order by CreationDate desc
  1. 建立保護群組,並在 [選擇群組成員] 頁面中選取 SQL Server (如果它在本機執行,請選取 DPM 伺服器下的 DPMDB)。Create a protection group and on the Select Group Members page select the SQL Server (if it's running locally select DPMDB under the DPM server).

  2. 選擇執行磁帶長期保護,並在 [選取媒體櫃和磁帶詳細資料] 中指定磁帶詳細資料。Select to do long-term protection with tape and specify the tape details on the Select Library and Tape Details .

復原資料庫Recover the database

  • 還原程序將取決於可用的磁帶硬體以及採用磁帶型備份之 DPM 伺服器的目前狀態。The restore process will depend on the tape hardware available and the current state of the DPM server that took the tape-based backup. 如果您無法從執行備份的 DPM 伺服器還原磁帶,則必須從另一部具有同類型磁帶機的 DPM 伺服器進行還原,以便讀取磁帶。If you can't restore the tape from the DPM server that did the backup, you'll need to restore it from another DPM server that has the same type of tape drive so that the tape can be read. 如果唯一可用的磁帶硬體是連接到故障 DPM 伺服器的磁帶,您可能需要重建 DPM 伺服器。You might need to rebuild the DPM server if the only tape hardware available was the one attached to the failed DPM server.

  • 如果您使用 DPM 磁帶加密,則需要在替代 DPM 伺服器上安裝用來加密磁帶的相同憑證。If you're using DPM tape encryption, you'll need the same certificate used to encrypt the tape installed on the alternate DPM server.

若要復原,請:To recover:

  1. 找出包含您要還原之 DPM 資料庫的版本/日期/時間的實體磁帶。Locate the physical tape that contains the version/date/time of the DPM database you want to restore.

  2. 將備份磁帶插入到磁帶機或媒體櫃中,並在 DPM 主控台 -> [管理] -> [媒體櫃] 中執行詳細的清查。Insert the backup tape into the tape drive or library and perform a detailed inventory in the DPM console -> Management ->Libraries. 請注意,如果您作為還原來源的 DPM 伺服器是不同的 DPM 伺服器,或是在原始伺服器上新安裝的 DPM,則磁帶會顯示為 [已匯入] (不是由此 DPM 伺服器建立)。Note that If the DPM server you are restoring from is a different DPM server, or it's a new installation of DPM on the original server, the tape will be shown as imported (not created by this DPM server).

  3. 如有需要,請重新編目已匯入的磁帶。If necessary, re-catalog the imported tape.

  4. 在 [復原] 索引標籤上,找出資料庫的資料來源。On the Recovery tab, locate the database data source. 如果資料來自已匯入的磁帶,則復原點會在 [外部 DPM 磁帶] 之下。If it was from an imported tape, the recovery point will be under External DPM tapes .

  5. 復原資料庫 (DPMDB) 檔案。Recover the database (DPMDB) files. 您可以選擇 [復原到任何 SQL Server 執行個體] 或 [複製到網路資料夾]。You can select to Recover to any instance of SQL Server or to Copy to a network folder. 從磁帶還原檔案之後,請使用 SQL Management Studio 或 DPMSYNC -RESTOREDB 繼續執行復原步驟。After the files are restored from tape, continue with recovery steps using SQL Management Studio or DPMSYNC -RESTOREDB.

利用原生 SQL Server 備份來備份到本機磁碟Back up with native SQL Server backup to a local disk

您只要利用原生 SQL Server 備份將 DPM 資料庫備份到本機磁碟,與 DPM 無關。You can simply back up the DPM database to a local disk with native SQL Server backup, independent of DPM.

  1. 取得 SQL Server 備份的概觀Get an overview of SQL Server backup.

  2. 深入了解如何將 SQL Server 備份至雲端。Learn more about backing up SQL Server to the cloud.

利用原生 SQL Server 備份來備份至 DPM 所保護的共用Back up with native SQL Server backup to a share protected by DPM

此備份選項運用原生 SQL 將 DPM 資料庫備份到共用,使用 DPM 保護共用,以及使用舊版 Windows VSS 以利進行還原。This backup option leverages native SQL to back up the DPM database to a share, protects the share with DPM, and uses Windows VSS previous versions to facilitate the restore.

開始之前Before you start

  1. 如果 DPM 資料庫位於遠端 SQL Server 上,請在該伺服器上安裝 DPM 代理程式。If the DPM database is located on a remote SQL Server, install the DPM agent on that server.

  2. 在 SQL Server 上,讓磁碟機上的某個資料夾有足夠的可用空間來保存一份備份副本。On the SQL Server make a folder on a drive with enough free space to hold a single copy of a backup. 例如:C:\DPMBACKUP。For example: C:\DPMBACKUP.

  3. 共用此資料夾。Share the folder. 例如,將 C:\DPMBACKUP 資料夾共用為 DPMBACKUP。For example share C:\DPMBACKUP folder as DPMBACKUP.

  4. 將下面的 OSQL 命令複製並貼到 [記事本] 中,然後將它儲存到名為 C:\DPMBACKUP\bkupdb.cmd 的檔案。Copy and paste the OSQL command below into Notepad and save it to a file named C:\DPMBACKUP\bkupdb.cmd. 請確定沒有使用副檔名 .txt。Make sure there is no .txt extension. 修改 SQL_Instance_name 和 DPMDB_NAME 以符合您的 DPM 伺服器所使用的執行個體和 DPMDB 名稱。Modify the SQL_Instance_name andDPMDB_NAME to match the instance and DPMDB name used by your DPM server.

    OSQL -E -S localhost\SQL_INSTANCE_NAME -Q "BACKUP DATABASE DPMDB_NAME TO DISK='C:\DPMBACKUP\dpmdb.bak' WITH FORMAT"
    
    
  5. 使用 [記事本] 開啟位於 ...\DPM\Scripting 資料夾之下的 ScriptingConfig.xml 檔案。Using Notepad, open the ScriptingConfig.xml file located under the ...\DPM\Scripting folder.

    • 在遠端 SQL Server 上: C:\Program Files\Microsoft Data Protection Manager\DPM\ScriptingOn a remote SQL Server: C:\Program Files\Microsoft Data Protection Manager\DPM\Scripting

    • 在 DPM 伺服器上: C:\Program Files\Microsoft System Center\DPM\DPM\ScriptingOn a DPM server: C:\Program Files\Microsoft System Center\DPM\DPM\Scripting

  6. 修改 ScriptingConfig.xml 並將 DataSourceName= 變更為包含 DPMDBBACKUP 資料夾/共用的磁碟機代號。Modify ScriptingConfig.xml and change DataSourceName= to be the drive letter that contains the DPMDBBACKUP folder/share. 將 PreBackupScript 項目變更為在步驟 5 儲存之 thebkupdb.cmd 的完整路徑和名稱。Change the PreBackupScript entry to the full path and name of thebkupdb.cmd saved in step 5.

    <?xml version="1.0" encoding="utf-8"?>
    <ScriptConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="https://schemas.microsoft.com/2003/dls/ScriptingConfig.xsd">
    <DatasourceScriptConfig DataSourceName="C:">
    <PreBackupScript>C:\DPMDBBACKUP\bkupdb.cmd</PreBackupScript>
    <TimeOut>120</TimeOut>
    </DatasourceScriptConfig>
    </ScriptConfiguration>
    
  7. 將變更儲存至 ScriptingConfig.xml。Save the changes to ScriptingConfig.xml.

  8. 使用 DPM 保護 C:\DPMBACKUP 資料夾或 \\sqlservername\DPMBACKUP 共用,並等候建立初始複本。Protect the C:\DPMBACKUP folder or the \\sqlservername\DPMBACKUP share using DPM and wait for the initial replica to be created. 由於執行中的備份前指令碼會複製到 DPM 複本,所以 C:\DPMBACKUP 資料夾中應該有 dpmdb.bak。There should be a dpmdb.bak in the C:\DPMBACKUPfolder as a result of the pre-backup script running which was in turn copied to the DPM replica.

  9. 如果您未啟用自助式復原,則會需要進行一些額外步驟以共用複本上的 DPMBACKUP 資料夾:If you don't enable self-service recovery, you'll need some additional steps to share out the DPMBACKUP folder on the replica:

    1. 在 [DPM 主控台] > [保護] 中,找出 DPMBACKUP 資料來源並選取。In the DPM console > Protection , locate the DPMBACKUP data source and select it. 在詳細資料區段中,按一下複本路徑連結上的 [按一下檢視詳細資料] 並將此路徑複製到 [記事本]。In the details section, click Click to view details on the link to the replica path and copy the path into Notepad. 移除來源路徑並保留目的地路徑。Remove the source path and retain the destination path. 路徑看起來應該像下面這樣: C:\Program Files\Microsoft System Center\DPM\DPM\Volumes\Replica\File System\vol_c9aea05f-31e6-45e5-880c-92ce5fba0a58\454d81a0-0d9d-4e07-9617-d49e3f2aa5de\Full\DPMBACKUPThe path should look similar to the following: C:\Program Files\Microsoft System Center\DPM\DPM\Volumes\Replica\File System\vol_c9aea05f-31e6-45e5-880c-92ce5fba0a58\454d81a0-0d9d-4e07-9617-d49e3f2aa5de\Full\DPMBACKUP .

    2. 使用共用名稱 DPMSERVERNAME-DPMDB ,製作該路徑的共用。Make a share to that path using the share name DPMSERVERNAME-DPMDB . 您可以在系統管理命令提示字元中使用以下 Net Share 命令。You can use the Net Share command below from an administrative command prompt.

      Net Share DPMSERVERNAME-dpmdb="C:\Program Files\Microsoft System Center\DPM\DPM\Volumes\Replica\File System\vol_c9aea05f-31e6-45e5-880c-92ce5fba0a58\454d81a0-0d9d-4e07-9617-d49e3f2aa5de\Full\DPMBACKUP"
      

設定備份Configure the backup

您可以備份 DPM 資料庫,如同備份任何其他使用 SQL Server 原生備份的 SQL Server 資料庫一樣。You can back up the DPM database as you would any other SQL Server database using SQL Server native backup.

復原資料庫Recover the database

  1. 使用檔案總管從任何 Windows 電腦連接到 \\DPMServer\DPMSERVERNAME-dpmdb 共用。Connect to the \\DPMServer\DPMSERVERNAME-dpmdb share using Explorer from any Windows computer.

  2. 以滑鼠右鍵按一下 dpmdb.bak 檔案以檢視屬性。Right-click the dpmdb.bak file to view properties. [舊版] 索引標籤會顯示您可以選取和複製的所有備份。On the Previous Versions tab are all the backups that you can select and copy. 此外,您也可以輕易地存取仍位於 C:\DPMBACKUP 資料夾中的最後一個備份。There is also the very last backup still located in the C:\DPMBACKUP folder which is also easily accessible.

  3. 如果您需要將 SAN 連接的 DPM 存放集區磁碟移到另一部伺服器,以便從複本磁碟區讀取,或要重新安裝 Windows 以讀取本機連接的磁碟,您必須事先知道 DPM 複本磁碟區的掛接點路徑或磁碟區 GUID,才能知道哪個磁碟區保有此資料庫備份。If you need to move a SAN attached DPM storage pool disk to another server to be able to read from the replica volume, or to reinstall Windows to read locally attached disks, you'll need to know the DPM Replica volume Mount point path or Volume GUID beforehand so you know what volume holds the database backup. 在初始的保護之後,但需要還原之前,您可以使用下列 SQL 指令碼隨時擷取該資訊。You can use the SQL script below to extract that information any time after initial protection but before the need to restore. 以裝載資料庫的 SQL Server 名稱取代 %dpmsqlservername%。Replace the %dpmsqlservername% with the name of the SQL Server hosting the database.

    Select ag.NetbiosName as
    ServerName,ds.DataSourceName,vol.MountPointPath,vol.GuidName
    from tbl_IM_DataSource as ds
    join tbl_PRM_LogicalReplica as lr on ds.DataSourceId=lr.DataSourceId
    join tbl_AM_Server as ag on ds.ServerId=ag.ServerId
    join tbl_SPM_Volume as vol on lr.PhysicalReplicaId=vol.VolumeSetID
    and vol.Usage =1
    and lr.Validity in (1,2)
    where ds.datasourcename like '%C:\%' -- volume drive letter for DPMBACKUP
    and servername like '%dpmsqlservername%' --netbios name of server hosting DPMDB
    
    
  4. 如果您需要在移動 DPM 存放集區磁碟或在 DPM 伺服器重建後復原:If you need to recover after moving DPM storage pool disks or a DPM server rebuild:

    1. 您有磁碟區 GUID,所以該磁碟區應掛接在另一部 Windows Server 上或在 DPM 伺服器重建之後掛接,請使用 mountvol.exe 指派使用 SQL 指令碼輸出中磁碟區 GUID 的磁碟機代號: C:\Mountvol X: \\?\Volume{d7a4fd76-a0a8-11e2-8fd3-001c23cb7375}\You have the volume GUID, so should that volume need to be mounted on another Windows server or after a DPM server rebuild, use mountvol.exe to assign it a drive letter using the volume GUID from the SQL script output: C:\Mountvol X: \\?\Volume{d7a4fd76-a0a8-11e2-8fd3-001c23cb7375}\ .

    2. 在使用此磁碟機代號和部分複本路徑 (代表資料夾結構) 的複本磁碟區上重新共用 DPMBACKUP 資料夾。Reshare the DPMBACKUP folder on the replica volume using the drive letter and portion of the replica path representing the folder structure.

      net share SERVERNAME-DPMDB="X:\454d81a0-0d9d-4e07-9617-d49e3f2aa5de\Full\DPMBACKUP"
      
      
    3. 使用檔案總管從任何 Windows 電腦連接到 \\SERVERNAME\DPMSERVERNAME-dpmdb 共用。Connect to the \\SERVERNAME\DPMSERVERNAME-dpmdb share using Explorer from any Windows computer

    4. 以滑鼠右鍵按一下 dpmdb.bak 檔案以檢視屬性。Right-click the dpmdb.bak file to view the Properties. [舊版] 索引標籤會顯示您可以選取和複製的所有備份。On the Previous Versions tab are all the backups that you can select and copy.

DPM 災害復原管理:備份 DPM DBDPM disaster recovery management: Backup DPM DB

以相同 DB 重新建構 DPM 伺服器的其中一個方法,是將 DPM DB 備份至本機磁碟。One of the ways to reconstruct your DPM server with the same DB is by backing up the DPM DB to local disks.

DPM 資料庫包含 DPM 設定以及 DPM 備份的相關資料。DPM database contains the DPM configuration together with data about DPM's backups. 萬一出現災害,您可以使用最近備份到本機磁碟的資料庫備份來重建 DPM 伺服器的大部分功能。In case of a disaster, you can rebuild the functionality of your DPM server by using a recent backup of the database to a local disk. 若 DPM 伺服器當機或無法運作,且您的存放集區仍然完整保留備份,則您可以用相同的 DPM DB 重新設定 DPM 伺服器。If your DPM server crashes or becomes un-operational, and you still have your storage pool intact containing your backups, you can reconfigure the DPM server with the same DPM DB.

請務必確保:Ensure:

  1. DPM DB 已在本機磁碟上備份。DPM DB is backed up on to local disks.
  2. 存放集區保持不變且可用。Storage pool is intact and available.

注意

在復原期間,DPM 伺服器的完整網域名稱 (FQDN) 必須與原始 DPM 服務器相同。The Fully Qualified Domain Name (FQDN) of the DPM server during recovery needs to be same as the original DPM server.

備份 DPM 資料庫Back up DPM database

  1. 在 DPM 主控台中,按一下 [保護] > [建立保護群組] 。In DPM console, click Protection > Create protection group .

  2. 在 [選擇保護群組類型] 頁面上,選取 [伺服器] 。On the Select Protection Group Type page, select Servers .

  3. 在 [選取群組成員] 頁面中,選取 [DPM 資料庫] 。On the Select group members page, select DPM database . 如果您從遠端執行 SQL Server,請選取已安裝的遠端 SQL Server,然後選取 [DPM 資料庫]。If you're running SQL Server remotely, select the remote SQL Server installed and select DPM database. 如果 SQL Server 正在 DPM 伺服器上執行,請展開 DPM 伺服器,然後選取 [DPMDB]。If SQL Server is running on the DPM server, expand the DPM server and select DPMDB.

  4. 在 [選擇資料保護方式] 頁面上,選取 [我想要使用磁碟短期保護] 。On the Select Data Protection Method page, select I want short-term protection using disk . 指定短期保護原則選項。Specify the short-term protection policy options.

  5. 初始複寫 DPM 資料庫之後,After initial replication of DPM database. 執行下列 SQL 指令碼:run the following SQL script:

    select AG.NetbiosName, DS.DatasourceName, V.AccessPath, LR.PhysicalReplicaId from tbl_IM_DataSource DS
    join tbl_PRM_LogicalReplica as LR
    on DS.DataSourceId = LR.DataSourceId
    join tbl_AM_Server as AG
    on DS.ServerId=AG.ServerId
    join tbl_PRM_ReplicaVolume RV
    on RV.ReplicaId = LR.PhysicalReplicaId
    join tbl_STM_Volume V
    on RV.StorageId = V.StorageId
    where datasourcename like N'%dpmdb%' and ds.ProtectedGroupId is not null
    and LR.Validity in (1,2)
    and AG.ServerName like N'%<dpmsqlservername>%' -- <dpmsqlservername> is a placeholder, put netbios name of server hosting DPMDB
    

復原 DPM 資料庫Recover DPM database

若要使用相同 DB 重新建構 DPM,您需要先復原 DPM 資料庫,並使用全新安裝的 DPM 同步。To reconstruct your DPM with the same DB, you need to first recover the DPM database and sync it with the freshly installed DPM.

請使用下列步驟:Use the following steps:

  1. 開啟系統管理命令提示字元並執行 psexec.exe -s powershell.exe,在系統內容中啟動 PowerShell 視窗。Open an administrative command prompt and run psexec.exe -s powershell.exe to start a PowerShell window in system context.
  2. 決定您要復原資料庫的哪個位置:Decide from where you want to recover the database:

若要從最後一次備份中複製資料庫To copy the database from the last backup

  1. 瀏覽至複本 VHD 路徑,亦即 <DPMServer FQDN><PhysicalReplicaId><PhysicalReplicaId>Navigate to replica VHD path i.e. <DPMServer FQDN><PhysicalReplicaId><PhysicalReplicaId>
  2. 使用 mount-vhd disk0.vhdx 裝載出現的 disk0.vhdxMount the disk0.vhdx present in it using mount-vhd disk0.vhdx
  3. 裝載複本 VHD 之後,透過 mountvol.exe 使用來自 SQL 指令碼輸出的實體複本識別碼,將磁碟機代號指派給複本磁碟區。Once replica VHD is mounted, use mountvol.exe to assign a drive letter to the replica volume using the Physical replica ID from the SQL script output. 例如:mountvol X: \?\Volume{<PhysicalReplicaId>}For example: mountvol X: \?\Volume{<PhysicalReplicaId>}\

若要從先前的復原點複製資料庫To copy the database from a previous recovery point

  1. 瀏覽至 DPMDB 容器目錄,亦即 <ReFSVolume><DPMServer FQDN><PhysicalReplicaId>,,您會在其下看到多個具備某些唯一 GUID 識別碼的目錄,這些目錄均分別對應至為 DPM DB 建立的各個復原點。Navigate to DPMDB container directory i.e. <ReFSVolume><DPMServer FQDN><PhysicalReplicaId>, you will see multiple directories with some unique GUID identifiers under it corresponding recovery points taken for DPM DB. 以外的其他目錄則表示 PIT/復原點Directories other than represents a PIT/recovery point

  2. 瀏覽至任何 PIT VHD 路徑,亦即 <ReFSVolume><DPMServer FQDN><PhysicalReplicaId><PITId>,並使用 mount-vhd disk0.vhdx 裝載出現的 disk0.vhdx。Navigate to any PIT vhd path i.e. <ReFSVolume><DPMServer FQDN><PhysicalReplicaId><PITId> and mount the disk0.vhdx present in it using mount-vhd disk0.vhdx.

  3. 裝載複本 VHD 之後,透過 mountvol.exe 使用來自 SQL 指令碼輸出的實體複本識別碼,將磁碟機代號指派給複本磁碟區。Once replica VHD is mounted, use mountvol.exe to assign a drive letter to the replica volume using the Physical replica ID from the SQL script output. 例如:mountvol X: \?\Volume{<PhysicalReplicaId>}For example: mountvol X: \?\Volume{<PhysicalReplicaId>}\

    在上述步驟中所有以大括號括起來的文字均為預留位置,請以適當的值取代。All of the following text with angular braces in the above steps are place holders, replace them with appropriate values.

    • ReFSVolume - SQL 指令碼輸出中的存取路徑ReFSVolume - Access path from the SQL script output
    • DPMServer FQDN - DPM 伺服器的完整名稱DPMServer FQDN - Fully qualified name of DPM server
    • PhysicalReplicaId - SQL 指令碼輸出中的實體複本識別碼PhysicalReplicaId - Physical replica ID from the SQL script out
    • PITId - 不同於容器目錄中實體複本識別碼的 GUID 識別碼。PITId - GUID identifier other than physical replica ID in the container directory.
  4. 開啟另一個系統管理命令提示字元並執行 psexec.exe -s cmd.exe,在系統內容中啟動命令提示字元。Open another administrative command prompt and run psexec.exe -s cmd.exe to start a command prompt in system context.

  5. 將目錄變更為 X: 磁碟機,並瀏覽到 DPM 資料庫檔案的位置。Change directory to the X: drive and navigate to the location of the DPM database files.

  6. 請將它們複製到可輕鬆執行還原的位置。Copy them to a location that's easy to restore from. 複製之後,結束 psexec cmd 視窗。Exit the psexec cmd window after you copy.

  7. 前往在步驟 1 中開啟的 psexec PowerShell 視窗,瀏覽至 VHDX 路徑,並使用 dismount-vhd disk0.vhdx 命令卸載 VHDX。Go to the psexec PowerShell window opened in step one, navigate to the VHDX path, and dismount the VHDX by using the command dismount-vhd disk0.vhdx.

  8. 重新安裝 DPM 伺服器之後,您可以執行 DPMSYNC-RESTOREDB,使用還原的 DPMDB 連結至 DPM 伺服器。After reinstalling the DPM server, you can use the restored DPMDB to attach to the DPM server by running DPMSYNC-RESTOREDB.

  9. DPMSYNC-RESTOREDB 完成之後,請執行 DPMSYNC-SYNC。Run DPMSYNC-SYNC once DPMSYNC-RESTOREDB is complete.

使用 DPMSyncUsing DPMSync

DpmSync 是命令列工具,可讓您將 DPM 資料庫與存放集區中的磁碟狀態與已安裝的保護代理程式進行同步處理。DpmSync is a command-line tool that enables you to synchronize the DPM database with the state of the disks in the storage pool and with the installed protection agents. DpmSync 會還原 DPM 資料庫、將 DPM 資料庫與存放集區中的複本同步處理、還原報表資料庫,以及重新配置遺失的複本。DpmSync restores the DPM database, synchronizes the DPM database with the replicas in the storage pool, restores the Report database, and reallocates missing replicas.

參數Parameters

參數Parameter 說明Description
-RestoreDb-RestoreDb 從指定的位置還原 DPM 資料庫。Restores a DPM database from a specified location.
-Sync-Sync 同步處理已還原的資料庫。Synchronizes restored databases. 還原資料庫之後,您必須執行 DpmSync –Sync。You must run DpmSync –Sync after you restore the databases. 執行 DpmSync –Sync 之後,某些複本可能仍會標示為遺失。After you run DpmSync –Sync, some replicas may still be marked as missing.
-DbLoc 位置-DbLoc location 識別 DPM 資料庫備份的位置。Identifies the location of backup of DPM database.
-InstanceName-InstanceName
伺服器\執行個體server\instance
DPMDB 必須還原的執行個體。Instance to which DPMDB must be restored.
-ReallocateReplica-ReallocateReplica 重新配置所有遺失的複本磁碟區,不進行同步處理。Reallocates all missing replica volumes without synchronization.
-DataCopied-DataCopied 指出您已經完成將資料載入到剛配置的複本磁碟區中。Indicates that you have completed loading data into the newly allocated replica volumes.
這只適用於用戶端電腦。This is applicable for client computers only.

範例 1: 從 DPM 伺服器上的本機備份媒體還原 DPM 資料庫。Example 1: To restore the DPM database from local backup media on the DPM server.
執行下列命令:Run the following command:

DpmSync –RestoreDb -DbLoc G:\DPM\Backups\2005\November\DPMDB.bak

還原 DPM 資料庫之後,若要同步處理資料庫,請執行下列命令:After you restore the DPM database, to synchronize the databases, run the following command:

DpmSync -Sync

在您還原並同步處理 DPM 資料庫之後,且在還原複本之前,請執行下列命令來重新配置複本的磁碟空間:After you restore and synchronize the DPM database and before you restore the replica, run the following command to reallocate disk space for the replica:

DpmSync -ReallocateReplica

範例 2: 從遠端資料庫還原 DPM 資料庫。Example 2: To restore the DPM database from a remote database.
在遠端電腦上執行下列命令:Run the following command on the remote computer:

DpmSync –RestoreDb -DbLoc G:\DPM\Backups\2005\November\DPMDB.bak –InstanceName contoso\ms$dpm

還原 DPM 資料庫之後,若要同步處理資料庫,請在 DPM 伺服器上執行下列命令:After you restore the DPM database, to synchronize the databases, run the following command on the DPM Server:

DpmSync -Sync

還原並同步處理 DPM 資料庫之後,且在還原複本之前,請在 DPM 伺服器上執行下列命令,以重新配置複本的磁碟空間:After you restore and synchronize the DPM database and before you restore the replica, run the following command on the DPM Server to reallocate disk space for the replica:

DpmSync -ReallocateReplica