• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

VM Incremental Forever Backup for TSM?

Spree

ADSM.ORG Member
#1
On VM backup, I may not be too familiar with TSM and Veeam and some other backup software so I'm looking for some advice.

I am currently configuring a TSM server for internal use, one of the purposes is to take care of the VM farm.

To my limited knowledge Veeam should be able to consolidate backups automatically, but I am not sure about the case of TSM, for example:
Is it OK for me to take a forever incremental approach? I mean, if I can't keep the whole backup chain due to capacity problems, for example I only keep 3 versions of backups, when TSM purges old backups, is the backup chain still valid? If yes, does that mean TSM can consolidate backups automatically? Or if not, that means I still need a periodic full? Is there any article on how TSM and VMware forever incremental backups?

Please advise, thanks.
 

marclant

ADSM.ORG Moderator
#2
If you keep 3 versions, you can restore all 3 versions.

Every time you do an incremental backup (the first one is incremental too, it just happens to backup everything because nothing was previously backed up). Internally, Spectrum Protect keeps track of all the data blocks that are part of that version.

The next incremental backup, many of the data blocks in the first backup are not changed, so those are cataloged as also belonging to the 2nd backup, as well as the new data blocks that were changed since the last. And so-on for each subsequent backups.

When you add a 4th version, you lose the 1st one. However, the 2nd, 3rd, and 4th version included data blocks that were initially backed up by the first backup. Those are still kept because they are still needed by 2, 3, and 4.

There's no need for a consolidation process, things are tracked automatically as backups happen.

More info: https://www.ibm.com/support/knowled....ibm.itsm.ve.doc/c_ve_backup_incrforever.html
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 16 18.8%
  • Keep using TSM for Spectrum Protect.

    Votes: 52 61.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.8%
  • Other (please comement)

    Votes: 7 8.2%

Forum statistics

Threads
31,448
Messages
133,971
Members
21,548
Latest member
cburns
Top