[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

348.0. "backup-f-writeerr" by MDR01::NIEVES (MCS Madrid) Wed Mar 19 1997 05:52

    Hi,
    
    a customer says backup is playing an strange game. This is the problem.
    He has a cluster with 2 VAXES 6XXX, and 2 ALPHAS. 
    
    He usually does backup from the VAX with VMS 5.5-2 of all the disks,
    about 11 disks, and has no problem.
    
    When he does  the backup from the ALPHA with VMS 6.2 of all the disks,
    using the same procedure, he receives the following error:
    
    %BACKUP-F-WRITEERR, Error writing RBSPAXP:[LIS]7-MAR_$1$DRA2.LIS;1
        -RMS-E-EXT, ACP file extend failed
        -SYSTEM-F_EXQUOTA, process quota exceeded.
    
    He has a .com procedure which submits when the system starts every
    morning. The strange thing is why is this procedure going wrong when
    this is done from the Alpha and not from the VAX.
    
    We went through the user quotas and system parameters and changed them, 
    now they are very high (in the Alpha).
    
    Thanks in advance,
    
    Nieves
T.RTitleUserPersonal
Name
DateLines
348.1what about *disk* quotas?CUJO::SAMPSONWed Mar 19 1997 07:322
    Did he check for *disk* quotas on the destination disk?
    Use the SYSMAN DISKQ command set to look at and change these.
348.2Check Quota Ratios, Per DocumentationXDELTA::HOFFMANSteve, OpenVMS EngineeringWed Mar 19 1997 08:1824
   I will assume you (.0) have checked COMET for any previous reports.

   This does not appear to be a disk quota problem (.1), it appears to
   be a process quota problem.

   Blindly changing the process quotas may/will lead to this error, as
   BACKUP is programmed to try to use the available quotas, and if the
   quotas are not in the correct ratio, problems such as this have been
   reported.

   Have the customer verify the BACKUP username meets the documented
   minimum process quotas for BACKUP operations, and that the quota
   values meet the documented ratios and relationships, as documented
   in the OpenVMS System Management: Essentials manual "Using BACKUP"
   chapter.

	--

   Be aware that this VMScluster will have skewed proxy files and all
   proxy mantenance must be performed from the OpenVMS Alpha systems.
   (I'd encourage the customer to upgrade the OpenVMS VAX systems to
   at least V6.2 -- OpenVMS V7.1 is the current release.)