On Wednesday, May 18, 2016 at 3:58:12 PM UTC-5, [email protected] wrote: > I'm sure I'm not doing this properly, but I cannot figure out what the issue > is. I'm new to bareos, and trying to get a backup of a windows system. > Everything works fine on Linux, and I can backup multiple linux boxes. > > I have the following definition: > > FileSet { > Name = "Windows D: Drive" > Enable VSS = yes > Include { > Options { > Signature = MD5 > Drive Type = Fixed > Ignore Case = Yes > #WildFile = "[A-Z]:/pagefile.sys" > #WildDir = "[A-Z]:/RECYCLER" > #WildDir = "[A-Z]:/$RECYCLE.BIN" > #WildDir = "[A-Z]:/System Volume Information" > #Exclude = yes > } > File = D:/ > } > } > > > Everytime I run this against a client, it says it completes, but it backs up > nothing. I have tried using the default "Windows All Drives" fileset, the > only difference being it has a "File = /" instead of File = D:/, and it will > backup all the drives on the system without issue. > > Hopefully someone can point me in the right direction. From the docs, it > looks like what I am doing is correct, but it sure isn't working.
I gave that a try, and doesn't seem to be any different. Here's the messages I get: 18-May 17:04 usw1backup01-dir JobId 2: No prior Full backup Job record found. 18-May 17:04 usw1backup01-dir JobId 2: No prior or suitable Full backup found in catalog. Doing FULL backup. 18-May 17:04 usw1backup01-dir JobId 2: Start Backup JobId 2, Job=usw1data006-D.2016-05-18_17.04.19_04 18-May 17:04 usw1backup01-dir JobId 2: Using Device "FileStorage" to write. 18-May 17:04 usw1backup01-sd JobId 2: Volume "Full-0001" previously written, moving to end of data. 18-May 17:04 usw1backup01-sd JobId 2: Ready to append to end of Volume "Full-0001" size=1142 18-May 17:04 usw1data006-fd JobId 2: Created 24 wildcard excludes from FilesNotToBackup Registry key 18-May 17:04 usw1data006-fd JobId 2: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="D" 18-May 17:04 usw1data006-fd JobId 2: VolumeMountpoints are not processed as onefs = yes. 18-May 17:04 usw1data006-fd JobId 2: Top level directory "d:/" has an unlisted drive type "fixed" 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "IIS Config Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "IIS Metabase Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1data006-fd JobId 2: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) 18-May 17:04 usw1backup01-sd JobId 2: Elapsed time=00:00:14, Transfer rate=35 Bytes/second 18-May 17:04 usw1backup01-dir JobId 2: Bareos usw1backup01-dir 15.2.2 (16Nov15): Build OS: x86_64-redhat-linux-gnu redhat CentOS Linux release 7.0.1406 (Core) JobId: 2 Job: usw1data006-D.2016-05-18_17.04.19_04 Backup Level: Full (upgraded from Incremental) Client: "usw1data006-fd" 15.2.2 (16Nov15) Microsoft Windows Server 2012 Standard Edition (build 9200), 64-bit,Cross-compile,Win64 FileSet: "Windows D: Drive" 2016-05-18 17:04:19 Pool: "Full" (From Job FullPool override) Catalog: "MyCatalog" (From Client resource) Storage: "File" (From Job resource) Scheduled time: 18-May-2016 17:04:18 Start time: 18-May-2016 17:04:22 End time: 18-May-2016 17:04:36 Elapsed time: 14 secs Priority: 10 FD Files Written: 1 SD Files Written: 1 FD Bytes Written: 0 (0 B) SD Bytes Written: 498 (498 B) Rate: 0.0 KB/s Software Compression: None VSS: yes Encryption: no Accurate: no Volume name(s): Full-0001 Volume Session Id: 2 Volume Session Time: 1463604657 Last Volume Bytes: 2,078 (2.078 KB) Non-fatal FD errors: 0 SD Errors: 0 FD termination status: OK SD termination status: OK Termination: Backup OK 18-May 17:04 usw1backup01-dir JobId 2: Begin pruning Jobs older than 6 months . 18-May 17:04 usw1backup01-dir JobId 2: No Jobs found to prune. 18-May 17:04 usw1backup01-dir JobId 2: Begin pruning Files. 18-May 17:04 usw1backup01-dir JobId 2: No Files found to prune. 18-May 17:04 usw1backup01-dir JobId 2: End auto prune. Now I know that there is data on that drive, actually about 200GB on it. Any idea why it would just completely ignore the data on the drive? I changed the fileset to be a lowercase d:/ and it did the exact same thing. -- 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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
