Quantcast
Channel: Backup – Windows and Windows Server forum
Mark channel Not-Safe-For-Work? cancel confirm NSFW Votes: (0 votes)
Are you the publisher? Claim or contact us about this channel.
0
Previous Article Next Article

Windows Server Backup and virtual machines

0
0

We setup Windows Server Backup. We chose to do full backups, system state and some selected virtual machines. The backup works properly and no errors are generated. But whne we look into the details of the backup we can see, that there happened no transfer of data of the virtual machines. Why is this? Is this because we already do a full backup and therefore the virtual machines are not backed up separately?

When we try to restore only VMs instead of the whole server, it never works... What are the requirements, that one can restore a VM on a new server? Is this even possible or is the VM recovery only intended to be done on the server where it was originally stored on?

Thanks for the help in advance

Joël

VSS Event ID:12347 and 1234 The Registry Writer failed to respond to a query from VSS

0
0

Hi Folks , 

Getting below error on server with OS :Win2k12 r2 
Log Name:      Application
Source:        VSS
Date:          6/7/2020 7:36:47 AM
Event ID:      12347
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      not mentioned 
Description:
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. 


Issue : Backup is getting failed , system writers are missing .Upon restarting cryptsvc all the writers are stable.but still not able to take system state backup.Also tried taking local system state backup which went through successfully.
When i checked Eventvwer found below VSS related events : 
Also could see below event IDs:

Log Name:      Application
Source:        VSS
Date:          6/6/2020 1:01:46 AM
Event ID:      12348
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Notmentioned 
Description:
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{61a44f4f-5d9d-11e7-80c8-000d3a02ca79}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again.



VSS Event ID:12291 and 12292 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.

0
0

Hi Folks,

We are not able to trigger the backup , as the system state srivers are missing, Upon checking VSSadmin list writers.

We have restarted the CryptSVC and VSS , WMI services but still backup is not completing.

mentioned server OS :WIN2K8 R2

Please advise. Here Im attaching the VSS Logs for reference .

Log Name:      Application
Source:        VSS
Date:          5/9/2020 1:50:25 AM
Event ID:      12291
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
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.
].

===========================================

Log Name:      Application
Source:        VSS
Date:          5/9/2020 1:50:25 AM
Event ID:      12293
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {5fdb6ef5-6ead-4610-995b-401c88626115}. Routine details PostCommitSnapshots({8ef031ed-cb91-4d17-a2c9-32d390b16102}, 8) [hr = 0x800706be, The remote procedure call failed.
]. 

Operation:
   Executing Asynchronous Operation

Context:
   Current State: DoSnapshotSet

Windows Server Backup

0
0

Hi. I have problem with Windows Server Backup.
I’m using Server 2016 standard edition and Wbadmin.msc suddenly stop working. When I try to start Wbadmin.msc, the error says:
A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation.
Error details:
Server execution failed.
Close Wbadmin.msc and then restart it.

I have tried that and course it didn’t work. I tried to uninstall and install again WSB and it didn’t work, also I have search to forums and I didn’t find anything concrete. 
Does anybody have any idea?

Windows Server Backup

0
0

Hello. I’m currently testing some of my server backups. Right now the server’s OS (Windows Server 2019) are currently running on the physically server. I’m running the backup test in a virtual environment (VMWare) and making sure that I can recover them. I successfully made a backup of the physical servers using the Windows Server Backup in my Storage Server that’s hosting the share folder for my backup. However, I’m still having issue recovering them using the repair disk. The set up I have are listed below.

Physical Server: 192.168.1.2/24
Virtual Server: 192.168.1.101/24

Storage Server: 192.168.1.102/24 (Share path: \\192.168.1.102\Backup)

The machines are able to see each other. I’m able to access the share folder from my Virtual Server and Physical Server. The Physical Server Backup is mapped to \\192.168.1.102\Backup. After mounting the DVD Windows Server 2019 install into the Virtual Server, I ran the repair this computer. I opened up the command prompt and inputted the info below.

-startnet
-netsh
-interface ip
-set address “Ethernet” static 192.168.1.101 255.255.255.0 192.168.1.1
-wpeinit
-ping 192.168.1.102 (Success)
-net use \\192.168.1.102\Backup
-Entered credentials (Success)
-wbadmin get versions -backupTarget:\\192.168.1.102\Backup 
-Use the version from the previous command (12-120-20) 

-wbadmin start sysrecover -version:12-120-20 -backupTarget:\\192.168.1.102\Backup

