CMS Backup - backup.success

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • sampa17
    Member
    • Dec 2017
    • 4

    CMS Backup - backup.success

    Hi Guys !!!
    Does anybody knows how the /cms/maint/backup/backup.success is update ?

    When I check the CMS data daily backup, the logs entry shows that backup is perfect, as follows:

    tail /cms/maint/backup/back.log

    End date: 43084(12/16/2017)
    status: Backing up Historical data: wvector
    (ACD = 1)
    status: Updating backup history ...
    state: 1
    error:
    status: Last backup finished 12/19/2017 01:35:38.
    state: 0
    /cms/install/bin/compress_backup successfully finished: Tue Dec 19 01:11:55 BRST 2017
    =======================


    But, the /cms/maint/backup/backup.success keeps on the same date.

    ls -l
    total 408
    -rw-rw-r--. 1 root cms 30598 Dec 19 01:11 back.log
    -rw-rw-r--. 1 root cms 100305 Dec 18 01:06 back.log.01
    -rw-rw-r--. 1 root cms 100278 Dec 12 01:06 back.log.02
    -rw-rw-r--. 1 root cms 100294 Dec 6 01:06 back.log.03
    -rw-rw-rw-. 1 root cms 2 Dec 19 01:11 backup_mt.err
    -rw-rw-rw-. 1 root cms 40361 Dec 19 01:11 backup_mt.out
    -rw-rw-rw-. 1 root cms 4247 Dec 18 17:39 backup_mt.out.01
    -rw-rw-r--. 1 root cms 0 Oct 19 14:43 backup.success
    -rw-r--r--. 1 root root 2 Oct 31 01:54 threads_num
    ================================================

    The cms group was setup by me.
    Before was root root, but the scenario was the same with no updating for backup.success.

    Does anybody can help me ?

    Thaks in advance and sorry for my english !!!

    Claudio
    Last edited by sampa17; 12-19-2017, 09:34 AM.
  • sampa17
    Member
    • Dec 2017
    • 4

    #2
    UPDATING ...
    A friend post a comment about it on other forum ...

    kyle555 (TechnicalUser)19 Dec 17 16:42
    Mine does the same. Ask Avaya maybe? Best guess is that is a 0 byte file and is trying to tell you that life is good since Oct 19. If your backup failed today, it might be Dec 19 backup.fail and if it works on the 20th, then you'll have a backup.success with that date until it fails again.

    I suppose its more informative to let you know your backups have been successful since X.

    The script probably says "on fail, rm -rf backup.success, touch backup.fail" and the inverse when it works so it creates the backup.success if it doesn't exist already, but does pretty much nothing if it already exists. Just a guess.

    Comment

    • sampa17
      Member
      • Dec 2017
      • 4

      #3
      Updating ...

      I'm looking for the right backup script to check how it works and under what condition it uses the "touch $LOGSUCCESS" to update the "backup.sucess" file.

      Lets waiting to see if somebory know more about CMS backup process and can shere it with us.

      Thanks in advance, to all !

      Comment

      Loading