Thanks Richard ..I appreciate your help!
Richard Sims wrote:
On Feb 23, 2010, at 3:55 PM, Timothy Hughes wrote:
Richard thanks again!
Question - It shouldn't come to this but would another possible
solution be since we still have the node on the source server intact,
could I just DELETE a
On Feb 23, 2010, at 3:55 PM, Timothy Hughes wrote:
Richard thanks again!
Question - It shouldn't come to this but would another possible
solution be since we still have the node on the source server intact,
could I just DELETE all the file spaces on the Target server remove
the node and star
Richard thanks again!
Question - It shouldn't come to this but would another possible
solution be since we still have the node on the source server intact,
could I just DELETE all the file spaces on the Target server remove
the node and start over from the beginning?
I know if this is done I
Timothy -
Query FIlespace won't give you an indication of completeness, for your
determination of which instances are unuseful. Best to use Query OCCupancy in
conjunction with success indications in the Activity Log. Be prepared for an
arduously long DELete FIlespace for those you dispose of,
Richard...Thank you!
Looks like the command I use started the export from the beginning. Now
the question becomes which filespaces (extras) should I delete? I am
guessing the
botton filespaces.
SNIX222\f19 WinNT
SNIX222 \\SNIX222\c1
SNIX222 \\SNIX222\d1
SNIX222 \\
See "restartable export" in IBM Tivoli Storage Manager Versions 5.4 and 5.5
Technical Guide for the 5.5 enhancement which allows that.
On Feb 23, 2010, at 2:01 PM, Timothy Hughes wrote:
> Hello all,
>
> I have been exporting a node from one server to another the past couple
> of days. I have ha
Hello all,
I have been exporting a node from one server to another the past couple
of days. I have had to cancel it a couple of times due to the log
filling up.
Does the export pick up from where it left off? I thought it did,
however I took a look at the filespace scenario and it looks wrong (t
