Re: What would you think would happen..........
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
Re: What would you think would happen..........
The restartable restore blocks all access to the filespace, including things like reclamations and backup stgpools! We've forgotten and left a couple out there a few times. Do a "q restore" to see what restartable restores if any you have. Do a "can restore" to kill them if not needed anymore. Just another part of the dynamics of this flexible system. David Longo >>> [EMAIL PROTECTED] 07/17/01 05:06PM >>> 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. "MMS " made the following annotations on 07/17/01 20:26:42 -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
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
Re: What would you think would happen..........
Yes, we just saw this last week. We had rebuilt an NT client (let's call
it XYZ) that lost its C: drive, but the restore had terrible throughput
(that's another topic). So, after it was all done, we wanted to test the
theory that maybe the NT client machine was causing the slow throughput.
We restored the same data to another NT machine (let's call it ABC), and
the restore went much faster, so we were happy that it wasn't a TSM
problem. However, this second restore did not complete 100%. Later that
night, the daily backup ran for XYZ, but failed because "a recoverable
restore for this node is pending". SO, I think that's the answer... the
server keeps track of recoverable restores, and won't let a backup run at
the same time. Now, I don't know what happens for a NON-recoverable
restore...
Also, come to think of it, we did the restore on machine ABC by using the "
-nodename XYZ" parameter... I wonder if the same check would occur if we
used the "access another node" from the menu?
Robin Sharpe
Berlex Laboratories
"Martin, Jon
R."
cc:(bcc: Robin Sharpe/WA/USR/SHG)
Subject:
07/17/01 Re: What would you think would
happen..
03:00 PM
Please
respond to
"ADSM: Dist
Stor Manager"
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
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
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
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
