×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

CCM V3.3: STIrestore takes longtime cleaning database for publishing

Unanswered Question
Apr 22nd, 2003
User Badges:

Hello,

I've just restored a backup from a publisher in production to an other CCM in a test environment in order to try some functionallities without disturbing users.


The restore utility seems to have finished well. However, it stood for almost one hour at the line "cleaning database for publishing". So that i had been about to cancel the procedure.


Can somebody tell me what is really occuring to take so much time at that point ??


I include the stirestore.log:


[19:12:10] ______________________________________

[19:12:10]

[19:12:10] Cisco IP Telephony Applications Restore Utility

[19:12:10] by Spirian Technologies Inc

[19:12:10]

[19:12:10] Backup service 3.5.18

[19:12:10] Restore applet 3.5.18

[19:12:10] Viewer applet 3.5.18

[19:12:10] stiTape.dll 1.0.1093

[19:12:10] ______________________________________

[19:12:10]

[19:12:10] Opening stiRestore.log on 04/22/2003

[19:12:10] Local machine name is M2-CCM2

[19:12:10] Local IP address is 10.101.216.221

[19:12:10] Service account is Administrator

[19:12:10] Administrator has local administrative rights

[19:12:21] Opening backup media to create tree from C:\temp\v33-22apr2003_0200am.sti

[19:12:27] Finished getting file information from backup

[19:12:41] Staging files from archive

[19:13:25] Opening backup media to extract catalog C:\temp\v33-22apr2003_0200am.sti

[19:13:25] Finished getting file information

[19:13:25] Closing backup media

[19:13:25] Catalog created successfully

[19:13:26] All files in staging directory compared successfully

[19:13:26] Restoring Cisco CallManager target M2-Ccm2

[19:13:26] M2-Ccm2 was configured as a publisher

[19:13:26] M2-Ccm2 published to subscriber M2-Ccm1

[19:13:34] Stopping Cisco CallManager service

[19:13:35] Stopping Cisco Database Layer Monitor

[19:13:38] Stopping Cisco IP Voice Media Streaming App

[19:13:39] Stopping Cisco Messaging Interface

[19:13:41] Stopping Cisco TFTP service

[19:13:42] Stopping Cisco Telephony Call Dispatcher

[19:13:43] Stopping SQL Server Agent service

[19:13:45] Stopping DC Directory service

[19:13:46] Stopping Cisco RIS Data Collector service

[19:13:47] Stopping Compaq Foundation Agents

[19:13:49] Stopping Compaq NIC Agents

[19:13:50] Stopping Compaq Server Agents

[19:13:52] Stopping Compaq Storage Agents

[19:13:53] Stopping SNMP service

[19:13:56] Stopping World Wide Web Publishing service

[19:14:03] Removing database subscriptions from the subscribers

[19:16:25] Skipping restoration of all subscriptions

[19:16:25] Removing database publishing from Ccm0307

[19:16:36] Stopping Cisco Database Layer Monitor

[19:16:39] Stopping SQL Server

[19:16:42] Starting SQL Server

[19:17:51] Service has been started

[19:17:57] Closing remaining connections to Ccm0307 database on M2-Ccm2

[19:17:59] Dropping Ccm0307 from M2-Ccm2

[19:18:07] Restoring Ccm0307 database to M2-Ccm2

[19:18:35] Database Ccm0307 on server M2-Ccm2 restored successfully

[19:18:35] Fixing restored users on database Ccm0307

[19:18:38] Cleaning database for publishing

[20:10:32] Recreating database publishing on Ccm0307

[20:10:32] Starting SQL Server Agent service

[20:10:40] Service has been started

[20:10:41] Invoking process osql -S M2-Ccm2 -i C:\Progra~1\Cisco\Bin\PublishRestore.sql -o PublishRestoreSQL.log -E

[20:12:23] Stopping SQL Server Agent service

[20:12:41] Closing remaining connections to CDR database on M2-Ccm2

[20:12:43] Dropping CDR from M2-Ccm2

[20:12:50] Restoring CDR database to M2-Ccm2

[20:13:02] Database CDR on server M2-Ccm2 restored successfully

[20:13:02] Fixing restored users on database CDR

[20:13:05] Restoring CDR files on M2-Ccm2

[20:13:07] Restoring CDR files to C:\Program Files\Cisco\CallDetail\CDR

[20:13:19] Starting SQL Server Agent service

[20:13:26] Service has been started

[20:13:27] Recreating database subscription to M2-Ccm2 on remote server M2-Ccm1

[20:14:44] Creating database snapshot for replication. This process may take 15-30 minutes depending on the size of your database

[20:14:53] Starting Cisco CallManager service

[20:15:06] Service has been started

[20:15:07] Starting Cisco IP Voice Media Streaming App

[20:15:08] Service has been started

[20:15:08] Starting Cisco Messaging Interface

[20:15:09] Service has been started

[20:15:09] Starting Cisco TFTP service

[20:15:15] Service has been started

[20:15:16] Stopping SQL Server Agent service

[20:15:34] Stopping Cisco CDR Aupair service

[20:15:34] Stopping SQL Server

[20:15:39] Starting SQL Server

[20:16:44] Service has been started

[20:16:45] Starting Cisco Database Layer Monitor service

[20:17:04] Service has been started

[20:17:05] Starting Cisco Telephony Call Dispatcher

[20:17:07] Service has been started

[20:17:08] Starting SQL Server Agent service

[20:17:16] Service has been started

[20:17:17] Starting DC Directory service

[20:17:29] Service has been started

[20:17:29] Service: DCDirectory is already started

[20:17:29] Service: DCDirectory is already started

[20:17:31] Starting Cisco RIS Data Collector service

[20:17:36] Service has been started

[20:17:36] Starting Compaq Foundation Agents

[20:17:40] Service has been started

[20:17:41] Starting SNMP service

[20:17:41] Service: SNMP is already started

[20:17:42] Starting World Wide Web Publishing service

[20:17:45] Service has been started

[20:17:46] Restoring DC Directory database

[20:17:47] Stopping DC Directory service

[20:17:48] Invoking restore command

[20:18:01] Invoking schema update command

[20:18:11] DC Directory schema update completed

[20:18:11] Starting DC Directory service

[20:18:22] Service has been started

[20:18:22] Service: DCDirectory is already started

[20:18:22] Service: DCDirectory is already started

[20:18:22] Restoring DC Directory configuration file

[20:18:22] Invoking replication command

[20:18:34] Invoking replication command

[20:18:45] DC Directory database restored successfully

[20:18:45] Restoring files to TFTPPath folder

[20:19:16] Restoring BAT CSV Files

[20:19:16] Restoring BAT Templates

[20:19:16] Closing stiRestore.log on 04/22/2003

[20:19:16] RESULT: M2-Ccm2 has been successfully restored


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
albert_coll Tue, 04/22/2003 - 12:40
User Badges:

As an additional information,

Both CCM are running the latest patches available:

ciscocm.3-3-2-spB.exe

win-OS-Upgrade.2000-2-3spJ.exe

SQL2K-MS02-061.exe

SQL2K-ServicePack3.1-0-1.exe

MCSbackup.3-5-18.exe


Actions

This Discussion