- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: BACKUp and end-of-tape processing
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
тАО07-24-2005 11:27 PM
тАО07-24-2005 11:27 PM
BACKUp and end-of-tape processing
I wrote backup tape in the /NOREWIND mode, appending savesets one to one. Now I need to remove last saveset from the end of the tape. I tried it on the test tape:
$ back login.com;0 mkb400:test1/sav
$! point1
$ set mag /rewind mkb400:
$ dump/bl=cou=100 mkb400:
VOL1...
HDR1...
HDR2...
*** End of file ***
data blocks...
*** End of file ***
EOF1...
EOF2...
*** End of file ***
*** End of file ***
$! now append 2nd saveset
$ back login.com;0 mkb400:test2/sav/norew
$! now trying to put 2nd tapemark after
$! the 1st saveset to cut off 2nd saveset
$ set mag /rewind mkb400:
$ set mag /skip=file=3 mkb400:
$! now tape positioned at the HDR1 record of
$! the 2nd saveset
$ copy sys$input mkb400:
^Z
$! point2
$ set mag /rewind mkb400:
$ dump/bl=cou=100 mkb400:
... output is exactly the same as after the point1...
But backup on that crafted tape failed with
%BACKUP-F-LABELERR, error in tape label processing on MKB400:[000000]TEST2.;
-SYSTEM-W-ENDOFVOLUME, end of volume
But why? Content of the tape (till the double tapemarks) is exactly the same in the both cases (I checked it DIFFing the DUMP output). Tape drive is Tandberg DLT8000
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2005 02:11 AM
тАО07-25-2005 02:11 AM
Re: BACKUp and end-of-tape processing
/skip=file:3 skips tape markers, not files.
Whatever that exactly means.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2005 02:19 AM
тАО07-25-2005 02:19 AM
Re: BACKUp and end-of-tape processing
Check also the SET MAG/END_OF_FILE which writes an end of file marker. Two end of file markers means end of tape.
Bojan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2005 02:37 AM
тАО07-25-2005 02:37 AM
Re: BACKUp and end-of-tape processing
Per default, backup will write starting at eot.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2005 02:48 AM
тАО07-25-2005 02:48 AM
Re: BACKUp and end-of-tape processing
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2005 03:02 AM
тАО07-25-2005 03:02 AM
Re: BACKUp and end-of-tape processing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2005 07:49 PM
тАО07-25-2005 07:49 PM
Re: BACKUp and end-of-tape processing
> Check help set mag /skip.
> /skip=file:3 skips tape markers, not files.
Yes, I know. I checked tape position before setting 2nd tapemark (DUMP/BL=COU=2 and rewind tape and skip files again)
> Also check help backup/rewind.
> Per default, backup will write starting at eot.
But I don't want to rewrite tape from the beginning (BACKUP/REWIND) but only the last saveset
> You could try to do set mag/end before
> overwriting the last saveset.
COPY SYS$INPUT MKB400: followed by ^Z and SET MAG /END (also suggested by Bojan Nemec) do exactly the same - they set tapemark in the current position and the result exactly the same: BACKUP-F-LABELERR,
-SYSTEM-W-ENDOFVOLUME.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2005 09:50 PM
тАО07-25-2005 09:50 PM
Re: BACKUp and end-of-tape processing
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2005 12:51 AM
тАО07-26-2005 12:51 AM
Re: BACKUp and end-of-tape processing
When your tape is positioned somewhere, and you want one saveset back , you have to give:
$ set mag /skip=files=-4
If you want three savesets back, you have to specify:
$ set mag /skip=files=-12 !
Bit strange, but it works..
When you are positioned at the beginning:
$ set mag /skip=files=2
when you want to go to the next saveset
$ set mag /skip=files=4
when you want to skip 2 savesets
So when you go back double the numbers....
See the attachment
Also tried the same trich as Wim vd Wijgaert did, but got an error:
-SYSTEM-W-ENDOFVOLUME
See the attachment
I'm using a different version, 7.3-1
Jeroen Bleeker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2005 01:33 AM
тАО07-26-2005 01:33 AM
Re: BACKUp and end-of-tape processing
Default depends on the tapedrive. But I guess my drive (TZ88) is doing /fast=never and your drive (?) is doing /fast=always.
May be the functionality is not exactly the same ? Try your test with /fast=never.
Wim