The error says that the backup doesn’t exist, which makes no sense because I see that the Windows Server Backup is successful and I also verified the content of the share folder. Also, I remember seeing that I don’t have enough permission on the folder even though I added myself in the security group and have full control. I was able to access the share from the Physical Server as well with the same user. 

I also tried a different this other method. 
-cmd from the repair disk
-startnet
-netsh
-interface ip
-set address “Ethernet” static 192.168.1.101 255.255.255.0 192.168.1.1
-wpeinit
-ping 192.168.1.102 (Success)
-net use \\192.168.1.102\Backup
-Entered credentials (Success)
-exit
-System Image Recovery
-used the path to the share folder \\192.168.1.102\Backup
-The error I get is “Multiple connections to a server or shared resource by the same user”
-I tried using the same user and different user both have admin rights, which didn’t work

I wonder if I’m missing something simple. Thank you for reading this.

Problem with bakup recovery. Server 2012 r2

0
0
Hey,
I have set Bare Metal backup on a dedicated disk.
Windows backup shows that the copies from the following days were successful. However, when I try to restore - I can only restore the last copy. I am asking for help because ransomware attacked me.
Greetings:
japko

Windows Server backup failing with "The specified network name is no longer available"

0
0

Hello,

I have a Windows 2016 server running Exchange 2016 and trying to do a full backup using Windows Backup to a remote share (shared from another Windows 2019 server). The backup gets to about 75% and then fails with the following:

JobType          : Backup
StartTime        : 20/04/2020 14:13
EndTime          : 20/04/2020 14:19
JobState         : Completed
CurrentOperation : 
HResult          : 8078015B
DetailedHResult  : 80070040
ErrorDescription : Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.
                    Detailed error: The specified network name is no longer available
JobItems         : {ConsistencyCheckResultList, VolumeList, SystemState, BareMetalRecovery}
VersionId        : 
SuccessLogPath   : C:\Windows\Logs\WindowsServerBackup\Backup-20-04-2020_13-13-52.log
FailureLogPath   : C:\Windows\Logs\WindowsServerBackup\Backup_Error-20-04-2020_13-13-52.log


This keep happening even if I delete the partial backup attempt. There is plenty of room on the remote share around 1TB and i am backing up around 100GB of data.

The Exchange 2016 server is using ReFS drives and can see the remote share, and I can copy large files over it no problem.  The connection never drops.

I have ran chkdsk on both the Windows 2016 server and Windows 2019 server (where the drive is shared) and no errors.

SMB 1.0 is enabled on both servers.

Computer Browser, Server and Work stations services are running.

I have used the ip for the backup job and it still fails.

Any ideas? 


Backup Hiper-v host

0
0
Hi.
I have a WS 2019 Standard ed. that has configured Hiper-v with 3 VMs.
I configured the WSB to do a full backup but I always have the warning that the VMs are online.
Is it possible to use the WSB in this scenario?
How to make?

Thank you for your help.

Backup succeeded but some components backup up were inconsistent in the snapshot. The application this component belongs to might not function properly after this backup is used for recovery. Windows Server 2019

0
0

Hello Technical Team,

I have a Windows Server 2019 running Hyper-V with two host. One is Windows Server 2019 Domain Controller and another is CentOS. It is ok when I take a backup of CentOS host. Windows Server 2019 host throwing error. "Backup succeeded but some components backup up were inconsistent in the snapshot. The application this component belongs to might not function properly after this backup is used for recovery." Below is the error log:

Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {B40CCC71-69C8-4349-82DB-0076D5122EFB}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 0
Failure Result: 81000112
Application Result: 0
Application Message: (null)
   Component: 14F383F1-4264-4C1A-8E33-26AECB1882B1
   Logical Path: 
   Component Result: 8100010F
   Component Message: Component reports path on volume which has been excluded. (0x8100010F)
   Component: Host Component
   Logical Path: 
   Component Result: 8100010F
   Component Message: Component reports path on volume which has been excluded. (0x8100010F)
*-----------------------------*


Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 14F383F1-4264-4C1A-8E33-26AECB1882B1
   Caption     : Offline\Windows Server 2019 - DC
   Logical Path: 
   Error           : 80780175
   Error Message   : Component was skipped from volume shadow copy.

   Detailed Error  : 8100010F
   Detailed Error Message : Component reports path on volume which has been excluded.



Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: Host Component
   Caption     : Host Component
   Logical Path: 
   Error           : 80780175
   Error Message   : Component was skipped from volume shadow copy.

   Detailed Error  : 8100010F
   Detailed Error Message : Component reports path on volume which has been excluded.

Please advise me what could be the issue...

Thank you,

Kind Regards,

