error during restore from backup

[petar2188]

Hi all, can anyone help me with error below which I am getting during the restore from image


$$$ backup/image/verify dka100:[backup]system.bck/save/nocrc
_To: dka0:
%BACKUP-E-READERRS, excessive error rate reading DKA100:[BACKUP]SYSTEM.BCK;1
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-I-OPERSPEC
%BACKUP-I-OPERASSIST, operator assistance has been requested
%BACKUP-I-NOOPER, no operator is available to handle the request
%BACKUP-I-OPERSPEC, specify option (QUIT or CONTINUE)
Requesting PID:00000025, Target Device:_DKA100

Thank you

[Steven Schweda]

> [...] can anyone help me with error below [...]

   What's the hardware?  VMS version?

> $$$ backup[...]

   Does "$$$ " mean that you're using a VMS installation CD/DVD?

   Your save set is a disk file ("DKA100:[BACKUP]SYSTEM.BCK;1").  Is
that disk working as expected?  "SHOW ERROR"?

   Did you copy that file using a method like FTP (which might change
its record size)?  That kind of change can cause BACKUP to complain in
various ways.

   If the file attributes are wrong, then BACKUP /REPAIR or any of
various DCL scripts might help. See, for example:

      http://antinode.info/dec/sw/fixrec.html

Otherwase, my guess would be no.

ITS $ help /mess READERRS

 READERRS, excessive error rate reading 'save-set-spec'

  Facility: BACKUP, Backup Utility

  Explanation: The Backup utility encountered numerous read errors in the
                specified save set. The save-set media is probably unusable.

  User Action: Retire the save-set media.

In your case, the "save-set medi[um]" would seem to be DKA100.  If
the data on the disk are bad, then you might be doomed.

[petar2188]

hi man,

let me give you alittle bit background what I did.

So I have created backup image of the OpenVMS v8.2 on Alpha station DS15.

then using reflaction software I extracted that backup on my windows PC.

then I have copied system.bck using ftp on my virtual mashine. command promt ftp.

when I tried to restore it on virtual machine it came with that error.  I am using openvms 8.4 cd for restore.

I hope this tells you a little bit more about my problem.

thx

[Volker Halle]

Copying an OpenVMS savesets via FTP to a Windows system is guaranteed to corrupt the file atributes of the saveset.

Use BACKUP/REPAIR (on OpenVMS V8.3 or higher) to repair the Backup saveset file attributes

For an example see: Fixing Backup Saveset (hgenhart.ch)

Volker.

[Steven Schweda]

> [...] I have created backup image of the OpenVMS v8.2 on Alpha station
> DS15.

   Ok.

> then using reflaction software I extracted that backup on my windows
> PC.

   Where "extracted on" means "copied to"?  I know approximately nothing
about Reflection, or exactly what you did with it, so I don't know what
kind of damage it might have done to your BACKUP save set.

> then I have copied system.bck using ftp on my virtual mashine. command
> promt ftp.

   Even if you did a binary/image FTP transfer, I'd expect that to
change the original save-set record size from its default value (8192
for tape, 32256 for disk) to 512.  Which might explain what you see.
(Even if Reflection did no damage, FTP would do enough.)

ITS $ backup login.com login.bck /save

ITS $ write sys$output f$file_attributes( "login.bck", "mrs")
32256

ITS $ ftp proa   ! A Mac, so UNIX-like.
220 10.0.0.87 FTP server (tnftpd 20100324+GSSAPI) ready.
Connected to proa.antinode.info. 
Name (proa.antinode.info:system): sms
331 User sms accepted, provide password.
Password: 
230 User sms logged in.
FTP> bin
200 Type set to I.
FTP> put login.bck
200 PORT command successful.
150 Opening BINARY mode data connection for 'login.bck'.
226 Transfer complete.
local: SYS$SYSROOT:[SYSMGR]login.bck;1  remote: login.bck
258048 bytes sent in 00:00:00.12 seconds (2.02 Mbytes/s)
FTP> get login.bck login_2.bck
200 PORT command successful.
150 Opening BINARY mode data connection for 'login.bck' (258048 bytes).
226 Transfer complete.
local: SYS$SYSROOT:[SYSMGR]login_2.bck;1  remote: login.bck
258048 bytes received in 00:00:00.05 seconds (4.73 Mbytes/s)
FTP> quit
221-
    Data traffic for this session was 516096 bytes in 2 files.
    Total traffic for this session was 516724 bytes in 2 transfers.
221 Thank you for using the FTP service on 10.0.0.87.

ITS $ write sys$output f$file_attributes( "login_2.bck", "mrs")
512

   My file is so small that this change might not matter to BACKUP, but
I'd expect such a change to cause problems with a bigger file.

> [...] I am using openvms 8.4 cd for restore.

   Ok.

   If the attributes of your copied save set are wrong, then you need to
fix them.  You can use one of the DCL scripts cited above, or else add
"/REPAIR" to your BACKUP command.  The scripts do what they do.  I'd
expect BACKUP /REPAIR to give you a suggestive message like:

%BACKUP-I-REPAIRED, saveset attributes changed to RFM=FIX, MRS=32256

>       http://antinode.info/dec/sw/fixrec.html

   Did you look at it?

[petar2188]

Hi,

I did all what you have suggest but the error msg is coming that .bck is not save_set when I try to repair it. 

any other suggestion?

[Volker Halle]

It would certainly help, if you would show the actual commands used and the actual error messages (copy them with copy & paste to this forum).

To prevent a possible corruption of the contents of the backup saveset, ZIP "-V" it on the source and unzip it, before trying to restore it.

Volker.

[petar2188]

Hi,

Can you help me with zip command as I never used it before?

File on original Alpha is in the second disk, dka100:[backup]system.bck, this is exact location. 

I want on the same location to add zip file, can you send me command?

Petar

[Volker Halle]

Petar,

first of all, you need ZIP.EXE and UNZIP.EXE for OpenVMS Alpha. One possible download location would be:

Index of /openvms/freeware/v80/000tools/alpha_images (digiater.nl)

Then you need to define a foreigen commadn pointing to ZIP.EXE and UNZIP.EXE

$ ZIP:==$device:[directory]ZIP.EXE

$ unzip:==$device:[directory]UNZIP.EXE

Then zip your backup saveset:

$ SET DEFAULT dka100:[backup]

$ ZIP "-V" system_bck.zip system.bck

The above command will create system_bck.zip preserving the SYSTEM.BCK file attributes.

Copy system_bck.zip to your destination disk and unzip it:

$ UNZIP system_bck.zip

Then restore you system.bck file using

$ MOUNT/FOR destination-disk:

$ BACKUP/IMAGE system.bck/SAVE destination-disk:

Good luck,

Volker.

[Steven Schweda]

> I did all what you have suggest but the error msg is coming that .bck
> is not save_set when I try to repair it.

   None of that is a useful problem description.  Copy+paste is your
friend.

> [...] ZIP "-V" [...]

   That might help, but if Reflection is damaging your BACKUP save set
in some way, or if you're not using binary/image FTP, then whatever
you're doing might damage the zip archive, too.

   If you use _only_ binary/image FTP to transfer the BACKUP save set,
then the only problem should be a bad block size, and that should be
easy to fix using BACKUP /REPAIR or one of the DCL scripts cited above.

[petar2188]

Hi, 

Looks like I am very close to finish with this but now I am having issue with unzip file... see below

$ unzip system_bck.zip
Archive: DKA100:[BACKUP]SYSTEM_BCK.ZIP;1
warning [DKA100:[BACKUP]SYSTEM_BCK.ZIP;1]: 196 extra bytes at beginning or with
in zipfile
(attempting to process anyway)
[ Create file QIO failed. ]
[ %SYSTEM-W-DEVICEFULL, device full; allocation failure ]

any advice please?

Petar

[Steven Schweda]

> Looks like I am very close to finish with this [...]

   I wouldn't bet on that.

> $ unzip system_bck.zip

   Which version of UnZip?  Zip?

      unzip -v
      zip -v

   Zip 3.x and UnZip 6.x should work.  How big are these files?

   On the system where you created the zip archive, try:

      unzip -t system_bck.zip

Does it work _before_ you tranfer the zip archive?

> warning [DKA100:[BACKUP]SYSTEM_BCK.ZIP;1]: 196 extra bytes at beginning
> or with in zipfile

   As I wrote earlier:

> [...] whatever you're doing might damage the zip archive, too.

   How, _exactly_, did you transfer that zip archive from the source
system to the destination system?

> [ Create file QIO failed. ]
> [ %SYSTEM-W-DEVICEFULL, device full; allocation failure ]

   A corrupt zip archive could explain that.  A full destination disk
could also explain that.

