locked
Windows Server Backup 出現『要先停止備份磁碟區的操作,操作才能開始執行。』的錯誤。 RRS feed

  • 一般討論

  • 大家好! 目前的作業系統為 Server 2008 R2,主機為 HP ProLiant ML350G5 RAM為10G 在操作 Windows Server Backup 時,出現出現『要先停止備份磁碟區的操作,操作才能開始執行。』的錯誤。 備份的項目為:裸機復原、系統狀態、系統磁碟 查閱事件檢視器,eventID 為 521 訊息為: 【在 '?2011?-?06?-?15T06:33:38.973000000Z' 啟動的備份操作失敗,因為建立所備份磁碟區陰影複製的磁碟區陰影複製服務操作失敗,錯誤碼如下: '2155348129'。請檢閱事件詳細資料以找出解決方案,然後在問題解決後,重新執行備份操作。】 請問如何才能備份呢? 謝謝
    2011年6月15日 上午 08:19

所有回覆

  • Hi, 跟據外國討論區的經驗:

    ---------------------------------------------------------------------------

    Based on the error code and the experience, this is a known issue when you are using Window Server backup feature to backup the system partition which was created by the OEM tools.
    You can find that the first partition is OEM partition if you run "diskpart" in the command line, "select disk 0" and then "list part".
    As we know, the system partition should be marked Active so that the Windows Server Backup can read information there. However, sometimes when we create the partition and install the operating system with OEM tools (ex. Intel Embedded Server RAID II) , the OEM partition will be created and marked active. This could cause this backup failure. This is the same issue that we saw in Windows Vista, but poses a huge problem in Windows Server 2008. Not only does it break full backups, but also system state backups.
    Currently, there is no hotfix or official workaround for this issue.
    You may try the following steps to manually change the active partition and check if the issue will re-occur.
    Steps:
    Please open the Disk Management console, find and locate "Server Manager\Storage\Disk Management" and see which partition has been marked as Active volume. If the Active volume is different from the volume in which you install the operating system, try changing the Active volume to the volume containing the operating system by using the following commands:

    1.Open a command prompt as Administrator.
    2.Run diskpart.
    3.At the diskpart> prompt type "list disk" (without quotations), see which disks are listed there
    4.At the diskpart> prompt type "list volume", see which volume is the volume containing operating system
    5.At the diskpart> prompt type "select disk 0" <enter>.
    6.At the diskpart> prompt type "select volume 2" <enter> (I assume the volume 2 is the volume containing operating system).
    7.At the diskpart> prompt type "active" <enter>.
    Please note: since changing active partition may cause potential problem or even result in an unbootable system, it is highly suggested that you contact the manufacturer and work with them to change the active partition. This is because the OEM partition may contain some useful information (including drivers) to boot the system.
    Thank you for your understanding and cooperation.
    ---------------------------------------------------------------------
    Yeah, all of these won't work if the bootmanager is on a non-ntfs partition. Here is the way I fixed it.

    Vista and SBS 2008 BCD change

    Windows Backup and VSS fail with the following:
    VSS: Volume Shadow Copy Service warning: ASR writer Error 0x80070001. hr = 0x00000000.
    SPP: Shadow copy creation failed because of error reported by ASR Writer. More info: Incorrect function. (0x80070001).
    Backup: Backup started at <DATETIME> failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.


    This article works for the following condition:
    1. Vista or Server 2008 Installed
    2. Boot loader resident on C:
    3. Boot manager (BCD) on non-NTFS (OEM) partition
    4. bootrec /fixboot fails in DVD boot command line
    5. OEM partition is marked (EISA CONFIG, ACTIVE)

    In this configuration Windows backup will not operate. It cannot skip the OEM partiton, which is non-NTFS. All volumes must be NTFS in order for Windows Backup to work.

    To correct this situation, you will need approximately 1 hour.

    Caveats:

    Your RAID controller must point to BIOS for boot container, or you must set your boot container after the second reboot.

    Please use a 3rd party backup app like BackupExec, to do a complete backup prior to making changes. BackupExec has no issues with non-NTFS partitions. Symantec has a free working 60 day trial available.

    Solution:

    1. In Vista / Server, go into disk manager. Shrink an available volume by say 2 gigs. Then create a new simple volume on that freed space. Format it NTFS. Assign it, for sake of argument, the letter S.
    2. Open a command prompt and complete the following commands
    a. bcdedit /export s:\boot\bcd
    b. bcdedit /store S:\boot\bcd /set {9dea862c-5cdd-4e70-acc1-f32b344d4795} device partition=S:
    c. bcdedit /store S:\boot\bcd /set {b2721d73-1db4-4c62-bf78-c548a880142d} device partition=S:
    d. bcdedit /store S:\boot\bcd /set {466f5a88-0af2-4f76-9038-095b170dc21c} device partition=S:
    e. bcdedit /store S:\boot\bcd /enum all /v
    f. From the DVD Vista / Server media, run bootsect /NT60 S: /Force
    g. Reboot system, notice it is non bootable. Therefore boot with Windows install disk.g
    h. Load into command prompt via recovery console.
    i. Lets use the following assumptions for the next command OEM = Disk 0, Partition 1, S: = Disk 1, Partition 1
    j. Diskpart, list disk, select disk 0, select partition 1, inactive, select disk 1, select partition 1, active, exit.
    k. Reboot. This should work. Failing that try the last step again, it may not have taken.
    l. While in windows, launch command prompt and open diskpart.
    m. Using the previous assumptions. list disk, select disk 0, select partition 1, delete, exit.
    n. reboot
    o. Open Windows backup, delete current configuration and recreate.

    This should work.

    --------------------------------------------------

    你可參考一下以上的方案!

     


    Microsoft MVP for Windows Server-Networking, MCT, http://msmvps.com/blogs/richardwu
    2011年6月15日 下午 04:10