Howdy,
I'm running bacula 2.0.2 dir, sd, fd on a Fedora 6 system using MySQL (on
the same server) backing up to a SATA 500GB hard drive. The bacula-dir.conf
is set to only allow 1 job to run at a time.
The full backup on it (100GB's or so compressed down to 49GB) took about 3
hours, which I would consider pretty decent.
The server and all clients are connected via Gigabit ethernet and Cat6
wires.
The full backup on my Windows XP 64 bit box, dual core AMD, started at 3 AM
this morning and is still running (I'd guess it has approx 100GB's to
backup). It's backed up approx 15 GB's in 6 hours.
* status client=winxp64-fd
Running Jobs:
JobId 3 Job winxp64.2007-02-28_03.05.01 is running.
VSS Backup Job started: 28-Feb-07 03:08
Files=47,674 Bytes=15,959,398,901 Bytes/sec=756,764
Files Examined=47,674
Processing file: C:/scripts/perl/enumerate.pl
SDReadSeqNo=5 fd=624
I read that as just over 1/2 a MB/s.
Now, if I do a tcpdump -i eth0 on my server, I only see bacula-sd activity
in bursts. Here's a sample of the output covering 3 minutes:
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
09:06:17.217834 IP winxp64.qotps > 192.168.2.100.bacula-sd: P
2493618154:2493619614(1460) ack 4049850142 win 65388
09:06:17.218992 IP 192.168.2.100.bacula-sd > winxp64.qotps: . ack 1460 win
65535
09:06:22.218142 arp who-has winxp64 tell 192.168.2.100
09:06:22.218214 arp reply winxp64 is-at 00:17:31:ce:54:67 (oui Unknown)
09:06:23.248976 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: P
3845934961:3845934966(5) ack 842975595 win 64428
09:06:23.332040 IP by1msg5276706.phx.gbl.msnp > winxp64.qip-login: P 1:9(8)
ack 5 win 64202
09:06:23.451931 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: . ack 9
win 64420
09:06:55.607110 IP winxp64.qotps > 192.168.2.100.bacula-sd: P
1460:2920(1460) ack 1 win 65388
09:06:55.607357 IP 192.168.2.100.bacula-sd > winxp64.qotps: . ack 2920 win
65535
09:07:00.606194 arp who-has winxp64 tell 192.168.2.100
09:07:00.606265 arp reply winxp64 is-at 00:17:31:ce:54:67 (oui Unknown)
09:07:04.325571 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: P 5:10(5)
ack 9 win 64420
09:07:04.410594 IP by1msg5276706.phx.gbl.msnp > winxp64.qip-login: P 9:17(8)
ack 10 win 64197
09:07:04.575481 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: . ack 17
win 64412
09:07:47.402215 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: P
10:15(5) ack 17 win 64412
09:07:47.486796 IP by1msg5276706.phx.gbl.msnp > winxp64.qip-login: P
17:25(8) ack 15 win 64192
09:07:47.667718 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: . ack 25
win 64404
09:07:52.485501 arp who-has winxp64 tell 192.168.2.100
09:07:52.485584 arp reply winxp64 is-at 00:17:31:ce:54:67 (oui Unknown)
09:08:12.385659 IP winxp64.qotps > 192.168.2.100.bacula-sd: P
2920:4380(1460) ack 1 win 65388
09:08:12.385873 IP 192.168.2.100.bacula-sd > winxp64.qotps: . ack 4380 win
65535
09:08:13.066907 IP 192.168.2.100.40273 > winxp64.bacula-fd: . ack 904760237
win 6432
09:08:13.066998 IP winxp64.bacula-fd > 192.168.2.100.40273: . ack 1 win
64514
09:08:13.588652 IP winxp64.bacula-fd > 192.168.2.100.40273: . 0:1(1) ack 1
win 64514
09:08:13.588723 IP 192.168.2.100.40273 > winxp64.bacula-fd: . ack 1 win 6432
09:08:28.494530 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: P
15:20(5) ack 25 win 64404
09:08:28.579103 IP by1msg5276706.phx.gbl.msnp > winxp64.qip-login: P
25:33(8) ack 20 win 64187
09:08:28.791337 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: . ack 33
win 64396
09:08:33.578210 arp who-has winxp64 tell 192.168.2.100
09:08:33.578276 arp reply winxp64 is-at 00:17:31:ce:54:67 (oui Unknown)
09:09:09.571163 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: P
20:25(5) ack 33 win 64396
09:09:09.653956 IP by1msg5276706.phx.gbl.msnp > winxp64.qip-login: P
33:41(8) ack 25 win 64182
09:09:09.805463 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: . ack 41
win 64388
09:09:14.652912 arp who-has winxp64 tell 192.168.2.100
09:09:14.652979 arp reply winxp64 is-at 00:17:31:ce:54:67 (oui Unknown)
09:09:54.647776 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: P
25:30(5) ack 41 win 64388
09:09:54.732949 IP by1msg5276706.phx.gbl.msnp > winxp64.qip-login: P
41:49(8) ack 30 win 64177
09:09:54.866375 IP winxp64.qip-login > by1msg5276706.phx.gbl.msnp: . ack 49
win 64380
I can't log into the XP system until later tonight to try shutting down
various running processes (Avast Antivirus, DiskKeeper defragger, etc...).
Has anyone with XP64bit SP2 experienced a similar scenario?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
