> Would it be possible to give main advantages and disadvantages for two > different ways of backup/restore for VMs: > 1) TSM + VCB based on "dsmc backup vm"; > 2) TSM + TBMR on each VM with direct backups to TSM Server.
> 1) using VCB you take off the load from the ESX server (VCB proxy sends the > data to TSM, ESX just creates the snapshot) I am sorry, but I do not understand, how it is possible take off load from ESX server. After creating snapshot you still need to read full image or some files and send to proxy. Almost the same is with normal TSM backups excluding load, created by TSM Client. Maybe I am wrong, but I really do not understand why? > 2) Using TMBR in each VM - question is why to do that. In virtualized > environments you do not need to think about dissimilar HW so TSM based image > backups can help you with DR (speaking of Windows world). > Running all VM backups concurrently can be very stressful to the ESX host. It depends on nature of applications (24/7 or just working hours) and it is a matter of correct scheduling to avoid overlapped backups for VMs. Grigori G. Solonovitch Senior Technical Architect Information Technology Ahli United Bank Kuwait http://www.ahliunited.com.kw Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: [email protected] Please consider the environment before printing this Email ________________________________ CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. Please consider the environment before printing this Email.
