Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 12-19-2017, 06:05 AM
sampa17 sampa17 is offline
Member
 
Join Date: Dec 2017
Posts: 4
sampa17 has 10 reputation points
Smile 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 at 08:34 AM.
Reply With Quote
  #2  
Old 12-20-2017, 06:56 AM
sampa17 sampa17 is offline
Member
 
Join Date: Dec 2017
Posts: 4
sampa17 has 10 reputation points
Default

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

Quote:
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.
Reply With Quote
  #3  
Old 12-20-2017, 06:57 AM
sampa17 sampa17 is offline
Member
 
Join Date: Dec 2017
Posts: 4
sampa17 has 10 reputation points
Question 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 !
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 11:22 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.