> any advice please?

   My advice is the same as before: Use only binary/image FTP (or some
other scheme which does not change the data) to move the original BACKUP
save-set file from the source system to the destination system.  Then
use BACKUP /REPAIR or one of the DCL scripts cited above to restore its
original block size.

   If you do that, then you don't need to use Zip and UnZip.

   You can use Zip and UnZip if you want, but whether or not you use Zip
and UnZip, if you use a file-transfer method which changes the data,
then you can expect trouble.

   If you use _ONLY_ binary/image FTP (or equivalent), then you should
even be able to include your Windows system in the file transfer.
However, if it's possible, I'd try to transfer the file directly from
one VMS system to the other.

[petar2188]

HI,

I have tried this command unzip -t system_bck.zip on both sides, source and target and says no error founds and all good.

But I am still getting error when I try to unzip it. my system disk is full and disk where I copied file is another empty disk. 

Maybe its trying to unzip it on the system disk? what is command to change location for unziping? 

Backup /repair sounds good, but I am not able to find how and where to use it. 

It owuld be perfect if you can send me some commands for repair and how to use link which you sent to. I do not have that much of expiriance with Alphas.

Thank you in advance

[Volker Halle]

Petar,

UNZIP tries to write the output file to the current default directory, so try this

$ SET DEF empty_disk:<directory>

$ UNZIP DKA100:[BACKUP]SYSTEM_BCK.ZIP;1

If required, you can use the BACKUP /REPAIR qualifier after the /SAVE_SET qualifier after the input-specifier, e.g.

$ BACKUP/LIS SYSTEM.BCK/SAVE/REPAIR

Volker.

[petar2188]

HI,

I tried suggested but I am getting same error for unzip even on the new drive.

$ unzip dka100:[backup]system_bck.zip;1
Archive: DKA100:[BACKUP]SYSTEM_BCK.ZIP;1
warning [DKA100:[BACKUP]SYSTEM_BCK.ZIP;1]: 196 extra bytes at beginning or with
in zipfile
(attempting to process anyway)
[ Create file QIO failed. ]
[ %SYSTEM-W-DEVICEFULL, device full; allocation failure ]

same error also when I try to repair backup.

$ backup/lis system.bck/save/repair
Listing of save set(s)

%BACKUP-F-NOTSAVESET, SYSTEM.BCK is not a BACKUP save set

I am really stuck here...

[Volker Halle]

Petar,

what's the size ofthe SYSTEM.BCK saveset (on the source system) ? Depending on the version of ZIP being used, there may be problems with ZIPping 'big' files...

Volker.

[petar2188]

Hi,

File size is around 2.02GB... I am using ZIP.EXE and UNZIP.EXE from the link you shared with me.

[Steven Schweda]

> File size is around 2.02GB...

    _Which_ "File"?  The zip archive, or the BACKUP save set, or what?

   That might be too large for Zip and UnZip programs which are older
than 3.x and 6.x.  Look for "LARGE_FILE_SUPPORT" in the "-v" reports,
(Blocks would have been more helpful than "around [...] GB".)

> [...] ZIP.EXE and UNZIP.EXE from the link you shared with me.

   Trust no one, I always say.

> https://www.digiater.nl/openvms/freeware/v80/000tools/alpha_images/

>    unzip.exe                     2006-07-20  17:34  160K

>    zip.exe                     2006-07-20  17:35  110K

   I can't easily see the versions of those programs, but I'd guess that
they're too old.  UnZip 6,00 was released in 2009.

      http://antinode.info/ftp/info-zip/unzip60s4/unzip60s4_vms.zip
      http://antinode.info/ftp/info-zip/zip30s3/zip30s3_vms.zip

   An old UnZip program should be good enough to unpack those newer
kits.

> Which version of UnZip? Zip?
>
>       unzip -v
>       zip -v

   Why not simply answer the question about the program versions???

> [...] Copy+paste is your friend.

   Still true.

>    If you do that, then you don't need to use Zip and UnZip.

   Also still true.

> [...] whatever you're doing might damage the zip archive, too.

   Also still true.

[Volker Halle]

Petar,

> File size is around 2.02GB...

or try again using BACKUP/GROUP=0 ... to reduce the size of your SYSTEM.BCK saveset file on your source system (default group size is 10, so using /GROUP=0 should reduce the .BCK file size by about 10%).

Volker.,

[Steven Schweda]

    Does a week of silence mean that you solved the problem?  Some future
reader might be interested in what you did wrong, and what you did to
correct the problem.