11-16-2005 12:37 PM - edited 07-04-2021 11:20 AM
Hi,
1) BBSD version 5.2 was able to execute the backup and restore functions for BBSM servers. BBSD 5.3 does not support that anymore, what are the files that must be backup, where reside the configuration parameters ?
2)NTP service is not included in the provided OS services, can we add it from Callmanager NTP add-on program or if not, what are the strategy to be used for network synchronization of the clock.
thanks
Solved! Go to Solution.
11-22-2005 08:02 AM
You have couple of options to backup BBSM data:
1) Stop SQL Server and copy the C:\ATCOM\DATA folder to a media capable of holding this folder. Build the new server with the same name and setup as the original, then place the contents copied earlier in the same location. The C:\ATCOM\EKGNKM folder should also be copied in the same way. Caution: The new server must match the same software version
and patches as the original server.
2) You can also backup the database by exporting the most important tables. The port mappings are stored withing Port_Map table in AtDial database. So you can perform export of Port_Map and Switches tables to text files and import the files after BBSM
re-installation.
Here is the procedure:
Export tables to txt files and place files somewhere safe:
---
bcp AtDial..Port_Map out c:\portmap.txt -c -T
bcp AtDial..Switches out c:\switches.txt -c -T
after upgrade import the files:
---
bcp AtDial..Port_Map in c:\portmap.txt -c -T
bcp AtDial..Switches in c:\switches.txt -c -T
Please note procedure mentioned above will only copy portmap and
switches. If you use AccessCodes it will be necessary to backup table
Access_Codes.
3)A lot of our customer also use the Norton Ghost utility to make an identical copy of
disk.
In either way I strongly suggest to make backup of C:\ATCOM\DATA and
C:\ATCOM\EKGNKM before reinstalling and place it somewhere safe.
I do not believe there is any issue running and NTP client on the BBSM. The only gotcha I remember is not to run the MS NTP server as part of IIS.
11-22-2005 08:02 AM
You have couple of options to backup BBSM data:
1) Stop SQL Server and copy the C:\ATCOM\DATA folder to a media capable of holding this folder. Build the new server with the same name and setup as the original, then place the contents copied earlier in the same location. The C:\ATCOM\EKGNKM folder should also be copied in the same way. Caution: The new server must match the same software version
and patches as the original server.
2) You can also backup the database by exporting the most important tables. The port mappings are stored withing Port_Map table in AtDial database. So you can perform export of Port_Map and Switches tables to text files and import the files after BBSM
re-installation.
Here is the procedure:
Export tables to txt files and place files somewhere safe:
---
bcp AtDial..Port_Map out c:\portmap.txt -c -T
bcp AtDial..Switches out c:\switches.txt -c -T
after upgrade import the files:
---
bcp AtDial..Port_Map in c:\portmap.txt -c -T
bcp AtDial..Switches in c:\switches.txt -c -T
Please note procedure mentioned above will only copy portmap and
switches. If you use AccessCodes it will be necessary to backup table
Access_Codes.
3)A lot of our customer also use the Norton Ghost utility to make an identical copy of
disk.
In either way I strongly suggest to make backup of C:\ATCOM\DATA and
C:\ATCOM\EKGNKM before reinstalling and place it somewhere safe.
I do not believe there is any issue running and NTP client on the BBSM. The only gotcha I remember is not to run the MS NTP server as part of IIS.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide