Hello,
I am currently working on a project. Please does anyone know How can a User Authenticate with Active Directory while connected to Private Internet.
Kindly provide me with the solutions.
Thank you
Iniobong Nkanga
How can a user authenticate with AD while connected to private internet.
↧
↧
Backup All Share perminsiion " 2008 r2" and restore on windows 2012 r2
Dears,
please i have a file server " windows 2008 r2 " and i need to backup all shared permission and restore it on a new server " windows 2012 r2"
could you please help me?
↧
VSS System Writer missing on Windows Server 2008
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!! :)
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!! :)
↧
Backup All Share permision " 2008 r2" and restore on windows 2012 r2
Dears,
please i have a file server " windows 2008 r2 " and i need to backup all shared permission and restore it on a new server " windows 2012 r2"
could you please help me?
↧
Windows Native backup
Dear Team,
Please help the procedures to be followed for taking Backup for Active Directory, SSCM, and DHCP services and what are the permission required for system admin for defining ACL for sys admin. Also how to automate the same windows backup
↧
↧
Bare Metal Recovery Partition
Hi -
I am doing a test restore if a windows 2016 essential server on Hyper-V. The restore works fine and the Hyper-V boots into windows 2016 essential however it does not seem to restore drive D: (data drive). there is no error message just at the end of the restore saying drive C: restored sucesffully drive D not restored. i have made sure i have clicked the options to format and repartition all disk etc thanks.
↧
Backup failed due to Ä Volume Shadow copy service operation failed.
Hi IT Experts,
Since one week, backup in one of our servers shows "A Volume shadow copy service operation failed" and Bare Metal Recovery and System State failed, resulting no backup is happening, for testing purpose i manually enabled the VSS service to Automatic also checked the destination folder has enough space but no luck.
Further more, I check the Disk mgmt and found "System Reserved"" partition doesn't shows System but only Active & Primary, attached snapshot shows the current Disk Mgmt for your advice.
Appreciate your support
TIA
Maz
↧
How do I stop sub folders being automatically added to my Windows 10 file history back up list?
On the backup options page (Settings>Update & Security>Backup>More Options), there is a list of folders to include when performing a backup. For example, Pictures C:\Users\me backups all the folders in my pictures folder. This works well.
However, all the new sub-folders in my picture folder are automatically added to the list. I've already set the backup to save my pictures folder and all its sub folders so I don't need all my new sub folders on the list.
To make matters worse, after I go through and remove all the sub folders, they are then automatically added to the exclude list so then I have to go through and remove all of them from my exclude list.
How do I stop sub folders being automatically added to my Windows 10 file history back up list?
↧
Is it possible to restore a bare metal backup to a different disk layout on the new server in Windows Server?
I have a backup of a server and am trying to recover that to a new system (test system right now) that has a different disk layout... I would like to restore/recover to this new layout... Is this possible? Right now it tries to restore to the C: drive and there is not enough space there... Help!
:-)
Thanks!
↧
↧
System Administrator
I am trying to backup of Active directory System State with WBADMIN but it fail because "System Writer" is missing, please help.
↧
امل الحصول على رابط تحميل خاص بالويندوز
Windows Server 2016 Standard
↧
Why do all my backup copies disappear when the disk reaches capacity?
Windows Server 2016 running Exchange 2016. Windows Server Backup does a Full backup every night.
I check the backups every Thursday. Last week it had 20-copies and this week it has 1-copy. This has happened 3-times now. It resets back to one instead of deleting older copies to make room.
What's going on?
Thank you in advance!
↧
Why is "wbengine" of Windows Server 2008 R2 always creating new VHD files when targeting network shares?
This is a follow up to things I've written down in an answer to another
question:
I'm somewhat sure that `wbengine` of Windows Server 2008 R2 always creates new VHD files if targeting a network share. Here's what some docs and other people say to that topic:
If you save a backup to a remote shared folder, that backup will be overwritten if you use the same folder to back up the same computer again.[...]
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc742130(v=ws.10)
Note that if you are backing up to a network share then a full backup will be run every time (because VSS is unavailable) overwriting the previous full backup. In this case there is no backup policy at all, you are simply maintaining a remote shadow/copy of the system.
https://lennox-it.uk/a-complete-guide-to-wbadmin-windows-backups
Das kommt darauf an auf welches Medium du sicherst. Wenn auf Festplatten ect. gesichert wird, dann wird immer inkrementell gesichert. Wird auf ein Share gesichert, dann ist es immer ein Vollbackup, wobei das letzte Backup überschrieben wird.
https://administrator.de/forum/verständnisfragen-windows-server-backup-2012-294395.html
Looking at my own tests using Windows 2008 R2, "overwritten" seems to be a bit misleading here, because it seems that really new files get created, as not only names of the images change, but their inodes as well:
root@[...]:~# ls -lisa "/volume1/[...]/WindowsImageBackup/[...]/Backup 2019-11-01 190024" total 247604492 435 0 drwx------+ 1 [...] users 2582 Nov 2 09:12 . 430 0 drwx------+ 1 [...] users 108 Nov 1 19:58 .. 8200 214832596 -rwx------+ 1 [...] users 220521977856 Nov 1 21:33 3e4779f7-b3e1-11e0-b58f-001999a28c91.vhd 8199 32764536 -rwx------+ 1 [...] users 42484091904 Nov 1 20:12 5d3e4b2f-b386-11e0-ac00-806e6f6e6963.vhd 8214 4 -rwx------+ 1 [...] users 1078 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_AdditionalFilesc3b9f3c7-5e52-4d5e-8b20-19adc95a34c7.xml 8216 12 -rwx------+ 1 [...] users 11940 Nov 1 21:34 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Components.xml 8213 8 -rwx------+ 1 [...] users 5500 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_RegistryExcludes.xml 8203 4 -rwx------+ 1 [...] users 3138 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writer0bada1de-01a9-4625-8278-69e735f39dd2.xml 8210 4 -rwx------+ 1 [...] users 1934 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writer2a40fd15-dfca-4aa8-a654-1f8c654603f6.xml 8208 4 -rwx------+ 1 [...] users 3414 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writer4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f.xml 8207 4 -rwx------+ 1 [...] users 1488 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writer542da469-d3e1-473c-9f4f-7847f01fc64f.xml 8212 4 -rwx------+ 1 [...] users 1630 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writer59b1f0cf-90ef-465f-9609-6ca8b2938366.xml 8202 4 -rwx------+ 1 [...] users 1628 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writer75dfb225-e2e4-4d39-9ac9-ffaff65ddf06.xml 8211 4 -rwx------+ 1 [...] users 950 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writera65faa63-5ea8-4ebc-9dbd-a0c4db26912a.xml 8209 4 -rwx------+ 1 [...] users 1484 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writera6ad56c2-b509-4e6c-bb19-49d8f43532f0.xml 8206 4 -rwx------+ 1 [...] users 3844 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writerafbab4a2-367d-4d15-a586-71dbb18f8485.xml 8205 8 -rwx------+ 1 [...] users 4288 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writerbe000cbe-11fe-4426-9c58-531aa6355fc4.xml 8201 4 -rwx------+ 1 [...] users 1746 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writerd61d61c8-d73a-4eee-8cdd-f6f9786b7124.xml 8204 7284 -rwx------+ 1 [...] users 7455796 Nov 1 21:33 9506dbe7-82a5-4559-96b3-0a2632ae05f9_Writere8132975-6f93-4464-a53e-1050253ae220.xml 8215 4 -rwx------+ 1 [...] users 1098 Nov 1 21:33 BackupSpecs.xml
root@[...]:~# ls -lisa "/volume1/[...]/WindowsImageBackup/[...]/Backup 2019-11-02 190054" total 247603788 435 0 drwx------+ 1 [...] users 2582 Nov 2 21:51 . 430 0 drwx------+ 1 [...] users 108 Nov 2 19:59 .. 8247 4 -rwx------+ 1 [...] users 1078 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_AdditionalFilesc3b9f3c7-5e52-4d5e-8b20-19adc95a34c7.xml 8249 12 -rwx------+ 1 [...] users 11940 Nov 2 21:51 0d420c40-f14c-4622-85d0-da11
6fc45608_Components.xml 8246 8 -rwx------+ 1 [...] users 5500 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_RegistryExcludes.xml 8236 4 -rwx------+ 1 [...] users 3138 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writer0bada1de-01a9-4625-8278-69e735f39dd2.xml 8242 4 -rwx------+ 1 [...] users 1934 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writer2a40fd15-dfca-4aa8-a654-1f8c654603f6.xml 8239 4 -rwx------+ 1 [...] users 3414 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writer4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f.xml 8243 4 -rwx------+ 1 [...] users 1488 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writer542da469-d3e1-473c-9f4f-7847f01fc64f.xml 8241 4 -rwx------+ 1 [...] users 1630 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writer59b1f0cf-90ef-465f-9609-6ca8b2938366.xml 8235 4 -rwx------+ 1 [...] users 1628 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writer75dfb225-e2e4-4d39-9ac9-ffaff65ddf06.xml 8244 4 -rwx------+ 1 [...] users 950 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writera65faa63-5ea8-4ebc-9dbd-a0c4db26912a.xml 8245 4 -rwx------+ 1 [...] users 1484 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writera6ad56c2-b509-4e6c-bb19-49d8f43532f0.xml 8240 4 -rwx------+ 1 [...] users 3844 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writerafbab4a2-367d-4d15-a586-71dbb18f8485.xml 8238 8 -rwx------+ 1 [...] users 4288 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writerbe000cbe-11fe-4426-9c58-531aa6355fc4.xml 8234 4 -rwx------+ 1 [...] users 1746 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writerd61d61c8-d73a-4eee-8cdd-f6f9786b7124.xml 8237 7284 -rwx------+ 1 [...] users 7455796 Nov 2 21:51 0d420c40-f14c-4622-85d0-da116fc45608_Writere8132975-6f93-4464-a53e-1050253ae220.xml 8233 214832596 -rwx------+ 1 [...] users 220521977856 Nov 2 21:51 3e4779f7-b3e1-11e0-b58f-001999a28c91.vhd 8232 32763832 -rwx------+ 1 [...] users 42481994240 Nov 2 20:11 5d3e4b2f-b386-11e0-ac00-806e6f6e6963.vhd 8248 4 -rwx------+ 1 [...] users 1098 Nov 2 21:51 BackupSpecs.xml
That is different to what I see on my USB-disks, where images keep their names and file-IDs(/inodes) and only most of the XML files get new UUIDs. On the USB-disks the parent directory of the VHD(X) changes as well, but that is simply a rename and hence doesn't influence the child files in any way. At one point during the tests I managed that `wbengine` decided to keep names of VHD files, but their inode changed always. Didn't invoke with any new command line, though, but simply subsequently:
8260 32767464 -rwx------+ 1 [...] users 42481994240 Nov 3 12:47 5d3e4b2f-b386-11e0-ac00-806e6f6e6963.vhd
8266 32764416 -rwx------+ 1 [...] users 42481994240 Nov 3 13:18 5d3e4b2f-b386-11e0-ac00-806e6f6e6963.vhd
I don't know why they implemented things this way in case of using shares, as it breaks e.g. underlying BTRFS-snapshots. But that's exactly what I see: All the snapshots my NAS creates for the folder where I store those backups almost have all associated
storage exclusively instead of sharing large parts of the data. Additionally, according to log file sizes and runtime lengths of `wbengine`, all backups almost take the same amount of time, even though files in the backed up source don't change too much.
So, why did MS choose that implementation of recreating image files?
↧
↧
Does “wbengine” of Windows Server 2019 support incremental backups when targeting network shares?
This is a follow up to things I've written down in an answer to another
question:
How does Windows Image Backup decide which files to backup?
Windows/NTFS manages [change journals][2] on each volume, keeping track of which file has changed, how it has changed and because those are part of all NTFS volumes by default, they are available in the VHD(X) of the backup target as well. From my understanding,
`wbengine` simply compares those journals to know which files need backup. This makes it easy to support different backup targets without caring about archive bits of files or stuff like that, because those change journals are bound to volume-unique file-IDs
and those IDs are exactly the same in the backup target:
C:\>fsutil file queryfileid "C:\Program Files\ActiveState Perl Dev Kit 9.5.1\bin\perlapp.exe"
Datei-ID: 0x000000000000000000080000000ea5f1
C:\>fsutil file queryfileid "D:\Program Files\ActiveState Perl Dev Kit 9.5.1\bin\perlapp.exe"
Datei-ID: 0x000000000000000000080000000ea5f1
In the above example, `C:\` is my current system volume while `D:\` is the mounted last backup on one of the two available backup targets. Even file sizes, timestamps etc. are all the same:
C:\>dir /A "C:\Program Files\ActiveState Perl Dev Kit 9.5.1\bin\perlapp.exe" Datenträger in Laufwerk C: ist System Volumeseriennummer: 266B-2863 Verzeichnis von C:\Program Files\ActiveState Perl Dev Kit 9.5.1\bin 03.02.2016 17:08 560.640 perlapp.exe 1 Datei(en), 560.640 Bytes 0 Verzeichnis(se), 1.337.040.216.064 Bytes frei C:\>dir /A "D:\Program Files\ActiveState Perl Dev Kit 9.5.1\bin\perlapp.exe" Datenträger in Laufwerk D: ist System Volumeseriennummer: 266B-2863 Verzeichnis von D:\Program Files\ActiveState Perl Dev Kit 9.5.1\bin 03.02.2016 17:08 560.640 perlapp.exe 1 Datei(en), 560.640 Bytes 0 Verzeichnis(se), 1.281.302.233.088 Bytes frei
By using this approach, backup can decide at any time with any older VHD(X) which files need to be backed up, as long as the current journal and the one in the image have something in common, which are entry-IDs in my understanding. Without such a shared ID,
e.g. because too many I/O happend productive and the backup is too old, wbengine would simply do a full backup instead of an incremental one.
Using those journals makes it as well pretty fast to know which files to backup, because one doesn't need to iterate the whole tree of files. That's what one actually sees in practice as well: Backup seems to know pretty soon which files to backup and starts
processing those instead of iterating a file tree.
Behaviour in case of network shares as backup target for Windows Server 2012+.
In older versions of Windows, wbengineseems to have always recreated VHD files, making it pretty incompatible
with snapshots supported by some underlying file system like BTRFS or ZFS. Additionally, each and every backup was a full one, simply because wbengine didn't have access to any former backup to compare with.
Things seem to be a little bit different with newer versions of Windows: I'm somewhat sure that one customer of mine ran into troubles with wbadmin and Windows Server 2012 and during debugging those using Process Monitor, I verified that
existing VHDX files were kept instead of deleted and recreated. I've tested this right now with Windows Server 2019 again and multiple invocations ofwbadmin led to successful backups while KEEPING inodes of VHDX files the same:
root@[...]:~# ls -lisa "/volume1/[...]/Backup 2019-11-02 200024" total 549063256 271 0 d---------+ 1 user group 594 Nov 2 20:58 . 266 0 d---------+ 1 user group 108 Nov 2 20:58 .. 273 507813736 ----------+ 1 user group 520061190144 Nov 2 22:02 165c4b13-8376-4c55-9643-a8c1b2c17d6b.vhdx 3814 4 ----------+ 1 user group 776 Nov 1 22:47 52e1a857-4620-43af-9f6e-a03fb53c7c30_AdditionalFilesc3b9f3c7-5e52-4d5e-8b20-19adc95a34c7.xml 3816 440 ----------+ 1 user group 450488 Nov 1 22:47 52e1a857-4620-43af-9f6e-a03fb53c7c30_Components.xml 3813 8 ----------+ 1 user group 6212 Nov 1 22:47 52e1a857-4620-43af-9f6e-a03fb53c7c30_RegistryExcludes.xml 3815 4 ----------+ 1 user group 1192 Nov 1 22:47 BackupSpecs.xml 272 41249064 ----------+ 1 user group 42289070080 Nov 2 22:03 f7650533-11ca-4db4-80f5-2db42f7b900a.vhdx root@[...]:~# ls -lisa "/volume1/[...]/Backup 2019-11-03 132201" total 549318872 271 0 d---------+ 1 user group 594 Nov 2 20:58 . 266 0 d---------+ 1 user group 108 Nov 3 14:19 .. 273 507813736 ----------+ 1 user group 520061190144 Nov 3 14:19 165c4b13-8376-4c55-9643-a8c1b2c17d6b.vhdx 3814 4 ----------+ 1 user group 776 Nov 1 22:47 52e1a857-4620-43af-9f6e-a03fb53c7c30_AdditionalFilesc3b9f3c7-5e52-4d5e-8b20-19adc95a34c7.xml 3816 440 ----------+ 1 user group 450488 Nov 1 22:47 52e1a857-4620-43af-9f6e-a03fb53c7c30_Components.xml 3813 8 ----------+ 1 user group 6212 Nov 1 22:47 52e1a857-4620-43af-9f6e-a03fb53c7c30_RegistryExcludes.xml 3815 4 ----------+ 1 user group 1192 Nov 1 22:47 BackupSpecs.xml 272 41504680 ----------+ 1 user group 42289070080 Nov 3 14:21 f7650533-11ca-4db4-80f5-2db42f7b900a.vhdx root@[...]:~# ls -lisa "/volume1/[...]/Backup 2019-11-03 133308" total 41262660 271 0 d---------+ 1 user group 2504 Nov 3 14:44 . 266 0 d---------+ 1 user group 108 Nov 3 14:30 .. 3851 4 ----------+ 1 user group 776 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_AdditionalFilesc3b9f3c7-5e52-4d5e-8b20-19adc95a34c7.xml 3853 440 ----------+ 1 user group 450488 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Components.xml 3850 8 ----------+ 1 user group 6212 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_RegistryExcludes.xml 3840 4 ----------+ 1 user group 3138 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writer0bada1de-01a9-4625-8278-69e735f39dd2.xml 3848 4 ----------+ 1 user group 2284 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writer2707761b-2324-473d-88eb-eb007a359533.xml 3844 8 ----------+ 1 user group 5386 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writer4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f.xml 3846 4 ----------+ 1 user group 1488 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writer542da469-d3e1-473c-9f4f-7847f01fc64f.xml 3839 4 ----------+ 1 user group 1628 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writer75dfb225-e2e4-4d39-9ac9-ffaff65ddf06.xml 3842 24 ----------+ 1 user group 21686 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writera65faa63-5ea8-4ebc-9dbd-a0c4db26912a.xml 3847 4 ----------+ 1 user group 1484 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writera6ad56c2-b509-4e6c-bb19-49d8f43532f0.xml 3845 4 ----------+ 1 user group 2940 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writerafbab4a2-367d-4d15-a586-71dbb18f8485.xml 3849 4 ----------+ 1 user group 1850 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writerb2014c9e-8711-4c5c-a5a9-3cf384484757.xml 3843 8 ----------+ 1 user group 6048 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writerbe000cbe-11fe-4426-9c58-531aa6355fc4.xml 3838 4 ----------+ 1 user group 1746 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writerd61d61c8-d73a-4eee-8cdd-f6f9786b7124.xml 3841 13068 ----------+ 1 user group 13379228 Nov 3 14:44 22c1a052-3d01-438c-87f8-acf63f14f5b5_Writere8132975-6f93-4464-a53e-1050253ae220.xml 3852 4 ----------+ 1 user group 758 Nov 3 14:44 BackupSpecs.xml 272 41249064 ----------+ 1 user group 42289070080 Nov 3 14:44 f7650533-11ca-4db4-80f5-2db42f7b900a.vhdx
So in theory this should allow incremental backups replacing files in-place and efficient snapshots of e.g. underlying BTRFS or ZFS at the same time. Looking at storage of the snapshots of the tested Windows Server 2019, at least some of those really share some space:
Total Exclusive Set shared Filename 424.41GiB 417.69GiB 6.72GiB /volume1/@sharesnap/[...]/GMT+01-2019.10.29-00.00.09 446.53GiB 400.16GiB 46.37GiB /volume1/@sharesnap/[...]/GMT+01-2019.10.30-00.00.08 483.05GiB 448.36GiB 34.70GiB /volume1/@sharesnap/[...]/GMT+01-2019.10.31-00.00.08 553.78GiB 209.26GiB 344.52GiB /volume1/@sharesnap/[...]/GMT+01-2019.11.02-00.00.09 204.68GiB 204.63GiB 0.05GiB /volume1/@sharesnap/[...]/GMT+02-2019.10.01-00.00.07 410.24GiB 405.37GiB 4.87GiB /volume1/@sharesnap/[...]/GMT+02-2019.10.27-00.00.06
It's not as much as I would expect, though. The thing is that it might be that not much space is shared even though VHDX files are reused, because when I subsequently invoke backing up C:\ of that server, backup doesn't seem to get faster.
The first backup might take longer as much data has changed, but after that is finished and with the server doing nothing, a second backup only a few minutes later should be a lot faster, because of only backing up differences of the files. But that doesn't
seem to be the case, instead it seems to take the same time like before. Additionally, while BTRFS can share differences in created snapshots between different invocations of wbadmin with the exact same command line, those are much smaller
than expected when really only backing up changed files:
root@[...]:~# btrfs filesystem du -s --gbytes /volume1/@sharesnap/[a-zA-Z]*/GMT*
Total Exclusive Set shared Filename
446.53GiB 400.20GiB 46.33GiB /volume1/@sharesnap/[...]/GMT+01-2019.10.30-00.00.08
483.05GiB 448.36GiB 34.70GiB /volume1/@sharesnap/[...]/GMT+01-2019.10.31-00.00.08
553.78GiB 546.54GiB 7.24GiB /volume1/@sharesnap/[...]/GMT+01-2019.11.02-00.00.09
39.35GiB 37.68GiB 1.67GiB /volume1/@sharesnap/[...]/GMT+01-2019.11.03-15.36.52
39.35GiB 31.18GiB 8.17GiB /volume1/@sharesnap/[...]/GMT+01-2019.11.03-15.49.03
39.35GiB 37.98GiB 1.37GiB /volume1/@sharesnap/[...]/GMT+01-2019.11.03-16.03.06
410.24GiB 409.72GiB 0.52GiB /volume1/@sharesnap/[...]/GMT+02-2019.10.27-00.00.06That is different to what I see when backing up to my USB-disks, subsequent backups are much faster if nothing has changed. What is interesting is that others seem to be not so sure about how things behave on network shares as well:
If you create a scheduled backup job to network shared folder or a mapped network drive, all the backups will only be performed by full backup because network location is not a volume. If you need to create differential backup or incremental backup to network folder, you need to third party backup software.
https://www.ubackup.com/windows-server/windows-server-backup-differential-4348.html
While the same people write the following, which doesn't make much sense:
Tip: You can also use WBADMIN to create incremental backup to network share, like this: wbadmin start backup –backupTarget: \\backupshare\backup1 -allCritical -include:C: -vssFull –quiet
https://www.ubackup.com/articles/wbadmin-incremental-backup-5740.html
In case of backing up to shares, if VHD is recreated always, like seems to be the case for older versions of Windows, one doesn't get incremental backups. But even though VHDX files are kept in newer versions of Windows, it seems like only backing up changed
files still doesn't work the same way like it does when using USB-disks.
Using -vssFull vs. -vssCopy didn't make any difference in my tests and according to my understanding is not even intended to do so. Those arguments are only relevant to 3rd party software and don't influence which files
are backed up how. Reasons to believe so are documented in my former answer:
Influence of -vssFull and -vssCopy.
https://serverfault.com/a/990394/333397
Questions
Does `wbengine` of Windows Server 2019 support incremental backups when targeting network shares? Does anyone see any improvement in backup times and storage allocations in case of snapshots?
↧
Event ID 55 - A corruption was discovered in the file system structure on volume
Hi guys,
I have two failover clusters with three nodes (based on Windows Server 2019) in each cluster.
Virtual machines are protected by means of Altaro Backup.
After continuous period of warnings generated by Altaro Backup it has been found in both Windows System log and Altaro backup log that some volume (which obviously Altaro backup refers to) MFT contains corrupted file record.
A corruption was discovered in the file system structure on volume \\?\Volume{8a4d749a-3081-4ba5-a001-c70bb335c2de}.
The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000029104. The name of the file is "<unable to determine file name>".
2019-11-05 02:39:30.037 0059 BackupMilestoneProvider.ScanEventLog : Suspicious record: <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Ntfs' Guid='{dd70bc80-ef44-421b-8ac3-cd31da613a4e}'/><EventID>55</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated
SystemTime='2019-11-04T13:41:03.583214500Z'/><EventRecordID>491689</EventRecordID><Correlation/><Execution ProcessID='4' ThreadID='25808'/><Channel>System</Channel><Computer>hvhost01.company.com</Computer><Security
UserID='S-1-5-18'/></System><EventData><Data Name='DriveName'>\\?\Volume{8a4d749a-3081-4ba5-a001-c70bb335c2de}</Data><Data Name='DeviceName'>\Device\HarddiskVolume9415</Data><Data Name='CorruptionState'>0x0</Data><Data
Name='HeaderFlags'>0x922</Data><Data Name='Severity'>Critical</Data><Data Name='Origin'>File System Driver</Data><Data Name='Verb'>Bad FRS</Data><Data Name='Description'>The Master File Table (MFT) contains
a corrupted file record. The file reference number is 0x1000000029104. The name of the file is "<unable to determine file name>".
</Data><Data Name='Signature'>0x504df163</Data><Data Name='Outcome'>Read Only Volume</Data><Data Name='SampleLength'>0</Data><Data Name='SampleData'></Data><Data Name='SourceFile'>0x1</Data><Data
Name='SourceLine'>1250</Data><Data Name='SourceTag'>203</Data><Data Name='AdditionalInfo'>0xd00000a2</Data><Data Name='CallStack'>Ntfs+0x11e86, Ntfs+0x1710f4, Ntfs+0x15374f, Ntfs+0x15fec1, Ntfs+0xf3d56,
Ntfs+0x19a5e, ntoskrnl+0x5d11a, ntoskrnl+0x1216c5, ntoskrnl+0x1b849c</Data></EventData></Event>
2019-11-05 02:39:30.037 0059 BackupMilestoneProvider.ScanEventLog : Suspicious record: <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Ntfs' Guid='{dd70bc80-ef44-421b-8ac3-cd31da613a4e}'/><EventID>55</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated
SystemTime='2019-11-04T13:41:16.366578900Z'/><EventRecordID>491714</EventRecordID><Correlation/><Execution ProcessID='4' ThreadID='26308'/><Channel>System</Channel><Computer>hvhost01.company.com</Computer><Security
UserID='S-1-5-18'/></System><EventData><Data Name='DriveName'>\\?\Volume{8a4d749a-3081-4ba5-a001-c70bb335c2de}</Data><Data Name='DeviceName'>\Device\HarddiskVolume9420</Data><Data Name='CorruptionState'>0x0</Data><Data
Name='HeaderFlags'>0x922</Data><Data Name='Severity'>Critical</Data><Data Name='Origin'>File System Driver</Data><Data Name='Verb'>Bad FRS</Data><Data Name='Description'>The Master File Table (MFT) contains
a corrupted file record. The file reference number is 0x1000000029104. The name of the file is "<unable to determine file name>".
I went through the thread below:
https://social.technet.microsoft.com/Forums/ie/en-US/510db7df-35cf-4e20-a1fd-23bdb934712c/event-55-ntfs-the-file-system-structure-on-the-disk-is-corrupt-and-unusable?forum=winservergen
https://social.technet.microsoft.com/Forums/windowsserver/en-US/5cbed1b1-63e3-4c15-8fff-b48746d5ba44/2008r2-backup-causing-event-55-ntfs-errors?forum=windowsbackup
Found no shadow copies. Also, not sure if chkdsk would shed some light if I run it.
Is there anything else worth to try?
↧
Backup job failed. Cannot notify writers about the ''BACKUP FINISH'' event
Dear Team,
Please help us to fix the below issue
VSS: Backup job failed. Cannot notify writers about the ''BACKUP FINISH'' event. A VSS critical writer has failed. Writer name: [Microsoft Exchange Writer]. Class ID: [{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}]. Instance ID: [{b9c55704-4b55-4a1f-886e-0922334a6199}]. Writer''s state: [VSS_WS_FAILED_AT_BACKUP_COMPLETE]. Error code: [0x800423f3].
Regards
Aghil
↧
Windows Backup fail after update
Hi all, need your kind help.
OS is Windows Server 2012 R2 Standard 6.3.9600 Build 9600, after online windows update, the windows server backup function cannot work.
- When open window backup UI, got error message as below:
There are too few disks on this computer or one or more of the disks is too small...
- When using wbadmin command, got error message as below:
A fatal error occured during a Windows Server Backup snap-in(Wbadmin.msc) operation...
Aready tried below but still not work.
Remove/backup the log files: C:\Windows\Logs\WindowsServerBackup
Uninstall the feature: “windows backup server”
Restart the Server
Restart again for good measure
Install the feature: “windows backup server”
↧
↧
System image restore failed with error: 0x807800B8
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
↧
Windows server 2008 (incorrectly) applying drive letter to windows server backup drive.
Typically, When Windows server backup drive is formatted, it is formatted in such a way where it is hidden from explorer (and subsequently ransomware) but can be seen in Drive Management.
This has been the behavior of all the systems I use MS server backup on which are many.
However, I have one problem child windows server 2008 std system that doggedly applies Z: drive letter to the usb backup drive.
Can I turn this off? I have two drives I swap in daily and while I can remove the drive letter it is reapplied as soon as I plug the other drive in.
↧
System image restore failed with error: 0x807800B8
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
↧
More Pages to Explore .....
