Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

This forum supports questions for the default backup utility in Windows Vista, Server 2008 and beyond. For questions on NTBackup or Windows Server 2003/XP, please use the “File services and storage" forum.
    0 0

    After the Windows 10 version 1803 upgrade on April 30, 2018, my System Image Backup keeps failing withe two messages. "The backup failed" "The RPC server is unavailable (0x800706BA)".

    Note that the System Image Backup worked before the upgrade. The upgrade completed OK and I have not found any other issues.

    I checked that =1= The RPC (Remote Procedure Call) service in Services is active and running and =2= the DCOM (Distributed COM) is enabled. There used to be a SYSTEM disk when I did the defrag, the defrag does not show the SYSTEM disk in version 1803.

    Is it a bug, or is there a fix or should I try the Image Recovery (that might fail as well).


    0 0

    What is the best practice for backing up a Windows Server 2008 R2 environment so that it can be restored to different hardware if need be with Active Directory etc. intact?

    What needs to be considered in setting up the environment so that it can be recovered later and work correctly? In this case just two servers.

    Can I just use the bare metal backup from wbadmin?

    0 0
  • 08/01/18--23:46: VSS Error while backup
  • Dear All,

    I am trying to take native backup of c:\ drive of exchange server, I am getting below error

    Writer Failures
    Writer Id: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}
    Instance Id: {A01059CF-04ED-4AA6-A02A-C7ACC78B9A3B}
    Writer Name: Microsoft Exchange Writer
    Writer State: 9
    Failure Result: 800423F3
    Application Result: 1
    Application Message: (null)

    Thanks

    Aziz



    Aziz


    0 0
  • 08/06/18--06:20: Back up error
  • An error prevented Backup from creating a snapshot of the volumes on this computer.

    For more information about this issue, see the event logs on the computer that you are backing up. For information


    0 0

    Have setup the backup destinations for the external drives I am trying to use on two servers. It works fine on one but keep getting this error on the second one that is running oracle/opera database software tried a couple different external drives using the Wbadmin get disks command and like I said the one server no issues. Both servers are running Server 2008 R2 Standard. Any ideas why the error ?

    Regards,

    Randy Mykes

    Netdigix


    0 0

    I have the backup set to backup roughly 2,2Tb of data to an internal 3,2Tb HDD. The issue becomes after the first backup is completed no further backups can be done do to wsb not overwriting the old backups.


    When in doubt empty the magazine...


    0 0

    We have a Windows Server 2012 R2 fully patched.

    Running the Native Windows Backup hangs the Server and we have to cancel it. In backup logs show (below).

    We stop/started the relevant VSS services and ran a SFC we comes up ok. I'm at a loss what could cause this.

    Writer Failures
    Writer Id: {BE000CBE-11FE-4426-9C58-531AA6355FC4}
    Instance Id: {AF62ABED-1801-4922-8239-E117D995CC44}
    Writer Name: ASR Writer
    Writer State: 9
    Failure Result: 800423F2
    Application Result: 1
    Application Message: (null)
       Component: ASR
       Logical Path: ASR
       Component Result: 800423F2
       Component Message: (null)
       Component: Volume{a56d3c5e-2871-499b-84e2-ad086d27839f}
       Logical Path: Volumes
       Component Result: 800423F2
       Component Message: (null)
       Component: harddisk0
       Logical Path: Disks
       Component Result: 800423F2
       Component Message: (null)
    Writer Id: {542DA469-D3E1-473C-9F4F-7847F01FC64F}
    Instance Id: {2EFE3C03-DEED-42CD-8E9C-6F1E8331D05B}
    Writer Name: COM+ REGDB Writer
    Writer State: 9
    Failure Result: 800423F2
    Application Result: 1
    Application Message: (null)
       Component: COM+ REGDB
       Logical Path: (null)
       Component Result: 800423F2
       Component Message: (null)
           File Spec: C:\Windows\Registration\* Recursive: 1
    Writer Id: {4DC3BDD4-AB48-4D07-ADB0-3BEE2926FD7F}
    Instance Id: {8A902016-0DAE-4F71-A627-34978D8F198E}
    Writer Name: Shadow Copy Optimization Writer
    Writer State: 9
    Failure Result: 800423F2
    Application Result: 1
    Application Message: (null)
       Component: IISMETABASE
       Logical Path: (null)
       Component Result: 800423F2
       Component Message: (null)
    Writer Id: {AFBAB4A2-367D-4D15-A586-71DBB18F8485}
    Instance Id: {06D0F689-C3D2-4766-B95A-8C6C967F1193}
    Writer Name: Registry Writer
    Writer State: 9
    Failure Result: 800423F2
    Application Result: 1
    Application Message: (null)
       Component: Registry
       Logical Path: (null)
       Component Result: 800423F2
       Component Message: (null)
           File Spec: C:\Windows\system32\config\default Recursive: 0
           File Spec: C:\Windows\system32\config\SAM Recursive: 0
           File Spec: C:\Windows\system32\config\SECURITY Recursive: 0
           File Spec: C:\Windows\system32\config\software Recursive: 0
           File Spec: C:\Windows\system32\config\system Recursive: 0
           File Spec: C:\Windows\System32\SMI\Store\Machine\schema.dat Recursive: 0
           File Spec: C:\Windows\system32\config\COMPONENTS Recursive: 0
           File Spec: C:\Windows\system32\config\DRIVERS Recursive: 0
           File Spec: C:\Windows\system32\config\BBI Recursive: 0
    Writer Id: {2A40FD15-DFCA-4AA8-A654-1F8C654603F6}
    Instance Id: {0CDBEC47-9461-4EE5-827A-02FD7349F86F}
    Writer Name: IIS Config Writer
    Writer State: 9
    Failure Result: 800423F2
    Application Result: 1
    Application Message: (null)
       Component: IISCONFIG
       Logical Path: (null)
       Component Result: 800423F2
       Component Message: (null)
           File Spec: C:\Windows\system32\inetsrv\config\* Recursive: 0
    Writer Id: {A6AD56C2-B509-4E6C-BB19-49D8F43532F0}
    Instance Id: {45680552-4D9F-4962-875A-237274A27681}
    Writer Name: WMI Writer
    Writer State: 9
    Failure Result: 800423F2
    Application Result: 1
    Application Message: (null)
       Component: WMI
       Logical Path: (null)
       Component Result: 800423F2
       Component Message: (null)
           File Spec: C:\Windows\system32\wbem\repository\*.* Recursive: 1
    Writer Id: {59B1F0CF-90EF-465F-9609-6CA8B2938366}
    Instance Id: {42233C65-D27C-4D90-8BCC-CAB3D41716C9}
    Writer Name: IIS Metabase Writer
    Writer State: 9
    Failure Result: 800423F2
    Application Result: 1
    Application Message: (null)
       Component: IISMETABASE
       Logical Path: (null)
       Component Result: 800423F2
       Component Message: (null)
           File Spec: C:\Windows\system32\inetsrv\MetaBase.XML Recursive: 0
           File Spec: C:\Windows\system32\inetsrv\MBSchema.XML Recursive: 0
    *-----------------------------*


    Backup of volume C: has failed. The operation was cancelled by the user.


    www.software-kinetics.co.uk Dependable Software


    0 0

    I have three Microsoft Windows Server 2012 R2 Standard servers running on Dell PowerEdge machines that serve as Hyper-v hosts for my various virtual machines.   Each server has a scheduled backup similar to the following:

    Notes:

    • Each scheduled backup is configured to be a "VSS Full Backup".
    • Some backups show the VMs as online and some show as offline.

    The issue is that the backups will run for several days successfully and then will stop running.   After the backups begin to fail, I see the following when I open Windows Server Backup tool.

    I also see Event 19 in the event log when the scheduled backup runs:

    • The backup operation attempted at '?2018?-?06?-?04T02:00:01.583169900Z' has failed to start, error code '0x8007000E' ('Ran out of memory'). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    If I attempt to run the backup using the wbadmin command line, I see the following error:

    • Not enough storage is available to complete this operation.

    If I sign out and then sign on, the issue is immediately resolved and I can see the backup history in the Windows Server Backup tool.   The backup will run again for several days until the issue occurs again.

    The cycle of the issue on the three machines is very similar.  In other words, the backup will run successfully on all three machines for 2 days and then fail on all three machines and continue to fail until I sign in, sign out and then sign in.

    Note: After verifying that the server backup is running with a sign in, sign out & sign in.  I typically sign out again.

    Any ideas?



    0 0

    Hi,
    When I create a Windows Server 2012 R2 backup, I receive the error:
    "This version does not support this version of the file format."
    What could be the reason and how to eliminate it?
    Thank you,
    Pawel

    0 0
  • 08/10/18--03:04: VSS Bakcup Service
  • I have server 2008R2 Standard OS.

    Windows Server backup is not working, VSS Writers also not listed and Tried to re register but nothing work for me. When open windows server backup it also gave error " A Fatal error occurred during a windows server backup snap in(wbadmin.msc) operation error detail  unknown error 0x80042302

    System Event ID : 7031 : The Volume Shadow Copy service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.

    Application Event ID : 12347 : Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. The Registry Writer failed to respond to a query from VSS. Check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.

    Event ID : 521 : The backup operation that started at '‎2018‎-‎08‎-‎01T07:16:00.109000000Z' 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 '2164261129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Windows server backup unknown error 0x80042318


    I have also tried to remove Windows Server Backup feature and installed again.

    Can anyone help on this?

    Thanks

    Ashu



    0 0
  • 08/10/18--03:11: Resilient Change Tracking
  • Can i use Resilient Change Tracking with Windows Server Backup? - If yes, how?

    I did a backup on Hyper-v Server 2016 with performance set to incremental to an internal volume. I expected to see files like *.mrt and *.rct in the directory of the virtual hard disks, but there isn't.

    Any links to that topic are welcome.

    Thanks, S.


    0 0

    I have tried to run a bare metal backup on 2 servers now. 2016 Server with Hyper-V with 1 VM(MS SQL) and an RD server with 2016 server. Both have failed. 

    So... I find it funny that there is a dedicated forum to Windows Server backup and what the hell am I doing wrong. Both servers throw and error something along the lines of: "

    Backup of volume C: has failed. The requested operation could not be completed due to a virtual disk system limitation.  Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.

    Is this telling me I need to move all VMs and RD's to a secondary volume?


    0 0

    Hello,

    I am experiencing sporadic Windows backup failures on my server. I am backing up to an 8TB USB drive and have tried multiple drives from different vendors. Some nights the backups complete successfully. Some nights I get the following errors:

    There was a failure in preparing the backup image of one of the volumes in the backup set. 
    Detailed Error: The  process cannot access the file because it is being used by another process.

    Other nights I get a warning with this message:

    There was a failure while compacting the virtual hard disk on the backup location.


    I have Antivirus completely disabled and have ensured that no other backup sets are running at the time of the backups. I have also disabled other non-Microsoft services. I have turned of all power-saving settings on the server. I can't seem to track down what could be causing file locks. Any help is much appreciated.


    0 0

    Hi Guys,

    We have a Multi DC domain setup with 2 servers in the main office, which are used as main DCs. Each of the branches has a DC on site (all are in the same domain).

    We want to set up a disaster recovery plan wherein we want to restore the AD to a particular date. How should we go about restoring the machines?

    Cheers

    Edward.


    0 0

    I just got off a chat with McAfee support and they acknowledged an existing critical issue with the current (as of 8/15/2018) version of McAfee and Quickbooks 2017.  The problem is when you start QB the McAfee process MFEVTPS.EXE uses virtually all cpu resources rendering the PC unusable and requiring the reboot of the PC.  Since this critically affects businesses using QB I asked if they could pull the defective version and post the prior version till this issue is resolved.  They declined stating that people could either wait for the fix, upgrade to QB2018, or uninstall McAfee and use Windows security.  I need to access QB for my business so I'm going to uninstall McAfee and install Norton till this is fixed. It took me about 2 days to figure out what the issue was, so I'm hoping this post will help people who are having this issue

    0 0

    Dear All,

    I have a problem with Shadow Copy on Windows Server 2016 Standard (Licensed). I am running as File Server Failover Cluster. My storage is Synology DS1517+ (HA Storage). I have created a volume and a storage pool (12TB). I have create 4 ISCSI targets and 4 LUNs to provide ISCSI client to connect. I have connected and succeed via ISCSI client and the drives are usable. 

    Next, I want to configure Shadow Copy for all drive that linked from ISCSI initiator client to the storage (Synology). I can configure shadow copy volume on ONLY one drive (Y: drive) and show on previous version of windows explorer and another drives (X, Q and Z) are can create on drive property but it's not show on the previous version of Windows explorer on that drive.

    What is the main issue? Is it issue from Single Volume/Storage pool or another issue?

    Note: if I can configure shadow copy on many drives on VMWare

    Thank you,

    Sor


    0 0

    Hi everyone,

    I got a problem when I use Avamar on some servers, only Windows Server Enterprise. The backup is not working, and when I'm looking into logs, I can see that I got an error about "System Writer". Indeed, when I launch "vssadmin list writers", I should see "System writer" but I don't.

    I searched on internet to get some solutions, like giving some rights on some folders, but it changed nothing and then I saw that I could install the Fix484021 to fix it. But... the fix isn't working on my OS :( (link : https://support.microsoft.com/en-us/help/2911752/system-writer-is-missing-and-backups-fail-in-windows-server-2008)

    I tried to contact the support by chat, but I don't get an answer from it because it's laggy.

    Waiting for help.

    Thanks in advance.

    Regards,

    Clément.


    0 0

    Hi,

    one of our W2K12 R2 Std Server always stops with BSOD 0xEF or 0x7A when Windows Server Backup ist starting.

    After many hours of research and trying, i found out, that there must be a problem with the registered writers for VSS. The 'DISKSHADOW' command 'LIST WRITERS' leads to same BSOD's.

    My questions about that:

    1. I did not find the registry key's where the vss writers are registered to check them manually. Does any1 know where the writers are registered?

    2. Does any1 know how to repair the registry for the vss writers? I found this article 'http://kb.macrium.com/KnowledgebaseArticle50010.aspx' from 2014 but im not sure if this is still a good advice for W2K12 R2 server?

    Any help appreciated. Thanks in advance!

    Michael



    0 0

    I have a Windows 2016 server with a 3rd party backup solution installed and working.  But it is failing every other night because Windows Server Backup is also running.  The problem is that I never scheduled Server Backup to run.  The Server Backup GUI states that "A scheduled backup has not been configured for this computer".  I find nothing in Task Manager related to backups.  And running Get-ScheduledTask also shows nothing that appears to be related to Server Backup.  Below is a list of everything from Get-ScheduledTask.  Am I missing something?  There are 289 backups listed in the GUI!

    Thanks,
    Joe




    0 0

    Hi,

    We have a situation while using WBADMIN in a scheduled task. We have a user, called Admin that belongs to the Domain Administrators. There's a task that performs a backup to a USB hard disk, defined in the Scheduled Tasks.

    This is the command line

    wbadmin start backup -BackupTarget:F: -include:C:, E: -allcriticall -SystemState -quiet

    The operating system is Windows Server 2012.

    The task is set to run with highest privileges and regardless if the user is logged on or not.

    The task doesn't execute, however the command line does run if we run CMD as Administrator and execute the above command.

    How can we solve this?

    Best Regards,

    Nélio Abreu