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.
Hi
i am relatively new to tsm and would like to know how the process of adding a new datacenter node as well as a new datamover node works.
It depends, you haven't answered this question:So if i'm correct then i won't be able to set up 2 datacenters on a single server
There are many data movers - NDMP, VM, etc. Which one?
Sorry, don’t think secondary nodes will be the way to go. Works fine for client based backup, but not vmware. Problem is that both your nodes (daily and monthly) will update/reset vmware’s change block tracking (CBT). So every time you run the montly, it will find that CBT makes no sense, do a full backup, and then reset the CBT. Next day, when you run the daily, it will find that CBT has been reset, it will do a full backup, and reset the CBT again. If it all goes to the same storage pool, dedup will probably handle most of the extra data, so storage will not neccessarily be an issue, but the time to required to do two full backups every month is probably too time consuming.So if i'm correct then i won't be able to set up 2 datacenters on a single server, i am trying to configure daily incremental backups as well as monthly backups, i have found some help eluding to the fact that i would have to create a new datamover node as well as a new datacenter node.
Sorry, don’t think secondary nodes will be the way to go. Works fine for client based backup, but not vmware. Problem is that both your nodes (daily and monthly) will update/reset vmware’s change block tracking (CBT). So every time you run the montly, it will find that CBT makes no sense, do a full backup, and then reset the CBT. Next day, when you run the daily, it will find that CBT has been reset, it will do a full backup, and reset the CBT again. If it all goes to the same storage pool, dedup will probably handle most of the extra data, so storage will not neccessarily be an issue, but the time to required to do two full backups every month is probably too time consuming.
As far as I know, no one has come up with a way to handle this using TSM for VE in larger environments.
When using TSM baclient, you’re absolutely right, it is incremental forever. TDPs also contains various incremental options. In these instances TSM is keeping track of the changes. However, when TSM for VE is used, TSM relies on VMware’s CBT to find what data blocks have changed since the last backup. And if two different datacenter nodes are being used, there will be no valid CBT data when switching between the nodes.This where you are wrong.
TSM is not like any other backup software - the concept of doing weekly or monthly is simply not there. TSM runs incremental forever and nothing gets reset.
You have to make a paradigm shift when using TSM.
https://www.ibm.com/support/knowledgecenter/en/SSERB6_8.1.0/ve.user/r_techchg_ve.html
https://www.ibm.com/support/knowled....ibm.itsm.ve.doc/c_ve_backup_incrforever.html
Never been so happy to be proven wrong before! Thanks!It is possible to do daily incremental forever + monthly backups. Here's a technote that explains how: http://www-01.ibm.com/support/docview.wss?uid=swg21688752
That was not my intent. I only wanted to provide a possible solution.Never been so happy to be proven wrong before