none
Win2008 Backup Failure: Volume Shadow copy operation failed for backup volumes with following error code '2155348129'

    Question

  • I recently performed a clean install of Win2008 x32 and have been trying for several days to get the Windows Backup program to work on my system drive C: (hardware RAID 5 - Intel Embedded Server RAID II on S5000PSLSAS with 3- 146GB 15K drives. I updated all drivers/bios from Intel before the install).

    I have a removable SATA drive (500GB) which the Windows Backup program cleared for backups. I later assigned drive X: so I could see what was being placed on the drive (e.g. X:\WindowsImageBackup\APICELLA\Backup 2008-08-18 015309).

    These are the things that do work using the Backup Once Option:

    1) Backing up 100GB from an IDE Drive B: - no errors. Data appears on X:

    2) Backup up 100GB separate RAID Array D: (I have two separate RAID arrays on this machine) - no errors. Data appears on X:

    3) Problem: Everytime I chose to backup C: I get this error message: Backup started at '8/18/2008 1:55:08 AM' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.

    Event Viewer:
    - System
      - Provider
       [ Name]  Microsoft-Windows-Backup
       [ Guid]  {1db28f2e-8f80-4027-8c5a-a11f7f10f62d}
       EventID 521
       Version 0
       Level 2
       Task 0
       Opcode 0
       Keywords 0x8000000000000000
      - TimeCreated
       [ SystemTime]  2008-08-18T01:55:12.764Z
       EventRecordID 962
       Correlation
      - Execution
       [ ProcessID]  3032
       [ ThreadID]  3852
       Channel Application
       Computer APICELLA
      - Security
       [ UserID]  S-1-5-18

    - EventData 
      BackupTime 2008-08-18T01:55:08.427Z
      ErrorCode 2155348129
      ErrorMessage %%2155348129

    I have turned on Shadow Copying all both drives C: and X:.

    Any suggestions?

    - Pete

    Monday, August 18, 2008 2:19 AM

Answers

  • Hello Pete,
     
    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.

    David Shen - MSFT
    • Marked as answer by David Shen Thursday, August 21, 2008 5:56 AM
    Monday, August 18, 2008 10:10 AM
  • Hi Pete,
     
    As several similar issues has been reported before, the issue is under investigation by the product team now. If we have any update or hotfix on it, we will let you know as soon as possible. Currently, I would like suggest that you contact Intel to check if there is any workaround or solution to the issue.
     
    As you mentioned, you have backuped the second RAID array D: with no error. Personally, I think this array has no related to the issue. In this way, it is recommended that you retain it.
     
    Thanks for the understanding and co-operation.

    David Shen - MSFT
    • Marked as answer by David Shen Thursday, August 21, 2008 5:56 AM
    Tuesday, August 19, 2008 9:56 AM
  • 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.

    • Proposed as answer by brutus2001x Monday, March 16, 2009 2:13 PM
    • Edited by brutus2001x Monday, March 16, 2009 3:45 PM Added a condition
    • Marked as answer by David Shen Tuesday, March 17, 2009 1:23 AM
    Monday, March 16, 2009 2:13 PM

