Hi Heitor,

Great! See the job log below. It's the last incremental job log, but it gives a good indication anyway (the actual Dir, Fd and Sd entries redacted).

Best regards,

Peter

28-Feb 23:05 MyDir JobId 1015: Start Backup JobId 1015, Job=Server2017.2019-02-28_23.05.00_03
28-Feb 23:05 MyDir JobId 1015: Using Device "ULT-0" to write.
28-Feb 23:05 MySd JobId 1015: Spooling data ...
28-Feb 23:06 Srv201701Fd JobId 1015: Generate VSS snapshots. Driver="Win64 VSS"
28-Feb 23:06 Srv201701Fd JobId 1015:     Snapshot mount point: C:\
28-Feb 23:19 Srv201701Fd JobId 1015:      Could not stat "C:/Users/Administrator.MYDOM/AppData/Local/Microsoft/Windows/INetCache/Low/Content.IE5": ERR=System cannot find the path.

28-Feb 23:20 Srv201701Fd JobId 1015:      Could not stat "C:/Users/jojo/AppData/Local/Microsoft/Windows/INetCache/Low/Content.IE5": ERR=System cannot find the path.

28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "FSRM Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "WIDWriter", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "Microsoft Hyper-V VSS Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "NPS VSS Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 Srv201701Fd JobId 1015: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) 28-Feb 23:24 MySd JobId 1015: Committing spooled data to Volume "F01028L5". Despooling 2,218,489,341 bytes ... 28-Feb 23:25 MySd JobId 1015: Despooling elapsed time = 00:00:38, Transfer rate = 58.38 M Bytes/second 28-Feb 23:25 MySd JobId 1015: Elapsed time=00:19:14, Transfer rate=1.920 M Bytes/second 28-Feb 23:25 MySd JobId 1015: Sending spooled attrs to the Director. Despooling 2,564,116 bytes ...
28-Feb 23:25 MyDir JobId 1015: Bacula MyDir 9.0.6 (20Nov17):
  Build OS:               x86_64-redhat-linux-gnu redhat (Core)
  JobId:                  1015
  Job:                    Server2017.2019-02-28_23.05.00_03
  Backup Level:           Incremental, since=2019-02-27 23:06:26
  Client:                 "Srv201701Fd" 7.4.4 (28Sep16) Microsoft Standard Edition (build 9200), 64-bit,Cross-compile,Win64
  FileSet:                "Server2017Set" 2018-02-01 21:34:30
  Pool:                   "Default" (From Job resource)
  Catalog:                "MyCatalog" (From Client resource)
  Storage:                "MySd" (From Pool resource)
  Scheduled time:         28-Feb-2019 23:05:00
  Start time:             28-Feb-2019 23:05:58
  End time:               28-Feb-2019 23:25:24
  Elapsed time:           19 mins 26 secs
  Priority:               10
  FD Files Written:       9,141
  SD Files Written:       9,141
  FD Bytes Written:       2,214,193,994 (2.214 GB)
  SD Bytes Written:       2,216,237,073 (2.216 GB)
  Rate:                   1899.0 KB/s
  Software Compression:   None
  Comm Line Compression:  None
  Snapshot/VSS:           yes
  Encryption:             no
  Accurate:               no
  Volume name(s):         F01028L5
  Volume Session Id:      2
  Volume Session Time:    1551386754
  Last Volume Bytes:      113,804,070,912 (113.8 GB)
  Non-fatal FD errors:    2
  SD Errors:              0
  FD termination status:  OK
  SD termination status:  OK
  Termination:            Backup OK -- with warnings


On 01.03.2019 13:21, Heitor Faria wrote:
Hello Peter,

Time for VSS generation is included and sometimes can be very slow.
I recommend you to post your job log.

Regards,

