Re: Moving Node Data
2015-10-04 18:07:24
Subject: |
Re: Moving Node Data |
From: |
INTERNET.OWNERAD at SNADGATE |
To: |
Jerry Lawson at ASUPO |
Date: |
6/9/97 12:48PM |
Be careful with this suggestion - if there is nothing "special" about =
this
node, then this will work. But deleting all of the old files will =
delete
Archived files, as well as any other copies of old files that no longer =
exist
("Only copies" that might be kept for longer periods of time). You may =
wish
to wait a while before deleting the original backups.
Jerry Lawson
jlawson AT thehartford DOT com
______________________________ Forward Header =
__________________________________
Subject: Re: Moving Node Data
Author: INTERNET.OWNERAD at SNADGATE
Date: 6/9/97 12:48 PM
I believe the easiest way by far is simply to use Admin to rename the =
node
you wish to move from "nodename" to "nodename-old", and leave the =
nodename
in your dsm.opt unchanged. This means you'll do a full backup the next =
time
you do an incremental, but, at our shop, that's more efficient than =
doing a
tape-to-tape copy. Then after a week or so, you can delete the =
file-spaces
for "nodename-old", and then "nodename-old" itself.
Bob Siska
National Computer Systems
Iowa City IA
Bob_Siska AT ncs DOT com
----------
"Let's pretend you're Sherman and I'm Mister Peabody..."
----------
From: owner-adsm-l
To: ADSM-L
Subject: Re: Moving Node Data
Date: Monday, June 09, 1997 8:46AM
The only way I can think of is to do an export for the node. =
Delete
all the data for it, and then import it. This is of course time
consuming at best. The ? is what is the point in moving a node at =
a
time from non-collated to non-collated. Even if you do get all the
data together for a node, it's not going to stay that way.
Al Barth
______________________________ Reply Separator
_________________________________
Subject: Moving Node Data
Author: David Ong <david AT BABYONG.NSC DOT COM> at ~Internet
Date: 6/6/97 2:04 PM
Hello ADSMers,
We currently have a non-collocated 3490 tape storage pool which is used =
to
store data for most of our nodes. Now we would like to use a new
non-collocated 3590 tape pool for a select group of nodes. I know that
changing the 'destination' parameter in the copygroup will send new =
backup
data to the 3590 pool. The question I have is how to move the existing
backup data that is on the 3490 tape pool to the new 3590 pool. Are =
there
any 'undocumented' commands that will allow me to move data for a =
specific
node on a volume?
By the way, our ADSM server is 2.1.0.9 running on AIX 4.1.4.
Thanks in advance.
Have a nice day or whatever's left of it.
David Ong
National Semiconductor Corp.
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: Moving Node Data, (continued)
- Re: Moving Node Data, Dwight E. Cook
- Moving Node Data, Jerry Lawson
- Re: Moving Node Data, Kirsten Gloeer
- Re: Moving Node Data, ALLEN BARTH
- Re: Moving Node Data, Siska, Bob
- Re: Moving Node Data, Jerry Lawson
- Re: Moving Node Data, Kelly J. Lipp
- Moving Node Data, INTERNET . OWNERAD at SNADGATE
- Re: Moving Node Data, INTERNET . OWNERAD at SNADGATE
- Re: Moving Node Data, Jerry Lawson [SMTP:jlawson
- Re: Moving Node Data,
INTERNET . OWNERAD at SNADGATE <=
|
|
|