Skip to Content
avatar image
Former Member

backupserver utiltiy

HI,

I'm in testing installation of our existing ASE12.5.4(64bit) on Rhel 6.6(64 bit) machine on a virtual machine, and I've successfully run dataserver but the backupserver utility failed prompting segmentation fault error. I've already tried export LD_POINTER_GUARD=0 but no luck upon retrying to install backupserver. I tried to extract /bin/backupserver and /bin/sybmultbuf from the installed developer edition of SAP ASE 16 and import it to my testing environment and backupserver works. The question is what happened if we use higher version of backupserver utility came from installed developer edition of ASE16? what are the pros and cons of that?

Hoping for your inputs. Thanks advance.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Dec 09, 2016 at 03:04 PM

    My recollection is that the definition of some of the RPC parameters used to communicate between ASE and Backup Server during dumps changed in between these two versions, so attempts to DUMP will fail with some sort of datatype mismatch or invalid pointer error.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 09, 2016 at 03:26 PM

    I've already tested ASE12.5 on RHEL 6.6 64bit and ASE 6 as its backupserver and found no errors dumping and loading small database. I'm just wondering for the large database size if backupserver came from ASE 16 dev edition can handle large database. would there be any limitations on that?

    Thanks advance

    Add comment
    10|10000 characters needed characters exceeded

    • You stated:

      "I tried to extract /bin/backupserver and /bin/sybmultbuf from the installed developer edition of SAP ASE 16 and import it to my testing environment and backupserver works."

      If by this you mean you placed the ASE 16 backupserver/sybmultbuf binaries into the ASE 12.5.4 installation directory ... that's not a good idea, mixing versions like that. If you want to run the ASE 16 backupserver then you should install ASE 16 under its own $SYBASE directory and run the associated backupserver under this new $SYBASE directory. [On linux/unix it's quite easy to run different versions of Sybase/SAP software; just install the software packages under different $SYBASE directories and make sure you source the associated $SYBASE/SYBASE.sh resource file before starting a server; for the different versions of software to communicate with each other you just need to make sure the $SYBASE/interfaces files are identical (eg, define as soft links that point to a master interfaces file).]

      ----------------

      As for whether the ASE 16 backupserver will work with your ASE 12.5.4 dataserver ... *shrug* ... Bret's already mentioned a potential conflict so you're left with running some tests (dump/load database, dump/load transaction, multiple stripes, compression (?)) against your actual/full-sized ASE 12.5.4 databases to see if you can in fact use the ASE 16 backupserver.

      ----------------

      'course, another option would be to troubleshoot the ASE 12.5.4 backupserver issue to see if you can get the 12.5.4 backupserver working properly (thus eliminating the need for the ASE 16 backupserver).

  • avatar image
    Former Member
    Dec 12, 2016 at 01:47 AM

    Thanks for the replied Mark.

    Will do some testing. Aside from mentioned (dump/load database, dump/load transaction, stripes, compression..) is there anything else that will cause conflict when using ASE16 backupserver?

    Add comment
    10|10000 characters needed characters exceeded