Hi,

sorry for being late!

On Thu, 9 Jun 2011, Timothy Hughes wrote:
>[...]
> Question - this may be obvious but I want to make absolutely sure
>
> Does exporting data at the same time it is backing up cause a issue?
>
> Example: I am exporting a client node from TSM SERVER A to TSM SERVER  B an=
> d it's a large export and it has run more than a day. Can I allow the backu=
> ps to run (on the TSM Server A original server) while the export is still g=
> oing on without causing a problem? It will eventually export any new data o=
> ver to the new TSM SERVER correct?

Not correct. A single EXPORT command (including possible RESTARTs)
will export precisely all data that's available when the command starts
(have a look at "Q EXPORT F=D" to note that there's a "file identification"
 stage preceding the actual data transmission).

So the "correct" process (which I've performed many times) goes like ...

(1) SERVER-A> export node CLIENT tos=SERVER-B filed=all merge=y
    Note _start_ date/time for use in step (4).

When done (do check the ACTLOG for "ANR0617I EXPORT NODE ... SUCCESS"!), 
eventually
(2) re-direct CLIENT's backup to SERVER-B

(3) SERVER-A> lock node CLIENT
(4) SERVER-A> export node NODE tos=SERVER-B filed=all merge=y fromd=STARTDATE 
fromt=STARTTIME

And in case your aim was to "move" the client's data,
wait for at least one database backup on SERVER-B to take place
prior to deleting CLIENT's file space(s) on SERVER-A.

If it takes too long to reach step (2), you'll want to perform
occasional additional "incremental" exports ala (4), and - only
when successful - advance STARTDATE & STARTDATE accordingly,
prior to the first backup of CLIENT to SERVER-B.


Best regards,

        Wolfgang J. Moeller <moeller AT gwdg DOT de>

Tel. +49 551 201-1516 ... not representing ... GWDG, Goettingen, Germany