On 17/02/16 10:47, Matt . wrote:
I have tested your way out and it seems to be OK.
The reason why I need this was is so I can perform a stop and
ipa-backup before I start my backup to my backupserver. (pre-command).
If I use ipa-backup directly it errors between the stop of ipa and the
actual ipa backup. I need to check that out further.
An ipactl start is not needed it seems as the ipa-backup command seems
to start ipa at any time again.
Do you understand/agree here ?
unfortunately I don't understand. The backup procedure AFAIK should work
# ipa-backup && rsync -r /var/lib/ipa/backup/ backup.example.test:/ipa/
You ca run it manually or place it into the crontab or use it in your
It will backup the ipa server with necessary stop and start and then
copy the new backup to the backup server.
Still I don't see the need for stopping the server manually.
ipa-backup calls "ipactl start" . If you remove the else branch it
will not start the server.
2016-02-17 8:00 GMT+01:00 David Kupka <dku...@redhat.com>:
On 16/02/16 20:26, Matt . wrote:
I'm fugiring out if it's possible to strip the ipa start and stop from
the backup method and actually do a fullbackup manually started.
Any idea ?
you can perform data only backup where freeipa server is still running
(ipa-backup --data --online).
But IIUC you want full backup with stopped freeipa sever only want to
manually run sequence ipactl stop ; ipa-backup ; ipactl start
Could you please explain why do you need such behavior? Honestly, I'm unable
to find use for this.
There's no way how to do it without touching the code. If you don't mind
editing code just remove two else branches starting on lines 293 and
316 in ipaserver/install/ipa_backup.py (on recent Fedoras located in
With this change full backup will be performed on running server unless you
stopped it before. It can result in inconsistent data in backup archive.
Manage your subscription for the Freeipa-users mailing list:
Go to http://freeipa.org for more info on the project