Been there seen that.
I assume you are doing the export from TSM 5.5 with fromdate/todate to pick up
the data since the DB backup?
Turns out fromdate/todate on an export is honored for files, but not honored
for directories.
So when I tried this at a customer, it included kabillions of directory
objects, because directories were being bound to a management class going back
6 months. So you get a lot of objects exported, but only a few GB per hour.
To test, try running the export on just a node that has TDP data. If that runs
a lot faster, that's an indicator you have the directory problem.
With a customer I did that had long retentions, we let the export run a couple
of days but found we could never gain ground on the daily backups.
Ultimately I gave up trying this for customers that had more than 14 day
retention. Couldn't find a workaround, it's WAD.
After that I told customers when doing a hybrid migration to just export the
API clients;
Rely on TSM incrementals on the new server to pick up most of the changed files
with incremental backups;
Leave the old server intact for a while in case they needed a restore from
something that got backed up in the gap.
Best I could come up with.
W
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Loon, EJ van - SPLXM
Sent: Thursday, November 14, 2013 5:00 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Export server-to-server slooooooooooow
Hi guys!
We just completed our first server migration (hybrid method) from 5.5 to 6.2.
Everything went smoothly, but now I want to export the missing data (written to
the v5 server after the database backup) to the v6 server, but the export
process is running soooooooo sloooooooooooow!
Anybody know why this is? There is no load on the source server en plenty of
bandwith on the target server, but export is crawling (about 5 Gb/hour).
Thanks for any help in advance!
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
|
