Skip to main content
commvault.com commvault.com
Solved

Sybase cross server restore (linux)

  • September 29, 2022
  • 2 replies
  • 633 views
R
Byte
Forum|alt.badge.img+1

Hello All, 

Did any of you performed cross server sybase restore ? I have a task to restored Prod to sandbox. 

 

But the restore is failing with different error each time. 

 

If you are successful with cross server Sybase restore, Please share you experience. 

Thank you. 

 

Description: Loading database failed :[WARNING: In order to LOAD the master database, the ASE must run in single-user mode. If the master database dump uses multiple volumes, you must execute sp_volchanged on another ASE at LOAD time in order to signal volume changes. Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE boot directory. Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE boot directory. Could not establish communication with Backup Server 'SYB_BACKUP'. Please make sure that there is an entry in Sysservers for this server, and that the correct server is running. ] Source: 

 

 Loss of control process SrvSybAgent.exe. Possible causes: 1. The control process has unexpectedly died. Check crash dump or core file. 2. The communication to the control process machine umbdc-cvt-034.umbcloud.local might have gone down due to network errors. 3. If the machine umbdc-cvt-034.umbcloud.local is a cluster, it may have failed over. 4. The machine umbdc-cvt-034.umbcloud.local may have rebooted. 5. Antivirus/Malware software may be blocking the process. Please ensure that all exclusions are in place: http://documentation.commvault.com/commvault/v11/article?p=8665.htm Source: umbdc-cvt-034, Process: JobManager

 

Loading database failed :[WARNING: In order to LOAD the master database, the ASE must run in single-user mode. If the master database dump uses multiple volumes, you must execute sp_volchanged on another ASE at LOAD time in order to signal volume changes. Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE boot directory. Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE boot directory. Could not establish communication with Backup Server 'SYB_BACKUP'. Please make sure that there is an entry in Sysservers for this server, and that the correct server is running. ]

 

 

Regards, 

Rajes

Best answer by Mahender Reddy

@Rajes_Singh 


To perform Sybase cross server restore, please follow below procedure.

1. On destination, We need the Sybase Server (dataserver) to be shutdown and backupserver should be up and running.
2. The sa user password on the destination should be same as source. Because, you are restoring source master db, so the sa password should be the same to start the db
3. Then run the restore ensuring to select Sybase Create Devices from the Commvault GUI.

View original
Did this answer your question?

2 replies

M
Vaulter
Forum|alt.badge.img+5

@Rajes_Singh 


To perform Sybase cross server restore, please follow below procedure.

1. On destination, We need the Sybase Server (dataserver) to be shutdown and backupserver should be up and running.
2. The sa user password on the destination should be same as source. Because, you are restoring source master db, so the sa password should be the same to start the db
3. Then run the restore ensuring to select Sybase Create Devices from the Commvault GUI.

Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19

@Rajes_Singh from which console are you performing the recovery, what kind of recovery are you performing (full server) and which version are you running? we've had issues in the past as well and we were performing the restores via Command Center and it was failing because Command Center was lacking some capabilities in comparison to the Commcell Console. 

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings