- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: copy saveset to PC
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2010 12:47 PM
тАО10-11-2010 12:47 PM
So, I create a saveset:
backup *.dat abc.bck/sav/log/ver
then copy to the PC (issuing these commands on the PC):
FTP 192.168.xx.xx
bin
get abc.bck
bye
I then copy this file to a PC connected to my local network and do the reverse
FTP 10.2.xx.xx
bin
put abc.bck
bye
The save set set is not readable. When I try backup/lis abc.bck/sav I see the save set header and then error messages:
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-READERRS, excessive error rate reading EXE_BASELINE:[EXE]ABC.BCK;1
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-I-OPERSPEC
My experience is that this is consistent with specifying the wrong file type in FTP.
Any tips for copying savesets between computers?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2010 12:57 PM
тАО10-11-2010 12:57 PM
SolutionEasiest fix: forget backup. Use zip "-V". Works better.
If you really want BACKUP, then Google for the sequence or fetch the saveset reset tool via the following path:
http://decuslib.com/decus/freewarev80/000TOOLS/
Related:
http://labs.hoffmanlabs.com/node/684
This is listed in the OpenVMS FAQ, as well:
http://labs.hoffmanlabs.com/node/1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2010 01:10 PM
тАО10-11-2010 01:10 PM
Re: copy saveset to PC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2010 01:11 PM
тАО10-11-2010 01:11 PM
Re: copy saveset to PC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2010 02:06 PM
тАО10-11-2010 02:06 PM
Re: copy saveset to PC
Actually, with all due respect to the ZIP/UNZIP team, I generally use the ZIP/UNZIP combination to process the BACKUP save set. Then, I then use BACKUP to do the actual restore.
ZIP/UNZIP with file attributes does work, but I trust BACKUP more when with arbitrary files. In effect, I am using ZIP/UNZIP to containerize the file for FTP.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2010 03:25 PM
тАО10-11-2010 03:25 PM
Re: copy saveset to PC
As of OpenVMS V8.3, BACKUP can repair some broken savesets
$ BACKUP/REPAIR ABC.BCK/SAVE
(still not documented).
For earlier versions of OpenVMS there are plenty of DCL procedures to do the equivalent repair.
The one I use exploits Hein's clever hack:
$IF p1.EQS."" THEN INQUIRE p1 "Save set file name ?"
$IF f$search(p1).EQS."" THEN EXIT
$IF p2.EQS."" THEN WRITE SYS$OUTPUT -
" RFM = ", F$FILE(p1,"RFM"), ",",-
" MRS = ", F$FILE(p1,"MRS"), ",",-
" LRL = ", F$FILE(p1,"LRL"), "."
$SET FILE /ATTR=(RFM=FIX, MRS=44, LRL=44) 'p1 ! Easier for DCL
$OPEN/READ file 'p1
$READ file record
$CLOSE file
$mrs = F$CVSI(40*8,32,record)
$IF p2.EQS."" THEN WRITE SYS$OUTPUT "Setting blocksize to: ",MRS
$SET FILE /ATTR=(RFM=FIX, MRS='mrs', LRL='mrs') 'p1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2010 03:41 PM
тАО10-11-2010 03:41 PM
Re: copy saveset to PC
> computers?
A Web search for related error messages might
have led you to (among other places):
http://antinode.info/dec/sw/fixrec.html
which leads to a command procedure intended
to repair the damage to a BACKUP save set
caused by (binary) FTP.
> Easiest fix: forget backup. Use zip "-V".
> Works better.
With Zip 2.32 or newer, on VMS V8.2-1 (with
"Parse Style: Extended"), you can even leave
out the quotation marks.
If you're interested in any exotic file
attributes (ACLs, seriously weird ODS5
extended file names, ...), then you might
wish to run some tests to verify that
Zip+UnZip won't lose anything, but, for most
purposes, They should be pretty safe. (The
known ACL problems should be fixed in the
current Zip 3.1 development code. Complain
if you notice a problem.)
> [...] I generally use the ZIP/UNZIP
> combination to process the BACKUP save set.
> [...]
Extra (often pointless) time and disk space
required, but probably safer. For normal
stuff, I wouldn't bother.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2010 04:19 AM
тАО10-12-2010 04:19 AM
Re: copy saveset to PC
>
> $IF p1.EQS."" THEN INQUIRE p1 "Save set file name ?"
> $IF f$search(p1).EQS."" THEN EXIT
> $IF p2.EQS."" THEN WRITE SYS$OUTPUT -
> " RFM = ", F$FILE(p1,"RFM"), ",",-
> " MRS = ", F$FILE(p1,"MRS"), ",",-
> " LRL = ", F$FILE(p1,"LRL"), "."
> $SET FILE /ATTR=(RFM=FIX, MRS=44, LRL=44) 'p1 ! Easier for DCL
The fix is simply to reset the record size to the original size used by the BACKUP command. I would NOT call this corruption since all of the data is intact. (Just my two cents.)
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2010 01:39 PM
тАО10-12-2010 01:39 PM
Re: copy saveset to PC
>I would NOT call this corruption since all
>of the data is intact.
So if the file is just a little bit corrupt, but sufficient that it can't actually be used, you don't call it corruption?
Doesn't seem like a very useful definition to me. Looks like a duck, quacks like a duck...