ADSM-L

[ADSM-L] How does EXPORT MERGEFILESPACES really work

2011-02-25 14:01:25
Subject: [ADSM-L] How does EXPORT MERGEFILESPACES really work
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 25 Feb 2011 13:59:49 -0500
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
zforray AT vcu DOT edu - 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

<Prev in Thread] Current Thread [Next in Thread>