Re: [ADSM-L] tsm tcp for vm versus veeam
2014-04-28 14:12:51
We are using Veeam Backup and Replication and Veeam ONE as a management
software for VMware itself and Veeam Backups for VMs. Perfect combination! I
would like to recommend to use Windows 2012 R2 as Veeam Repository servers with
native Windows deduplication for drives with backup data to reduce required
storage size.
By the way, most of the critical production VMs we are backing up using
traditional TSM backups used on source standalone servers before
virtualization. Yes, it is a little bit expensive solution, but combination
Veeam + TSM backups (without TDP for VM) is extremely reliable and I do not
think TDP for VM is less expensive. We are using only traditional TSM backups
for MS Clusters with RDMs, where Veeam is not working.
Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait,
www.ahliunited.com.kw
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: 28 04 2014 4:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] tsm tcp for vm versus veeam
We are looking to start using TSM TDP for VM for our VM backup strategy. Our VM
support staff has looked into using Veeam as an alternative. Does any have
opinions on which approach they would recommend.
Thanks,
Tim
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.
|
|
|