Hello All ,
I have CISCO Blade physical server. I have taken baremetal and data drive backup of the server.
While restoring it from the network I am getting this error.
"System image restore failed with error: 0x807800B8"
When I try to do restore from another disk within the same Server, it work fine.
Any help much appreciated.
Thanks
Their storage capacity - up to 256 GB - equals that of many backup tapes (200 GB for example).
*
(This would probably be beyond most budgets:
http://www.cfgear.com/what-is-the-biggest-usb-flash-drive/ )
*
With USB 3.0, backup and restore could be very rapid.
Why can't we use them as a target for Windows Server Backup operations?
Unless something has changed (and maybe it has), we are limited to:
1. External hard drive (with nothing else on if we want to run scheduled backups to that drive).
2. Network target (shared folder on another server somewhere else).
3. DVD (given that maximum capacity is just under 10GB, this option is next to useless).
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.
I am backing up about 260GB of data to a 1TB disk.
For 2 weeks Backup has been reporting a error " there is not enough space" at the end of the backup proces.
This 1TB disk is completly empty. I also tried to send a backup over the network to QNAP but there is the some error.
--
Robert Stuczynski (Noise) - VirtualStudy.pl: http://VirtualStudy.pro
Hi,
A backup job has been setup on Windows Server 2012 (Platform: Win32NT; ServicePack: ; Version: 6.2.9200.0; VersionString : Microsoft Windows NT 6.2.9200.0) via Windows Backup Software UI (Local Backup 1.0).
It is appearing as a scheduled task "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup" belonging to user 'nt authority\system' in task scheduler.
The problem is that the Backup job never start despite the scheduled task running and completing successfully (when run automatically or manually)!
Would you be able to explain why and assist in resolving that issue?
Here is what we know:
When the backup is run manually via the Windows Backup Software UI, it works fine.
When the backup is run via command line (as set in schedule task) in a cmd command prompt (as local/domain 'administrator' or as 'nt authority\system' which is possible by running command prompt via 'PsExec.exe -i -s cmd'), something like "%windir%\System32\wbadmin.exe start backup -templateId:{f11eb3aa-74e7-4ff4-a57b-d8d567ee3f77} -quiet", it works fine.
If you manually run the preset scheduled task while logged in as administrator, the task run and complete successfully but the backup job does not start.
Idem if you schedule task is run automatically at scheduled time.
The schedule task run and complete successfully but the backup job does not start.
It is confirmed by running the following in a command prompt as 'nt authority\system':
schtasks /run /tn "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup"
SUCCESS: Attempted to run the scheduled task "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup".
Despite success result, the Backup job does not start running...
No errors or warning appears anywhere in Event Logs (Microsoft > Windows > Backup or Task Scheduler) nor in the scheduled task History tab. The schedule task complete successfully but no Backup job is run...
If scheduled task automatically set by Windows Backup software is duplicated (copied) and set manually it runs fine as 'administrator' and as 'nt authority\system' (subject that 'nt authority\system' is added to the 'Backup Operators' AD group).
Here is an export of the current pre-set schedule task, is there any settings that need to be changed to make it works?
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Author>MYDOMAIN\SERVER1</Author>
<SecurityDescriptor>D:AR(A;OICI;GA;;;BA)(A;OICI;GR;;;BO)</SecurityDescriptor>
</RegistrationInfo>
<Triggers>
<CalendarTrigger id="Trigger 1">
<StartBoundary>2014-07-14T21:00:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>Parallel</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>false</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
<UseUnifiedSchedulingEngine>false</UseUnifiedSchedulingEngine>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>P3D</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>%windir%\System32\wbadmin.exe</Command>
<Arguments>start backup -templateId:{f11eb3aa-74e7-4ff4-a57b-d8d567ee3f77} -quiet</Arguments>
</Exec>
</Actions>
</Task>
Thank you in advance for your feedback.
Hello,
I have just read that you can restore Windows 2008 to a different hardware, like Windows 7.
I was wondering: Is there the need of third-party software anymore?. I mean, you just backup the whole system in a network share or a san volume or elsewhere (outside the 2008 box), and that is that, no Acronis anymore.
Am I missing something?. To me, it looks so great.
Thanks in advance!
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)
Can someone confirm that it is reasonable to expect that when I use a 3rd party backup solution that I should be able to recover;
I have tested with the built-in Windows backup and this is working and I do know from a few years ago my previous backup solution would as well.
Am I wrong to expect in this example, say you are retiring an old file server and want ot migrate all exist data to a new file server. You should be able to backup/restore an exact copy of that data along with all custom permissions and file time stamps to a new server?
Another example would be in a disaster recovery, where you have to restore all your data to a new file server.
Your comments and clarifications are appreciated.
Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.
Hi all;
I'm using windows server backup to backup data on windows server 2012 R2, and was working fine until recently.
For a backup destination I tried external usb brand new 1 TB disk, and a built-in SCSI disk as well.
Both source and destination are GPT formatted. The Process fails with the error 0x8004245F regardless if it is manually started or scheduled.
Any idea? Thanks in advance.
I have a server with a 1TB SSD as the OS disk and a 1TB HDD as a data drive. I am using WBAdmin to backup the two drives to an external USB 4TB HDD. The command I am using is WBAdmin Start Backup -BackupTarget:F: -AllCritical -SystemState -Include:D: -Quiet and to restore to a new set of disks I am using the install disk and restore from an image.
My issus is that when I do a restore to a new set of disks the D: drive is restored to the SSD and the C: drive is restored to the HDD which is opposite of what I want and had from the backup. What determines which drive is restored to which? They are in an Intel 2600WT chassis and each drive is on a separate SATA controller. I put the new drives into the same slots the backed up drives were in.
I'm trying to solve a backup problem which started with Veritas Backup Exec failing to back up directories on a remote server. The BE error simply said that the directories could not be found yet I could browse to them in BE and Windows Explorer.
I then tried a full VSS backup in Windows Server Backup on the target server (2008 R2) and this also failed but there was no error in the WSB console, just the failed status. Looking in the Event Viewer I found two entries for the backup:
| - | System |
|
|
|
|
|
|
|
|
|
|
| - | EventData |
| IVssAsync::QueryStatus |
| 0x800706ba, The RPC server is unavailable. |
| Operation: BackupComplete Event Executing Asynchronous Operation Context: Current State: BackupComplete |
| 2D20436F64653A2042554543584D4C4330303030353934302D2043616C6C3A2042554543584D4C4330303030353833392D205049443A202030303030393736342D205449443A202030303031303234342D20434D443A202022433A5C57696E646F77735C73797374656D33325C7762656E67696E652E657865222020202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820 |
Binary data:
In Words
0000: 6F43202D 203A6564 43455542 434C4D58
0008: 30303030 30343935 6143202D 203A6C6C
0010: 43455542 434C4D58 30303030 39333835
0018: 4950202D 20203A44 30303030 34363739
0020: 4954202D 20203A44 31303030 34343230
0028: 4D43202D 20203A44 5C3A4322 646E6957
0030: 5C73776F 74737973 32336D65 6562775C
0038: 6E69676E 78652E65 20202265 20202020
0040: 7355202D 203A7265 656D614E 544E203A
0048: 54554120 49524F48 535C5954 45545359
0050: 53202C4D 533A4449 352D312D 2038312D
In Bytes
0000: 2D 20 43 6F 64 65 3A 20 - Code:
0008: 42 55 45 43 58 4D 4C 43 BUECXMLC
0010: 30 30 30 30 35 39 34 30 00005940
0018: 2D 20 43 61 6C 6C 3A 20 - Call:
0020: 42 55 45 43 58 4D 4C 43 BUECXMLC
0028: 30 30 30 30 35 38 33 39 00005839
0030: 2D 20 50 49 44 3A 20 20 - PID:
0038: 30 30 30 30 39 37 36 34 00009764
0040: 2D 20 54 49 44 3A 20 20 - TID:
0048: 30 30 30 31 30 32 34 34 00010244
0050: 2D 20 43 4D 44 3A 20 20 - CMD:
0058: 22 43 3A 5C 57 69 6E 64 "C:\Wind
0060: 6F 77 73 5C 73 79 73 74 ows\syst
0068: 65 6D 33 32 5C 77 62 65 em32\wbe
0070: 6E 67 69 6E 65 2E 65 78 ngine.ex
0078: 65 22 20 20 20 20 20 20 e"
0080: 2D 20 55 73 65 72 3A 20 - User:
0088: 4E 61 6D 65 3A 20 4E 54 Name: NT
0090: 20 41 55 54 48 4F 52 49 AUTHORI
0098: 54 59 5C 53 59 53 54 45 TY\SYSTE
00a0: 4D 2C 20 53 49 44 3A 53 M, SID:S
00a8: 2D 31 2D 35 2D 31 38 20 -1-5-18
I've checked a load of services: DCOM, VSS, RPC, RPC Endpoint Mapper, Virtual Disk... These are all running with only the VSS one set to Manual, the rest are all Automatic. Checking over the VSS Writers, all are Stable with No Error. Windows firewall is disabled and so is the ESET AV one. I've also tried this with the AV disabled - same problems. Looking through the registry keys for the services and all seems to be as it should. I seem to have hit a wall with this, every forum and question I've read so far lists a load of things to check which I've done and all seems okay, the only other "solution" suggested is to reinstall the OS which is not an option here. Any help at all would be greatly appreciated. |
Hi IT experts,
after successfully configure the GPO for folder redirection for Desktop, My Documents & Download only, since then all the users complaining that windows search option doesn't show the recent opened or available MS office documents.
Can you pls. suggest how to overcome this problem.
Thanks in advance
MAZ
I performed backup of a volume storing a database on my server using Windows Server Backup (WSB).
Now I have some old shadows that I would like to remove.
To do that, I use the vssadmin command with ShadowID that I'd like to remove:
vssadmin delete shadows /Shadow={9bae879d-979e-4ec0-b252-720de085d2bf}
However, I get the response
Error: Snapshots were found, but they were outside of your allowed context. Try
removing them with the backup application which created them.
Well, the application that created these shadows was WSB, and WSB GUI does not have command to delete old shadows.
How can I delete these shadows?
TIA
Les
Hi,
Can anyone recommend Data Backup Software that has the ability to enter a date, and will allow you to browse a directory structure for that date, and allow you to view/recover files which existed at that date?
Can Windows Backup do this?
By this I mean…
the Data Backup Software makes periodic (or real time) backups of all your files and folders within My Documents… to an external hard drive.
And let’s say that you want to recover a file which was deleted at some stage… or even a version of a file that was deleted.
That one can enter any date (in the past since the backup software was running), and search back for the file version that existed on that date… ideally by being able to view a directory structure for that date showing all the files that existed back then. And recover any file on an individual rather than having to recover a large zipped file of some date.
Ideally so that one could enter the date without specifying what file one is looking for... and just browse the directory structure and files that existed at that date.
For many of the Data Backup Software application, I often see good descriptions about all the setting one can use to run the backups… but very little description on how to go about searching for deleted files and how to recover a file that one is searching for.
Any suggestions?
Thanks in Advance.
Dave
When doing a bare metal backup of Windows Server 2019 Standard, I get a completed with warnings status. When looking at the "View list of all failed files", I see the following: "Backup of volume\\?\Volume{20912232-1c6d-4233-a28d-16211a55924b}\ has failed. The volume contains system data but is not included in the backup configuration." In Disk Management, the partition shows healthy. This volume is the OEM partition on Disk 0. This error just started after upgrading the server from 2012R2.
Any suggestions as to how to resolve this error so that the back can complete normally?JKS
Error received when attempting to run system state backup with WBAdmin utility: Error in backup of C:\windows\\systemroot\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.
Windows Server 2016 Standard running on VMware ESXi 6.5.0 build-8935087 (VMKernel Release 6.5.0) which runs on a Dell PowerEdge R740. I have tried using the VMware PowerCLI to set the vsock registry image path, but it is already selected correctly it reports. Please assist!Hi,
I have installed the Windows Server Backup feature several times in Windows Server 2012, but the "Windows Server Backup UI" is missing under the "Administrative Tools" and under the \System32\wbadmin.msc .
Any ideas how to re-create or workaround this problem ?
I really appreciate your help !
With kind regards,
Cengiz Kuskaya
نحن شركة جولد ماستر
لدينا مشكلة في الكمبيوتر الخاص بالشركة تم عمل نسخه جديده من ميكروسوفت ويندوز 10 وتم حذف ملفات هامه نريد حل لإرجاع الملفات مره اخري
I am using robocopy to replicate various data on multiple local storage devices to my home Synology DS218+ NAS. I noticed that throughput for large (multi GB) files was significantly slower than what is achieved through Windows explorer. With Explorer, reads and writes of large files would usually be around 113MB/s (~900Mbps) for the duration of the transfer. With robocopy, based on what I could see from Windows performance monitor, and verified with the NAS management console, reads and writes of large files (multi GB) would usually be around 40MB to 50MB/s (~300-400Mbps). The /mt option had no impact, as expected (since it would generally translate to improved performance with multiple smaller transfers) on throughput. Neither did the /j (unbuffered I/O) switch affect throughput. As the scripts and task schedule I had put in place were working well, I was about ready to give up on the performance discrepancy and say "Ah, it works. Good enough." but I just had to figure it out. After multiple trial-and-error runs, it turns out it's the /B switch. If I simple remove /B (which has the added benefit of not needing to be run with administrator privileges) performance is unleashed back to the full 900Mbps+ and even a little faster than Explorer. Any ideas why backup mode would negatively impact performance on large file transfers so much? Just for the additional info, this is effectively the cmd line I'm using, though not exactly because I am use job (rcj) files to keep things more tidy:
robocopy "E:\" "\\NAS\backup\E-Drive" /MIR /A-:SH /FFT /SL /XJD /R:1 /W:3 /LOG+:output.log /NDL /TEE /NP
It appears that this has been an issue for over 10 years now, and there is yet a resolution to be had.
Once you fill up the available shadow copy storage allocated, then push a lot of disk I/O's, your snapshots will eventually be deleted and you will incur data loss.
Here is how:
When one first creates a VSS snapshot, it shows 50GB of available shadow storage space, which is great:
C:\Users\root>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
For volume: (E:)\\?\Volume{8a5b0a31-7564-491e-a150-2fc8889ae217}\
Shadow Copy Storage volume: (E:)\\?\Volume{8a5b0a31-7564-491e-a150-2fc8889ae217}\Used Shadow Copy Storage space: 0 bytes (0%)Allocated Shadow Copy Storage space: 50 GB (0%)
Maximum Shadow Copy Storage space: 38.2 TB (100%)But as time goes by, this will fill up and then the VSS service will only try and stay ahead by about 300MB.
So what happens if you push too many I/O's, and the VSS service can't allocate space faster than it is writing? Does it re-allocate the space requested when the disk is idle? No. Does it pause the disk if it needs to allocate more shadow storage? No.
It will simply DELETE ALL of your snapshots.
Eventually, you will fill up the 50GB of shadow copy allocated storage, like so:
C:\Users\root>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
For volume: (E:)\\?\Volume{8a5b0a31-7564-491e-a150-2fc8889ae217}\
Shadow Copy Storage volume: (E:)\\?\Volume{8a5b0a31-7564-491e-a150-2fc8889ae217}\Used Shadow Copy Storage space: 50 GB (0%)Allocated Shadow Copy Storage space: 50.3 GB (0%)
Maximum Shadow Copy Storage space: 38.2 TB (100%)And from this point on, it will barely stay ahead, except by a measly 300MB, which isn't much when you're dealing with large volumes (the one above is about 40TB).
Here's a snapshot that is just waiting to disappear any day now...
C:\Users\root>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
For volume: (E:)\\?\Volume{8a5b0a31-7564-491e-a150-2fc8889ae217}\
Shadow Copy Storage volume: (E:)\\?\Volume{8a5b0a31-7564-491e-a150-2fc8889ae217}\
Used Shadow Copy Storage space: 151 GB (0%) <-- any moment my snapshot could be destroyed!Allocated Shadow Copy Storage space: 151 GB (0%) Maximum Shadow Copy Storage space: 38.2 TB (100%) Note that it stops showing decimals after 100GB, but I timed it as the space increases and the allocated space is still staying around 300MB ahead of the used space.
If you happen to write too many I/O's, you will get this in your event log and ALL of your snapshots will be deleted.
This is not acceptable, and I've seen it on multiple systems from Windows Server 2008 through Windows Server 2016. I need a resolution to this issue because we have customer data at stake, and we cannot move forward unless we know, for a fact, that snapshots will not be magically deleted because the hard drive decided to be slow one day, for some arbitrary reason.
I've also read the Microsoft suggestion of putting the shadow storage on another volume. That is a band aid and NOT a good solution, as that could also incur failures. If for some reason the SAN becomes unavailable, you will lose your snapshots. If for some reason the disk degrades on the second volume, you will lose your snapshots. If for some reason the second volume runs out of space, you will lose your snapshots.
It might also be worth mentioning that the registry setting MinDiffAreaFileSize was also suggested by Microsoft, but that does nothing to alleviate the issue.