Quantcast
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


Showcase


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.

older | 1 | .... | 128 | 129 | (Page 130) | 131 | 132 | .... | 160 | newer

    0 0

    I'm Using Windows Server backup.

    I think there's a bug in the bare-metal restore  (Re-Image) Process in server2016TP5

    I have created a Bare-Metal backup from Windows server 2016tp5, into a network shared folder.

    The restore (Re-Image) process is loading the installation media, choose repair, and restore the image from the network.

    what I did: Loading the Server2016TP5 ISO (Bootable USB), and trying to connect to the shared folder, It failed to connect to the server with the following error: "A specified logon session does not exist. It may already have been terminated (0x80070520)"

    I get the same error for Hyper-V Virtual computer, and a Bare Metal (Physical) Server.

    Why I think it is a bug ?

    I tried to Bare-Metal restore the 2016TP5 with ISO of 2012R2, with exactly the same process (Same network account), it finds the backup files, but I get different error because it can restore Windows 2012R2 only (That error indicate that the backup data is accessible to the 2012R2 Re-Image process

    I Also Try to bare-metal backup an restore 2012R2, on the same shared folder (Same account), It worked great on virtual, and Physical system.

    can anyone confirm ?

    did I do something wrong here ?




    0 0

    Summary:

        The Windows Backup utility fails when run automatically.

    Details:

        The backup fails with error code "'0x80780034' (Windows Backup failed to create the shadow copy on the storage location.)"

       The associated VSS error event: "Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy549\,0x80000000,0x00000003,...).  hr = 0x80070013, The media is write protected."

    Step Already Taken:

        Checked to make sure the VSS was actually running, and changed the startup type to "automatic"

        Checked to make sure the backup volume was writable. (it is)

        Searched google for similar issues and found none. (though a plethora of windows backup and VSS errors were found, none fit the issue)

    Notes:

        The volume is a mounted iSCSI drive.

        The backup succeeds if triggered manually.




    0 0

    OK, we all know that BMR is really intended for restore on identical HW.  For reasons that some of you may know, I need to migrate from a Dell server with a PERC S130 to the same HW but using a real RAID card, say a PERC H330.  Here's what I tried:

    a) Did a BMR backup to an external drive

    b) Removed the old drives and old RAID controller

    c) Inserted brand spanking new drives and the new RAID controller

    d) Restored

    Restore went well, but got the proverbial blue screen of death.  I realized that there is probably a driver issue at hand, but not certain as the restore proceeded -- that is, the restore wrote onto the new disk array.

    In any case, I have two ideas in my head:

    a) Try putting the NEW RAID controller in the box without any drives connected to it while running on the old RAID.  Hopefully Windows will detect new HW and either load a driver or ask to have a driver loaded (which I have).  After that, do the BMR backup, remove the old RAID, swap in the new RAID and drives and hopefully, the restore image will have the right drivers.

    b) Just install the driver for the new RAID while running on the old RAID (not bothering with actually installing the HW), then doing the BMR backup, and so forth.

    Before blowing another few hours on this, any words of wisdom?

    Ken


    0 0

    Hi,

    Am using SBS 2011 - have an external drive with backups on it (Server Backup), the drive has corrupted etc and on inspecting it through active partition the data is there but it shows the drive as unallocated space, I need to do a bare metal restore, what is the best way to do this, without destroying the data

    The drive has only ever been used as a backup drive on the server

    Any help would be appreciated

    Thanks in advance


    0 0

    Environment:

    Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.

    Background:

    My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.

    I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.

    For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.

    Problem:

    When I try to run the Backup Once operation to test my backup, I get the following error message:

    "Windows Backup cannot read the backup destination."

    What I've tried:

    I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.

    Adding the backup user to the Administrators group did not have an effect.

    Update 2014-02-18

    I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully.However, Backup Once always results in the above error message. So the problem is confined to the "Backup Once" operation.



    0 0

    good morning to all,

    here is what i am trying to accomplish: I have one server (server1) that i would like to backup on another server (server2). i am already running a windows server backup and excluded some folders because of the 2tb size limit, so i want to backup those excluded files onto another server. this is what i am typing in:

    wbadmin start backup -backupTarget:e: -include:\\server1\sharedfiles\photos

    this should backup server1 to server 2 e drive. i see retrieving volume information... ERROR-the file "\\server1\sharedfiles\photos" is invalid

    i have tried 'before the\\ and after photos, i have tried to enter the volume name of server 1 as

    wbadmin start backup -backupTarget:e: -include:\\server1\Volume{b9e7a2d0-0000-0000-0000-000000000000}sharedfiles\photos

    i still get the the specified file name in the file spec is invalid

    any ideas?


    0 0

    I am running windows server 2012 as a Domain controller and wanting to trim the backups as the disk is getting full.

    I would like to know if running "Wbadmin delete backup -deleteoldest" deletes BOTH backup and systemstate of combined backups?

    I run a daily backup job of the main drive and system state and I seem to have the impression I needed to delete both the backup and systemstate elements separately?

    The issue is that when I run the delete process for the system state it states that "ERROR - No system state backups were found."

    I have read that you need to run the two seperate deleations if your running the backup and system state elements seperatly which I am not.

    Can you clarify this for me?

    Secondly, Do the backups automatically trim themselves when the drive gets full?

    Many thanks

    Don



    0 0

    Summary:

        The Windows Backup utility fails when run automatically.

    Details:

        The backup fails with error code "'0x80780034' (Windows Backup failed to create the shadow copy on the storage location.)"

       The associated VSS error event: "Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy549\,0x80000000,0x00000003,...).  hr = 0x80070013, The media is write protected."

    Step Already Taken:

        Checked to make sure the VSS was actually running, and changed the startup type to "automatic"

        Checked to make sure the backup volume was writable. (it is)

        Searched google for similar issues and found none. (though a plethora of windows backup and VSS errors were found, none fit the issue)

    Notes:

        The volume is a mounted iSCSI drive.

        The backup succeeds if triggered manually.




    0 0

    What is the difference between VSS full backup and VSS copy backup?

    Kindly help me to with simple explanation which is easy to understand, instead of sharing reference web link.

    If anyone can tel each points one by one.

    0 0
  • 09/10/16--08:46: Not savvy
  • Since my external drive died I will be using the cloud and in the past I always used the clone back up because when restored there is nothing to think about. Win7 is getting wonky and I was thinking of doing another clone back up, restoring Win7 to factory then restoring the clone. Will clone just give me back the wonkiness and negate the fresh Win7. Any adice is appreciated.

    0 0

    I have found fixes for Server 2008 and 2008 R2 but have yet to find a resolution 
    for Server 2012 R2.  I have worked with EMC to try a resolve with no
    luck.  The issue is the e:\ volume is on the other node in the cluster but
    is looking at this path due to a SAP service that installed to this
    cluster volume location on this node "e:\usr\sap\trn\ascs01\exe\sapstartsrv.exe".  
    Below is the VSS event id, vssadmin list writers, and diskshadow output for
    further information.

    ________________________________________

    Event Id 8193, VSS -- I am receiving at every backup attempt:

    Volume Shadow Copy Service error: Unexpected error calling
    routine GetVolumePathName is fail on the path e:\usr\sap\trn\ascs01\exe,
    winerror 0x00000002.. hr = 0x80070002, The system cannot find the file
    specified.

    Operation:

    PrepareForSnapshot Event

    Context:

    Execution Context: Writer

    Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}<o:p></o:p>

    Writer Name: System Writer

    Writer Instance ID:
    {b37cf597-c4a9-46ec-a4f1-f834daf9295c}

    ______________________________________________

    Output for vssadmin list writers

    Microsoft Windows [Version 6.3.9600]

    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001-2013 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'

       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

       State: [1] Stable

       Last error: No error

    Writer name: 'VSS Metadata Store Writer'

       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

       State: [1] Stable

       Last error: No error

    Writer name: 'Performance Counters Writer'

       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

       State: [1] Stable

       Last error: No error

    Writer name: 'System Writer'

       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

       Writer Instance Id: {51014fc6-79fc-4719-a47e-890c12eae4af}

       State: [1] Stable

       Last error: No error

    Writer name: 'Cluster Shared Volume VSS Writer'

       Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}

       Writer Instance Id: {ca77048d-6a55-429d-8156-cd20cd480286}

       State: [1] Stable

       Last error: No error

    Writer name: 'SqlServerWriter'

       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Instance Id: {02ce344c-fee1-471e-add1-80fc0f0eab1c}

       State: [1] Stable

       Last error: No error

    Writer name: 'ASR Writer'

       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

       Writer Instance Id: {7470832b-d895-43e1-bb24-4ba2411fa7bf}

       State: [1] Stable

       Last error: No error

    Writer name: 'Registry Writer'

       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

       Writer Instance Id: {0591d297-755a-426e-83de-20dbc24d4a8a}

       State: [1] Stable

       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'

       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

       Writer Instance Id: {a163cc77-d300-4089-a5fb-2a45c33deb14}

       State: [1] Stable

       Last error: No error

    Writer name: 'Cluster Database'

       Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}

       Writer Instance Id: {a717560f-50db-4771-99bc-03a68aa01f5d}

       State: [1] Stable

       Last error: No error

    Writer name: 'COM+ REGDB Writer'

       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

       Writer Instance Id: {6a4a6d8b-4b54-4904-8bf9-9433120b1aad}

       State: [1] Stable

       Last error: No error

    Writer name: 'WMI Writer'

       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

       Writer Instance Id: {2ff1dddd-8586-43f0-a824-e4025d538a3f}

       State: [1] Stable

       Last error: No error

    ______________________________________________

    Output for diskshadow

    C:\Windows\system32>diskshadow

    Microsoft DiskShadow version 1.0

    Copyright (C) 2013 Microsoft Corporation

    On computer:  AOTRNCL01,  9/11/2015 8:08:51 AM



    DISKSHADOW> add volume c:

    DISKSHADOW> create

    COM call
    "lvssObject4->GetRootAndLogicalPrefixPaths" failed.

    Alias VSS_SHADOW_1 for shadow ID {a817c807-f00b-496b-b799-06a15a6f9e0f} set as
    e

    nvironment variable.

    Alias VSS_SHADOW_SET for shadow set ID {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}
    se

    t as environment variable.

    Querying all shadow copies with the shadow copy set ID
    {e9ce9d2b-97d0-4415-ae49-

    2ec7b5b3c87d}

            * Shadow copy
    ID = {a817c807-f00b-496b-b799-06a15a6f9e0f}

    %VSS_SHADOW_1%

                   
    - Shadow copy set: {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}

    %VSS_SHADOW_SET%

                   
    - Original count of shadow copies = 1

                   
    - Original volume name: \\?\Volume{bcb4e1e6-f8a3-11e4-80bf-806e6

    f6e6963}\ [C:\]

                   
    - Creation time: 9/11/2015 8:09:38 AM

                   
    - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeS

    hadowCopy1

                   
    - Originating machine: AOTRNCL01.waterone.org

                   
    - Service machine: AOTRNCL01.waterone.org

                   
    - Not exposed

                   
    - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}

                   
    - Attributes:  Auto_Release Differential

    Number of shadow copies listed: 1




    0 0

    Summary:

        The Windows Backup utility fails when run automatically.

    Details:

        The backup fails with error code "'0x80780034' (Windows Backup failed to create the shadow copy on the storage location.)"

       The associated VSS error event: "Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy549\,0x80000000,0x00000003,...).  hr = 0x80070013, The media is write protected."

    Step Already Taken:

        Checked to make sure the VSS was actually running, and changed the startup type to "automatic"

        Checked to make sure the backup volume was writable. (it is)

        Searched google for similar issues and found none. (though a plethora of windows backup and VSS errors were found, none fit the issue)

    Notes:

        The volume is a mounted iSCSI drive.

        The backup succeeds if triggered manually.




    0 0

    Dear All 

    good Day 

    we issue From windows server standard R2 2008

    black screen with mouse pointer  when logging into windows server 2008 r2  

    the user profile service failed the logon windows

    i tested several command from Dos And safe mode ; Not solved The issue

    i have a original copy with serial windows server standrd 2012 can i upgrade from windows server 2008 to windows server 2012 

    i have image  backup before 2 years can i restore without remove any new  files and  configuration role

    please help



    0 0

    - Have a Hyper-V Host (Server Core) that I want to backup to a locally attached USB Disk.

    - Have a 2012 R2 management server where I have installed the Windows Backup feature as well.

    Although it's not possible to connect to the remote Hyper-V host from the Windows Backup GUI directly (very strange and I can not understand this), it's possible to launch "Computer Management", connect to the remote Hyper-V host, and then launch the Windows Backup GUI from inside the computer management.

    Can successfully configure and monitor the Windows Server Backup jobs this way. However, when I try to recover anything from the Hyper-V Host to an alternate location, absolutely no recovery  destination is accepted. Have tried a path on the management server, as well as on the Hyper-V host, but always getting the following error:

    How can I recover anything from the Hyper-V host from the Windows Backup GUI? Recover data directly on the Hyper-V host with wbadmin.exe or any scripts is much too complicated for our service desk employees.

    Thank you in advance for any help.

    Franz



    0 0
  • 09/14/16--02:59: LTO 7 Support
  • Hi,

    I only have a short question:

    Does Server 2008 R2 or older support LTO 7?

    I got an IBM Streamer but can't find driver for it.

    Thanks for help.


    0 0

    I have a number of Windows 2012 R2 server domain controllers backing up to network shares at their locations.
    In testing I have never been able to get the restore environment to see/recognize and work with any of my backups. 
    I get the error: Windows cannot find a system image on this computer with any attempt to restore when I try to use a copy from the network share back to a USB thumb drive or USB hard drive or locally connected hard disk.  

    I also have been unable to restore directly from the network share. \\servername\sharename 
    Where the original WindowsImageBackup folder resides.  

    Everything appears to work fine when backing up to the share no errors and get a success message. But I have been unable to use my backups they are not recognized in the restore environment after being copied to a hard drive from the network share or directly on the network.  

    All files on the copy appear to be fully intact not corrupt the correct size and in the correct expected place on the root of the drive I am copying to.  

    Also a further note is that it works fine if I backup to a locally connected drive (sata or usb)
    The recovery environment does recognize this locally made backup. 

    However if I take the WORKING WindowsImageBackup hard drive and hook it to my laptop
    And simply copy the WindowsImageBackup directory to a USB thumb drive (on my laptop) 
    the recovery environment does NOT recognize my backup on that thumb drive or on any other drive I copy it to even though the files were copied directly from the working drive (I bypassed the network and backup to share).

    Recovery environment in all cases sees the drive itself and all my backup files as I can browse the drive just fine with command prompt or "browse for driver" function. 
    But it will not see/recognize my image backup once copied to another drive or if I backup to a network share and copy that to a drive.  

    Incredibly frustrating and confusing.  

    I am on day 4 trying to figure this out and have been all over Google have not found an answer.  

    I also have a lot of servers in the field backing up to NAS systems that may be completely useless for restore other than good VHDX files where I could mount them for files. 
    But I need to be able to restore these servers from my backups. 











    0 0

    I am using 2012 R2 WSB. All of my backups are within the last 30 days. However, the oldest copy is January 2016. It indicates in on a volume I think no longer exist. When I launch the recovery wizard and go to the backup in question, it says the status is offline.

    How can I correct this?

    Thank you


    0 0

    Backups Fail due to VSS error due to C:\Windows\Microsoft.Net have more than 1k subdirectories... no hotfix for server 2012 r2?  Found this KB https://support.microsoft.com/en-us/kb/2807849 but it won't apply to server 2012 r2.  We're about ready to spend $500 dollars to have some Microsoft lacky NOT be able to help for months I'm sure.  Anyone experience this?

    0 0

    I have found fixes for Server 2008 and 2008 R2 but have yet to find a resolution 
    for Server 2012 R2.  I have worked with EMC to try a resolve with no
    luck.  The issue is the e:\ volume is on the other node in the cluster but
    is looking at this path due to a SAP service that installed to this
    cluster volume location on this node "e:\usr\sap\trn\ascs01\exe\sapstartsrv.exe".  
    Below is the VSS event id, vssadmin list writers, and diskshadow output for
    further information.

    ________________________________________

    Event Id 8193, VSS -- I am receiving at every backup attempt:

    Volume Shadow Copy Service error: Unexpected error calling
    routine GetVolumePathName is fail on the path e:\usr\sap\trn\ascs01\exe,
    winerror 0x00000002.. hr = 0x80070002, The system cannot find the file
    specified.

    Operation:

    PrepareForSnapshot Event

    Context:

    Execution Context: Writer

    Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}<o:p></o:p>

    Writer Name: System Writer

    Writer Instance ID:
    {b37cf597-c4a9-46ec-a4f1-f834daf9295c}

    ______________________________________________

    Output for vssadmin list writers

    Microsoft Windows [Version 6.3.9600]

    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001-2013 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'

       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

       State: [1] Stable

       Last error: No error

    Writer name: 'VSS Metadata Store Writer'

       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

       State: [1] Stable

       Last error: No error

    Writer name: 'Performance Counters Writer'

       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

       State: [1] Stable

       Last error: No error

    Writer name: 'System Writer'

       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

       Writer Instance Id: {51014fc6-79fc-4719-a47e-890c12eae4af}

       State: [1] Stable

       Last error: No error

    Writer name: 'Cluster Shared Volume VSS Writer'

       Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}

       Writer Instance Id: {ca77048d-6a55-429d-8156-cd20cd480286}

       State: [1] Stable

       Last error: No error

    Writer name: 'SqlServerWriter'

       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Instance Id: {02ce344c-fee1-471e-add1-80fc0f0eab1c}

       State: [1] Stable

       Last error: No error

    Writer name: 'ASR Writer'

       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

       Writer Instance Id: {7470832b-d895-43e1-bb24-4ba2411fa7bf}

       State: [1] Stable

       Last error: No error

    Writer name: 'Registry Writer'

       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

       Writer Instance Id: {0591d297-755a-426e-83de-20dbc24d4a8a}

       State: [1] Stable

       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'

       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

       Writer Instance Id: {a163cc77-d300-4089-a5fb-2a45c33deb14}

       State: [1] Stable

       Last error: No error

    Writer name: 'Cluster Database'

       Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}

       Writer Instance Id: {a717560f-50db-4771-99bc-03a68aa01f5d}

       State: [1] Stable

       Last error: No error

    Writer name: 'COM+ REGDB Writer'

       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

       Writer Instance Id: {6a4a6d8b-4b54-4904-8bf9-9433120b1aad}

       State: [1] Stable

       Last error: No error

    Writer name: 'WMI Writer'

       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

       Writer Instance Id: {2ff1dddd-8586-43f0-a824-e4025d538a3f}

       State: [1] Stable

       Last error: No error

    ______________________________________________

    Output for diskshadow

    C:\Windows\system32>diskshadow

    Microsoft DiskShadow version 1.0

    Copyright (C) 2013 Microsoft Corporation

    On computer:  AOTRNCL01,  9/11/2015 8:08:51 AM



    DISKSHADOW> add volume c:

    DISKSHADOW> create

    COM call
    "lvssObject4->GetRootAndLogicalPrefixPaths" failed.

    Alias VSS_SHADOW_1 for shadow ID {a817c807-f00b-496b-b799-06a15a6f9e0f} set as
    e

    nvironment variable.

    Alias VSS_SHADOW_SET for shadow set ID {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}
    se

    t as environment variable.

    Querying all shadow copies with the shadow copy set ID
    {e9ce9d2b-97d0-4415-ae49-

    2ec7b5b3c87d}

            * Shadow copy
    ID = {a817c807-f00b-496b-b799-06a15a6f9e0f}

    %VSS_SHADOW_1%

                   
    - Shadow copy set: {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}

    %VSS_SHADOW_SET%

                   
    - Original count of shadow copies = 1

                   
    - Original volume name: \\?\Volume{bcb4e1e6-f8a3-11e4-80bf-806e6

    f6e6963}\ [C:\]

                   
    - Creation time: 9/11/2015 8:09:38 AM

                   
    - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeS

    hadowCopy1

                   
    - Originating machine: AOTRNCL01.waterone.org

                   
    - Service machine: AOTRNCL01.waterone.org

                   
    - Not exposed

                   
    - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}

                   
    - Attributes:  Auto_Release Differential

    Number of shadow copies listed: 1




    0 0

    Summary:

        The Windows Backup utility fails when run automatically.

    Details:

        The backup fails with error code "'0x80780034' (Windows Backup failed to create the shadow copy on the storage location.)"

       The associated VSS error event: "Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy549\,0x80000000,0x00000003,...).  hr = 0x80070013, The media is write protected."

    Step Already Taken:

        Checked to make sure the VSS was actually running, and changed the startup type to "automatic"

        Checked to make sure the backup volume was writable. (it is)

        Searched google for similar issues and found none. (though a plethora of windows backup and VSS errors were found, none fit the issue)

    Notes:

        The volume is a mounted iSCSI drive.

        The backup succeeds if triggered manually.




older | 1 | .... | 128 | 129 | (Page 130) | 131 | 132 | .... | 160 | newer