Jose

BSOD error: faulty driver on teh kernel stack

0
0

Windows Server 2008 R2

Recently got a BSOD that stated there was a faulty driver in the kernel stack and after looking through drivers, found one driver that has an issue (Microsoft Tunneling Teredo Adapter).

Tried uninstalling and reinstalling the adapter but no success and still says: The device cannot start (Code 10).

Kernel-Power alert (Event ID 41) in event manager at 5:38am on 24th May 2020.

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

BugCheck alert (Event 1001) at 5/24/2020 5:39:38 AM

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000010c (0x0000000000000015, 0x0000000000000000, 0x0000000000000000, 0xfffff880092fba88). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052420-88421-01.

"Windows Backup cannot read the backup destination" when trying to backup to Backup Once to Samba share on NAS

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.


Windows Server 2019 - Sometimes Window Server Backup Failed

0
0

 i have used Windows Backup on Windows Server 2019. However, sometimes the Backup appear error:

Backup of volume \\?\GLOBALROOT\Device\HarddiskVolume2\ has failed. Windows Backup failed to get an exclusive lock on the EFI system partition (ESP). This may happen if another application is using files on the ESP. Please retry the operation.

and sometimes it have been successful. i don't know the reason. Any people has experience this issues please help me resolve it.

Thank you so much.

Windows server backup failed none of the items included in backup were backed up

0
0

I was backed up my files and folders (size 2.7 TB), the Windows Server Backup are copying files and folders about 377 GB was found the Windows server backup status: failed none of the items included in backup were backed up and error: Access is denied, I'm using the Windows Server 2019 Standard edition Version 1809 (OS Build 17763.1217).

Remark: There are no list of all failed files in log file.

Please advice me to solve the issue.


Thank you.

vssadmin stops responding

0
0

hello all,

I have an issue with vssadmin. We have a server which has about 200 vss snapshots which I want to remove cause they are no longer needed. However, If I try to run vssadmin to list the snapshots, it doesnt respond at all. 

I checked the writer status and all are up and running. I can no longer switch to previous versions on the explorer tab.

anyone has a similiar experience on vssadmin?

Can not recover back up from windows server backup (Catalog corrupted)

0
0

I had an issue in the server 2019 so i had to do a fresh installation and when i am trying to restore the servers (Active directory machines) it return:

An operation on the backup catalog failed because the catalog is corrupted. Please restore the catalog using the wbadmin.exe command line tool.

please help

Windows Server 2008: Possible to restore the full backup to another VM host?

0
0

Is it possible to restore the back up file (.VHD) to another VM host? (Hyper-V)

The back up file will be extracted from a network server/file (\\IPaddress\foldername)

Thanks!

Win 7 Backup fails with 0x8007007b

0
0

I have a dual boot Windows 7 Ultimate and XP pro machine. They are both fresh installs. However, when I try to backup with an image of C:(Win7) and H:(XP) the backup fails with error 0x8007007B. Manually backups with disk imaging turned off fails too. I am doing backups to a USB drive that has a 500 MB partition. I have tried to a couple of days to find a work around this problem. Any advice would be appreciated?

Does the old fashion NT backup work under Windows 7. It was a much friendly product that work flawlessly for me for years.

ERROR in Backup Windows Server Backup

0
0

Dear Please help me,

I'm trying to get FULL server backup on Windows Server and getting this error, I have tried many things,

by resting VSS service etc.. but can't succeed.

Please find attached screen shot error

https://drive.google.com/file/d/1iMalaV_Q9ipUtXtzX5IXlrc8C3TpKwkd/view?usp=sharing

Thanks

Abdul WAhab

Server Backup 2019 and BD-XL

0
0

Is Server Backup 2019 supposed to support BD-XL (100 Gb) DVDs? It certainly doesn't on my server. I've seen Hotfixes for Windows Backup (Windows 10) to work with BD-XL but noting for Server 2019. Is there such a fix or is there one planned?

Also, I tried to copy the files on from the WindowsImageBackup directory created by Server Backup to DVD but that gave me errors (saying the files had changed although it's a dedicated drive). Without spending over $1000 for new software, I'm not sure what to do.

Has anyone got any suggestions for a poor, small academic lab?

Thanks so much.

Previous Article Next Article

How to fix Event Log is inaccessiable. Only messages for currently running operations will be displayed.

0
0

Running Windows Backup on a Windows Server 2012 to a Network share

I think the backup is completing & is listed in ALL Backups but I see the message

"Event Log is inaccessible. Only messages for currently running operations will be displayed."

Any ideas how to fix the issue?