[BlackBetty]

Hi all,

I need to totally rebuild my BES 3.6 server due to problems outside of BES. Is there anywhere with documentation on how to backup all the database, rebuild and reattach all the handhelds afterwards?

Thanks in advance

Simon

[Kul]

Iam not sure about the DBs etc. but have a look at this.

http://www.blackberryforums.com/showthread.php?t=9019

[Digger]

Doc can be found on Blackberry's web site or Microsoft's (Using the OSQL command) to backup and restore the database. If the server name (BES name) and SRP's are the same as before, all you will have to do is import the user list. The users will have to do a synch from the DM to generate the keys and that should be it.

Please correct me if I missed anything...

[Northern_Monkey]

Do a maintenance plance, backup the transaction logs and database.

The following is our procedure which has bee tried and tested - it includes the install of SQL 2KSp3:

Prerequisites
In order to complete this procedure, the following will/may be required:
• A server machine running an operating system capable of supporting Microsoft SQL Server 2000 SP3, e.g. Windows 2000 Server or Windows 2003 Server.
• Optionally, a existing instance of SQL Server 2000 can be used. However, please note that Mixed-mode authentication needs to be enabled, and that the sa account password may be different from that used on a BES SQL database.
• Installation sources for SQL Server 2000 SP3 (Unless an existing instance is used).
• A recent backup of the BESMgmt data (BESMgmt_db_xxxxxxxxxxxx.BAK) and transaction log (BESMgmt_tlog_xxxxxxxxxxxx.TRN).
Installing Microsoft SQL Server on the server computer
Note: if there is already a suitable SQL Server that can be used as the BES SQL Server, this stage can be omitted. A suitable server will need to have SQL Server SP3 applied and have Mixed-Mode authentication enabled.
1. Install Microsoft SQL Server on the machine hosting the server with the following options, accepting the defaults otherwise. However, depending on the server build, it may be appropriate to locate the data and log files on separate volumes.
• SQL Server (Mixed-Mode) Authentication
• The sa password should be ***********
• Service account should be domain\BESAdmin account
2. Install SQL Server Service Pack 3 on the server, accepting the defaults.
3. Check that SQL Server can be accessed remotely by creating a connection in Enterprise Manager on a remote PC, using the sa login details.
Restoring the BESMgmt database from a backup
The following procedure can be carried out either on the server itself, or from a remote machine, using the Enterprise Manager and Query Analyser software packages.
1. Copy the most recent .BAK and .TRN backup files to a location on the server that is hosting the SQL Server database.
2. Determine the location of the Data folder for SQL Server. It is normally contained in the MSSQL folder which is installed by default at C:\Program Files\Microsoft SQL Server\MSSQL\Data, but is often moved to another drive, e.g. D:\MSSQL\Data.
3. Start the Query Analyser application (part of the SQL Server Client Tools) and connect to the current SQL Server. Log in with the sa account.
4. Enter the SQL script from Appendix A into the right-hand pane of Query Analyser.
5. Replace the placeholders (identified by <>) with the correct values for the server in question, as detailed in Appendix A.
6. Click the button on the toolbar to start the script running. It may take several seconds to run.
7. When completed, it should return results like the following:

Processed 6936 pages for database 'BESMgmt', file 'BESMgmt' on file 1.
Processed 1 pages for database 'BESMgmt', file 'BESMgmtLog' on file 1.
RESTORE DATABASE successfully processed 6937 pages in 4.468 seconds (12.717 MB/sec).
Processed 163 pages for database 'BESMgmt', file 'BESMgmtLog' on file 1.
RESTORE LOG successfully processed 163 pages in 0.197 seconds (6.762 MB/sec).

8. If the script failed, double-check the file paths and the location of the Data folder and run the script again. If the script still fails, try the next most recent backup files.

Thanx Sam for the documentation.