Veeam was designed as a backup product(not archive). The way Veeam
historically recommended longer-term tape backups (which still works and still
criticized) is for you to use TSM (or any product that supports tape properly)
to archive the data from the Veeam repository. The image files are dated and
identifiable (full backups vs incrementals, etc).
A restore would be a 2 step process of first retrieving from the TSM archive
then restoring from Veeam.
The idea is that you would run a TSM archive job on the Veeam repository and
look for all *vbk files or whatever pattern you wanted to keep.
The new version of Veeam does support basic library control, but there is no
vault tracking or anything like that.
Regards,
Shawn
________________________________
Shawn Drew
> -----Original Message-----
> From: ADSM-L AT VM.MARIST DOT EDU [mailto:ADSM-L AT VM.MARIST DOT EDU]
> Sent: Monday, April 28, 2014 11:13 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] tsm tcp for vm versus veeam
>
> No, Veeam is not able to store backups within TSM Server. Veeam and TSM
> are totally independent. Veeam is capable to use tape drives to store
> backup data, but we are not using tapes. Veeam supports data encryption
> and compression for data repositories on disks under Windows. In
> addition, it is compatible with Windows 2012 drive deduplication. We are
> using four Veeam repositories on Windows 2012 R2 VMs running on VMware
> hosts directly connected to not expensive SAN disk subsystem. Each
> repository has 2TB de-duplicated Windows 2012 drive (de-duplication rate
> 60-80%).
>
> 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 11:47 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] tsm tcp for vm versus veeam
>
> So your Veeam backups don't end up within TSM but are stored and
> replicated totally within the Veeam environment.
> Isnt Veaam capable of storing the backed up objects within TSM itself?
>
> Tim
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Grigori Solonovitch
> Sent: Monday, 28 April, 2014 2:11 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] tsm tcp for vm versus veeam
>
> 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.
>
>
> ________________________________
>
> 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.
This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
|
