System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure (1072 Views)
Reply
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 1 of 18 (1,072 Views)

System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

[ Edited ]

Hi,

 

Looking for advice on how to restore Backups from a DS20E(VMS 8.3) / MSA1000 (old system) config to a RX2800 (VMS 8.4) /HP D2700 (new system) config.

 

DS20E connects to an SDLT Tape Drive via SCSI - the RX2800 connects to an HP Ultrium 3280 SAS Drive.

 

I know these tape drives are not compatible, and I dont think the RX2800 can connect to the Super DLT via SCSI?

 

So looking to another way of restoring MSA1000 data onto  the new system

The MSA1000 has a San Switch 2/8 which connects to the DS20E via a PCI Fibre Optic Card.

 

Can the new RX2800 connect to the old MSA1000? the RX2800 has a 1 port 8 gb fc sr hba card.

 

Many Thanks

 

Please use plain text.
Trusted Contributor
abrsvc
Posts: 362
Registered: ‎06-08-2010
Message 2 of 18 (1,065 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

At first glance, a few questions come to mind:

 

1) Are both systems running and on a network?

2) Are you trying to move everything but the system disk itself?

 

Perhaps a standard image backup of the data drives to the RX2800 (using a scratch disk) and a restore onto the target data drive on the RX2600 would be the easiest.  Use a backup of any specific files on the Alpha system disk to a temporary saveset on the RX2800 as well.

 

The above method will retain the current directory structures without the need for a tape.

 

Dan

Please use plain text.
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 3 of 18 (1,063 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

yes both systems will be on the same network and running - although the new system is not currently "live"

 

its a an alpha ds20e/msa100  trying to restore to the rx2800/d2700 disk enclosure that i will be attempting.

 

are you suggest the backup is done across the network?

 

the data involved is about 300Gb in size

 

thanks

 

Please use plain text.
Trusted Contributor
abrsvc
Posts: 362
Registered: ‎06-08-2010
Message 4 of 18 (1,060 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

With our production systems, I create backup savesets in the 150GB range every evening. This takes between 2-3 hours over the network.  If you have a reasonably quiet network, I would expect a 4 hour timeframe for the saveset creation.  This would depend upon the number of files rather than the total dat size however.  Typically, the time is for file processing at the source side rather than the actual data transfer.  Without seeing the actual systems/fiels involved, any estimate is pure conjecture.

 

Realize that you will incur both the save and restore operations, so the time will be longer.  Also, I would believe that even with a moderatly slow network connection, the backup would take less time than to tape.  The same goes for the restore.

 

Dan

Please use plain text.
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 5 of 18 (1,058 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

ok so do you use the vms "backup" utility across the network?

or is it a case of using something like NFS and copy?

 

Please use plain text.
Trusted Contributor
abrsvc
Posts: 362
Registered: ‎06-08-2010
Message 6 of 18 (1,054 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

I use backup with a network login to a specific directory and saveset. Please note that a network reference for output requires a saveset. You cannot use backup to create a directory structure or "copy" files directly.

For example:

$BACKUP/IMAGE -
srcdsk: -
node"acct pass"::trgdsk:[savesets]x.sav/save
$

Where:
srcdsk is the source disk on the Alpha
node is the RX2800 nodename
acct is an account with privs to write to the disk on the RX2800
pass is the password for the above account
trgdsk is the disk to be used to store the saveset.
[savesets] is the directory for the savesets
x.sav is the target saveset name (change to be meaningful to you.)

Hope this helps,
Dan
Please use plain text.
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 7 of 18 (1,051 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

[ Edited ]

Dan Thanks

 

I'm getting the following error when I try to backup over the network?

 

$ CHAS:SYSTEM> BACKUP/IMAGE DKA100: DAVE"SYSTEM PASSWORD"::D:[000000]X.SAV/SAVE
%BACKUP-F-PARSE, error opening DAVE"SYSTEM password"::D:[000000]X.SAV;
-RMS-F-DEV, error in device name or inappropriate device type for operation

DAVE  is the name of the VMS box i am trying to save too - CHAS is the live box

 

Network is 100BaseT Full Duplex

 

"DKA100:" is an internal drive on CHAS & "D:" is a Internal Drive on DAVE.

 

 Incidentally these boxes are NOT clustered.

 

Please use plain text.
Trusted Contributor
abrsvc
Posts: 362
Registered: ‎06-08-2010
Message 8 of 18 (1,042 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

My first guess would be that "D" is not defined for the account that you are using.  Try specifying the disk directly (ie: DKA100 or whatever the disk designation actually is.).

 

Dan

Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,079
Registered: ‎02-23-2005
Message 9 of 18 (1,036 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

Please use plain text.
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 10 of 18 (1,036 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

We are not clusterd

 

im still getting this

 

$ CHAS:SYSTEM> BACKUP/IMAGE DKA100: DAVE"SYSTEM password"::DKB1:[000000]X.SAV/SAVE
%BACKUP-F-PARSE, error opening DAVE"SYSTEM password"::DKB1:[000000]X.SAV;
-RMS-F-DEV, error in device name or inappropriate device type for operation

 

Please use plain text.
Honored Contributor
Hoff
Posts: 4,921
Registered: ‎01-29-2006
Message 11 of 18 (1,035 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

[ Edited ]

In no particular order...

 

1: Get BACKUP out of the way here.  Test with a DIRECTORY or other command.  You can perform most anything via this specification, so a DIRECTORY, COPY or other commands will work in this context.

 

2: make sure the logical name is defined in the context of the target process.  D, in this case.  That's almost certainly missing here, as was mentioned upstream.  That's the likely trigger.  Define this in the LOGIN.COM or SYLOGIN.COM in the context of NETWORK access.  (There's a template LOGIN or two around that show how f$mode and related work.  eg: the sys$manager:login.template file.  Read them.)  If the device (or the device that the logical name references) exists, make sure it's available.

 

3: use the logging tools that are available to you.  NET*SERVER.LOG is created in the context of the target system.  Read it.

 

4: Google is your friend here.   (The "search engine" at HP is not.)   Google gets you answers for common questions more quickly than forum postings.  In particular, Google for the error diagnostics and related materials, and look for existing discussions.  You're thirty years into an operating system, which means the chances of this not having been discussed are vanishingly small.  For this case, there's a generic Google and (because Google adopted some of HP's search engine skills here) you'll want to separately Google the comp.os.vms newsgroup archives.

 

5: Start a new thread for a new question.

 

6: Read the error messages, and see if they help understand the trigger.

.  %BACKUP-F-PARSE, error opening DAVE"SYSTEM password"::D:[000000]X.SAV;

-RMS-F-DEV, error in device name or inappropriate device type for operation

BACKUP hit a file specification parsing error on the output file specification.  It thinks the error is with the device name.  The device name here is D.  Check that.  (As was mentioned earlier.)

 

7: you've told us you're not clustered twice now, which tells us you don't understand clustering, and you don't understand DECnet.  DECnet and clustering are NOT related, NOT the same protocols, and clustering (or not clustering) would NOT be involved with this error message.  You CAN generate this error WITH or WITHOUT a cluster, for the specific file specification syntax you are using.

 

8: Look for errors in the remote LOGIN.COM.   (These should show usually in the NET*SERVER.LOG file.) 

 

9: make sure there is NOT a DAVE logical name in the local process context.  That'll get translated.

Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,079
Registered: ‎02-23-2005
Message 12 of 18 (1,029 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

Please use plain text.
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 13 of 18 (1,024 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

1.Directory/Copy dont work either

 

Im not running decnet either - only CIFS/SAMBA on both machines

 

 

Please use plain text.
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 14 of 18 (1,020 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

steve,
tried the dir but also failed
also as you suggested tried the actual physical name eg dave$dkb1:

$ CHAS:SYSTEM> dir DAVE"SYSTEM password"::Dave$dkb1:[000000]x.sav
%DIRECT-E-OPENIN, error opening DAVE"SYSTEM password"::DAVE$DKB1:[000000]X.SAV;* as inp
ut
-RMS-F-DEV, error in device name or inappropriate device type for operation
Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,079
Registered: ‎02-23-2005
Message 15 of 18 (997 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

Please use plain text.
Honored Contributor
Hoff
Posts: 4,921
Registered: ‎01-29-2006
Message 16 of 18 (987 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

If you're not running DECnet, then using DECnet syntax won't work.   Full stop.

 

You can choose to configure and start that, presuming either DECnet Phase IV or DECnet Phase V (that latter stuff is also known as DECnet-Plus, DECnet/OSI) is installed.  Phase IV is far easier to configure and manage, though Phase V can operate over an IP network link. 

 

As for the use of CIFS/Samba here, that means you're also running IP, which means you can configure and use ftp or sftp or related file-transfer tools.

 

There are no CIFS/Samba file system clients for OpenVMS.  (There's a half-eared file transfer client, but there's no point in using that if there's ftp or sftp or other tools involved.

 

The "COPY/FTP/BINARY from to" command is the DCL-level access into ftp and can be used to copy a BACKUP saveset, but (to avoid the next question) ftp stomps on BACKUP saveset file attributes (metadata), so you'll want to learn how to reset the saveset attributes or you'll want to use zip "-V" (and to avoid the next question) you DO need to quote the "-V" switch here outside of cases where extended filename parsing is enabled and (even with that enabled) "-V" works fine.

 

Here is a detailed description on how to ask a question. 

Please use plain text.
Super Advisor
robert70
Posts: 336
Registered: ‎10-20-2004
Message 17 of 18 (896 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

I take it I would require DECNET installed on both systems?

Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,079
Registered: ‎02-23-2005
Message 18 of 18 (877 Views)

Re: System Migration from DS20E & MSA1000 to an RX2800 and HP2700 Disk Enclosure

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation