Fromdate/Todate is actually your friend. Look at the backups you have for this server, and how far back they go. Try an export with FROMDATE/TODATE that specifies, say, Jan 1- Jan 5 (with merge=yes). See how long it runs. If it doesn't run too long, try more days in the interval the next time.
By doing that repetitively, you can get your exports down to something that doesn't run so long you have to cancel it. Rinse and repeat with additional date ranges until you've brought over everything you need. With merge =yes, what you get in the target filespace is whatever your mgmt. class specifies on the target server. If you bring over more versions than your target mgmt. class allows, they immediately roll off. If you accidentally run the same import twice, the imported backups replace existing ones, without forcing a version rolloff. (It works like you want it to). I've done this before and it works like a champ! W -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Zoltan Forray/AC/VCU Sent: Friday, February 25, 2011 2:00 PM To: [email protected] Subject: [ADSM-L] How does EXPORT MERGEFILESPACES really work Is there a document that explains the logic behind EXPORT NODE, in particular the MERGEFILESPACES option, when it comes to merging into existing filespaces and TDP data? How does it select what to export (active first? inactive?, FIFO? LIFO?) I am trying to move large nodes (>6TB each - 8-nodes to move) from an old 5.5 server to my newest 6.2.2.x server. Since the node daily backups (DOMINO TDP) can not be stopped while the move is going on, I can't move this much data within 24-hours (after running for 3-days, I killed it). So, I moved the definitions and starting clean will full backups (we run full selective backups bi-weekly, anyway - don't ask......). However, the existing data must be retained/moved from the old TSM server. Since it will take multiple days to move, what happens with what is targeted to move (inactives plus the active) when new backups are occurring, expires are running, etc? Since it is TDP data, I can't separate by filespace. Not sure if the FROMDATE/TIME would be of much value since some of the daily incrementals run for >24-hours. Thoughts? Suggestions? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
