The proposed solution for this CTL data problem was to send the CTL data to a disk pool for quicker access. However, when you try to restore from your offsite copies at a DR site, TSM restores the CTL data and then a data block separately, leading to terrible restore times. (4Gb/hour). I've tried to copy the CTL data to a disk pool at the DR site, but it was still too slow. Maybe TSM for VE v6.4 is better? I haven't had a chance to try this yet.
On 1/8/2013 11:24 AM, Neil Schofield wrote: Incremental VM backups work less well. Under the covers, incremental backups involve a significant amount of restore processing by the client as it restores previously backed up CTL data. In the scenario above, we naively expected the process for restoring the CTL data to be the reverse of the backup process - ie the CTL data would be accessed over the LAN from the primary disk storage pool on the TSM servers. +---------------------------------------------------------------------- |This was sent by fswanep...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +----------------------------------------------------------------------
