[bareos-users] Backup Windows 10 Client

[Stefan Harbich]

Hi,

why do I get the following warnings:

nmanwwme01-fd JobId 1133: Cannot open "C:/Program Files (x86)/TotalAV/SAVAPI/names_cache/AV-malware-names-3820-lBjTYO": ERR=Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

Although I have activated VSS?

nmanwwme01-fd JobId 1133: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"

My "Windows All Drives.conf"

FileSet {
Name = "Windows All Drives"
Enable VSS = yes
Include {
Options {
Signature = MD5
Drive Type = fixed
IgnoreCase = yes
Portable = yes
WildFile = "[A-Z]:/pagefile.sys"
WildFile = "[A-Z]:/hiberfil.sys"
WildDir = "[A-Z]:/RECYCLER"
WildDir = "[A-Z]:/$RECYCLE.BIN"
WildDir = "[A-Z]:/System Volume Information"
Exclude = yes
}
File = "C:/"
}
}

Greetings from Stefan Harbich

[Dakota Pilot]

This post might be inappropriate. Click to display it.

[Stefan Harbich]

Hello Dokata Pilot,

If I change the following in my file "Windows All Drives.conf" my backup aborts.

FileSet {
...
AutoExclude = yes
...

If I exclude all files and directories that are reported during the backup with the following warning message: "ERR = The process can not access the file because it is being used by another process." or "ERR = access denied" and then I make a complete restore Windows 10 does not start properly. On average, 50 to 200 files are reported that can not be backed up. Is synonymous but strongly dependent on what is being done on the computer. I always thought VSS is responsible for taking a good look at used files and then backing up the image? That does not seem to be the case. Unfortunately, this backup solution does not help me at all in the Wondows environment. Thus, a full restore in the disaster recovery environment of Windows is not possible.

Greetings from Stefan Harbich

[Stefan Harbich]

This post might be inappropriate. Click to display it.

[Stefan Harbich]

Hello my dears,
Unfortunately, I have to say that bareos does not properly secure a Windows 10 client. Although the VSS = yes option is enabled. Among other things, the following important Windows files are not backed up:

SAM, NTUSER.DAT, ...
(Excluding files is not an option because they are needed for recovery).

The following error message always appears:
nmanwwme01-fd JobId 1199: Can not open "C: / Windows / System32 / config / SAM": ERR = The process can not access the file because it is being used by another process.

I secure the system directory with the Windows VSS possibilities everything works without problems.

I suspect that the following driver is not working properly:

nmanwwme01-fd JobId 1199: Generate VSS snapshots. Driver = "Win64 VSS", Drive (s) = "C"

For me, the backup solution Bareos is not useful because we have a mixed (Unix, Linux Win) environment in our company.

Greetings from Stefan Harbich

[Dakota Pilot]

Not sure what to say. My Win10 machine is backed up including the NTUser files for the users. Not sure it will help but attached is my file for backing up a Windows 10 box. I ran a list files jobid= and checked the files existed in the backup. I used the command line on the server to do this command and then searched in less for NTUser.

echo "list files jobid=xxx" | bconsole | less

since the WebUI is pretty much useless for listing files since it throws an error about too many files.

I assume the Win10 box is updated to the latest patches, etc.?