How to deal with paused linux disk backup which is run by cron?
We made a shell script which contains command line below, and registered it to crontab for running weekly.
acrocmd backup disk --volume=1-1,Dyn5,Dyn6,Dyn7,Dyn8,Dyn9,Dyn10,Dyn11 --loc=/osbak --arc=$HOSTNAME --progress
Last week while running backup process with "acrocmd backup disk ~~" command line, /osbak filsystem became full.
We deleted files, but the backup process was still running.
So we checked logfile, and found logs as below.
|
Free up additional disk space to continue. You can either empty the Recycle Bin or delete old data files. Click Retry to try again or click Cancel to cancel the operation. There is not enough space in backup destination '/osbak/'. [R(Retry)/C(Cancel)] |
But this process is run by cron, so we cannot click R or C.
And this system doesn't have GUI, so we cannot resolve this with acronis gui.
So here's solutions that I thought:
1) kill process : I'm not sure there's no side effects.
2) stop activities : There're two activies which aren't completed state. Maybe I can stop those activities with "acrocmd stop activity --id=XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX" command. but I'm not sure there's no side effects, and I also don't know correct order of stop activities.
## activity list..
Backing up ${hostname} paused 20% ~~~~
Running backup plan 'Backup Now' ${hostname} running 20% ~~~~~
3) make backup process foreground : I think we cannot do this in linux.
4) send 'C' character to the running process : I think the backup process waiting for user's input, so maybe we can use send 'C'
I found some ways to do that, but they weren't worked well when I tested with other shell scripts.
Which one is best or is there any other suggestion??
Sadly this is not about an error state, rather it's a normal state.
But the reason why this state is a problem for us, we run the command "acrocmd backup disk " with cron on the linux server(not windows server), so this process is not connected with any tty session.
so we cannot send "R" or "C" to the process directly.
This process is alive very long time, so I think about how to stop this process.
Maybe we can kill the process or stop activities but I'm not sure those actions doesn't affect on my server.
If we ran this command on tty session , we can solve this problem with clicking "R" or "C" button on our keyboard.
But this process is run by cron daemon, so we cannot send "R" or "C" to the process with a keyboard typing.
Maybe this is kind of error log -- this is on the log file, but we cannot send any message to running acrocmd process.
log contents ======================
Click Retry to try again or click Cancel to cancel the operation.
There is not enough space in backup destination '/osbak/'.
[R(Retry)/C(Cancel)]
======================
I found some informations about send data with pipe, file descriptor of acrocmd is pipe currently, maybe the command below can solve this problem. But I cannot test this.
# echo "C" > /proc/26008/fd/0 ## can this command resolve this problem??
current state ========================
# ps aux | grep acrocmd
root 26008 0.0 0.0 591936 20888 ? Sl May27 6:52 /usr/lib/Acronis/CommandLineTool/acrocmd backup disk --volume=1-1,Dyn5,Dyn6,Dyn7,Dyn8,Dyn9,Dyn10,Dyn11 --loc=/osbak --arc=prodserver1 --progress
# ls -ltr /proc/26008/fd/0
lr-x------ root root 64 Jun 8 18:29 0 -> pipe:[2989265040]
===================================
Hello!
To address this situation, here are a few possible solutions you can consider:
-
Increase available disk space: You can try freeing up additional space on the destination filesystem (/osbak) to allow the backup process to continue. This could involve deleting unnecessary files or increasing the storage capacity of the filesystem.
-
Modify backup location: If feasible, you can consider changing the backup destination to a different filesystem or storage location with sufficient space available.
-
Implement disk space management: Set up a mechanism to monitor and manage disk space on the /osbak filesystem to prevent it from becoming full in the future. This could involve regular cleanup processes, archiving or deleting old backup files, or allocating more disk space to the filesystem.
-
If there is enough space and the error persists I would advise you to re-install the program. Unfortunately this version is out of lifecycle and there aren't any updates or support since many years ago.
Thanks in advance!