Results 1 to 3 of 3

Thread: Backup Problem

  1. #1
    Join Date
    Mar 2008
    Posts
    1

    Unanswered: Backup Problem

    Good Morning,

    Running ASE 12.0 on a HPUX11.11. Regulary we getting the following Error during the midnight full dumps/stripes:

    ************************************
    Mar 14 01:28:14 2008: A00: SYBMULTBUF ERROR: Error writing to archive device /danzas1/dump/vie07hpr1ss/vie07hpr1ss_eupszgp_dmp. Atte
    mpted to write 65536 bytes, 40959 bytes were written.
    Mar 14 01:28:14 2008: Backup Server: 4.145.2.22: [3] Error for device '/danzas1/dump/vie07hpr1ss/vie07hpr1ss_eupszgp_dmp'. Error wri
    ting to archive device /danzas1/dump/vie07hpr1ss/vie07hpr1ss_eupszgp_dmp. Attempted to write 65536 bytes, 40959 bytes were written.
    Mar 14 01:29:00 2008: Backup Server: 4.15.2.2: Label validation error: seek to trailer labels failed.
    Mar 14 01:29:01 2008: Backup Server: 4.41.1.1: Creating new disk file /danzas1/dump/vie07hpr1ss/vie07hpr1ss_eupinnp_dmp.
    Mar 14 01:29:01 2008: Backup Server: 6.28.1.1: Dumpfile name 'eupinnp08074014DD' section number 1 mounted on disk file '/danzas1/dum
    p/vie07hpr1ss/vie07hpr1ss_eupinnp_dmp'
    ************************************

    The dumps on the archive device are ok, we try to restore and it works.
    Shut down and restart the backup and data server has no effect. Shut down and restart the HPUX Cluster has no effect. There are no SYBMULTBUF or DEFUNCT processes. The archive device is a 70GB RAID5 Volume (EVA5000) with operational status OK. It should not be a hardware issue.

    Any ideas for solving this Error?
    Thank you and greetings
    Susanna

  2. #2
    Join Date
    Sep 2003
    Location
    Switzerland
    Posts
    443
    Check with your SA if large files is enabled on the Unix side. Think its SAM in Unix. Also, probably you have done this, but check your dump file system and /tmp to make sure its not full.

  3. #3
    Join Date
    Sep 2003
    Location
    Switzerland
    Posts
    443
    Also, hope this works in HP.

    Do, ipcs -a and paste the output. It could be that you have too many defunct shared mem segments hanging around, although the error doesnt match this, its good to get rid of defunct shared mem segments, as it results in odd errors in backup servers.

    You should have only one shared mem segment for ASE and one for Backup Server.

    If you have many sybase owned shared memory segments and if the nattach column is Zero, that means you can get rid of it as its not used.

    To get rid of a defunct shared mem segment.

    Do.

    ipcrm -m <shmem_number>

    If you are not sure, just paste the output of ipcs -a and I can walk you thro it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •