Can you confirm the databases are configured in full mode on the sql server?
Have you completed an initial full backup of the SQL subclient yet?
You must have a backup in order to perform a Live Sync operation. If you have installed the SQL Server agent on the client, but have not yet performed a backup, then the software does not display any databases in the SQL Live Sync Options dialog box.
Note: You can only use the Live Sync feature with SQL databases that use the Full Recovery model.
Ricardo, I told you the same yesterday. I’m afraid the problem is that publico01 (source) has a SQLExpress version SQL 2014 while publico02 (destination) version SQL 2019 has a Standard.
Can you try to use a standard SQL 2014 instead of SQLExpress in source?
Also, not sure the commvault version you have in lab, SQL 2019 is supported in v11.16 onwards.
Please list the available destination instance to see what it is listed and if desired destination instance is selected it populates the destination client publico02 and once destination is selected the databases are displayed in square below:
The database team access the server and viewed that change some parameters and appear the database in commserv, i make full backup early and create the CDR, but have an error when start the replication:
Some questions to ask you: 1) After preparing the CDR for another server, didn´t migrate the transaction logs, does anyone know why this doesn´t work? Note: I had already setup to configure Live Sync and CDR. 2) Do i need to use live sync with the CDR and do a full backup before setup it on the CDR?
CDR stands for Continous Data Replication, so having the phase of Replication in Unavailable is normal status.
Why are you still using CDR? I already mentioned a few times that is not the proper way to migrate SQL from source machine to destination machine. You have already configured SQL Live Sync, this relies on SQL agent for backup and restore, CDR is not needed for SQL Live Sync to work so please don’t use it.
As a summary, you have already working in your lab the SQL Live Sync between source SQL client publico01 and destination SQL client publico02. Live Sync for SQL is used to have and SQL standby server in sync for the instance and databases specified from a source production machine. For performing a migration from 1 server to another, it is enough performing backup on source and restoring to destination.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.