BACKUP changes from V5.0 to V5.5

[Stanley F Quayle]

> Set up a private DECnet network between the
> two systems and copy over all the NON-system
> stuff using BACKUP across the network.

My preferred migration method is to use DECnet to do BACKUP/IMAGE on each drive to the target system. Works like a charm.

Unfortunately, the client has specified that I am to make NO changes to the original system, including configuring DECnet...

[Doug Phillips]

>>
But that doesn't account for the failure when using the 9-track drive.
<<

No, it doesn't. But according to the doc's, the v5.0 and v5.5 backup are compatible.

It doesn't seem like you're able to use the same actual tape drive on both systems, so since the v5.5 system appears not to even "see" the v5.0 tapes, there's some other problem.

Darn. The way this forum's reply works, I can't go back and read the entire thread, but can the v5.0 read a 9-track tape that's been init'ed on the v5.5?

Maybe, try backup up a small file to a save-set on the v5.5, then on the v5.0 system, use /norewind/ignore=label (or give it the label name). If the v5.0 system can't find the tape, then what's common between the v5.5's two tape drives?

I'm guessing the v5.5 system is CHARON-VAX, and you're the expert on that, so I guess you've expored all of those issues.

[Stanley F Quayle]

> upgrade that new system to v5.5-2 if you can,
> as that is still kinda supported and always
> works well

I try to get everyone to V5.5-2H4. That allows them to use newer servers, such as the 4000-106.

But first, I have to get their system migrated...

[Stanley F Quayle]

> can the v5.0 read a 9-track tape that's been
> init'ed on the v5.5?

That's a good idea to try. No one else has suggested that...

> I'm guessing the v5.5 system is CHARON-VAX,
> and you're the expert on that, so I guess
> you've expored all of those issues.

I wasn't trying to drag CHARON-VAX into the discussion, but thanks for noticing...

[Antoniov.]

Hi Stanley,
suppose backup is not changed by V5.5;
suppose tape is readable on new unit;
suppose tape is good;
message is invalid ANSI label.
I can imagine ANSI stdandard is changed, no VMS. In this case you can restore within /OVER=ACCESS qualifier.

Antonio Vigliotti

[Antoniov.]

Sorry,
fingers are quicker than my mind :-(
I forgot you can use /OVER on MOUNT command. not on restore (BACKUP command).
You can try something like
$ MOUNT DUA1: /FORE/OVER=(ACCESS,OWNER)
Perhaps there is /OVER=SETID too.

Antonio Vigliotti

[Bojan Nemec]

Stanley,

Have you try the dir command I suggested in my previous post? A second try could be:

$ mount/foreign mua0:
$ dump mua0:

If the target system is a CHARON-VAX, can you configure a MicroVAX II and install VMS 5.0 to try to restore the tape to a disk and then start the system with VMS 5.5 and use the restored disk.


Bojan

[Stanley F Quayle]

> If the target system is a CHARON-VAX, can you
> configure a MicroVAX II and install VMS 5.0
> to try to restore the tape to a disk and then
> start the system with VMS 5.5 and use the
> restored disk.

I can do that. But I still feel like it's the original tape drive that's the problem. But you're right -- the tape drive and VMS V5.0 are the two things from the old system that haven't been eliminated as candidates.