Quantcast
Channel: Backup – Windows and Windows Server forum
Viewing all 3921 articles
Browse latest View live

How to backup the ProgramData\Microsoft\Crypto\RSA\MachineKeys directories and files

$
0
0

Using an Axcient appliance to backup Windows 2008 server.  The axcient appliance will not back up the ProgramData/Microsoft/Crypto/RSA/MachineKeys directories and files due to permission denied error messages.  First of all do these files really need to be backed up?  Gather from the reading that some of the files are important but not always all of them.  Also gathered from the reading that improperly changing permissions on the files can render some of the files invalid which could cause issues for the users that really own them.  In examing the file permissions the owner of the file cannot be displayed.  How can one determine who owns the directory/file?  Also caught some hints in some of the newsgroups and discussion threads that changing permissions is not enough to allow backups of the MachineKeys and Registry Hacks may be required.

Am looking for a simple checklist, in laymen's terms, of steps to follow to get the Axcient appliance to back up these directories and files.

Thank You.


Windows Backup After Reboot

$
0
0
Hello,
I have a problem with Windows Backup on Windows Server 2012 R2. I'm using Windows Backup for backing up my Hyper-V virtual machines and "Host Component". I'm using planned backup with dedicated external harddrive. Everything works fine, until I reboot host server. After reboot, backup stops working with error code 0x80780049. What helps is deleting and recreating planned backup job, but I can't recreate backup jobs on every Hyper-V host after every reboot. Has someone an idea what can cause this?

Thank you..

Unable to do incremental backups?

$
0
0

Hi guys!

We are trying to make incremental backups to a dedidacted attached external disk on Windows Server 2008 r2.

No matter if we use LINE1 or LINE2, it always does full backup:

wbadmin start backup -allCritical -backupTarget:E: -include:d: -vssfull-quiet | Out-FileForce "$backuplog"

wbadmin start backup -allCritical -backupTarget:E: -include:d: -quiet | Out-FileForce "$backuplog"

Any hints how to achieve doing incremental backups using Windows Server Backup tool?

with best regards,


bostjanc

Windows Server Backup failing to protect System State on Server 2008 Ent. SP2

$
0
0

My DPM2010 System State protection for another DPM 2010 Server started failing all of a sudden. Windows server backup also fails on the protected server when I run it manually. I know that if the wbadmin doesn't work then DPM can't work either. This problem appears to be an issue on the protected server with wbadmin and numerous writer errors. I'm including the details I've collected at this point. Thank you for reading this thread...any helpful ideas would be greatly appreciated.

Windows Server Backup error message:

C:\Windows\system32>wbadmin start systemstatebackup -backuptarget:m:

wbadmin 1.0 - Backup command-line tool

(C) Copyright 2004 Microsoft Corp.

Starting System State Backup [3/25/2014 7:05 AM]

Retrieving volume information...

This would backup the system state from volume(s) Local Disk(C:),DPM Vol(D:) to m:.

Do you want to start the backup operation?

[Y] Yes [N] No Y

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Summary of backup:

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

Backup of system state failed [3/25/2014 7:11 AM]

Log of files successfully backed up

'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup 25-03-2014 07-10-05.log'

Log of files for which backup failed

'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup_Error 25-03-2014 07-10-05.log'

Failure in a Volume Shadow Copy Service operation.

ERROR - Volume Shadow Copy Service operation error (0x800423f3)

The writer experienced a transient error. If the backup process is retried,

the error may not reoccur.

 

DPM protection error message:

Affected area: Computer\System Protection

Occurred since: 3/24/2014 7:04:24 AM

Description: The replica of System Protection Computer\System Protection on [Server Name] is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x807800A1). (ID 30229 Details: Internal error code: 0x809909FB)

More information

Recommended action: For resolution actions and more information on the WSB error, go to

http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.

Synchronize with consistency check.

Run a synchronization job with consistency check...

Resolution: To dismiss the alert, click below

Inactivate alert

 

Windows Event Viewer log error messages:

Log Name: Application

Source: VSS

Date: 3/25/2014 7:10:59 AM

Event ID: 8204

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: [Server Name]

Description:

Volume Shadow Copy Service error: An invalid XML document was returned from writer {d156f92e-363a-471e-a70f-34b4536e86b4}.

