- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Job aparently freezze
Operating System - OpenVMS
1748181
Members
3689
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО04-20-2010 02:29 PM
тАО04-20-2010 02:29 PM
Re: Job aparently freezze
Roberto,
As Volker suggested, use the /REWIND qualifier. Since this backup is taking multiple tapes anyway, I can't think of any reason to append to any previous tape. Also, without it the use of /media=compaction will be ignored (at least for the first tape).
You stated you are using new media. I would expect that to work, but there may have been some bugs with backup from 7.1-2 with continuation volumes not being initialized. See $help backup /label for a description of what Backup will do if a label isn't specified.
Try this:
1. Before backup starts, initialize your tapes, each with a unique 6-character label (I would also put a paper label with that label printed in the slot in the tape cartridge. (What type of tape drive is this? DLT, DAT, something else? Please specify model number). The output of show device/full mka600: should provide a clue (at least in VMS versions from the last 10 years or so, I am not sure if 7.1-2 did).
2. In the backup command, use /LABEL=(label1,label2,label3)/exact_order/rewind [/tape_expiration=date] [/media_format=compaction] [/protect=(S:RWED,...)]. The combination of /label and /exact_order causes VMS BACKUP to verify that the correct tapes are used, and that all 6 characters of the label are significant. This prevents mistakes, like putting the same tape back into the drive and overwriting it with a continuation volume. /TAPE_EXPIRATION allows you to specify a date that you want to save the tape until, before allowing BACKUP to overwrite it. (This is a blade guard, and can be overridden). The /media_format /protect and /density are used when initializing and rewriting the tape headers.
3. I would use /BLOCKSIZE=32256 or 31744 instead of 32255 (which will be rounded down to the previous multiple of 512, or 31,744). This is just so the qualifier is consistent with the actual value that is used.
4. If you use list, I would recommend having it go to a file. I.e. /list=backup_lst:sngsbkp_1904.lis There is no problem with using /list while the backup is being made. Since this backup will have
5. /SAVE is default for tape save sets, but specifying it definitely causes no harm, and removes any doubt as to what is being written.
Example:
$! init tapes. This only has to be done the first time you use a tape (and define its tape label)
$! put in second tape
$ init mka300: rbf002 /own=system /prot=(s:rwed,o:rwed,g,w) /media=compaction
$! put in third tape
$ init mka300: rbf003 /own=system /prot=(s:rwed,o:rwed,g,w) /media=compaction
$! put in first tape
$ init mka300: rbf001 /own=system /prot=(s:rwed,o:rwed,g,w) /media=compaction
$
$! now do the backup...
$
$ Backup -
/BLOCK_SIZE=32256 /log /List=sngsbkp_1904.lis /rewind -
/Media=Compact /label=(rbf001,rbf002,rbf003) /exact_order -
sngs_pro.rbf; mka600:sngsbkp.1904 /Save /tape_expiration=1-jan-2011 ! example of tape_expiration
Jon
As Volker suggested, use the /REWIND qualifier. Since this backup is taking multiple tapes anyway, I can't think of any reason to append to any previous tape. Also, without it the use of /media=compaction will be ignored (at least for the first tape).
You stated you are using new media. I would expect that to work, but there may have been some bugs with backup from 7.1-2 with continuation volumes not being initialized. See $help backup /label for a description of what Backup will do if a label isn't specified.
Try this:
1. Before backup starts, initialize your tapes, each with a unique 6-character label (I would also put a paper label with that label printed in the slot in the tape cartridge. (What type of tape drive is this? DLT, DAT, something else? Please specify model number). The output of show device/full mka600: should provide a clue (at least in VMS versions from the last 10 years or so, I am not sure if 7.1-2 did).
2. In the backup command, use /LABEL=(label1,label2,label3)/exact_order/rewind [/tape_expiration=date] [/media_format=compaction] [/protect=(S:RWED,...)]. The combination of /label and /exact_order causes VMS BACKUP to verify that the correct tapes are used, and that all 6 characters of the label are significant. This prevents mistakes, like putting the same tape back into the drive and overwriting it with a continuation volume. /TAPE_EXPIRATION allows you to specify a date that you want to save the tape until, before allowing BACKUP to overwrite it. (This is a blade guard, and can be overridden). The /media_format /protect and /density are used when initializing and rewriting the tape headers.
3. I would use /BLOCKSIZE=32256 or 31744 instead of 32255 (which will be rounded down to the previous multiple of 512, or 31,744). This is just so the qualifier is consistent with the actual value that is used.
4. If you use list, I would recommend having it go to a file. I.e. /list=backup_lst:sngsbkp_1904.lis There is no problem with using /list while the backup is being made. Since this backup will have
5. /SAVE is default for tape save sets, but specifying it definitely causes no harm, and removes any doubt as to what is being written.
Example:
$! init tapes. This only has to be done the first time you use a tape (and define its tape label)
$! put in second tape
$ init mka300: rbf002 /own=system /prot=(s:rwed,o:rwed,g,w) /media=compaction
$! put in third tape
$ init mka300: rbf003 /own=system /prot=(s:rwed,o:rwed,g,w) /media=compaction
$! put in first tape
$ init mka300: rbf001 /own=system /prot=(s:rwed,o:rwed,g,w) /media=compaction
$
$! now do the backup...
$
$ Backup -
/BLOCK_SIZE=32256 /log /List=sngsbkp_1904.lis /rewind -
/Media=Compact /label=(rbf001,rbf002,rbf003) /exact_order -
sngs_pro.rbf; mka600:sngsbkp.1904 /Save /tape_expiration=1-jan-2011 ! example of tape_expiration
Jon
it depends
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2010 05:39 PM
тАО04-20-2010 05:39 PM
Re: Job aparently freezze
I don't see an answer to Hoff's question about whether any hardware errors are being logged.
A hardware problem with a tape drive can ruin your whole day.
Also check that all cables to your tape drive are seated properly. The fact that the backup runs sometimes but not others is curious, so we need to look for possible intermittent faults.
A hardware problem with a tape drive can ruin your whole day.
Also check that all cables to your tape drive are seated properly. The fact that the backup runs sometimes but not others is curious, so we need to look for possible intermittent faults.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-22-2010 11:40 AM
тАО04-22-2010 11:40 AM
Re: Job aparently freezze
Thank you guys!
I think that there are enough hints to hold this problem so I'm closing this thread.
I think that there are enough hints to hold this problem so I'm closing this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-22-2010 11:41 AM
тАО04-22-2010 11:41 AM
Re: Job aparently freezze
The problem was fixed, so I'm closing the thread
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP