Thanks for the info.

Yes, we are doing a "point in time" restore.





"Churchfield, Glen" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/17/2001 05:06 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        Re: What would you think would happen..........


Zoltan,

If you start a restore to another box from the gui, you'd have a
restartable restore on the server. That blocks that filespace from
backing up until the restore is finished. If you started from the cmd
line, the same would happen unless you used the -pittime or some other
option that kept it from being a restartable restore. In that case, the
backup would go ahead during the restore. I think in that case, that the
backup marking files inactive wouldn't interfere because you'd already
be restoring only inactive files. The problem with doing that is that it
takes maybe three times longer because of the additional processing.

-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 2:59 PM
To: [EMAIL PROTECTED]
Subject: Re: What would you think would happen..........


What I mean is that the machine performing the restore (AIX) does not
perform backups. It simply connects as NODENAME XYZ.

It is not *THE* XYZ node that did the backup.

How would you lockout the source node since this machine is signing in
using the NODENAME of the "source" node ?

===========================
Zoltan Forray
Virginia Commonwealth University
University Computing Center
e-mail: [EMAIL PROTECTED]
voice: 804-828-4807




"Martin, Jon R." <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/17/2001 03:00 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        Re: What would you think would happen..........


Zoltan,

Interesting subject I was just talking about this possibility the other
day.
My question refers to part 1.  When you say the node is not a TSM-client
I
am assuming that they have the TSM client installed they are just not
registered with the server as a node?  Otherwise how would they access
the
utilities to open the connection in the first place?

Besides taking the safety precaution of locking the source node out has
anyone experienced this situation before?

Jon

-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 2:24 PM
To: [EMAIL PROTECTED]
Subject: What would you think would happen..........


if the following occured:

1.  Client (lets call it ABC for this arguement since it is not a TSM
client) signs into TSM using nodename XYZ to restore XYZ's files to
another system
2.  Restore is progressing. Large compress files take many hours to
restore.
3.  Node XYZ signs into TSM and does a BACKUP while ABC is still signed
on
as XYZ and is still restoring XYZ's files to another machine.

===========================
Zoltan Forray
Virginia Commonwealth University
University Computing Center
e-mail: [EMAIL PROTECTED]
voice: 804-828-4807

Reply via email to