Changes

From SME Server
Jump to navigationJump to search
3 bytes removed ,  02:07, 17 October 2007
m
Line 456: Line 456:  
==== Performance ====
 
==== Performance ====
   −
It is hardly to predict how much time a backup job needs to complete. It depends on the number of files, the total file size, the file changes since last run, the network speed and not least on the CPU power, disk speed and RAM of the source and backup server. The following table of measured values will give you an idea of what you can expect.
+
It is hard to predict how much time a backup job needs to complete. It depends on the number of files, the total file size, the file changes since last run, the network speed and not least on the CPU power, disk speed and RAM of the source and backup server. The following table of measured values will give you an idea of what you can expect.
 
        
 
        
 
{|  border="1" cellpadding="3" cellspacing=0
 
{|  border="1" cellpadding="3" cellspacing=0
Line 482: Line 482:     
'''Note:''' The last action of a job run is to remove the oldest backup, e.g. if archive scheduled.11 exists and you have set the scheduledKeep property to 12, then it must be deleted. This can take a significant long time, which increases the total job execution time.
 
'''Note:''' The last action of a job run is to remove the oldest backup, e.g. if archive scheduled.11 exists and you have set the scheduledKeep property to 12, then it must be deleted. This can take a significant long time, which increases the total job execution time.
      
==== Bug report ====
 
==== Bug report ====
95

edits

Navigation menu