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 | .... | 57 | 58 | (Page 59) | 60 | 61 | .... | 148 | newer

    0 0

    I have a new Dell R710 that I have 2008 Server R2 64-bit installed. It's role is file server. I first noticed there were VSS initialization issues in BackupExec and that the system state wasn't getting backed up.
     
    Then I would run "vssadmin list writers" from CMD and system writer would be timing out....
     
    Writer name: 'System Writer'
        Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
        Writer Instance Id: {18370018-3454-46cf-a352-db13b2536aa6}
        State: [7] Failed
        Last error: Timed out
     
    I would also get Event ID 12289 Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} - 0000000000000140,0x0053c020,00000000003BDFD0,0,00000000003BBFA0,4096,[0]).  hr = 0x80070057, The parameter is incorrect.
     
    I would also get Event ID 12293 Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = 0x8000ffff, Catastrophic failure
     
    Also event ID 22 for volsnap The shadow copy storage volume specified for shadow copies on volume\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} could not be added.
     
    Also I can't configure shadow copies due to error 0x8004230f "Failed to retrieve volumes that are eligible for shadow copies.

    PLEASE HELP!


    0 0

    Hello!

    I have a problem with two VM´s on a HP Proliant ML350p Gen8, that has Windows Server 2012R2 operating system with Hyper-V role installed.

    Both VM´s are also 2012R2, one is DC/DNS/FILE/PRINT and the other one is Exchange 2013.

    The problem itself is that, when Windows backup (wbengine.exe - Block level backup engine service) inside VM starts, it uses almost maximum CPU resource, so the VM´s CPUs are 100% used. Backup itself is not working, there is no network trafic. Only way to get rid of 100% CPU usage is to restart the server.

    When i start backup manually (Backup once - scheduled backup options), it is working and the CPU usage is around 20-30%.

    One VM (DC/DNS/FILE/PRINT) has 2x vCPU and Exchange has 4x vCPU.

    The problem started suddenly, the backup were performing slowly and failed.

    Backups are scheduled on different time. Host level Hyper-V backup of VM´s works without any problem.

    The backup location is Synology DS414 NAS and the servers are set up using iSCSI, for connecting separate backup lun´s for each server.

    The Hyper-V host and both VM´s are patched up-to-date. Ofcourse i have tried a lot of restarts, looking event log, VSSADMIN - cannot find any errors...

    The network setup:

    Hyper-V host has a team of two physical adapters, that is set up with a external virtual switch (shared with management operating system) and used by the VM`s normal network trafic.

    Hyper-V host itself is using separte physcial network card, for connecting with iSCSI to Synology NAS.

    I tried to set up another physical network card on the host and create a new virtual swich, add extra virtual nic to VM`s and use this for iSCSI traffic for Windows backup and it didnt make things better.

    I need to find a solution, because i cannot restart the server every night for the backups to work.


    0 0

    Server 2012 R2 Datacenter

    Source : volsnap

    event id : 20

    The shadow copies of volume C: were aborted because of a failed free space computation.

    Please Help


    0 0

    Server 2012 R2 Datacenter

    Source : volsnap

    event id : 20

    The shadow copies of volume C: were aborted because of a failed free space computation.

    Please Help


    0 0
  • 10/01/14--07:10: backup keep only six copies
  • Hi,

     I am backing up virtual machines by Windows Server Backup and everything work with exception of one server - RDS. The machine is backed up but Windows server backup keeps only last six copies altough there is 272GB of 459GB of free space. This is not he case for other servers(file, print, database, dc,...).

     Is there a way how to force WSB to use all the space?

    Thank you.

    Pete


    sfs


    0 0

    I have a Lenovo Yoga 2 Pro laptop that will not backup to my Windows 2008 R2 Storage Server.

    These are the most recent events:

    Log Name:      Application
    Source:        .NET Runtime
    Date:          10/2/2014 11:06:10 AM
    Event ID:      1026
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SMOSA03
    Description:
    Application: SharedServiceHost.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
    Stack:
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssComponent..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssWriter..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssExamineWriterMetadata)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet.CreateShadowVolume(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[])
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[], Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.IBackupReportProgress)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.Run()
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.BackupTask.OnBackupStart(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1026</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-02T16:06:10.000000000Z" />
        <EventRecordID>28116</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SMOSA03</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Application: SharedServiceHost.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
    Stack:
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssComponent..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssWriter..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssExamineWriterMetadata)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet.CreateShadowVolume(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[])
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[], Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.IBackupReportProgress)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.RunWithoutCatch()
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.Run()
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.BackupTask.OnBackupStart(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    </Data>
      </EventData>
    </Event>

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

    Log Name:      Application
    Source:        Application Error
    Date:          10/2/2014 11:06:11 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SMOSA03
    Description:
    Faulting application name: SharedServiceHost.exe, version: 6.1.1839.0, time stamp: 0x4d38a956
    Faulting module name: msxml3.dll, version: 8.110.9600.17120, time stamp: 0x536da0ed
    Exception code: 0xc0000005
    Fault offset: 0x00000000000194ea
    Faulting process id: 0x2600
    Faulting application start time: 0x01cfde4c9ff44873
    Faulting application path: C:\Program Files\Windows Server\Bin\SharedServiceHost.exe
    Faulting module path: C:\windows\System32\msxml3.dll
    Report Id: 06387ec6-4a4e-11e4-827a-8cae4cfd34be
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-02T16:06:11.000000000Z" />
        <EventRecordID>28117</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SMOSA03</Computer>
        <Security />
      </System>
      <EventData>
        <Data>SharedServiceHost.exe</Data>
        <Data>6.1.1839.0</Data>
        <Data>4d38a956</Data>
        <Data>msxml3.dll</Data>
        <Data>8.110.9600.17120</Data>
        <Data>536da0ed</Data>
        <Data>c0000005</Data>
        <Data>00000000000194ea</Data>
        <Data>2600</Data>
        <Data>01cfde4c9ff44873</Data>
        <Data>C:\Program Files\Windows Server\Bin\SharedServiceHost.exe</Data>
        <Data>C:\windows\System32\msxml3.dll</Data>
        <Data>06387ec6-4a4e-11e4-827a-8cae4cfd34be</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

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

    Log Name:      Application
    Source:        Windows Error Reporting
    Date:          10/2/2014 11:06:19 AM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SMOSA03
    Description:
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: SharedServiceHost.exe
    P2: 6.1.1839.0
    P3: 4d38a956
    P4: msxml3.dll
    P5: 8.110.9600.17120
    P6: 536da0ed
    P7: c0000005
    P8: 00000000000194ea
    P9:
    P10:

    Attached files:
    C:\Windows\Temp\WER975A.tmp.appcompat.txt
    C:\Windows\Temp\WER9807.tmp.WERInternalMetadata.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\memory.hdmp
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\triagedump.dmp

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 06387ec6-4a4e-11e4-827a-8cae4cfd34be
    Report Status: 4
    Hashed bucket:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Error Reporting" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-02T16:06:19.000000000Z" />
        <EventRecordID>28118</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SMOSA03</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>APPCRASH</Data>
        <Data>Not available</Data>
        <Data>0</Data>
        <Data>SharedServiceHost.exe</Data>
        <Data>6.1.1839.0</Data>
        <Data>4d38a956</Data>
        <Data>msxml3.dll</Data>
        <Data>8.110.9600.17120</Data>
        <Data>536da0ed</Data>
        <Data>c0000005</Data>
        <Data>00000000000194ea</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
    C:\Windows\Temp\WER975A.tmp.appcompat.txt
    C:\Windows\Temp\WER9807.tmp.WERInternalMetadata.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\memory.hdmp
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\triagedump.dmp</Data>
        <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805</Data>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>06387ec6-4a4e-11e4-827a-8cae4cfd34be</Data>
        <Data>4</Data>
        <Data>
        </Data>
      </EventData>
    </Event>


    0 0

    Hi

    I have a Windows Server 2012 that is running HyperV and two virtual machines. I set it up with Windows backup when I installed the machine about 6 months ago and it all worked fine (backing up to external hard drives on rotation).

    Recently backups have not been working properly. The backup is configured to backup everything (except for the backup target) as follows:

    • Bare metal recovery
    • System state
    • Hyper-V
    • - VM1 (Backup using child partition snapshot)
    • - VM2 (Backup using child partition snapshot)
    • (Disk does not have drive letter) - boot partition by HP
    • Local Disk (C:)

    The backup is now not working properly, with the message "Completed with warnings"

    Drilling down to the logs shows that although it is backing up the C drive, it is not correctly backing up the virtual machines which means I will have a lot of trouble when I want to restore them. Here's the full log:

    Backup of volume \\?\Volume{e30e3fba-40c1-11e3-93e8-806e6f6e6963}\ succeeded.

    Backup of volume C: succeeded.

    Application backup
    *-----------------------------*

    Error in backup of C:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
    Error in backup of C:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
    Error in backup of C:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
    Application backup
    Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
       Component: 128700EA-A66A-4722-9757-9473AE8E46F0
       Caption     : Backup Using Child Partition Snapshot\VWL-EX
       Logical Path:
       Error           : 8078010D
       Error Message   : Enumeration of the files failed.

       Detailed Error  : 80070003
       Detailed Error Message : (null)


    Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
       Component: CD8B7B3E-BF81-4A62-B7AB-FC0BD40AA2B1
       Caption     : Backup Using Child Partition Snapshot\VWL-DC
       Logical Path:
       Error           : 8078010D
       Error Message   : Enumeration of the files failed.

       Detailed Error  : 80070003
       Detailed Error Message : (null)


    Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
       Component: Host Component
       Caption     : Host Component
       Logical Path:
       Error           : 8078010D
       Error Message   : Enumeration of the files failed.

       Detailed Error  : 80070003
       Detailed Error Message : (null)


    *-----------------------------*

    What is causing this to happen please? I have completely re-setup the backup routine and am using a brand new external hard drive.


    0 0

    We have a DELL R510 server with Windows SBS 2011 (Data, Exchange, ...), we running out of space on the server. We currently have this configuration:

    • 2x 300GB SAS in RAID 1
    • 2x 2TB SATA in RAID 1

    We want to add 4x 4TB SAS in RAID 10. To be able to read the new hard drive we need to change the server boot option from BIOS to UEFI.

    My question is: Can I backup the server (bare metal with windows backup), change from BIOS to UEFI and restore the backup, without reinstalling ? If not, how can I proceed (convert MBR to GPT) ?


    0 0

    Hi



    In windows 2008 server R2, it is connecting to production network through the teamed network adapter.Ip of the teamed adapter is 10.157.86.31 255.255.255.0 and its gateway is 10.157.86.1



    And the server is getting backed up with the backup interface configured with 10.128.141.64 255.255.248.0 in one of the nic in the server connected to the NAS Drive with the ip address 10.128.141.28 .The backup was happening perfectly as the backup is a non-routed network.



    Once the motherboard of the server is changed, suddenly the backup stopped worked failing in authentication to the NAS drive because in NAS Drive authentication is setup based on the ip addresses of the servers connected to the NAS Drive.

    What I have found is that even though the server's backup ip address is not changed , still the NAS drive ip 10.128.141.28 is reached via another network gateway 10.157.86.31 even though the NAS DRive is connected in the same subnet.

    Since the NAS DRive is reached by the server through the ip address of the gateway 10.157.86.31, the authentication fails with the NAS drive because it expects the ip address to be as 10.128.141.64

    how to force the traffic to the ip 10.128.141.28 to initiate through the nic 10.128.141.64 ?


    Any suggestions please

    Below is the answer for the problem ; already implemented and backup is working

    But needed the clarification

    Below is the solution too:

    In spite of rebuild of the server from scratch by freshly installing the operating system , the backup vlan is not connected.So I decided to connect the cable coming from the switch port to the unused nic port of the server and it solved the issue by reconfiguring the ip address to the new nic port.

    But needed one clarification here:

    Before swapping the cable to spare nic the picture is below


    Highlighted above is the nic connected to the backup vlan through which no communication happens.

    So decided to swap the cable from lan1 (backup) which is a separate nic to the spare nic available in the server which is higlighted below





    After configuring the backup ip address to the new spare nic also resulted in the traffic routed the production vlan which should not be the case.And moreover my observation from the above screeshot , why swapping the cable from the lan1(non-teamed adapter) is showing that lan4 (teamed adapter)as disconnected .

    And moreover , currently the setup is working as below with the backup traffic happening through the backup vlan when it is configured in the above manner


    Thanks & Regards S.Swaminathan Live & let others live!!!



    0 0

    Hello,

    

    I am looking at changing out an older Windows 2003 Standard server and installing a new HP Proliant 310 server that will  run Windows 2008 R2.

    I did not setup the 2003 server and have not installed Terminal Server before. All the users RDP into the current server for everything - email (Outlook and Outlook Express), applications (Church application that handles all aspects of the congregation), files documents. 

    My purpose of this is inquiry is to make sure everything gets backed up properly.

    The proposed new server would be setup without Terminal Services. The clients would login to the domain and gain access to shared files on the server and have all the apps installed on their computer(s). 

    

    What is the best way to backup the existing server and make sure all the user profiles data get backed up?

    

    Doing some research on this I was thinking of connecting an external hardrive that is formatted as FAT32. Then open a Remote Desktop to the server under each client or profile, back up each clients files, PST files and so on to the external drive. Then transfer all the backup and move the files to their folder on the server and also the public folder as well. The main church application is in its own folder and I can move the entire folder to a backup drive per the software company.

    

    Is this the best way to accomplish the backup of their data? Will it work?

    

    Any thoughts tips, suggestions would be helpful.

    

    Thanks,

    Paul


    PAUL


    0 0

    Hello,

    

    I am looking at changing out an older Windows 2003 Standard server and installing a new HP Proliant 310 server that will  run Windows 2008 R2.

    I did not setup the 2003 server and have not installed Terminal Server before. All the users RDP into the current server for everything - email (Outlook and Outlook Express), applications (Church application that handles all aspects of the congregation), files documents. 

    My purpose of this is inquiry is to make sure everything gets backed up properly.

    The proposed new server would be setup without Terminal Services. The clients would login to the domain and gain access to shared files on the server and have all the apps installed on their computer(s). 

    

    What is the best way to backup the existing server and make sure all the user profiles data get backed up?

    

    Doing some research on this I was thinking of connecting an external hardrive that is formatted as FAT32. Then open a Remote Desktop to the server under each client or profile, back up each clients files, PST files and so on to the external drive. Then transfer all the backup and move the files to their folder on the server and also the public folder as well. The main church application is in its own folder and I can move the entire folder to a backup drive per the software company.

    

    Is this the best way to accomplish the backup of their data? Will it work?

    

    Any thoughts tips, suggestions would be helpful.

    

    Thanks,

    Paul


    PAUL


    0 0

    We have a HP Proliant ML350 running Server 2012 + 4 Hyper-V servers (Exchange, SQL, RDS and ADDC). The USB ports on the proliant are version 2.0 so backing up to an external harddisk is not an option (takes way too long since total is about 1.5Tb). We would like to create a backup to a NAS drive since the speed is a lot faster, so we bought a DLINK Nas. However, the backup starts creating a shadowcopy an than stops because it has permission issues. The strange thing is that every other application can write to the NAS without a problem. Since we have 2 smart fail drives in a RAID5 we would like to have a succesfull backup as soon as possible. Any tips or comments the will not need us to reboot the server (because of the risk with the failing drives)are most welcome!!!

    0 0

    I have a 2012 DC that crashed during a System State restore..the server hardware vendor believes my original issues and reasons for initial problems were caused by a bad raid card.

    I am now trying to get this DC back in a functioning state so I can demote it gracefully and remove some services from it (DNS/DHCP).

    If I boot the computer to DSR it will reboot sporadically.  Is there a way to do a system state restore besides this?  From a command prompt? 

    Thanks for any assistance.


    0 0

    Hello,

    I'm novice to this area, after the execution of all the instructions for setting up the backup agent gives an error message: "Microsoft Azure Recovery Services Agent was unable to create a snapshot of the selected volume. Please try the operation again. If the issue persists, contact Microsoft Support(0x186C2)".

    So,I experience a problem making a snapshot of selected volume.

    Operating System Windows Server 2012 installed on the virtual machine in the cloud, on the server the agent is installed and the file backup is also on this server.

    Thanks in advance for your help!

    Vyacheslav.


    0 0

    I wrote a program to copy server A’s volume 0 to server A’s volume 1.

    Volume 1 is then moved from server A and placed in server B.

    When server B is started I get the error: Windows failed to start. Status: 0xc000000e.

    http://support.microsoft.com/kb/2261423

    Running X:\Sources\Recovery\StartRep.exe will fix this problem.

    This will not be an option for my disaster recovery plan as no one will be there to enter this command.

    The above url indicates that I can run bcdedit to fix this problem. 

    On server A, once the volume copy is complete, drive letter I is assigned to the volume. I run the three bcdedit commands against drive I:

    bcdedit /set {default} device partition=i:

    bcdedit /set {default} osdevice partition=i:

    bcdedit /set {bootmgr} device partition=i:

    This does not resolve the Windows failed to start. Status: 0xc000000e error.

    Please advise.

    0 0

    We've got a 2008 R2 server connected via iSCSI initiator to a Readynas 3200 device, and Windows Server Backup is configured to backup to that disk nightly. Weeks will go by and it will work great... all backups appear in the history when the "View Details" link is clicked in the Destination Usage section. The last time I checked, we had 27 backups available.

    Today I was asked to restore some files from a backup from last week. However, upon opening Windows Server Backup, it now shows that there is only 1 backup available. Viewing the details only shows last night's backup in the list...none other exist. I checked to make sure it was still connected to the iSCSI disk, and it is...nothing has changed at all on the ReadyNas' configuration.
    Any ideas as to what might have caused the history to get wiped? Sadly this is not the first time this has happened, so it has me very concerned about whether we should continue using Windows Server Backup at all. Any help in figuring out what's causing the history to get wiped, or any way to recover the history, would be greatly appreciated!!!
    Thanks all!

    0 0

    Our server had 2TB mirror'd drives that both failed at the same time. Mirror / RAID 1 is software based.  Backup's partition is single mirror 1863GB and 332GB actual data.

    We're attempting to restore off a saved backup over the network using two new 3TB drives connected in the same way as the previous ones.

    Restore is being done with DVD of OS and selecting Repair Your Computer and going through all the steps. Everything is located and seems fine right up

    to where Restore attempts to prep the disks to write on.  (Same result with 1 physical disk connected too.)

    "Failed to update disk partition layout 0x0C0380037".  Disks seem fine and can be accessed and manipulated with diskpart. 

    Happens with clean / RAW state drives or even simple volume formatted ones of correct size.

     




    0 0

    I have a fresh install of Windows Server 2012 R2 on an IBM x3530 M4 server.  I'm trying to do a full bare metal backup to a local volume, which is presented from a SAN.

    The backup fails stating that there isn't enough disk space.  This is very misleading as the OS on the C:\ is only taking up 15GB and the free Space on the SAN volume is 800GB.

    From doing a little reading online i have found others who have had problems backing up Recovery Partitions, click here.  So i just did a backup of the C:\ to the same SAN volume and that works fine so i have a feeling this is something to do with the Recovery Partition.  I also have a partition which is called the EFI System Partition which i'm unsure what this is.  Below is a screen grab of the Disk Management on the system.  Can someone give me a way to do a full Bare Metal backup without having to reinstall the whole OS.  Thanks


    0 0

    Problem running systemstate backup using commandine utility wbengine.exe.

    operating system - Windows Server Standard 2008 R2 x64 with latest patch updates till date.

     Backup of system state failed [01/12/2009 16:21]

    Log of files successfully backed up
    'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup 01-12-2009 16-21-37.log'

    Log of files for which backup failed
    'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup_Error 01-12-2009 16-21-37.log'

    The backup of the system state failed [5/8/2012 8:12 PM].

    Log of files successfully backed up:

    C:\Windows\Logs\WindowsServerBackup\Backup-08-05-2012_20-11-54.log

    Log of files for which backup failed:

    C:\Windows\Logs\WindowsServerBackup\Backup_Error-08-05-2012_20-11-54.log

    The operation ended before completion.

    The system writer is not found in the backup.

    In the Application event log, the following events are logged:

    Log Name:      Application

    Source:        Microsoft-Windows-Backup

    Event ID:      517

    User:          SYSTEM

    Description:

    The backup operation that started at '‎2012‎-‎05‎-‎08T14:41:54.065259300Z' has failed with following error code '2155347997' (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Log Name:      Application

    Source:        Microsoft-Windows-CAPI2

    Date:          5/8/2012 8:12:21 PM

    Event ID:      513

    Keywords:      Classic

    Description:

    Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

    Details:

    AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed.

    This is a physical server.

    I have tried this KB http://support.microsoft.com/kb/2009272 to fix permission issue on Winsxs temp & filemaps folders but still no go.

    restarted cryptographic services, several server reboots also.

    then i found a hotfix http://support.microsoft.com/kb/2182466 from Micrsoft for same issue and tried that too but the hotfix is not applicable to my servers as the servers are patched upto date.

    wbengine.exe file version hosted on my server is 6.1.7601.17514 which is latest than the one in hotfix kb listed.

    when i run "vssadmin list writers" - system writer is not showing and is missing.

    C:\Windows\system32>vssadmin list writers

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

    (C) Copyright 2001-2005 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: 'Dhcp Jet Writer'

       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

       Writer Instance Id: {4ca26252-80aa-474d-9a11-c23308717f38}

       State: [1] Stable

       Last error: No error

    Writer name: 'ASR Writer'

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

       Writer Instance Id: {c08e323c-4591-426f-9bd6-f3555460fe42}

       State: [1] Stable

       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'

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

       Writer Instance Id: {4502c2d3-f5bb-4658-b422-f2549b7c48e4}

       State: [1] Stable

       Last error: No error

    Writer name: 'Registry Writer'

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

       Writer Instance Id: {b73c8c5a-a53e-40c7-8301-3e8b48ef1e3d}

       State: [1] Stable

       Last error: No error

    Writer name: 'BITS Writer'

       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

       Writer Instance Id: {c45879d1-ac05-4197-97e2-aebcd6ec7b35}

       State: [1] Stable

       Last error: No error

    Writer name: 'COM+ REGDB Writer'

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

       Writer Instance Id: {9c102277-7606-40ef-820b-f4e47b8ae868}

       State: [1] Stable

       Last error: No error

    Writer name: 'NTDS'

       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

       Writer Instance Id: {c814daf8-5863-4b33-bd7c-75040fe69de5}

       State: [1] Stable

       Last error: No error

    Writer name: 'DFS Replication service writer'

       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}

       Writer Instance Id: {a99c673a-66da-4472-8254-0edd872b1594}

       State: [1] Stable

       Last error: No error

    Writer name: 'WMI Writer'

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

       Writer Instance Id: {2fcc7a18-9a94-4f70-9fec-b347591c6f7d}

       State: [1] Stable

       Last error: No error 

    verified this reference article too but no go.

    RESOLVED - Backup failing on Server 2008 R2 - system writer missing

    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/764791ff-ecb5-4716-9f1c-9e22852e0f6b

    We have symatec end point protection installed - client version 11.0.7101.1056

    found a KB for similar issue when symantec end point protection 12.1 installed but not applicable for us. still tried the same for a good hope and it didnt work either.

    http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH168402


    0 0

    Hi,

    Firstly I'd like to mention that I have found posts with the same question-error, tried everything that was proposed as a solution and still face this situation. I have a windows 2008 server with AD and client PCs all living together on the same domain. This backup error is present at some client Pcs while others run the backup scheduled flawlessly.

    Once again I mention that I have double checked that I have correct Time Zones, correct date and time, both in Windows and BIOS. Have tried to change the scheduled tasks' "configure for" part to windows 7 and so, with no result. And generally everything else that was proposed at this post, http://answers.microsoft.com/en-us/windows/forum/windows_7-system/next-backup-date-reads-12301899-1200am/62637bf9-7de4-446a-be51-f68e299c9ea1?rtAction=1411015328406 , I have tried to do with no luck. So I am asking for help on this issue, because it can't be that some PCs of mine work fine and some are not. Thank you in advance for your support.


older | 1 | .... | 57 | 58 | (Page 59) | 60 | 61 | .... | 148 | newer