Another test i did, was to create the vss-snapshot manually on the
windows-host and then copy the data from the manually created
vss-snapshot-directory C:\TEST\C:
create-snapshot.ps1
$vss = [WMICLASS]"root\cimv2:win32_shadowcopy"
$vsssnapshot = $vss.Create('C:\', "ClientAccessible")
$vssshadow = Get-WmiObject Win32_ShadowCopy | Where-Object { $_.ID -eq
$vsssnapshot.ShadowID }
$vssshadowpath = $vssshadow.DeviceObject + "\"
$vsssnapshotid = "$vssshadow".Split('=')[1];
$vsssnapshotpath = "C:\TEST\C"
New-Item -ItemType Directory -Force -Path $(Split-Path $vsssnapshotpath
-Parent) | Out-Null
cmd /c mklink /J $vsssnapshotpath $vssshadowpath | Out-Null
Write-Output "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss") DEBUG:VSS ID:
$vsssnapshotid"
Write-Output "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss") DEBUG:VSS
Mountpoint: $vsssnapshotpath successfully mounted"
job.conf
...
ClientRunBeforeJob = "powershell.exe -noprofile -executionpolicy bypass
-file C:/scripts/create-snapshot.ps1"
...
The job runs without any errors or warnings. All files were able to be
backupped. One more thing i noticed:
Bareos creates a snapshot will following attributes: vssadmin list shadows
...
Typ: Backup
Attribute: Differential, Auto recovered
...
while the manually created snapshot contains following attributes:
...
Typ: ClientAccessible
Attribute: Persistent, Client-accessible, No auto release, No writers,
Differential
...
Any input is welcome
Best,
Timo
Vorname Nachname schrieb am Mittwoch, 9. Februar 2022 um 14:56:02 UTC+1:
>
> I've also tested the same with another program called restic. With restic
> iam able to backup the data from the vss-snapshot.
> I also tried to run the bareos-fd as different user (local-administrator)
>
> Any ideas?
>
> Best,
> Timo
> Vorname Nachname schrieb am Montag, 7. Februar 2022 um 08:20:01 UTC+1:
>
>> Hello,
>>
>> iam struggeling setting up the VSS-Support. Keep telling me, that the
>> file is used by another process.
>>
>> Fileset:
>> ```bash
>> FileSet {
>> Name = "client01-FileSet-2"
>> Enable VSS = yes
>> Include {
>> Options {
>> Signature = MD5
>> Drive Type = fixed
>> IgnoreCase = yes
>> WildFile = "[A-Z]:/hiberfil.sys"
>> WildFile = "[A-Z]:/pagefile.sys"
>> WildFile = "[A-Z]:/swapfile.sys"
>> WildDir = "[A-Z]:/RECYCLER"
>> WildDir = "[A-Z]:/$RECYCLE.BIN"
>> WildDir = "[A-Z]:/System Volume Information"
>> Exclude = yes
>> }
>> File = "C:/Users/User/NTUSER.dat"
>> File = "C:/ProgramData/Veeam/EndpointData"
>> }
>> }
>> ```
>>
>> Log:
>> ```bash
>> ...
>> 07-Feb 08:16 bareos-dir JobId 93: Start Backup JobId 93,
>> Job=client01-Job.2022-02-07_08.16.56_00
>> 07-Feb 08:16 bareos-dir JobId 93: Connected Storage daemon at
>> xxxxxxxxx.de:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
>> 07-Feb 08:16 bareos-dir JobId 93: Using Device "S3_ObjectStorage" to
>> write.
>> 07-Feb 08:16 bareos-dir JobId 93: Probing client protocol... (result will
>> be saved until config reload)
>> 07-Feb 08:16 bareos-dir JobId 93: Using Client Initiated Connection
>> (client01).
>> 07-Feb 08:16 bareos-dir JobId 93: Handshake: Immediate TLS
>> 07-Feb 08:16 bareos-sd JobId 93: Volume "client01-full-0013" previously
>> written, moving to end of data.
>> 07-Feb 08:17 bareos-sd JobId 93: Ready to append to end of Volume
>> "client01-full-0013" size=593072728
>> 07-Feb 08:16 client01 JobId 93: Created 27 wildcard excludes from
>> FilesNotToBackup Registry key
>> 07-Feb 08:16 client01 JobId 93: Connected Storage daemon at
>> xxxxxxxxx.de:9103, encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
>> 07-Feb 08:17 client01 JobId 93: Generate VSS snapshots. Driver="Win64
>> VSS", Drive(s)="C"
>> 07-Feb 08:17 client01 JobId 93: VolumeMountpoints are not processed as
>> onefs = yes.
>> 07-Feb 08:17 client01 JobId 93: Cannot open
>> "C:/Users/User/NTUSER.dat": ERR=The process cannot access the file because
>> it is being used by another process.
>> 07-Feb 08:17 client01 JobId 93: Cannot open
>> "C:/ProgramData/Veeam/EndpointData/VeeamBackup.mdf": ERR=The process cannot
>> access the file because it is being used by another process.
>> 07-Feb 08:17 client01 JobId 93: Cannot open
>> "C:/ProgramData/Veeam/EndpointData/VeeamBackup_log.ldf": ERR=The process
>> cannot access the file because it is being used by another process.
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Task
>> Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "VSS
>> Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Performance
>> Counters Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "System
>> Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete):
>> "SqlServerWriter", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "MSSearch
>> Service Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "WMI
>> Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "ASR
>> Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "BITS
>> Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Registry
>> Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "Shadow Copy
>> Optimization Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 client01 JobId 93: VSS Writer (BackupComplete): "COM+ REGDB
>> Writer", State: 0x1 (VSS_WS_STABLE)
>> 07-Feb 08:17 bareos-sd JobId 93: Releasing device "S3_ObjectStorage" (S3).
>> 07-Feb 08:17 bareos-sd JobId 93: Elapsed time=00:00:16, Transfer rate=186
>> Bytes/second
>> 07-Feb 08:17 bareos-dir JobId 93: Insert of attributes batch table with 4
>> entries start
>> 07-Feb 08:17 bareos-dir JobId 93: Insert of attributes batch table done
>> ...
>> ```
>>
>> Any suggestions?
>>
>> Best,
>> Timo
>>
>
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/921edf50-d09e-45a0-b175-1377fb1febb1n%40googlegroups.com.
