Jagdish Devaku
asked on
Log Shipping & Copy-Only to the same database
Hi,
I got stucked with the implementation of Log Shipping on our servers.
The issue is that the database 'A' is already configured with copy-only log and that will be restored to a database 'B' in different database. This entire process is configured using SSIS.
Now we need to implement Logshipping on database 'A' to database 'C'.
When running the both, there is a conflict and the jobs are failed to restore logs on both 'B' and 'C' databases.
But all the A,B,C databases are important and needs to be up and running all the time.
Database 'A' needs to be in sync with 'B' (Every 1hr copy-only log restores the db. 'B' should be in read write mode except during restoring)
Database 'A' needs to be in sync with 'C' (Planning for logshipping. 'C' can be only ready only or no recovery mode. every 15 mins log files need to be restored to C database.)
How can I implement logshipping without disturbing copy-only log. Is there a possibility to do this. If No, can you please suggest a better way for this?
Thanks in advance.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you configure Database Mirroring, then
* Server B would be in restoring state and hence can't be accessed
* Server C can't be mirrored since a server can be mirrored only to a single destination.
* Server B would be in restoring state and hence can't be accessed
* Server C can't be mirrored since a server can be mirrored only to a single destination.
ASKER
Thanks for you comments
rrjegan17,
Currently we cant go with the transactional replication as most of the tables doesn't have primary keys. We already have a plan to do this, but this take takes some time.
Is there any possibility to do this?
can we make a database from recovery to norecovery without restoring log using query?
ASKER
lcohan,
Right now I can't go with Mirroring.
Right now I can't go with Mirroring.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
rrjegan,
Thanks for the suggestions.
Copy-only backups suggested by you-- Will this works? I feel there will be a conflict.
Actually we got a method which is working. We are doing this totally by using scripts. I am posting everything in a article and will post the link here.
Thanks.
Thanks for the suggestions.
Copy-only backups suggested by you-- Will this works? I feel there will be a conflict.
Actually we got a method which is working. We are doing this totally by using scripts. I am posting everything in a article and will post the link here.
Thanks.
>> Copy-only backups suggested by you-- Will this works? I feel there will be a conflict.
If you use Copy-only backups, then it won't conflict.
But Regular backups would do conflict.
If you use Copy-only backups, then it won't conflict.
But Regular backups would do conflict.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
JagdishDevaku,
Will check on your article by this weekend and provide my comments accordingly..
Will check on your article by this weekend and provide my comments accordingly..
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
rrjegan17,
Thanks for your comments.
You are right on shrinking log, but it is required in our scenario. Even though we are scheduling it, we created a job for and will executed on requirement.
Scheduling Transactional Log Backup Maintenance plan should do it.---
Yes, this can be done using maintenance plans. The reason why I written them in scripts is I have a table (kind of master table) in secondary servers to track all the actions on primary and secondary servers. Anyways this a good suggestion, but I need to check it whether it works for me or not.
Thanks again.
Thanks for your comments.
You are right on shrinking log, but it is required in our scenario. Even though we are scheduling it, we created a job for and will executed on requirement.
Scheduling Transactional Log Backup Maintenance plan should do it.---
Yes, this can be done using maintenance plans. The reason why I written them in scripts is I have a table (kind of master table) in secondary servers to track all the actions on primary and secondary servers. Anyways this a good suggestion, but I need to check it whether it works for me or not.
Thanks again.
Sure and kindly revert with any clarifications.
ASKER
Thanks for your support.
Best way would be to implement Replication in your scenario.
Simple, Configure Transactional Replication from Server A to both Server B and C.