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

Embed this content in your HTML


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.

older | 1 | .... | 158 | 159 | (Page 160)

    0 0

    I'm backing up some Windows Server 2019 using wbadmin to some Synology-NAS using SMB. Once in a while the logs created during those backups mention that one of the created VHDX files gets compressed/compacted. The server is using German language for these logs and those use a term which means "compressing" actually, so not sure which of both is really done, but I strongly guess it means "compacting".

    Looking at the logs, that process is pretty fast for C:\ most likely, which only contains Windows itself and some installed applications. Most of the data is stored on D:\ instead and that data contains some databases, plain files available using network shares, a VM and stuff like that. So there's quite some amount of I/O on that volume.

    Looking at the logs of the last time that was done for D:\, I recognized two interesting things: 1. that process took around an hour to succeed and 2. the logs start at 30 % and stopped at 69 %. I know that it took around an hour because without compressing/compacting the backup finishes mostly around 22:45 o'clock.

    Von Volume "Daten(D:)" wird eine Sicherung erstellt. Kopiert: (100%).
    Die virtuelle Festplatte für das Volume "Daten(D:)" wird komprimiert. Abgeschlossen: (30 %).
    Die virtuelle Festplatte für das Volume "Daten(D:)" wird komprimiert. Abgeschlossen: (69 %).
    Ende Datensicherung 13.11.2019 23:59:36,66

    So what happens during that process, especially in case of storing to SMB?

    From my understanding, one needs to first know which blocks of the VHDX are not used anymore. Because there's NTFS inside that image, I guess Windows simply knows that and doesn't need to scan the file in some expensive process? After knowing which blocks are not needed anymore, those can be freed to actually reduce the storage needed for the VHDX. If it would sit on NTFS itself, I guess this would be done by unallocating blocks from some sparse file or would it really write 0s to the not needed blocks? However, the VHDX is accessed using SMB with BTRFS underneath, so most likely doesn't know about any spare file. So it might move blocks from the end of the file to allocated, but free blocks and simply trims the file afterwards?

    If large amounts of data really need to be copied, that would explain why the process takes pretty long and why 30 and 69 % are logged only, that being the copied range of data inside the VHDX maybe or even only copying the data itself and other operations before and after 30 and 69 % are pretty fast again.

    0 0

    Hi IT Experts,

    1.  Past few days our domain users (not specific user) complaining about their account locked out if the system is idle for few mins. I verified all the GPO's but there is no such GPO created except "Account Lock Out" if more than 5 times wrong password, so was manually unlock the account and advising users to spell check before entering the password, surprisingly yesterday it happens to one of our IT Security Admin user who is already into Administrator group.  It was more surprise to us while working on the system tried to connect to the one of the server via RDP using the same logged in account and received the error saying account is locked. 

    Now, I'm sure that our users may not be entering the wrong password but it is getting locked for unknown reason.  Kindly advice what could be the reason and solution? 

    2.  As staked above, I have enabled Block Inherit Policy to the IT security Group / OU but still the account lock out policy affect and getting locked, pls. advice what additional steps to configure 

    Thanks in advance.

    0 0

    Hi all,

    i have a fujitsu rx1330 server with Windows Server 2019 installed. The 2 gbit ports are connected to a switch. Network connection generally runs without any issues.

    At 3:00 a.m i run a complete windows backup, with  all hdd's, all hyper-v VMs, baremetal.... to a iscsi mounted network drive.

    For this Backup iam using the onboard windwos backup tool.

    Within this backup i got every day a short network connection loss, that is a problem because one of the hyper-v VMs needs a permanent network connection 7x24.

    I already updated the intel network adapter drivers to the newest version from July 2019 and VMQ i disabled.

    Do you have any solution for this issue?

    I wont use another commercial backup software for which i have to pay for it.


    0 0
  • 09/19/17--07:23: Rebuild USN Change Journal
  • I am getting an error from Backup Exec when trying to backup one of my Windows 2008 R2 Servers that indicates that I need to rebuild the usn change journal database. I looked up the commands for accomplishing this and just had a couple of questions about executing these. First: Are these the right sequence of commands to run? -->

    fsutil usn deletejournal /d c:
    fsutil usn createjournal m=1000 a=100 c:

    Second: I am assuming the best time to run these would be right before a full backup?

    0 0

    So this is strange issue that started occurring about a month ago, and I have been unable to find any useful resources online. This may or may not be related, but this started happening very soon after we migrate our VM disks to a new datastore on a new storage device in vmware. I have managed to get at least one successful backup weekly, but this is after many failed attempts with the same errors.

    I originally thought this was a Backup Exec issue but after spending hours on the phone with them they declared that this is a Microsoft issue since the same problem occurred using Windows Server Backup as well.

    Here are the errors occurring. This typically happens during the System State Backup or during the C: drive backup.

    Source: VSS Event ID: 8193 Level: Error Logged: 9/20/2017 9:25:20 AM

    Volume Shadow Copy Service error: Unexpected error calling routine IMultiInterfaceEventControl::GetSubscriptions.  hr = 0x80010108, The object invoked has disconnected from its clients.

    Source: VSS Event ID: 12291 Level: Error Logged: 9/20/2017 9:25:20 AM

    Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: BackupShutdown [0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
    Check the Application event log for more information.

    Source: VSS Event ID: 8193 Level: Error Logged: 9/20/2017 9:50:08 AM

    Volume Shadow Copy Service error: Unexpected error calling routine IVssAsync::QueryStatus.  hr = 0x800706ba, The RPC server is unavailable.

       BackupComplete Event
       Executing Asynchronous Operation

       Current State: BackupComplete

    Source: Backup Event ID: 517 Level: Error User: System

    The backup operation that started at '‎2017‎-‎09‎-‎20T13:04:54.929785700Z' has failed with following error code '0x807800AF' (The Volume Shadow Copy Service backup complete operation failed. See the event logs for more details.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Has anyone ever seen or encountered these problems before? They are making backup up our server almost impossible. Any suggestions would be greatly appreciated.

    Thank you!

    0 0


    How can we make sure the Azure VM Application consistent backup . We have few windows and Linux VMs with databases and we want to take application consistent backup to avoid any data corruption during backup/restore.

    Is it possible ?


    0 0

    Hello guys,

    Since Septembter 13th we have backups failing on one of our 2008 servers. The problem is that, for some reason, the VSS System Writer has disappeared.

    I have tried everything, re-registering the writers, changed permissions on COM Security, etc. None of them worked... Has anyone gone through this before? I also noticed that some updates were installed on the server the same day that the last successful backup happened (Sept 13th), so I am wondering if this was broken by an update...

    Any help will be really appreciated!! Thanks so much in advance for your time!!  :) 

    0 0


    Here I have a Windows Server 2012 R2 Standard server, using Netbackup software for the backup, which is a product of Symantec company.

    The server roles as file server, problem now is the backup process always failed when processing on an EFI partition.

    After consulted with the product vendor, they suggested to ask MS for help..

    Here is the log:

    - Type: VSS_CT_FILEGROUP [2]

    - Is selectable: TRUE

    - Is top level: TRUE

    - Notify on backup complete: FALSE

    - Paths affected by this component:

    - \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot<file:///\\%3f\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot>

    - Volumes affected by this component:

    - \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot<file:///\\%3f\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot> [Does not exist]

    Here is the BCD info:

    C:\Windows\system32>bcdedit /enum all /v > c:\bcd.txt

    Firmware Boot Manager
    identifier              {a5a30fa2-3d06-4e9f-b5f4-a01df9d1fcba}
    displayorder            {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    timeout                 2

    Windows Boot Manager
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device                  partition=\Device\HarddiskVolume2
    path                    \EFI\Microsoft\Boot\bootmgfw.efi
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    bootshutdowndisabled    Yes
    default                 {863b7735-7876-11e5-8f71-e4e140fa16a9}
    resumeobject            {863b7734-7876-11e5-8f71-e4e140fa16a9}
    displayorder            {863b7735-7876-11e5-8f71-e4e140fa16a9}
    toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 30

    Firmware Application (101fffff)
    identifier              {863b7731-7876-11e5-8f71-e4e140fa16a9}
    description             EFI Network

    Firmware Application (101fffff)
    identifier              {863b7732-7876-11e5-8f71-e4e140fa16a9}
    description             EFI SCSI Device

    Firmware Application (101fffff)
    identifier              {863b7733-7876-11e5-8f71-e4e140fa16a9}
    description             EFI SCSI Device

    Firmware Application (101fffff)
    identifier              {d344c614-8c42-11e5-80b9-806e6f6e6963}
    description             EFI SCSI Device

    Windows Boot Loader
    identifier              {863b7735-7876-11e5-8f71-e4e140fa16a9}
    device                  partition=C:
    path                    \Windows\system32\winload.efi
    description             Windows Server 2012 R2
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    recoverysequence        {863b7736-7876-11e5-8f71-e4e140fa16a9}
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {863b7734-7876-11e5-8f71-e4e140fa16a9}
    nx                      OptOut

    Windows Boot Loader
    identifier              {863b7736-7876-11e5-8f71-e4e140fa16a9}
    device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{863b7737-7876-11e5-8f71-e4e140fa16a9}
    path                    \windows\system32\winload.efi
    description             Windows Recovery Environment
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    displaymessage          Recovery
    displaymessageoverride  Recovery
    osdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{863b7737-7876-11e5-8f71-e4e140fa16a9}
    systemroot              \windows
    nx                      OptIn
    bootmenupolicy          Standard
    winpe                   Yes
    custom:46000010         Yes

    Resume from Hibernate
    identifier              {863b7734-7876-11e5-8f71-e4e140fa16a9}
    device                  partition=C:
    path                    \Windows\system32\winresume.efi
    description             Windows Resume Application
    locale                  en-US
    inherit                 {1afa9c49-16ab-4a5c-901b-212802da9460}
    recoverysequence        {863b7736-7876-11e5-8f71-e4e140fa16a9}
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    filedevice              partition=C:
    filepath                \hiberfil.sys
    debugoptionenabled      No

    Windows Memory Tester
    identifier              {b2721d73-1db4-4c62-bf78-c548a880142d}
    device                  partition=\Device\HarddiskVolume2
    path                    \EFI\Microsoft\Boot\memtest.efi
    description             Windows Memory Diagnostic
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    badmemoryaccess         Yes

    EMS Settings
    identifier              {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
    bootems                 Yes

    Debugger Settings
    identifier              {4636856e-540f-4170-a130-a84776f4c654}
    debugtype               Serial
    debugport               1
    baudrate                115200

    RAM Defects
    identifier              {5189b25c-5558-4bf2-bca4-289b11bd29e2}

    Global Settings
    identifier              {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    inherit                 {4636856e-540f-4170-a130-a84776f4c654}

    Boot Loader Settings
    identifier              {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

    Hypervisor Settings
    identifier              {7ff607e0-4395-11db-b0de-0800200c9a66}
    hypervisordebugtype     Serial
    hypervisordebugport     1
    hypervisorbaudrate      115200

    Resume Loader Settings
    identifier              {1afa9c49-16ab-4a5c-901b-212802da9460}
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

    Device options
    identifier              {863b7737-7876-11e5-8f71-e4e140fa16a9}
    description             Windows Recovery
    ramdisksdidevice        partition=\Device\HarddiskVolume1
    ramdisksdipath          \Recovery\WindowsRE\boot.sdi

    Please let me know if any other information you need to know.

    Really thanks for any help.



    0 0

    I have one (Server 2012 R2) guest on Hyper-V in Server 2012 R2 host. System Reserved and C backup completes data transfer and all but Server(Online) fails to complete. 

    "Failed to complete 0KB of 0KB"

    WSB Error: The component Server2012(Online) was skipped during the snapshot and will not be available for recovery. Error: The writer experienced a transient error. If the backup process is retried, the error may not occur.

    Log file: 

    Writer Failures
    Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
    Instance Id: {C1C2F8BB-2ACD-45C8-9B0E-D072A7B58F79}
    Writer Name: Microsoft Hyper-V VSS Writer
    Writer State: 5
    Failure Result: 80042336
    Application Result: 80004005
    Application Message: (null)
       Component: EBABEA20-1601-4521-855E-A286593543D0
       Logical Path: (null)
       Component Result: 800423F3
       Component Message: 
           File Spec: C:\VHDX\Server2012\Virtual Machines\Server2012\Virtual Machines\\EBABEA20-1601-4521-855E-A286593543D0.xml Recursive: 0
           File Spec: C:\VHDX\\C.vhdx Recursive: 0
           File Spec: C:\VHDX\\data.vhdx Recursive: 0
           File Spec: C:\VHDX\C-AutoRecovery.avhdx Recursive: 0
           File Spec: C:\VHDX\Vorhoff2012\Virtual Machines\Server2012\Snapshots\FAE18FA3-3CE5-4E7A-AE13-691603A0B96A.xml Recursive: 0
           File Spec: C:\VHDX\data-AutoRecovery.avhdx Recursive: 0

    Application backup
    Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
       Component: EBABEA20-1601-4521-855E-A286593543D0
       Caption     : Online\Server2012
       Logical Path: 
       Error           : 80780175
       Error Message   : Component was skipped from volume shadow copy.

       Detailed Error  : 800423F3
       Detailed Error Message : The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.

    Event Viewer:

    Event 10178

    Source: Hyper-V-VMMS

    The description for Event ID 10178 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event: 


    The locale specific resource for the desired message is not present

    Event 10172

    Source: Hyper-V-VMMS

    VSS writers inside virtual machine 'Server2012' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID EBEBBA20-1601-4521-856E-A286493543B0)

    Event 16010

    Source: Hyper-V-VMMS

    The operation failed.

    VSSADMIN LIST WRITERS shows all "State: [1] Stable Last error: No error" besides:

    Writer name: 'Microsoft Hyper-V VSS Writer'

       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

       Writer Instance Id: {c1c2f8bb-2acd-45c8-9b0e-d072a7b58f79}

       State: [1] Stable

       Last error: Unexpected error

    After running this script: http://www.nullskull.com/q/10115236/issue-with-windows-server-backup.aspx and turning VMMS service off and on, and then restart, backups appear to (or at least WSB says the Server2012(Online)) have completed BUT the data transferred says 0KB of 0KB! Then, the next backups say "failed" or "completed with warnings".

    The question is: HOW DO I GET WSB TO WORK? 

    Thanks in advance, everyone! I appreciate all replies very much.

    0 0

    I'm struggling with a problem that i've yet to find a solution to.  I have a brand new Windows Server 2012 R2 installation.  I've created a scheduled local backup to a local Hard drive, not a network location.  The backup configures and schedules properly, but when the time arrives for it to run, it never runs.  If I check the Scheduled tasks, I see the backup task changes from ready to queued.  The backup job shows as not running, not failed, not anything.  Wbadmin just shows next backup as being tomorrow, with no successful backup and no failed backup.  Each day is the same thing.  If I run the backup manually, it will run successfully every time.  I have tried to search for similar problems and found a few similar threads, but none of the suggested solutions have done anything.  Does anyone have any ideas as to what could be causing this?

    0 0

    I want to take backup but my device is shutting down again and again. 

    Also, Can I host and move my website to microsoft's cloud service? 

    My blog website is vashishthakapoor.com. I will move other sites to microsoft only because this service is very fast

older | 1 | .... | 158 | 159 | (Page 160)