On 05/23/2011 11:02 PM, Steven Jones wrote:
> ie on FDS I think you can do an export to a flat file and then import 
> it....that way the backup client can backup a flatfile and not attempt to do 
> the database....
>
> regards
>
>
>
> _______________________________________________
> Freeipa-users mailing list
> Freeipa-users@redhat.com
> https://www.redhat.com/mailman/listinfo/freeipa-users

We have not documented it yet.
But the general approach:
A) If you run just one server (which is not recommended) run a full
system backup frequently. It will be much simpler than trying to do
backup of all pieces and config files affected by IPA.
B) If you run replicated environment and lost one of the servers you can
stand up another server.
Variant 1: You want to preserve replica's name
a) Install a new replica on a new hardware/VM following a standard replica
installation procedure.
b) Remove replication agreements with the old replica that became
unavailable.

Variant 2: You want to preserve replica's name
a) Create a package for the failed replica following the standard procedure
(ipa-replica-prepare)
b) On the IPA server that generated the replica run:
ipa-replica-manage init replica.example.com
This will initialize replica as it will be empty at the beginning
c) Install replica on a new hardware/VM

This is the general direction but we have not done extensive testing
(thus have not documented it)

-- 
Thank you,
Dmitri Pal

Sr. Engineering Manager IPA project,
Red Hat Inc.


-------------------------------
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/



_______________________________________________
Freeipa-users mailing list
Freeipa-users@redhat.com
https://www.redhat.com/mailman/listinfo/freeipa-users

Reply via email to