Well, I guess I should clarify, that it's true it's not an exact copy. We copy several tables (not all) from one database to another using the Drop table... create table... select * into.
(drop and create in case there are any schema changes that are made). And yes, these tables are only a snapshot in time of the source tables.
The destination database has reporting tables and stored procs for reporting that are processed on its own SQL instance that are not available in the source.
Our support company take backups and our table processing times are overlapping these backups that are causing Link server errors. Apart from that, we just need to find a quicker way of transferring data whichever way that is as the database is growing quite quickly.
We have audit tables that store times, processed tables etc which are good enough for what we're trying to achieve at the moment so we aren't so concerned about extra logging/auditing for the moment. When we start to develop a data warehouse in future, this will change.