Stefan, Make sure your VMCTL data is on a diskpool. TSM needs the metadata for backups and restores. Next, I have found after extensive testing (and a PMR with IBM) that the transport method NBD is much quiker than hotadd for restore. If you have a physical data mover, you can use SAN as transport method, but I have not been able to test the restore performance of that method. If have created a seperate data mover node (and cad) for restores only with:
VMVSTORTRANSPORT nbd in the opt file. Furthermore, I recommend to read VMware's VDDK programming guide to fully understand the underlying infrastructure at: https://www.vmware.com/support/developer/vddk/ >From this guide on page 82: *Best Practices for SAN Transport* For array-based storage, SAN transport is often the best performing choice for backups when running on a physical proxy. It is disabled inside virtual machines, so use SCSI HotAdd instead on a virtual proxy. SAN transport is not always the best choice for restores. It offers the best performance on thick disks, but the worst performance on thin disks, because of round trips through the disk manager APIs, AllocateBlock and ClearLazyZero. For thin disk restore, NBDSSL is usually faster, and NBD is even faster. Changed Block Tracking (CBT) must be disabled for SANrestores. Also, SAN transport does not support writing to redo logs (snapshots or child disks), only to base disks. 2014-04-26 8:23 GMT+02:00 TSM <t...@profi-ag.de>: > Hello, > > our restore performance (restore vm) is very poor. We see this > on custom installations and also in some test areas. > > Environment: TSMVE 7.1 / 7.1.0.1, tsm ba client 7.1.0 and 7.1.0.2 > TSM-Server 6.3.4 and also 7.1 > > rate restore only 8 MB/s, backups are much faster 50 to 100 MB/s > > > Should we use the integrated ba client in the tsmve installation software? > > with best regards > Stefan Savoric > -- Kind Regards, Groetje, Marcel Anthonijsz T: +31(0)299-776768 M:+31(0)6-53421341
