- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Backup Issues
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
Forums
Discussions
Discussions
Discussions
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
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
03-18-2008 05:17 AM
03-18-2008 05:17 AM
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 05:33 AM
03-18-2008 05:33 AM
SolutionI assume you're talking about the following error:
%BACKUP-F-PROCINDEX, error processing index file on DISK$DEVSCRATCH1:, RVN 1
-SYSTEM-F-VOLINV, volume is not software enabled
Backup seemed to have a problem reading INDEXF.SYS of the disk DISK$DEVSCRATCH1.
VOLINV indicates that the 'volume valid bit' is not set for that disk. Please check the status of that disk as seen from the node running your backup procedure:
$ SHOW DEVICE DISK$DEVSCRATCH1
If this error is intermittend, include the SHOW DEV command in your backup procedure.
Any errors on that disk ? Any mount-verification messages regarding this disk ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 05:44 AM
03-18-2008 05:44 AM
Re: Backup Issues
I agree with Volker. I would highly recommend checking the error log for errors on this device.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 06:32 AM
03-18-2008 06:32 AM
Re: Backup Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 06:38 AM
03-18-2008 06:38 AM
Re: Backup Issues
The path to the device has been lost for more than MVTIMEOUT seconds (typically 1 hour). The disk may have failed and may be broken.
Check whether there are any files open on that disk. Does SHOW DEV DISK$DEVSCRATCH1 show a transaction count greater than 1 in the Trans Count column ?
If TransCount=1, try $ DISM/ABORT DISK$DEVSCRATCH1
Then try to mount the disk again with:
$ MOUNT/SYSTEM/NOASSIST disk-name DEVSCRATCH1
Be prepared for the mount to fail, if the disk has gone bad.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 06:56 AM
03-18-2008 06:56 AM
Re: Backup Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 07:00 AM
03-18-2008 07:00 AM
Re: Backup Issues
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 07:14 AM
03-18-2008 07:14 AM
Re: Backup Issues
It can be dangerous to diagnose problems like this over the phone. There are many possible causes, from a failed disk at one extreme to something as simple as loose cable at the other end of the range.
If there are no obvious problems (e.g., flashing red lights), I would recommend getting experienced assistance. I have seen many easily recoverable situations become far worse when incorrect action is taken.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 08:06 AM
03-18-2008 08:06 AM
Re: Backup Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 08:40 AM
03-18-2008 08:40 AM
Re: Backup Issues
Try $ SEARCH SYS$STARTUP:*.COM MOUNT,DEVSCRATCH1/MATCH=AND
Then use the mount command found.
The label should be DEVSCRATCH1, whether there had been an additional logical name (this is optional), I don't know.
If there had been a logical, you may be able to find it via:
$ PIPE SHOW LOG * | SEARCH SYS$PIPE
Use the phyiscal disk name (e.g. DKA200:).
OpenVMS has an extensive HELP system built in. If you see an OpenVMS error message (like SYSTEM-F-VOLINV), you always obtain help for this error message with:
$ HELP/MESSAGE VOLINV
Hope this helps ;-)
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2008 08:43 AM
03-18-2008 08:43 AM
Re: Backup Issues
This is one of the most arcane and cryptic areas of OpenVMS, and there are very few "blade guards" here; data can get clobbered. BACKUPs can get trashed.
For purposes of a hand-entered BACKUP command, you need not use the logical name on the MOUNT command.
The logical name parameter on MOUNT is useful within a command procedure however, as it can be used as the target for all subsequent device references within the procedure. MYCORP_TARGET and MYCORP_SOURCE could be used as the logical names for the output and input devices, for instance.
The volume label must be the assigned volume label found on the volume, or you must use the MOUNT /OVERRIDE, or you're using (as is often the case) MOUNT /FOREIGN.
Are there any bound-volume sets here?
Again, this area is data-hazardous. Please take the time to read and understand the DCL command syntax, and please consider practicing in a testing configuration where an errant command can trash data without harm to production. Do also look at the BACKUP command examples in the back of the BACKUP manual, as these provide many examples of the various sequences with BACKUP, and you can find and choose the particular command associated with what you want to do.
There are example BACKUP command procedures around that can be used as starting points, as well.
As for another potential hazard here, I see Rdb referenced. (Rdb itself isn't hazardous, but there are specific RMU commands needed to perform a successful and restore-able backup of an Rdb database. You can't use OpenVMS BACKUP directly on an Rdb database and expect to restore the database.)
And FWIW, the existing backup archives here potentially (probably?) contain silent data corruptions, too. (Those file interlocks that are being overridden were implemented for a reason, after all. Not because the engineers wanted to force folks to use another qualifier keyword on BACKUP.)
This whole area is comparatively ancient technology -- and not all that much past what RSX11M+ implemented. The UI and the tools are such that it is accordingly very easy to unintentionally corrupt critical data.
Stephen Hoffman
HoffmanLabs LLC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 08:00 AM
03-19-2008 08:00 AM
Re: Backup Issues
DPA300: (NRCAVB) MntVerifyTimeout 3598 DEVDISK1 3758040 39 1
DPA301: (NRCAVB) MntVerifyTimeout 3598 DEVDISK2 646806 15 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 08:14 AM
03-19-2008 08:14 AM
Re: Backup Issues
You need to use appropriate $ RAID SHOW commands to find out about the structure of your RAID sets and the physical disks involved.
You can use $ RAID ANALYZE/ERROR_LOG to find RAID-related errlog entries.
There should also be a SYS$MANAGER:RAID$DIAGNOSTICS_nodename.LOG file with diagnostic messages.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 08:20 AM
03-19-2008 08:20 AM
Re: Backup Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 09:40 AM
03-19-2008 09:40 AM
Re: Backup Issues
All the units have had a lot of errors reported against them.
Please look at the diagnostics file mentioned earlier and try to find out what happened when.
The HP RAID Software for OpenVMS - Guide to Operations can be found here:
http://h30266.www3.hp.com/odl/vax/sysman/raidv30/raid_ops_guide.pdf
You will at least need to dismount the DPA: devices, which are in MntVerifyTimeout, then re-mount them with the MOUNT commands to be found somewhere in your system startup procedures. But first try to find out what happened.
Consider to obtain qualified help to prevent damage to your data, if you're uncertain what to do...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 10:34 AM
03-19-2008 10:34 AM
Re: Backup Issues
%SEARCH-I-NULLFILE, file SYS$SYSROOT:[SYSMGR]ADDOPER.COM;2 contains no records
%SEARCH-I-NULLFILE, file SYS$SYSROOT:[SYSMGR]ADDSYS.COM;2 contains no records
I got this error when I attempted to remount.
******************************
SYS$SYSROOT:[SYSMGR]NRC_MOUNT_DISKS.COM;21
$ Mountxx/noass/sys/rebuild DPA302: DEVSCRATCH1 DEVSCRATCH1
******************************
SYS$COMMON:[SYSMGR]SYSHUTDWN.COM;18
$ dismountxx/abort/over=check DISK$DEVSCRATCH1 !dpa302:
$ Mountxx/noass/sys/rebuild DPA302: DEVSCRATCH1 DEVSCRATCH1
%MOUNT-F-MEDOFL, medium is offline
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 10:43 AM
03-19-2008 10:43 AM
Re: Backup Issues
Can you currently access DPA300: and DPA301: without problems ? Is only DPA302: giving you problems ?
Did you look at the drives behind the Mylex controller. Any yellow or red lights ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 10:53 AM
03-19-2008 10:53 AM
Re: Backup Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 11:04 AM
03-19-2008 11:04 AM
Re: Backup Issues
As you are using a partitioned RAID 0 stripeset, the failure of ANY physical DRA disk will cause the whole array to become inoperative !
First make sure to check for your last GOOD backup of these 3 DPA: devices !
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2008 01:58 PM
03-19-2008 01:58 PM
Re: Backup Issues
If that succeeded do a RAID UNBIND
Did all DRA devices dismount? If not issue DISMOUNTs for the DRA devices not dismounted yet.
Mount all DRA devices with MOUNT/OVER=ID/NOASSIST. If that fails...fix a DRA underlying problem.
If that worked for all DRA devices dismount them and do the RAID BIND command (parameters are somewhere in SYSTARTUP:*.COM - hopefully).
/Guenther
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2008 05:07 AM
03-20-2008 05:07 AM
Re: Backup Issues
$ raid analyze/units dpa300
Processing _DPA300:[000000]RAID$CONFIGURATION_MANAGEMENT.SYS
%RAID-I-OPENERR, error opening _DPA300:[000000]RAID$CONFIGURATION_MANAGEMENT.SYS
-RMS-E-DNF, directory not found
-SYSTEM-F-VOLINV, volume is not software enabled
Processing _DPA300:[000000]RAID$BC1.SYS
%RAID-I-OPENERR, error opening _DPA300:[000000]RAID$BC1.SYS
-RMS-E-DNF, directory not found
-SYSTEM-F-VOLINV, volume is not software enabled
%RAID-F-ANERR, check analyze report
$
$ raid analyze/units dpa301
Processing _DPA301:[000000]RAID$CONFIGURATION_MANAGEMENT.SYS
%RAID-I-OPENERR, error opening _DPA301:[000000]RAID$CONFIGURATION_MANAGEMENT.SYS
-RMS-E-DNF, directory not found
-SYSTEM-F-VOLINV, volume is not software enabled
Processing _DPA301:[000000]RAID$BC1.SYS
%RAID-I-OPENERR, error opening _DPA301:[000000]RAID$BC1.SYS
-RMS-E-DNF, directory not found
-SYSTEM-F-VOLINV, volume is not software enabled
%RAID-F-ANERR, check analyze report
$
$ raid analyze/units dpa302
$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2008 05:15 AM
03-20-2008 05:15 AM
Re: Backup Issues
Try to look for RAID related messages in SYS$MANAGER:OPERATOR.LOG
Look for SYS$MANAGER:RAID$DIAGNOSTICS_*.LOG. Any error messages in there ?
The command to decode the RAID errorlog entries is:
$ RAID ANAL/ERROR SYS$ERRORLOG:ERRLOG.SYS
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2008 06:22 AM
03-20-2008 06:22 AM
Re: Backup Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2008 06:27 AM
03-20-2008 06:27 AM
Re: Backup Issues
The DPA disks are showing a very high error count. Did you check $ RAID ANAL/ERR ERRLOG.SYS - maybe you were overwhelmed by the amount of output ?
If nothing else help, follow the advice given by Guenter - he knows the RAID software stuff !
First find the RAID BIND commands in your startup files then proceed as suggested...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2008 07:37 AM
03-20-2008 07:37 AM
Re: Backup Issues
How can I tell if that is our local disk array or the fabric SAN?