My question is difficult for me because the backup copy is created on the server (where the free space has been used up) and sent to a remote storage.
The documentation says that before creating a backup copy, for security purposes, the free space on the disk is first measured 2X of the used space, and then a copy is created if there is enough space.
My copy is not created and gives an error in the log:
================================
kolbaso
--------------------------------
Error: not enough disk space available (7408 mb) to perform the backup of kolbaso. ( 13488 mb * 2 = 26976 mb).
--------------------------------
There are 250 gigabytes in the HDD storage.
The server disk is 30 gigabytes
So now it turns out that there is no possibility to make a backup now?
What do you think, friends, maybe someone has encountered this, what should I do?
Is it possible to make settings so that the backup copy is immediately created on a remote storage?
Yes, that’s right.
You need to follow these steps, this is how you configure the option to store backups on a remote resource.
Now let’s take a break and relax.
Because we’ve fulfilled all the conditions in the documentation and will try to understand if it will work.
What happens when you run the backup script.
The script analyzes the disk size and if the used user space of 2x finds a place on the disk, then the backup is created.
If it doesn’t, the script stops for security reasons for the system.
We made sure that there is enough space and it will work if a backup is created.
If the script stopped for security reasons, after measuring the free space, then there will simply be nothing to send to the remote resource.
So, the backup is created locally, even if we correctly performed all the settings in the example you gave, and the storage will be successfully updated with new archives on schedule, this does not guarantee that we will receive a backup copy of the account there, the size of which is 2x greater than the size of the free space.
If the disk space used by the user is 2x less than the free disk space, then a backup will be created and sent to the remote storage.
Now, here is the question of the topic.
-Is it possible to make the script measure the availability of free space on the remote storage and create a backup there right away?
I would like to know how to do this
Best regards,
PS I tried very hard to explain, because I want to be useful as a token of gratitude for the support of my colleagues)
I don’t think this will work, because as you said correctly, a copy is created first, then transferred to the remote storage, and then deleted.
But if this is not so, and the creators of Hestia will correct me, then I myself wonder if this is possible))
Some hostings provide an additional hdd disk service.
It can be mounted to the backup folder and the script thinks that it is working with a local disk.
Here is a question for the developers. Will the backup script work in this case if the hdd disk is mounted as an additional one, and the backup copy is created locally
Thank you for your advice.
The incremental copies tool is great, we were able to set it up and make a backup copy.
It is interesting that there are many different files in the user folder, and not an archive, as expected.
Now the question arises, how to restore.
Maybe someone has documentation, many thanks
Here is another question.
Everything is configured according to the instructions, in the CLI
A schedule has appeared in the control panel interface, how many and what copies to store.
One thing is not clear, automatic backups are not going.
Everything is done manually correctly, we leave it for several days, nothing changes. I would like the backups to be updated.
Please tell me, who has similar experience.
