[Info-ingres] Refresh dev databases

Paul White shift7solutions at gmail.com
Wed Jan 19 00:04:03 UTC 2022


Hi Rich,

At my large sites, I use "log shipping" to replicate production 
databases to a DR standby machine then use copydb/unloaddb  from that 
location when I need.  One of the benefits of this arrangement is to be 
able to rollforward the DR database to a point in time for analysis and 
to assist reproducing transient problems.

clonedb and relocatedb cannot be used when users are connected. 
clonedb/relocatedb can be used on a replicated database after the final 
incremental journal is applied with:

rollforwarddb -c +j -incremental -rollback dbname
or
rollforwarddb -c +j -incremental_finish -rollback dbname

For more info see: 
https://communities.actian.com/s/article/Incremental-Rollforwarddb

I can confirm log shipping replication works very well for non x100 
databases on both Windows and Unix/Linux.  Sorry I don't have any 
experience replicating x100.

Paul White

&


On 19/01/2022 2:46 am, Rich Ford wrote:
> I've been looking at using clonedb to do a refresh of some dev databases from production. I've only used unloaddb before but checking out clonedb.
> One issue that concerns me is the fact that users can't be online which is a major drawback.
>
> Has anyone had success using clonedb?
>
> Rich
> _______________________________________________
> Info-ingres mailing list
> Info-ingres at lists.planetingres.org
> https://lists.planetingres.org/mailman/listinfo/info-ingres



More information about the Info-ingres mailing list