Archiving Best Practices and configurations

Version 2
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    Remedy AR System Server


    APPLIES TO:

    7.X, 8.X, 9.X, 18.X, 19.X



    DETAILS:

    Archiving Best Practices

    1.-Check the next options that can cause the archive process dont run:
        a.-Check if you have a Rank for the Archive Operation in the AR System Server Group Operation Ranking Form, for example:

    User-added image
        b.-
    Disable-Archive-Global T you can find this option on centralized configuration under Administration Console > System > General > Centralized Configuration > Component Name > com.bmc.arsys.server.shared > Disable-Archive-Global T
        c.-Disable-Archive:T you can find this option on the ar.conf or under Administration Console > System > General > Centralized Configuration > Component Name > com.bmc.arsys.server > Disable-Archive T
        d.-Disable Archive you can find this option on Administration Console > System > General > Server Information > Configuration Tap

    User-added image

    2.-Do not start (Mount) an archive while another archive is running. Always check the archive logs to see if an archive is running before starting an additional archive.

        a.-Archive logs are generally located in /ARSystem/db/ararchive.log
    archive.log example:
    archivelog
        b.-You can get more information about what is the archive doing with API/SQL/Filter logs from the moment when the archive process runs
    API/SQL/FIlter log with archive info example:

     API/SQL/Filter

    3.-Do not mount/run 2 or more archives at a time. If you have more than one archive that needs to run, start the first archive and let it run to completion before starting the second archive. Check the archive logs to see if the first archive is still running before starting a second. Starting 2 or more archives at a time can generate excessive system overhead and cause the entire process to completely stop, or consume an excessive amount of system resources which could cause other process outside of archiving to stop working.
    Note:The Archive process in the versions from 7.X to 18.X only use a single thread that's the reason we recommend to no try to run more than 1 policy at a time, in the version 19.X the Archive process uses multi thread to improve the performance of the archive process and the stability.

       4.-The initial run of any archive can take hours or days to complete this depend of the resources from the server and from the number of records waiting to be archived. After the initial archive run subsequent runs can complete in only a few minutes.
    Note:If you have more than 1 million of records to be archives our recommendation is to ask your DBA to truncate the database table.
     
    5.-Starting an archive:

        a.-Once an archive is started the first entries in the log will indicate what forms are about to be archived in relation to the archive policy that you are running:

    archive policy starting


    6.-The next log entry will include a count of how many records are actually being archived for each form related in the archive that is being run. Some archives policies have a large number of related forms, as where others may only have 1 or 2 related forms. There can be a gap or pause from when the log entry in item (a.) above and the log entry below is added. Do not take any additional archiving action during this pause. This includes stopping, starting, or disabling any archive policies. Additional actions can result in increased system overhead, resulting in a necessary restart of entire AR system process.
     

    User-added image
     
        a.-Once an archive is complete the below type of entry is written to the log before the archive engine moves on to the next enable archive.

    User-added image

    7.-There are two  Forms where you can run the Archive Policies:

        a.-AR System Archive Manager Console

    User-added image

        b.-AR System Archive Policy

    User-added image

    8.-You will notice 2 types of archives in the archive logs.

        a.-Continuous Archives - These are archive policies that are enabled and have specific frequency designations (Example: 24hrs). These policies will run automatically based upon the designated frequency.

        b.-Manually Run Archives - These archives show in the log once the Run Selected Policy Now button has been clicked on the Archive Manager Console.

    User-added image

        c.-You can also run the Archive Policy manually from the form AR System Archive Policy

    User-added image


    For more details about how the   'Archive Process' feature works the online documentation can be referenced with the following links: 
    Remedy - Server - Archive thread does not run after having enabled the Archive in Remedy
    How to configure archiving for AR server 9.X
    Archive Manager Console - policies configuration not persisting on restart
    AR System Archive Manager is really really slow

     


    Article Number:

    000167574


    Article Type:

    Product/Service Description



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles