On Wed, Jan 02, 2008 at 09:54:57AM -0500, Dan Langille wrote:
> > 
> > slower at 12MB/s but still tolerable. the last started on christmas day, 
> > birch:
> > 
> >   Job:                    birch.2007-12-25_16.47.08
> >   Backup Level:           Full
> >   Client:                 "molbio-fd" 2.2.6 (10Nov07) 
> > x86_64-unknown-linux-gnu,redhat,
> >   FileSet:                "Birch Set" 2007-12-22 09:56:56
> >   Pool:                   "Full" (From Job resource)
> >   Storage:                "LTO4" (From Job resource)
> >   Scheduled time:         25-Dec-2007 16:47:11
> >   Start time:             25-Dec-2007 16:47:25
> >   End time:               31-Dec-2007 23:09:01
> >   Elapsed time:           6 days 6 hours 21 mins 36 secs
> >   Priority:               10
> >   FD Files Written:       16,679,881
> >   SD Files Written:       16,679,881
> >   FD Bytes Written:       1,105,891,427,122 (1.105 TB)
> >   SD Bytes Written:       1,108,951,797,447 (1.108 TB)
> >   Rate:                   2043.0 KB/s
> >   Software Compression:   None
> >   VSS:                    no
> >   Encryption:             no
> >   Volume name(s):         000299L4
> >   Volume Session Id:      5
> >   Volume Session Time:    1198587778
> >   Last Volume Bytes:      1,504,677,113,856 (1.504 TB)
> >   Non-fatal FD errors:    0
> >   SD Errors:              0
> >   FD termination status:  OK
> >   SD termination status:  OK
> >   Termination:            Backup OK
> > 
> > not acceptable at 2MB/s. i cannot find any real difference in the network 
> > config or nfs mount
> > config on these filesystms. i suspect it has to do with the nature of the 
> > filesystems. masspec
> > has less than a millon files, aspen has around 8 million files and birch 
> > has nearly 17 million.
> > 
> > has anyone had similar experience working with nfs backups of this nature? 
> > anything i can do
> > to improve performance to get the filer backed up in a reasonable time 
> > window?
> 
> With the purpose of gathering facts: are these results repeatable?
>

hmmm ....

these are the only complete level 0's i've taken for these filers. i made an 
attempt at birch
a few days earlier and cancelled it because of the slowness:

  Build OS:               x86_64-unknown-linux-gnu redhat
  JobId:                  71
  Job:                    birch.2007-12-22_09.56.36
  Backup Level:           Full
  Client:                 "molbio-fd" 2.2.6 (10Nov07) 
x86_64-unknown-linux-gnu,redhat,
  FileSet:                "Birch Set" 2007-12-22 09:56:56
  Pool:                   "Full" (From Job resource)
  Storage:                "LTO4" (From Job resource)
  Scheduled time:         22-Dec-2007 09:56:44
  Start time:             22-Dec-2007 09:56:58
  End time:               25-Dec-2007 07:05:52
  Elapsed time:           2 days 21 hours 8 mins 54 secs
  Priority:               10
  FD Files Written:       6,206,323
  SD Files Written:       6,206,323
  FD Bytes Written:       444,458,726,167 (444.4 GB)
  SD Bytes Written:       445,477,079,297 (445.4 GB)
  Rate:                   1785.4 KB/s
  Software Compression:   None
  VSS:                    no
  Encryption:             no
  Volume name(s):         002042L4|000299L4
  Volume Session Id:      24
  Volume Session Time:    1198028560
  Last Volume Bytes:      305,032,863,744 (305.0 GB)
  Non-fatal FD errors:    0
  SD Errors:              0
  FD termination status:  Canceled
  SD termination status:  Canceled
  Termination:            Backup Canceled

i cancelled the job, checked networking, restarted postgres and bacula. then 
restarted the backup.

-- michael 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to