Operation:

Writer Modifying Modifying Backup Document

Context:

Execution Context: Requestor

Writer Instance ID: {D156F92E-363A-471E-A70F-34B4536E86B4}

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="VSS" />

<EventID Qualifiers="0">8204</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2014-03-25T14:10:59.000Z" />

<EventRecordID>233016</EventRecordID>

<Channel>Application</Channel>

<Computer> [Server Name] </Computer>

<Security />

</System>

<EventData>

<Data>{d156f92e-363a-471e-a70f-34b4536e86b4}</Data>

<Data>

Operation:

Writer Modifying Modifying Backup Document

Context:

Execution Context: Requestor

Writer Instance ID: {D156F92E-363A-471E-A70F-34B4536E86B4}</Data>

<Binary>2D20436F64653A2042554543584D4C4330303030303232332D2043616C6C3A2042554543584D4C4330303030303139302D205049443A202030303030303436382D205449443A202030303030303432342D20434D443A202022433A5C57696E646F77735C73797374656D33325C7762656E67696E652E657865222020202020202D20557365723A204E5420415554484F524954595C53595354454D20202020202D205369643A2020532D312D352D3138</Binary>

</EventData>

</Event>

______________________________________________________________________________

Log Name: Application

Source: Microsoft-Windows-Backup

Date: 3/25/2014 7:11:05 AM

Event ID: 521

Task Category: None

Level: Error

Keywords:

User: SYSTEM

Computer: [Server Name]

Description:

Backup started at '3/25/2014 2:10:05 PM' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-Backup" Guid="{1db28f2e-8f80-4027-8c5a-a11f7f10f62d}" />

<EventID>521</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2014-03-25T14:11:05.032Z" />

<EventRecordID>233017</EventRecordID>

<Correlation />

<Execution ProcessID="468" ThreadID="6540" />

<Channel>Application</Channel>

<Computer> [Server Name] </Computer>

<Security UserID="S-1-5-18" />

</System>

<EventData>

<Data Name="BackupTime">2014-03-25T14:10:05.862Z</Data>

<Data Name="ErrorCode">2155348129</Data>

<Data Name="ErrorMessage">%%2155348129</Data>

</EventData>

</Event>

 

 

Writer status before backup attemp:

Writer status after backup attempt:

C:\Windows\system32>vssadmin.exe list writers

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