All replies

  • Hello Pete,
     
    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.

    David Shen - MSFT
    • Marked as answer by David Shen Thursday, August 21, 2008 5:56 AM
    Monday, August 18, 2008 10:10 AM
  • David,

    You are correct, the computer shows my booting Win2008 server disk RAID C: as System, Boot, Page File, Crash Dump, Primary Partition and my extra RAID D: (originally my Win2003 server) as ACTIVE, Primary partition in Disk Management.

    I made the changes that you suggested using diskpart (selecting correct volumes for my system), and diskpart put a STAR in that row. Disk Management now shows "Active" in addition to other fields on C:. Please note that D: also retains the Active status.

    Unfortunately, when I try to backup, I recieve the same error.

    Do you feel this is a problem with Intel's driver or Windows 2008? I would like to send Intel the information if you feel like the problem is theirs. I cannot imagine that I am the only user of their Embeded Server RAID II product. If it s a Microsoft's problem, can you please forward to their developers for a fix when they get a service pack out?

    Do you think if I were to remove the second array, the backup would work? At this point, that disk is my old Win2003 system. I kept it available to assist in migration. I also hope you are not going to tell me that if I remove it, Win2008 will not boot!

    Thank you for your knowlegable and timely response.

    - Pete
    Monday, August 18, 2008 11:12 AM
  • Hi Pete,
     
    As several similar issues has been reported before, the issue is under investigation by the product team now. If we have any update or hotfix on it, we will let you know as soon as possible. Currently, I would like suggest that you contact Intel to check if there is any workaround or solution to the issue.
     
    As you mentioned, you have backuped the second RAID array D: with no error. Personally, I think this array has no related to the issue. In this way, it is recommended that you retain it.
     
    Thanks for the understanding and co-operation.

    David Shen - MSFT
    • Marked as answer by David Shen Thursday, August 21, 2008 5:56 AM
    Tuesday, August 19, 2008 9:56 AM
  • I just noticed this problem in my event logger. This system has been running for several weeks and the backup system was working fine as well. I've got an onboard raid running a raid 5 for operation and a raid 1 which is the backup array. Right before I started to receive the backup error (2 days in a row now on the scheduled backup) I installed Business Contacts Manager for Office 2007. That is the only change in weeks and until then, everything was running correctly. BCM was the only thing installed, office has been installed for quite a while. I'm also seeing errors with sqlwriter, mssql$mssmlbiz, sqlvdi. When I was installing BCM, event vewier recorded a lot of warnings from MsiInstaller 

     Product: Microsoft Office 2007 Primary Interop Assemblies. The application tried to modify a protected Windows registry key......

    And

    Product: Microsoft Office 2003 Web Components. The application tried to modify a protected Windows registry key.....

    So multiples of each of those. I don't know if an app tries to modify a protected key if it succeeds or if it fails and I have to do something else. I didn't think about putting the server into install mode, used to do that sometimes with server 2003, don't have a lot of 2008 experience yet.

    Wednesday, September 24, 2008 5:22 PM
  • Hey Guys,
      I'm having the same error show up in my logs when I try to run backups, but my hardware is totally different:

    -Athlon 64 X2 4400+
    -4 GB DDR
    -on IDE: 250GB, 500GB
    -on SATA: 74GB 10k
    -Server 2008 Standard (64-bit), Exchange 2007, and much more

      The OS boots from the 10k drive, with the 250GB drive being additional storage and the 500GB being the drive selected for backups. No RAID at all involved, just the NVIDIA IDE and SATA controllers from an NForce 4 SLI Chipset. Very boring ;)

      Anyways, I have verified shadow copies are on, but I get the following two errors when I try to launch a backup:

    Log Name:      Application
    Source:        ESE
    Date:          10/14/2008 8:07:40 PM
    Event ID:      2007
    Task Category: ShadowCopy
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NSServer08.nordic.local
    Description:
    Information Store (2852) Shadow copy instance 3 aborted.

    For more information, click http://www.microsoft.com/contentredirect.asp.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ESE" />
        <EventID Qualifiers="0">2007</EventID>
        <Level>2</Level>
        <Task>16</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-10-15T00:07:40.000Z" />
        <EventRecordID>128856</EventRecordID>
        <Channel>Application</Channel>
        <Computer>NSServer08.nordic.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Information Store</Data>
        <Data>2852</Data>
        <Data>
        </Data>
        <Data>3</Data>
      </EventData>
    </Event>
    And this one:

    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          10/14/2008 8:15:23 PM
    Event ID:      521
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      NSServer08.nordic.local
    Description:
    Backup started at '10/15/2008 12:14:37 AM' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Backup" Guid="{1db28f2e-8f80-4027-8c5a-a11f7f10f62d}" />
        <EventID>521</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2008-10-15T00:15:23.221Z" />
        <EventRecordID>128983</EventRecordID>
        <Correlation />
        <Execution ProcessID="4812" ThreadID="8528" />
        <Channel>Application</Channel>
        <Computer>NSServer08.nordic.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BackupTime">2008-10-15T00:14:37.111Z</Data>
        <Data Name="ErrorCode">2155348129</Data>
        <Data Name="ErrorMessage">%%2155348129</Data>
      </EventData>
    </Event>
    Here's the diskpart stuff:

    DISKPART> list disk
    Disk ###  Status  Size  Free  Dyn  Gpt
    --------  ------- ----- ----- ---  ---
    Disk 0    Online       233GB       0B
    Disk 1    Online       466GB       17MB
    Disk 2    Online       69GB        0B
    Disk 3    No Media        0B       0B

    DISKPART > list volume
    Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
    ----------  ---  -----------  -----  ----------  -------  ---------  --------
    Volume 0     D                       DVD-ROM        0 B  No Media
    Volume 1     E   OOo-2.4.1-4  CDFS   DVD-ROM      486MB  Healthy
    Volume 2     F   Local Disk   NTFS   Partition    233GB  Healthy
    Volume 3         NSServe 200  NTFS   Partition   466 GB  Healthy
    Volume 4     C                NTFS   Partition     69GB  Healthy     System
    Volume 5     G                       Removable      0 B  No Media

    I'm thinking that since the C drive isn't the OS's first one, maybe this is related?

    Thanks for any pointers you may have.

    -Nate

    Wednesday, October 15, 2008 12:45 AM
  • Hi Everyone.  Not sure if this thread is still active or not.  But, I'm having the same issue.  W2K8 server wit Exch 2007.  The server has been running and backing up fine with DPM 2007 for weeks.  Beginning at 2am the day after install ADMT 3.1, DPM started barfing on backing up the System State; however, all other protected members on this server are backing up successfully.  In addition to the error in other posts, there are several error log entries for SQLVDI and SQLWriter regaridng Cannot locate file and Cannot open backup device.

    Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013

    Error state: 1, Severity: 16

    Source: Microsoft SQL Native Client

    Error message: BACKUP DATABASE is terminating abnormally.

    SQLSTATE: 42000, Native Error: 3201

    Error state: 7, Severity: 16

    Source: Microsoft SQL Native Client

    Error message: Cannot open backup device '{D2959862-5EDE-456C-BAB1-B6AED05F94FF}1'. Operating system error 0x80070002(The system cannot find the file specified.).



    SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6920. Thread=7968. Client. Instance=MS_ADMT.
    VD=Global\{D2959862-5EDE-456C-BAB1-B6AED05F94FF}1_SQLVDIMemoryName_0. 

    Backup started at '12/10/2008 8:00:20 AM' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.


    And, my C: partition is Active; although, OEM installed.  Anyone have any luck with this?

    Thanks,
    Chris

    Wednesday, December 10, 2008 8:13 PM
  •  I have a Dell Server here, clean installed SBS 2008 on it, now I want to run backup, I get Unknown error (0x800423f4) related to Volume Shadow Copy.
    I also find a 63MB OEM partition. The server is configured as Raid-1. I had not used any Dell utilities to install.
    If I understand correctly, setting the system partition active, would solve the problem, but may leave my server unbootable.
    Since the server is already productive and I have no backup yet, I am very hesitant. Anyone heard back from Dell or Microsoft as to what a "safe" solution to the problem would be?
    Friday, January 30, 2009 4:45 PM
  • Anyone know a solution for this problem? 
    RVenes
    Friday, March 13, 2009 8:28 AM
  • 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.

    • Proposed as answer by brutus2001x Monday, March 16, 2009 2:13 PM
    • Edited by brutus2001x Monday, March 16, 2009 3:45 PM Added a condition
    • Marked as answer by David Shen Tuesday, March 17, 2009 1:23 AM
    Monday, March 16, 2009 2:13 PM
  • Hi Everyone

    I have a Dell Precision 490 Workstation on which I installed Windows 2008 Enterprise Edition.
    When I try to use Server Backup, I get the following error message :

    Log Name:      Microsoft-Windows-Backup
    Source:        Microsoft-Windows-Backup
    Date:          3/27/2009 12:58:36 PM
    Event ID:      9
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      vtomsa-pc.europe.corp.microsoft.com
    Description:
    Backup started at '{831f9bae-bdcf-42df-9d88-da5bba8a26fd}' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'.

    DISKPART INFO
    ==========

    DISKPART> list disk

      Disk ###  Status      Size     Free     Dyn  Gpt
      --------  ----------  -------  -------  ---  ---
    * Disk 0    Online       149 GB      0 B
      Disk 1    Online       699 GB      0 B

    DISK 0  Partition ###  Type              Size     Offset      
      -------------  ----------------  -------  -------
      Partition 1    OEM                110 MB    32 KB
      Partition 2    Primary             49 GB   110 MB
      Partition 3    Primary            100 GB    49 GB

    DISK 1  Partition ###  Type              Size     Offset
      -------------  ----------------  -------  -------
      Partition 1    Primary            293 GB  1024 KB
      Partition 2    Primary            195 GB   293 GB
      Partition 3    Primary            210 GB   488 GB

    Now, when I look in Server Manager --> Disk Managemenet, I see that C:, where Windows is installed is marked as being active.

    Can you please help me with this issue? it's very frustrating that I cannot backup my machine.

    Thank you
    Vlad

    Tuesday, March 31, 2009 1:47 PM
  • UPP!
    Wednesday, June 24, 2009 12:47 PM
  • UPP!
    Wednesday, June 24, 2009 12:48 PM
  • I get the following message "The backup failed on a volume containing system data.".  No eventlog entries :(
    Funny that there are several posts here where things were working and now in the past few weeks it fails...question would be, what fix was applied by are friends in Redmond that broke things?
    Ron

    Ron Mitchell
    Sunday, July 12, 2009 2:45 PM
  • Yesterday  I had a wild idea...what if the backup drive is full or corrupted? Hmmm...one can not look at the backup device because it is removed and reformated  by Windows Backup Service...hmmm...so I deleted the scheduled backup job which released the backup disk drive...okay..next I did all the things I needed to do to reformat the drive NTFS format...then created a new backup job...and lo' & behold it works...

    Thus the message "The backup failed on a volume containing system data." is just as meaningless as it sounds...one has no idea what volume or even if this is a valid error message....

    Ron Mitchell
    Monday, July 13, 2009 7:42 PM
  • Hello, I was just wondeing if there was an offical hotfix or work around for this yet? Ive just installed SBS 2008 on a Dell Power Edge. Im slightly scared of doing anything unsupportd because ive not got a full backup to fall back on to!

    Any advice would be apprecaited!!

    Regards

    Dave J
    Thursday, November 12, 2009 9:55 AM
  • I just started having this problem a few days ago when attempting to backup a drive holding several VHD files for running virtual machines. The problem turned out to be caused by one particular virutal machine whose VHD file was nearly full. It only had about 250MB of free space and the VSS Writer could not create a shadow copy on the virtual machine. 

    There was an error in the event log on the VM: 

    Volume Shadow Copy Service error: Cannot find diff areas for creating shadow copies. Please add at least one NTFS drive to the system with enough free space. The free space needed is at least 300 Mb for each volume to be shadow copied.

    The error on the Hyper-V host was this:

    Volume Shadow Copy Service operation error (0x800423f3)
    The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.

    It took me a while to figure this out so I thought I would share it here.

    Friday, November 13, 2009 1:06 AM
  • Here is another solution that doesn't risk any down time nor risk system not functioning.  I am a bit upset with the lack of documentation available on the Internet.

    When using Windows Server Backup (part of 2008 Server), Choose Backup Once, Different Options, Custom (rather than Full), Advanced Settings, VSS Settings Tab, and make sure that VSS full Backup radio button is clicked upon.  After this is selected backup specified files, System State or whatever you are looking to backup and it should work for you.

    I rattled by brain for 3 hours messing with Active Partitions, Attempting to fix non-broken boot records only to find out by stumbling into this option which fixed my problem.

    The error I was receiving is as follows "Backup failed to complete.  A Volume Shadow Copy Service operation..."
    Message is as stated "The operation was stopped.  Detailed error:  The volume shadow copy operation failed with error 0x800423F0.  View the event log for more information."

    After checking Event Log this is what it said "The backup operation that started at '?2010?-?01?-?17T19:39:02.163000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

    Hopefully this post will save many people time when running into this issue in the future.  Hopefully it will also notify Microsoft to better explain errors and have answers more readily available via the Internet.

    Thanks,

    Ray

    Sunday, January 17, 2010 7:50 PM
  • Thank you, Ray! So, did making this setting in one time backup cure the problems with scheduled backups failing?

    Michael
    Wednesday, January 20, 2010 3:44 PM
  • Ray - that is spot on I have a backup running now our first for a week!

    Just need to figure out how to get this to run every night now.  SBS Backup might be simple but its given me some major headaches this week as there is a serious lack of documentation on this subject and how I've missed this thread I really don't know.

    I do not know why but it was working - stopped which we thought (being a microsoft product) that it was in need to a reboot after WSUS updates - then appeared to work - then fails for a week.

    The backups which appeared to work were pretty much useless as this morning I needed to restore some files - accidently deleted - I have eventually had to assign the backup drive a letter and attached mount the VHD file through a 3rd party tool to recover the files I wanted as for all the backup showed as sucessful it couldn't/wouldn't read the shadow copy info!  I will be checking these more thoroughly in future

    Lesson learnt - don't trust Server 2008 Backup - even when it says its sucessful!

    Thanks

    Steve B
    Wednesday, February 03, 2010 3:49 PM
  • I've experienced similar problems with my Dell T110 Poweredge running SBS 2008.  My problem now is that the external HD shows up in Disk Manager but SBS 2008 can't locate the backup set to do a complete recovery.  How can I get it to find the data?  Thanks for any assistance.
    Techie Attorney
    Monday, February 08, 2010 2:01 AM
  • Boysie -

      I was able to recover an entire VM from the Server2008 Backup and put it into service, after applying Ray's "fix". I have another issue, when swapping the backup drives (usb external) the system (Dell T-410) does not see the drive unless I bring the whole system down and back up.

    Michael
    Tuesday, February 09, 2010 3:45 PM
  • Mark -
     In Disk Manager, remove the drive letter and partition of the external HD and set up your backup via the wizard. It was probably pre-formatted with an active partition before you connected it to the computer.

    Michael

    Tuesday, February 09, 2010 3:48 PM
  • Thanks for the suggestion, but I had already tried that before I posted.  Actually, my problem has now morphed.  After I upgraded the firmware, I was able to do a complete restore of my 250 gig original drive with 2 partitions.  I then removed that drive and installed a 4 drive RAID 10, and I'm trying to restore the backup set to the RAID. The restore says it completed both partitions, but the server will not boot.  I have tried deleting the OEM partition, making the system partition active with diskpart but still it won't boot.  Dell tech support is stumped as well but they are working on it with me.  This is very exasperating!


    Techie Attorney
    • Proposed as answer by Tokoh Wednesday, October 06, 2010 8:54 PM
    Wednesday, February 10, 2010 5:03 AM
  • I was having the exact same issue:

    Win 2008 Server - "The backup operation that started at '‎2011‎-‎07‎-‎01T14:37:18.160000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

    I logged in as Administrator and then the issue was gone. Backup worked just fine!

    Hope that helps you guys.

    Friday, July 01, 2011 2:59 PM
  • (Log in as Administrator)
    RUN CMD
    1. CHANGE directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN 
    2. RUN PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
    3. RESTART IIS - If worked - Done - If Not DO 4
    4. RERUN SharePoint Product Config Wizard - DONE
    Note - It was caused by SP2010 SP1 Update.  Uninstall SP2010 SP1 will work again too. Don't change to ACTIVE on your boot drive/volume. Unless you want re-install your server again.
    • Proposed as answer by dreadhead Wednesday, October 19, 2011 10:29 AM
    Sunday, September 25, 2011 5:08 AM
  • (Log in as Administrator)
    RUN CMD
    1. CHANGE directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN 
    2. RUN PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
    3. RESTART IIS - If worked - Done - If Not DO 4
    4. RERUN SharePoint Product Config Wizard - DONE
    Note - It was caused by SP2010 SP1 Update.  Uninstall SP2010 SP1 will work again too. Don't change to ACTIVE on your boot drive/volume. Unless you want re-install your server again.
    • Proposed as answer by LaraRene Wednesday, September 28, 2011 1:55 PM
    Sunday, September 25, 2011 5:08 AM
  • Thanks Bill~

    Your post is what solved my backup issue.  ( failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129')

    Thanks for taking the time.

    Monday, September 26, 2011 2:21 PM
  • Hi

     

    I got the same problem on my Win SBS 2011 after installing an update for SharePoint, so i am thinking about trying your solution.

    But what exactly does RUN "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures" do?
    Always nice to know what a command do before I run it ;).

    Thx

    Mikael

    Wednesday, October 19, 2011 10:44 AM
  • Found this article about this issue that suggested the same PSconfig command.

    http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx

    Did as the article suggested and it worked fine. :)

     

    // Mikael

    • Proposed as answer by Mikael.132 Monday, October 24, 2011 9:02 AM
    Monday, October 24, 2011 9:02 AM
  • This worked for me!

     

    New Dell PowerEdge T310

     

    error:

    Volume Shadow copy operation failed for backup volumes with following error code '2155348129'

     

    fix:

    (Log in as Administrator)
    RUN CMD
    1. CHANGE directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN 
    2. RUN PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
    3. RESTART IIS
    Thank you billynguyen

    Thursday, November 03, 2011 2:01 PM
  • I tried all of the above; none worked but the post by "Ray Wooge" got me thinking:

     

    I did exactly what he said:

    "When using Windows Server Backup (part of 2008 Server), Choose Backup Once, Different Options, Custom (rather than Full), Advanced Settings, VSS Settings Tab, and make sure that VSS full Backup radio button is clicked upon. After this is selected backup specified files, System State or whatever you are looking to backup and it should work for you."

    I did however do the following as the error persisted and no backups were working, Now MICROSOFT, pay attention:

    I had to share my backup disk and give myself full permissions to write to the disk.

    Chose the following name to share my disk as: "Backup"

    On the backup wizard I specified a remote location \\server_name\Backup.  I then had to authenticate with my windows username and password.

    I started the backup and it did the VS snap and the backups started.

    I trust this will all those who didn't find a solution in the above posts.

     

    • Proposed as answer by 100IT Monday, January 23, 2012 8:16 AM
    Saturday, November 19, 2011 7:17 AM
  • This is how we FIXED this problem and there are many fixes listed here:

    a) Our Fix:

    - Login to the server where Windows Server Backup runs

    - Check the Event Viewer Logs under Application Services -> Backup  (Operations)

    - If you have Hyper-V running, then go to the Hyper-V section under Application Services -> Hyper-V VMS (Operations).

    - In that log, it will states which VM is causing the error.

    - Login to that VM and check the Event Viewer logs. In our case it was SQLWriter causing it.

    - Solution is simple, batch a simple script on that VM and add it to Task Scheduler to stop SQLWriter few minutes before the backup starts and then start it up few minutes afterwards. (net stop sqlwriter , net start sqlwriter)

    - If you have a local SQL server on the server you're doing Windows backup, then this may need to be done.

     

    b) Other fixes reported by users:

    - from command prompt type: diskpart

    - from command prompt type: automount  and check if automount is enabled/disabled, it need to be enabled

     

    c) Another fix (not recommended in my opinion) only works if you have Hyper-V installed:

    - Disable VSS Writer for Hyper-V using the following:

    goto registry on the server running windows backup: 

    1. hklm\software\microsoft\windowsNT\currentversion\spp
    2. Add a new key as type reg_Multi_SZ
    3. Name for new key: DisabledWriters
    4. Value for new key: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} (remember that yours may be different - run a vssadmin list writers to determine your value for the key)
    5. net stop wbengine
    6. net start wbengine

     

    I thought to combine all fixes in one as it takes alot of time just searching and finding tons of different topics with 10s posts until you see the fix. Good luck!

    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/9166eda7-d702-4b5e-b04c-142b7e73b971/

    Monday, December 03, 2012 12:51 AM
  • I have been fighting this error for the past 2 months!  I just posted our solution (mix of others) at http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/:

    • Initially I triedhttp://support.microsoft.com/kb/2009272 but it did not help (I re-implemented later).
    • I re-registered the DLL’s as perhttp://social.technet.microsoft.com/Forums/da/winservergen/thread/b4bd0deb-45d0-4661-8c50-a2b45db41103 from NareshD. I do not believe this is necessary unless there is a corruption in the system but I am noting here just in case.
    • I tried to run The PSConfig but it was failing: I had to do the following in order to make it finish successfully:
      1. (from same page athttp://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/) :
        On the migrated SBS2011 PSCDiagnostic Log I found no entry to detect or start the services SPWriterServiceInstance and SPTimerServiceInstance.
      2. I run once again the command „PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures“ in the “Bin” Folder as an administrator console session.
      3. In the moment I saw the status “Configuration task 5 of 6 is executed” I start to run the command “net start SPTraceV4 & net start SPWriterV4 & net start SPAdminV4 & net start SPSearch4 & net start SPTimerV4” ina parallel administrator console session and after that, the configuration task finished successfully.  (I just opened another cmd window and copy/paste the sequence below when I saw the status “Configuration Task x of y” on the screen:
        net start SPTraceV4
        net start SPWriterV4
        net start SPAdminV4
        net start SPSearch4
        net start SPTimerV4
        -Note SPSearch4 is disabled in our system…
        Very awkward but it worked…
    • I implementedhttp://support.microsoft.com/kb/2009272 again.
    • Backup started working with no errors.

    Constantine

    Saturday, December 15, 2012 4:54 PM
  • (Log in as Administrator)
    RUN CMD
    1. CHANGE directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN 
    2. RUN PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
    3. RESTART IIS - If worked - Done - If Not DO 4
    4. RERUN SharePoint Product Config Wizard - DONE
    Note - It was caused by SP2010 SP1 Update.  Uninstall SP2010 SP1 will work again too. Don't change to ACTIVE on your boot drive/volume. Unless you want re-install your server again.

    just for info - I had the same error message on SBS 2008. Spent too many hours on it, arrived at this post and thought I'd try it . . . (on 2008 replace the \14\ in the bin pathe with \12\)  this worked for me.

    my customer's companyweb page wasn't working and neither was the backup. both are now fixed and working fine. Thanks! :)

    Thursday, February 21, 2013 10:06 PM
  • I have a client with an Standard FE server. Sharepoint has not worked correctly for a long time. Not sure if it had something to do with WSUS being uninstalled or whatever the case may be. Anyway I figured all the Windows Server Backup problems were from sharepoint issues since it cannot even "connect to database" and Windows Server Backup ALWAYS gets VSS errors right when it starts. Backup would complete randomly about once a month. Anyway I never really cared for fixing sharepoint as the client does not use it and I have spent far too much time on it. I do care about the Server Backup though.

    So along comes browsing through posts for days on end and sure enough, just stopping the SQLWRITER before backup allowed VSS to take over and Windows Server Backup completed successfully.

    Thank you Vinicius of two years ago :)
    Tuesday, March 11, 2014 3:46 AM