HP3000-L Archives

September 1998, Week 3

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: DSTAT Question
From:
Lars Appel <[log in to unmask]>
Reply To:
Lars Appel <[log in to unmask]>
Date:
Sat, 19 Sep 1998 12:49:59 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (14 lines) 
At 15:37 16.09.98 -0400, Bob after Evan wrote:
> ... However, based on your detailed description, it is
>likely that when you decabled the drives from a 5.5 system and recabled them
>to a 4.0 system, the drive failed to mount because the transaction manager
>couldn't access the log file built on the drive.  The format of the XM log
>files changed from 4.0 to 5.0 making backdating pretty darn  difficult.

Yes, I also recall XM changes between 4.0 and 5.x (vaguely). I believe there
are some utils for backdating volume sets, though. Don't know for sure but
it might be something like XMMIGBAK or BDREPORT1 and BDREPORT2 plus more. The
Install/Update/Patch manuals typically have (had?) some chapter on backdates.

Lars (haven't used those tools lately)

ATOM RSS1 RSS2