Am Montag, 4. September 2017 15:03:38 UTC+2 schrieb Doug Rand: > On 9/4/17 7:44 AM, [email protected] wrote: > > Hello, > > Hello > > > I have configured the backup system with the > > "Always-Incremental-Feature". I use the "Virtual-Full-Feature"to > > archive the data. > > > > It works perfectly! > > > > However, I would like to use the "Virtual-Full-Feature" to archive > > normal "Full-Backups". At the moment there is the problem that full > > backups which are larger than 1GB take too long to archive. > > > > A 2GB job took more than 5 hours before I quit the job. > > > > Measures I did were to tune the "mariadb" and benchmark the read and > > write speed of the different hard disks. > > > > After these changes and tests, the 2GB job took 1 hour to archive > > through "Virtual Full Feature". That's better, but still too slow. > > Unfortunately, some full backups have a size of up to 30GB. > > > > My questions would be.... How do you archive your backups for a > > longer time? Are there other options than archiving via VirtualFull? > > How can I make the data transfer from volume to volume faster? > > > > Some statistics... Server is in the cloud With a dualcore of the > > current generation And 8GB RAM Disk space is sufficient > > To what type of device are you writing the virtual full backups to? > Disk, tape, something else? > > I generally find that turning on spooling helps. Turn on "spool > attributes" to have Bareos write everything to your database at once at > the end of the job. Turn on "spool data" to have Bareos write the > output to a local disk and then flush to the output device. (The "spool > data" won't really help you if your final destination device is a local > disk.) > > The "server is in the cloud" part makes me curious, generally Bareos > doesn't care much about CPU performance but is all about I/O > performance. Since we don't know anything at all about your I/O setup it > is hard to provide advice.
The setup is as follows... The system is located in the Google Cloud platform. The "Backup-System" is equipped with an Intel Hashwel with 2 vCPUS and 7.5GB RAM. I have mounted 2 Google Cloud Storage Buckets for backups, with the help of fuse. I think performance should be about: Read IOPS per GB 0.75 Write IOPS per GB 1.5 Full backups are written on one bucket, with a VirtualFull backup the data should be transferred from the bucket to the second one. Therefore, I do not save the backups to the localdisk again. I will now try to configure the spool data. I hope this is the right information we need. -- 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.
