Zitat von Philipp Storz <[email protected]>:

Hello Andreas,

During virtualfull, all previous backups are consolidated which means that we have to copy the blocks from the previous backups but we only write the blocks that we still need. So more data is read than written. Also, if you are writing parallel jobs to your disks, the blocks of different jobs are intermixed, and have to be sorted out during the virtual backup.

If your drive is not getting its minimum write speed, you should think about configuring spooling.

best regards,

Philipp


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?


Regards

Andreas


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to