Rocket D3 | mvBase

 View Only
  • 1.  D3 database maintenance and administration

    Posted 6 days ago
    Good morning Rocketeers!

    Thanks much for the very helpful replies to my last thread...has already proven valuable.

    For D3, I would like to know what Rocket suggests for regular tuning, maintenance, administration.

    If possible, I had hoped to hear from the general D3 Rocketeer community, what practices they adopted for tuning, maintenance, and administration of the D3 database...

    THX in advance for your helpful replies!

    ~Doc

    ------------------------------
    [Doc] [Ruckel]
    [IT Guy]
    [Southwest Traders]
    [Temecula] [CA] [USA][Doc]
    ------------------------------


  • 2.  RE: D3 database maintenance and administration

    Posted 6 days ago

    Hy my tip is...

    every 3 months do a full restore.

    install linux updates, reinstall d3, reload patchs, then restore d3 files... the speed increases so much, i have i big database 200 GB, only for my data  ( not counting index space) .. a few months ago my backup was taking 16 hours to write... after the full restore is now done in 3 hours +-



    ------------------------------
    Alberto Leal
    System Analyst
    Millano Distribuidora de Auto Pecas Ltda
    Varzea Grande MT BR
    ------------------------------



  • 3.  RE: D3 database maintenance and administration

    Posted 6 days ago
    Wow Alberto, that is a full restore!

    Do you perform any Linux patching in between your quarterly restores?

    How often do you resize files and does that prevent performance degradation in you opinion?

    ~doc

    ------------------------------
    [Doc] [Ruckel]
    [IT Guy]
    [Southwest Traders]
    [Temecula] [CA] [USA][Doc]
    ------------------------------



  • 4.  RE: D3 database maintenance and administration

    Posted 6 days ago
    Edited by Alberto Leal 6 days ago
    I monitor my files daily, checking sizes, indexes, files that are used a lot, but have a lot of historical data, I move to secondary files to leave in the primary file only the information from the last 10 years (my programs are adjusted to read both files according to the date requested in the search), I use a lot of indexes, and dictionaries, and I constantly run a list-locks and list-lockq to see the files that are taking longer to be released, when I identify a pib that is taking longer than expected I run check.pib XX all (where XX is the number of the pib) to see what files it is open, what programs it is running, if it is stuck in a loop


    and about linux updates, you have to be extremely careful, I never update with the server running, as I work on a XEN server I create a snapshot, turn off d3, turn off the VM, create the SNAPSHOT then start the update, to avoid any problems, and backup copying is never enough... always have it in more than one location

    ------------------------------
    Alberto Leal
    System Analyst
    Millano Distribuidora de Auto Pecas Ltda
    Varzea Grande MT BR
    ------------------------------