Migrating from Arcserve to Veeam

[buckrogers82]

Sorry if this comes off the wrong way I'm trying to learn as much as I can in the shortest amount of time, but it seems we will be migrating our backup software from Arcserve to Veeam.
My questions are:

How do I use my LTO's with Veeam backups?
Can I use bar-codes for inventory processes?
If i'm doing snapshots of servers wouldn't this greatly increase my tape count?
How do I prune my data that has hit our retention period?

Thanks for any assistance you can give me.

[veremin]

First of all, please be aware that not until version 7 is released, will the tapes be fully supported.

How do I use my LTO's with Veeam backups?

The tape library should be attached to VB&R management server. So, VB&R server should be physical. As to support of particular appliances, all the tape devices that are visible inside Guest OS will be supported.

Can I use bar-codes for inventory processes?

The bar codes also will be recognized by VB&R without any issues.

If i'm doing snapshots of servers wouldn't this greatly increase my tape count?

Could you elaborate on it a little bit, since it’s not that clear what you’re talking about?

How do I prune my data that has hit our retention period?

Retention policy will handle the process of deleting obsolete data.

Thanks.

[buckrogers82]

Thanks for the responses! To elaborate a bit more on what I was asking it was primarily about vm servers. If i'm doing snapshots of servers (veeam) rather than file level backups (arcserve) wouldn't the level of data be increased? Since I am essentially backing up a full .vmdk?

[dellock6]

No because you do not save full backups everyday. After the first full backup you can run incremental jobs, leveraging savings both at the backup job level (Veeam proprietary compression and deduplication) and both at the vSphere level using CBT.

Luca.

[veremin]

Yep, Luca is completely right here. After initial full backup, subsequent runs are incremental ones, so to say, only blocks that are known to have changed since the latest run are being backed up. In order to achieve it Veeam utilizes VMware CBT; if the latter doesn’t work for some reason VB&R puts into use its proprietary mechanism.

More information regarding can be found in the corresponding User Guide (p.34).

Thanks.