We want to copy an enterprise geodatabase (SDE) from one location to another without shutting down the source database. We can use either SQL Server or Oracle. The dba's tell us they need to shutdown the database, which is an issue because users could have geoprocessing scripts running. ESRI replication is not an option because we have ETL's that delete and recreate feature classes.
Can you run a complete back up to a file and then transfer the back up file to the remote location and import/extract there?
With Oracle, you can try using exp or expdb for a full export to a dmp file that you can import in an different Oracle instance.
Jesús de Diego
If you have Oracle RMAN, I believe that it can take a hot backup of the database and then that could be restored to a new instance of Oracle.
Hot and Cold Backups - Overview - Oracle - Oracle - Toad World
SQL Server information:
These might be some good spots to start.........
The feedback I'm getting from the DBA's is that RMAN hot backup or exp/exdb can't be automated. We need to be able to automate the process.
For sure exp/imp process can be automated....
Jesús de Diego
Ideally nightly, but every other night would also work. We went down the RDBMS replication path but it did not work because the destination needed to be read only and the SDE schema needs write access.
Think that I am out of ideas. I do find it difficult that you could not script or schedule RMAN to do something like that.......
This is not an ideal way but you could create a python script that makes a FGDB each night and copies all feature class, datasets, and tables to it. Once they are in the FGDB you can copy them into other database. You could always go directly from the SDE and to SDE via the script and skip the FGDB if your system permits that. Then use windows task scheduler to automatically run the script at a certain time (ex: 2 am).
Problem with this method is that you are making a copy so you have to transfer everything not just the stuff that changed. In addition, you will need to delete the stuff at the destination before copying to prevent errors and duplication. In addition, you will have to copy every version you have if you are using versioning and they won't be linked properly in the destination.