Good Morning All,
We have exchange data on an old TSM server that we are trying to decommission.
What I need to do is, export the exchange data that still exists on the old
TSM server to our new TSM server that was just built approximately 6 months
ago. So my question is, can I export the
Hello Ricky,
You can do an export node with a mergefilespace=yes option, but I've found
that to be problematic when replicating application data. You could
rename the node on the source server first, before exporting, then the
node will import with a different name and will not have any
Hello guys!
I opened PMR and traced the problem. There is already an APAR open for this
problem and thankfully it has already been fixed in the TSM 7.1.1.3 patch.
http://www-01.ibm.com/support/docview.wss?uid=swg1IT01824
Im currently running some test backups, but it looks very good. Just wanted
Hi Karel!
That doesn't sound very promising... I can't upgrade the storage agents because
5.5 is the highest level available for RHEL4...
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Hi,
I have had a v 6.2.4.0 sta from an Exchange farm that stopped doing lan
free backups after upgrade the tsm aerver and lib manager to v 6.3.4.x
while all others kept on running.
After logging a call with IBM got told I had to upgrade the failing sta to
the same level as the servers. Even
Hi to all
In TSM Version 7.1.1+ there is a new feature called SET REPLRECOVERDAMAGED
To use it need to be ON with the command: SET REPLRECOVERDAMAGED ON
Here the help below but don’t understand what is the default YES or NO ?
During a replicate node.
RECOVERDamaged--=--+-Yes--
Hi guys!
We have several RedHat 4.x LANfree clients (TSM StorageAgent 5.5.4.0 and
lin_tape 1.66), currently using a TSM 6.2.6 server for the mounts. Since 6.2
will be out of support very soon we need to upgrade to 7.1.
Is anybody successfully using the 5.5 Linux StorageAgent in combination with
