Moving rdb files from one disk to another

[vmsserbo]

Does the copy command do the same thing as the backup/ignore=nobackup command

when moving rdb file over from one disk to another?

I would assume it does? Feedback?

Thanks!

[Sameer_Nirmal · Accepted solution]

Yes, COPY command and backup/ignore=nobackup commands do the same thing.

I guess you are making a copy of RDB file and want to use the copy on the another disk under RDB. Then you need to change the file path with new disk in the RDB enviornment. I guess you know that.

[vmsserbo]

Yes, Thanks!

[Thomas Ritter]

Miles, if these are active RDB files you will need to use the rmu/move utility.

Some thing like

$rmu/move/online/log/opt=option.opt Production_database

[Thomas Ritter]

Forgot to add...if the files are part of any RDB databsase, moving them without using the RMU utilities will break the database. Best you leave the work to those with some DBA training.
Or perform some trail runs on your test host.

[Klaes-Göran Carlsson]

rmu/backup followed by RMU/RESTORE/DIR=nnnn could also be used when you want to move files. Then you also have a backup in case your vms copy commands failed.

And a new question:
Is there any reason at all to use vms copy (or vms backup) commands when I want to move rdb files?
Think I heard somone said that the files will be "corrupt" if they are vms-copied.

[Albert Öttl]

Hi Klaes,
the reason for not copying RDB-Files is that
RDB stores the translated logical file location in its
RDB$SYSTEM file. So the files themselves do
not get corrupt, but the database system does
not find them anymore, if they are moved.

The only workaround ist to use concealed logical
names during database creation. Then you can
move the database files and redefine the logicals afterwards.

LG
Albert

[Jan van den Ende]

Albert,

just a small addendum: those concealed logical names must be in the SYSTEM table.
If not, all is working fine, UNTIL a process (or node) crashes during a transaction. It that case, the RDMON process needs to do the cleanup, and can only do that if that same logical with the same value exists from its view.

nb. CLUSTER logicals would be even (much) more appropriate. Those are available since VMS 7.2. The ugly part: Oracle does not honour those (at least in Rdb and DBMS V7.x)
I found out early in 2000, and reported it. It was confirmed, it would be repaired in "a" next version, and a patch would come "soon".
Until now I have not seen "that" next version, and over six years is not yet "soon" :-(

Until then, be sure to put the Concealed LNMs for database, RUJ, AIJ and SNP in the SYSTEM table.

hth

Proost.

Have one on me.

jpe

[GuentherF]

Was the question realy for /IGNORE=NOBACKUP or, was this about /IGNORE=INTERLOCK (which I believe it was)?

DON'T USE BACKUP/IGNORE=INTERLOCK with an application like Rdb which keeps cached disk data in memory. If the Rdb database is in use and has not reached a quiet point the data on disk maybe inconsitent during the duration of the BACKUP copy.

/Guenther

[Richard J Maher]

Hi Miles,

I don't think anyone else mentioned it, but you might want to look at the /OPTIONS file qualifier on the rmu/restore command. This will help you move your storage areas around especially if you want to have multiple copies of the same database on the same set of disks.

Regards Richard Maher