Aller au contenu principal

Acronis doesn't add schedules to crontab

Thread solved

I installed a backup console on Windows Server 2008 R2 SP1 64bit. 
For backup, I installed the agent on Linux server and add a schedule in the backup console. but no schedules are added to the crontab.

 

Manual backup is successfully done

 

I previously installed an agent connected to another backup server on that linux machine, and then it worked fine.


 
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 0
Commentaires: 2016

Hello Hyeong Seop Yun,

welcome to Acronis forums!

Did you miss any previously scheduled backup tasks on that machine?

I also recommend that you test if cron is running. Please go to a terminal and do

ps -A | grep cron

If it shows nothing, check cron status with ps -ef | grep cron 
Also do:

  • chkconfig --list | grep cron
  • check for log file in /var/log/cron
Maria Belinskaya wrote:

Hello Hyeong Seop Yun,

welcome to Acronis forums!

Did you miss any previously scheduled backup tasks on that machine?

I also recommend that you test if cron is running. Please go to a terminal and do

ps -A | grep cron

If it shows nothing, check cron status with ps -ef | grep cron 
Also do:

  • chkconfig --list | grep cron
  • check for log file in /var/log/cron

 

Thank you for the answer.

But cron is running.

Other schedules registered in cron run normally. 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 0
Commentaires: 2016

Hello Hyeong.

I advise that you open a case with Acronis Support Team for this issue investigation. You will be requested to collect Linux System Report and export your backup plan (which is not added to crontab).

 

This problem was related to cron file's attribution setting and solved it.

 

Thank you.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 0
Commentaires: 2016

Hello Hyeong,

thank you for sharing the output with forum users!