<lst_hoe02 <at> kwsoft.de> writes: > > One additional question: > > The backup the virtual full is based on is PKI encrypted and lz4 > compressed. For the virtual full i get the following summary: > > Build OS: x86_64-pc-linux-gnu ubuntu Ubuntu 12.04 LTS > JobId: 8991 > Job: VFULL-DIMENSIONS.2014-03-28_15.26.02_04 > Backup Level: Full > Client: "dimensions-fd" 13.2.2 (12Nov13) Microsoft > Windows XP Professional Service Pack 3 (build 2600),Cross-compile,Win32 > FileSet: "WIN32-C" 2012-10-05 20:35:00 > Pool: "DISASTER" (From Job Pool's NextPool resource) > Catalog: "MyCatalog" (From Client resource) > Storage: "Tape" (From Storage from Pool's NextPool resource) > Scheduled time: 28-Mär-2014 15:25:59 > Start time: 27-Mär-2014 19:15:01 > End time: 27-Mär-2014 19:15:32 > Elapsed time: 31 secs > Priority: 10 > FD Files Written: 27,647 > SD Files Written: 27,647 > FD Bytes Written: 3,079,321,192 (3.079 GB) > SD Bytes Written: 3,079,321,192 (3.079 GB) > Rate: 99332.9 KB/s > Software Compression: None > VSS: no > Encryption: no > Accurate: yes > Volume name(s): 000016L4 > Volume Session Id: 397 > Volume Session Time: 1394202015 > Last Volume Bytes: 3,082,141,696 (3.082 GB) > Non-fatal FD errors: 0 > SD Errors: 0 > FD termination status: > SD termination status: OK > Termination: Backup OK > > Does this mean that the data is decrypted/decompressed before going to > tape? I guess the summary is wrong because at least the PKI keys > needed shouldn't be available at dir/sd level, no? >
Nope the data doesn't get touched at all for this particular backup first the windows specific backup data is saved, then compressed and then encrypted before being send to the SD by the FD when a normal backup is done. This is stored a specific so called data stream on the backup media. A virtual backup does nothing more then what is normally done for a restore e.g. find out what backup streams belong to a backup and select those from the backup media and consolidate that data into a new backup. So it just copies the encrypted/compressed data without knowing anything about it. Things are normally first compressed and then encrypted as encrypted data doesn't compress to well. We do have some new features in master (and eventually 14.2.x when that gets stable.) which allows the SD to compress/decompress (or deflate/inflate) the data on the fly when reading or writing to/from a device in the SD but that won't do anything for encrypted data as that is kind of opaque for the system. Also in master is a patch that makes the summary of the virtual backups somewhat better e.g. now it still prints some counters for the number of files and data amount of the FD while the FD is never contacted in the case of a virtual full as its fully performed inside the SD. The data amounts printed are probably the amount of data that is contained in the actual backup e.g. the size of the encrypted and compressed data streams. (As we don't know the original size it doesn't print any compression statistics etc.) What you see now is the generic job summary which up until a year ago was always the same for each type of backup things have changes quite a bit in the meantime, where ever it makes sense we now print only the job data that makes sense for a certain type of Job. -- Marco van Wieringen [email protected] Bareos GmbH & Co. KG Phone: +49-221-63069389 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- 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.