(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'DPM Writer'

Writer Id: {0074a271-4f24-43e0-9ec7-28a44189cb80}

Writer Instance Id: {f63d8406-777c-4ad5-a000-c1fc509673fc}

State: [1] Stable

Last error: No error

Writer name: 'System Writer'

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

Writer Instance Id: {bcc605de-b52e-4ebe-8712-341e63c1c4c2}

State: [7] Failed

Last error: No error

Writer name: 'ASR Writer'

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

Writer Instance Id: {d156f92e-363a-471e-a70f-34b4536e86b4}

State: [7] Failed

Last error: Retryable error

Writer name: 'SqlServerWriter'

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

Writer Instance Id: {a21298a8-352d-4d27-acc8-531eb9dcd5d8}

State: [7] Failed

Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

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

Writer Instance Id: {37c43d93-ed3a-40f7-828e-b3b370d828e7}

State: [7] Failed

Last error: No error

Writer name: 'WMI Writer'

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

Writer Instance Id: {e1718057-885e-4008-b1f2-2c741e5ce2bc}

State: [7] Failed

Last error: No error

Writer name: 'Registry Writer'

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

Writer Instance Id: {e2a833f4-fcb5-4705-aedd-28e7e63a0a1d}

State: [7] Failed

Last error: No error

Writer name: 'IIS Config Writer'

Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

Writer Instance Id: {35c45908-d4a0-45fa-bd4d-147a95dd3977}

State: [7] Failed

Last error: No error

Writer name: 'COM+ REGDB Writer'

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

Writer Instance Id: {546d77e5-ea29-4e14-846a-394cc2f3009a}

State: [7] Failed

Last error: No error

Writer name: 'IIS Metabase Writer'

Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

Writer Instance Id: {a536a87b-1693-403a-9580-6e537e1624a5}

State: [7] Failed

Last error: No error

 

 

C:\Windows\system32>vssadmin.exe list writers

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

(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'System Writer'

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

Writer Instance Id: {bcc605de-b52e-4ebe-8712-341e63c1c4c2}

State: [1] Stable

Last error: No error

Writer name: 'DPM Writer'

Writer Id: {0074a271-4f24-43e0-9ec7-28a44189cb80}

Writer Instance Id: {f63d8406-777c-4ad5-a000-c1fc509673fc}

State: [1] Stable

Last error: No error

Writer name: 'ASR Writer'

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

Writer Instance Id: {d156f92e-363a-471e-a70f-34b4536e86b4}

State: [1] Stable

Last error: No error

Writer name: 'SqlServerWriter'

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

Writer Instance Id: {a21298a8-352d-4d27-acc8-531eb9dcd5d8}

State: [1] Stable

Last error: No error

Writer name: 'IIS Config Writer'

Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

Writer Instance Id: {35c45908-d4a0-45fa-bd4d-147a95dd3977}

State: [1] Stable

Last error: No error

Writer name: 'Registry Writer'

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

Writer Instance Id: {e2a833f4-fcb5-4705-aedd-28e7e63a0a1d}

State: [1] Stable

Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

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

Writer Instance Id: {37c43d93-ed3a-40f7-828e-b3b370d828e7}

State: [1] Stable

Last error: No error

Writer name: 'WMI Writer'

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

Writer Instance Id: {e1718057-885e-4008-b1f2-2c741e5ce2bc}

State: [1] Stable

Last error: No error

Writer name: 'COM+ REGDB Writer'

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

Writer Instance Id: {546d77e5-ea29-4e14-846a-394cc2f3009a}

State: [1] Stable

Last error: No error

Writer name: 'IIS Metabase Writer'

Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

Writer Instance Id: {a536a87b-1693-403a-9580-6e537e1624a5}

State: [1] Stable

Last error: No error

 

Windows 2012 System State Backup Fails

$
0
0

We have a Windows 2012 Domain Controller VM that we would like to backup the System State using DPM. Agent has been installed and the Windows Backup has been added.

When the backup runs in DPM, the job fails. Here is the error code:

  • DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x12363C0). (ID 30229 Details: Internal error code: 0x80990ED0)

When we try and create the backup using Windows Backup, the following error is in the log file:

  • following error code '0x807800C5' (There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

We have tried attaching a separate drive and backup to a shared location. Both fail.

We have tried backup of just a few files on the DC instead of the System State, this fails as well.

All VSS Writers show as Stable with no errors

Server has the latest updates

Server has been rebooted, same issue

VM is Windows 2012 on a Windows 2008 R2 clustered host and is using Dynamic Disks (not fixed disks).

Anyone have any thoughts on what could be going on?

Windows Server 2012 R2 Essentials Backup configurations/questions

$
0
0

Hi there,

Just set up a server for the first time running Windows Server 2012 R2 Essentials.

I have configured a backup to run once daily from a 300gb drive to both an internal 1TB drive and added an external 500gb drive for offsite storage however it doesn't seem to be creating a copy on the external drive at all.

Am I to assume that I need to create an entirely separate schedule somehow just for the external drive? Not sure how to do this, so instructions or link to an article on this would be excellent if this is the case.

Secondly, am I also right in assuming that by default it stores only incremental backups of data? Handy for saving storage space but wondered if I have the ability to configure the backups to store say, 10 days of data and write back over them after that? Or would incremental be easier/far superior?

Will the incremental backups occur until the drive is completely full?

I have struggled to find any detailed information regarding backups in Windows Server 2012, other than creating a schedule and choosing the disk to back up to, but none of the above questions can be answered from anything I've found.

Having mapped a network drive from the server to two client machines, overnight both the client machines required me to re-map them this morning. Any help on ensuring the drive stays mapped permanently would be most appreciated as well.

In terms of logging into the server on the mapped drive with user accounts, is there any way of logging which users edit/change files on the drive or restricting the user accounts from deleting things/viewing certain folders or files?

Recapping:

- Can't get backups to work on 500GB external drive

- How do the incremental backups actually work?

- Any supporting articles that actually have detailed information

- Mapped drives disconnecting/disappearing on client machines when turned off

- User account restrictions when logging into server via mapped network drive

Kind Regards.


Event ID 25 volsnap

$
0
0

I have a Windows Server 2008 R2 machine being backed up using Backupassist but also utilizing VSS.  The backups destination drive is iScsi drive (qnap). Recently I discovered that my previous backups were deleted and I am getting below log. The shadow copies were deleted during backup process.

Event ID:25  Source: volsnap

The shadow copies of volume Y: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

Which software will you use?

$
0
0
Which software will you use? Power data recovery or recuva?

Windows Server Backup: 2008R2 system state sometimes stalls

$
0
0

I have a 2008R2 SP1 server being backed up (C:, E:, system state) to disk on a remote client, using Windows Server Backup via a scheduled WBAdmin task. Usually the backup runs fine, but every now and then (and getting more frequent) the backup never finishes -- it stalls just after starting the system state backup (which is the last part of the backup).

The log of the WBAdmin output shows
  Starting to back up the system state [5/17/2012 4:36 AM]...
  Found (0) files.
  Found (0) files.
  [repeated 2000+ times]
and ends with "^C", with no errors or warnings shown.

Normally the system state backup takes under 15 minutes to run. When it stalls the Task Scheduler terminates it 6+ hours after it starts, so it's not a matter of insufficient time.

When it stalls wbengine.exe is left running, and I terminate it in Task Manager. This is all that's required to recover, and the backup will then run fine for weeks (or more recently, days).

There are no errors or warnings in the any of the event logs during the backup time.

"vssadmin list writers" shows "No error" for all writers, though some show the state as "[5] Waiting for completion"

This used to happen once a month and I ignored it. Recently it's happened 3 times in 2 weeks.

The [win]\Logs\WindowsServerBackup folder contains a Wbadmin.0.etl log file, but when I open it in Event Viewer it only goes back an hour or two, so it's clearly limited to a size too small.

How can I troubleshoot this issue?

Thanks!

Volsnap Event ID: 25 and Loss of Previous Backups

$
0
0
I have a Windows Small Business Server 2008 machine being backed up using the Windows Server Backup utility.  The backups are being made to two external USB attached 1TB drives.  Each drive is rotated out weekly, meaning that one drive is attached one week, then the other drive is swapped in the following week, ad infinitum for the best part of a year.  Two backups were being made each day to the attached drive, one at 12pm and one at 9pm.

About two weeks ago it appears that one of the two drives reached capacity and began shedding the oldest backups, as confirmed by the VOLSNAP Event ID: 33 entries in the System Event log.  On the second day, however, ALL shadow copies on the attached backup driver (volume) were deleted, as confirmed by a single VOLSNAP Event ID: 25.  (See below for both Event ID message contents.)  Unfortuneately, neither events were noted until the drive was swapped out with the other drive and some how the problem was propagated to the second drive, resulting in the deletion of all shadow copies on the second drive, too. 

The end result... BOTH drives lost ALL previous backups leaving only the most recent full backup and no clue as to why it happened or how to prevent it from happening again.  Virtually no older backup file versions could be recovered.

I was under the impression that, by design, the WSB utility would only start deleting the oldest backups (on a full drive) in order to make room for the newer backups.  Granted, had I been keeping attention, I would have actually swapped out the full drives before the actually got full, so that NO data was deleted.

If I'm to continue using the Windows Server Backup utility, I need to know what happened and how to absolutely prevent it from happening again.  I never expected to loose BOTH backups at the same time, and due to budget restraints, two rotating backup drives seemed a logical solution.

Here is text from the two VOLSNAP Event ID messages found in the System Log:

Event ID: 25
Source:  volsnap
Level: Error
Description:  The shadow copies of volume \\?\Volume{93896cfc-d904-11dd-8cb5-001ec9ef572e} were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

Event ID: 33
Source: volsnap
Level: Information
Description: The oldest shadow copy of volume \\?\Volume{93896cfc-d904-11dd-8cb5-001ec9ef572e} was deleted to keep disk space usage for shadow copies of volume \\?\Volume{93896cfc-d904-11dd-8cb5-001ec9ef572e} below the user defined limit.


NOTE:  Though I'm not sure if this has any bearing on the situation, the server is configured to make two snapshots a day of two volumes on the server, however, when I looked at the Shadow Copy settings I couldn't quite be sure if the VSS wasn't somehow also making snapshots on the two external drives, even though I haven't specified VSS to do so.  None show up on the two replacement drives I'm now using, so I'd say not.


Information on how to prevent this from happening again would greatly be appreciated.  (I'll be making sure no backup drive gets even close to being full from now on, that's for sure!)


Thanks,



Joseph.

Windows Registry Backup.

$
0
0

I want to set backup of registry for specific keys and folders. For that i use below command. 

"reg export HKLM\Software\etc E:\RegBakFolder\etc.reg /y" the issue is if i use"/y" then its will  Overwrite the existing file. i want command which will create new file every day with date and time + name which i give. is it possible.


Akshay Pate

Backup copy to two drives simultaneously? Win Server 2012 R2

$
0
0

Hi,

Just wondering if anyone knows how to create a scheduled backup in Windows Server 2012 R2 that will store a backup copy on both an internal drive and an external drive?

Windows backup makes a copy on the internal 1TB drive (incremental) but does not store a copy on the external drive (yes both are added in as destination drives). I get the feeling it only sees the external as additional space.

Cheers.

Problem with backup of DPM server system state

$
0
0

Since a few years we are using DPM to backup our servers but since some time the system state of the server where DPM is installed started to fail.

I was trying to do system state backup using command line windows backup:

wbadmin start systemstatebackup -backupTarget:C:

and it fails every time with different error (last 5 tries) after backing up a few tens %:

1. Error in backup of C:\Windows\winsxs\Manifests\x86_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7600.256_none_09f272fb52ab0c3f.manifest during read: Error [0x80070002] The system cannot find the file specified.
2. Error in backup of C:\Windows\System32\msmpeg2vdec.dll during write: Error [0x80070002] The system cannot find the file specified.
3. Error in backup of C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-WinMan-WinIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7601.16398.cat during read: Error [0x80070015] The device is not ready.
4. Error in backup of C:\ during read: Error [0x80070005] Access is denied.
5. Error in backup of C:\Windows\System32\ActionCenter.dll during write: Error [0x80070002] The system cannot find the file specified.

That's a Windows 2008 R2 server with DPM 2012 SP1 and OM servers installed.

The system state backup was doing fine for 2 or 3 years and suddenly it just stopped.:/

VSS - Exchange - Disk Management

$
0
0

Hello,

Last few days our backups (Veritas NetBackup) no longer work for Exchange 2010 server on Windows 2008 R2 SP1.VSSis still in error:

Microsoft Exchange Writer State [5]Waiting for completion / Last errorRetryable error.

After complete reboot it returns tostate [1] Stable / Last errorno error

Begins to turn again Veritas NetBackup and same error occurs.

I see also that my sevrver owns 2disks (in disk manager) with the following data

volume:<blank>/ Layout Single / Type Basic /File System <Blank> / Status Healthy / Capacity 0MB

Other disks are OK and DISKPART does not show this 2 disks.

Symantec tells us that the problem comes from VSS / Microsoft.

Any idea of the problem? How to troubleshoot VSS with Exchange provider/writer?VSSseems verypoorly explained by microsoft. Many problems andveryfew solutions (reboot and see)

Thank you in advance

Windows 2008 R2 state backup fails with various errors

$
0
0

Since a few years we are using DPM to backup our servers but since some time the system state of the server where DPM is installed started to fail.

I was trying to do system state backup using command line windows backup:

wbadmin start systemstatebackup -backupTarget:C:

and it fails every time with different error (last 5 tries):

1. Error in backup of C:\Windows\winsxs\Manifests\x86_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7600.256_none_09f272fb52ab0c3f.manifest during read: Error [0x80070002] The system cannot find the file specified.
2. Error in backup of C:\Windows\System32\msmpeg2vdec.dll during write: Error [0x80070002] The system cannot find the file specified.
3. Error in backup of C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-WinMan-WinIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7601.16398.cat during read: Error [0x80070015] The device is not ready.
4. Error in backup of C:\ during read: Error [0x80070005] Access is denied.
5. Error in backup of C:\Windows\System32\ActionCenter.dll during write: Error [0x80070002] The system cannot find the file specified.

That's a Windows 2008 R2 server with DPM and OM servers installed.

The system state backup was doing fine for 2 or 3 years and suddenly it just stopped.:/




Event 10172, Hyper-V-VMMS

$
0
0

VSS writers inside virtual machine 'CONTOSO' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID 9851BE14-F276-459D-8D60-DF73B67EB658)

What does it mean? Writers on virtual machine are OK and all backups are successfull. Every day I have one 10172 event for one backup in Hyper-V-VMMS event log.

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: {17daa546-f2b5-44a8-b88f-31fae0650076}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {75f7fecf-4696-4f0e-8d09-19809d5f35da}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {204ef83b-d168-4179-a6aa-ef01e93dae7d}
   State: [1] Stable
   Last error: No error

Writer name: 'WIDWriter'
   Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
   Writer Instance Id: {b45a4a13-60a4-4f38-bdc0-c4cc748f3513}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {aca59bd3-2f19-4c76-b54a-28f2c2d95f73}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {41ef02d7-38b9-424a-b35b-a4b1cf79bd17}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {7a6ef84a-4fff-46ed-8921-da0d12fb5028}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {6d28a625-90a9-47a4-bf9f-fd8a6c76e770}
   State: [1] Stable
   Last error: No error

Writer name: 'MSMQ Writer (MSMQ)'
   Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
   Writer Instance Id: {5bca99fe-6db6-4994-a744-e4149ba54364}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {d8249c2a-530f-48e9-92c3-179762ed0064}
   State: [1] Stable
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {51f5c94d-514b-4ca7-b5dd-2f11047d6a54}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {ce748865-451a-4189-8276-f2cb177629da}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {207fe098-42ab-430b-9285-c0b902729ade}
   State: [1] Stable
   Last error: No error

Backup config conflicts with Exchange

$
0
0

When I run the configuration for the native backup in SBS 2011 I get a warning saying "Warning cannot disable circular logging for backing up Exchange".

I did not setup this system originally. Exchange is not used for this company.

When I open up Exchange I get the following message: Connecting to the remote server failed with the following error message  The WinRm Client received an HTTP error server service error (500).

If Exchange is not active on this server, can I disable it entirely?

Thanks,

Paul


PAUL

windows could not start block level backup engine service

$
0
0

Hello,

              Im trying to perform system state backup for one of the server its unable to run. Last week we have performed the system state backup without any issue.

Operating System:2008

OS Version: R2 Small Business Server 2011 x64 Edition Build 7600

RAM-32 GB

Following event ID is reported in the logs;

Log Name:      Application

Source:        Microsoft-Windows-Backup

Date:          7/2/2013 2:25:35 PM

Event ID:      754

Task Category: None

Level:         Information

Keywords:     

User:          SYSTEM

Computer:      ABC

The Block Level Backup Engine service has stopped.

When we try to restart the Block Level Backup Engine service we get error as “Windows could not start the Block Level Backup Engine Service on Local Computer.

Error 0x800700b7: Cannot create a file when that file already exists.”

I have already restarted Virtual disk and Volume shadow copy service, but no luck.

Any help in resolving this issue will be much appreciated.

Thank you.

Keshava

Restarurar backup gerado pelo Windows Server 2012 Fundation, no Windows Server 2003 R2

$
0
0

Prezados,

Gostaria de saber se tem algum patch e/ou programa para que eu possa restaurar no Windows Server 2003 R2, backup gerado pelo Windows Server 2012 Fundation ?

Desde já agradeço a atenção,

Alexandre Delgado
Analista de TI

MMC CANNOT OPEN DE FILE C:\WINDOWS\system32\wbadmin.msc

$
0
0

The Windows Server Backup is forcibly closed. When I try to open it from the administrative tools I get the error "MMC can not open the file" and the file path with the error present in the print screen.
Check the path and this program, double click and give me actually get the error, the user that has execute permissions high, then the program was abruptly halted.
In the server manager can display the windows server backup no errors, it's just when I try to open it directly.
I want help resolving this error, the eventviewer presents no mistake.
  I attached the message ....




thanks




Viewing all 3921 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>