Sent from TypeApp <http://www.typeapp.com/r?b=14554>
On Mar 1, 2019, at 3:21 AM, Peter Milesson <mi...@atmos.eu <mailto:mi...@atmos.eu>> wrote:

    Hi Sergio,

    You are right about the file sets. The Windows file set is about a
    quarter the size, compared to the Linux one. There are no database
    backups, just files. Neither have I seen any network bottlenecks. Both
    servers are connected to the same switch, with a 10GbE trunk directly to
    the backup server. And the backup jobs are scheduled at different times,
    so there should not be any network bottlenecks with competition for
    bandwidth. The Windows server is using NTFS, whereas the Linux server
    uses the ext4 file system.

    I haven't got a clue if the the time it takes for creating the VSS
    snapshots is included in the total time, or if the time it takes is
    significant. I guess somebody with knowledge about the inner workings of
    Bacula FD could answer that question.

    Best regards,

    Peter


    On 01.03.2019 8:35, Sergio Gelato wrote:

        * Peter Milesson [2019-02-28 20:22:41 +0100]:

            I'm backing up 2 servers with Bacula, one with Windows
            2016, the other one with CentOS. The hardware is described
            below. The Windows server is much more powerful than the
            Linux server in all respects, and should theoretically
            deliver data to the Bacula server at a much higher rate.
            But in reality, the Linux server delivers data about 7
            times faster over the network, than the Windows server. Is
            this completely normal, or should I start to check up the
Windows server for problems?
        You didn't provide enough information. Are the filesets being
        backed up comparable? (I mean in terms of number and size of
        files and fraction of the filesystem being backed up.) It
        looks like both backups take nearly the same wallclock time
        but end up with vastly different transfer rates, so I'm
        guessing that the Windows backup job is a lot smaller. In
        fact, the wallclock times are so close that I wonder if they
        aren't dominated by some kind of fixed setup cost (slow
        database? network timeout issues?) With a storage throughput
        of only 60 MB/s on the SD the difference in network speeds
        (1Gb/s vs. 10Gb/s) is not going to be significant. You also
        didn't mention the filesystems involved. NTFS on Windows and
        one of the usual suspects (ext4, xfs, btrfs) on Linux? For
        backup jobs involving lots of small files filesystem overhead
        is likely to make a difference. How long does VSS snapshot
        creation take on the Windows side, by the way? Is that
        overhead included in the average transfer rate calculation? I
        suppose you meant TB instead of GB for the hard disk capacities.

            Best regards, Peter Windows server (file server,
            RDP-server, Hyper-V host with 2 very lightly loaded VMs)
            
------------------------------------------------------------------------
            Hardware: HP DL180 Gen9, Intel Xeon E5-2683v4, 48GB RAM,
            Smart Array P440 Controller, 6x SAS 1GB (7200 rpm, 12
            Gb/s) in RAID5 Network: 2x 10GbE to HPE 1950 switch (LACP)
            OS: Windows 2016 (build 1607) Throughput to Bacula server:
            23-Feb 08:52 MySd JobId 991: Elapsed time=00:26:09,
            Transfer rate=4.071 M Bytes/second Linux server (plain
            file server with Samba)
            
------------------------------------------------------------------------
            Hardware: HP DL120 Gen9, Intel Xeon E5-2603v3, 8GB RAM, HP
            Dynamic Smart Array B140i SATA Controller 2x SATA 2GB
            (7200 rpm) in RAID1 Network: 2x 1Gb to HPE 1950 switch
            (LACP) OS: CentOS Linux 7.5 (1804) Throughput to Bacula
            server: 23-Feb 08:26 MySd JobId 990: Elapsed
            time=00:26:08, Transfer rate=28.29 M Bytes/second Bacula
            server =========== Hardware: standard motherboard with a
            6-core AMD FX-6300 CPU, 4xSATA 8GB (7200 rpm) in RAID10
            Network: Tehuti 10GbE NIC to ProCurve 2910al switch OS:
            CentOS Linux 7.6 (1810) Bacula server throughput to the
            RAID array: ca. 60 Mbytes/second All switches are
            connected to our 10Gb/s optical network backbone.




    ------------------------------------------------------------------------

    Bacula-users mailing list
    Bacula-users@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/bacula-users


_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to