|
Concerning to Kaspersky Administration Kit 6.0 MP1
This article describes how to go to a new Administration Server and/or SQL-server: it means the Server database can be or already have been backed up and can be restored. If the Administration Server or SQL-Server has crashed and the database has not been backed up, follow the link, to get the necessary recommendations.
General relocation principles
How to go a new SQL-server and Administration Server
How to reconnect Administration Server to a new SQL-server
How to reconnect an Administration Server to a new database of SQL-server (it might be damaged)
How to go to a new Administration Server (the SQL-server remains the same)
General relocation principles
The three following conditions are necessary, to restore functions of the logical network after the Administration Server and /or the Server database has (have) been relocated:
1. the structure of the logical network (grouping of client computers and slave Servers, tasks, policies, Server properties) should be saved
2. certificates of the Server on client computers and on a new Server should correspond (coincide)
3. the Server address (NetBIOS-name, DNS-name or IP-address), by which client computers will connect to the Server, should be saved
 The Server address which the client computers will use to connect to the Server is defined in the Administration Agent’s properties: in the Console open properties of a client computer > the Applications tab > Kaspersky Network Agent > Properties > the Settings tab).
To fulfill the 1st and 2nd conditions, backup the database (using klbackup utility or create backup of Administration Server task) and restore it on a new Server. Together with the database the network structure and the certificate of the old Server are restored. If you can save the Server address on the computer on which you are going to install a new Server, then fulfill the 3rd condition too. Otherwise, to specify a new Server address to client computers, use
First restore the Server database from the backup, then run the Change Administration Server task on the old Administration Server.
 In order to be able to use the backup copy of the Server database the instances of old and new databases should coincide. By default, the database name is KAV. In Kaspersky Administration Kit 6.0 collation of the old and new SQL-servers is not necessary.
The password for the backed up database and the Server certificate are required to restore the backup copy. Beginning from Kaspersky Administration Kit version 5.0.1104 the certificate is backed up automatically. If you use an earlier version of the complex, save the certificate with a password when backing up (using the savecert key).
Top of page
How to go a new SQL-server and Administration Server
1. Backup the Administration Server database using klbackup utility or create backup of Administration Server task
2. Install new SQL-server (according to system requirements)
3. Install a new computer on which a new Administration Server is going to be installed (it is recommended to save the address of the old Administration Server).
4. install an Administration Server on this computer
-
better install the Server to the same folder in which the previous Administration Server was installed)
-
as SQL-server define new SQL-server (step 2)
-
give the name of the old database to new database
5. Restore the database of the backup copy on a new Server
6. Open the Administration Console and connect to a new Server. Make sure all client computers have established connection with the new Server (computer icons are bright) – it might take some time (about 60 minutes).
Old Administration Server and SQL-server can be deleted only after ALL client computers have connected to a new Server!
7. If the connection fails to be established you probably have not saved the address of the old Server. Then define the address of a new Administration Server for client computers the following ways:
1. in the Administration Console connect to the old Administration Server
2. create the Change Kaspersky Administration Server task for all computers
3. when the task is executed, in the Administration Console connect to a new Server
4. make sure all client computers have connected to the Server (the computer icons are bright) it may take some time (60 minutes)
First restore the Server database from the backup, then run the Change Administration Server task on the old Administration Server.
1. run the klmover utility on all client computers with the parameter of the new Server address (for example, writing it to login-script)
2. once the klmover utility has run on all workstations, connect to a new Server in the Administration Console.
3. make sure all client computers have connected to the Server (the computer icons are bright) it may take some time (60 minutes)
Top of page
How to reconnect Administration Server to a new SQL-server
1. Backup the Administration Server database using klbackup utility or create backup of Administration Server task
2. Install new SQL-server (according to system requirements)
3. Uninstall an Administration Server
4. Install an Administration Server on he same computer
-
Better install it to the same folder, to which the old Administration Server was installed;
-
as SQL-server define new SQL-server (step 2)
-
give the name of the old database to new database
5. Restore the database of the backup copy on the Administration Server
6. Open the Administration Console and connect to the Server. Make sure all client computers have established connection with the new Server (computer icons are bright) – it might take some time (about 60 minutes).
Top of page
How to reconnect an Administration Server to a new database of SQL-server (it might be damaged)
1. Backup the Administration Server database using klbackup utility or create backup of Administration Server task
2. Delete MSDE, if you use it and install once again If you use SQL, delete the database of the old Server.
3. Delete the Administration Server (installed Administration Server cannot be reconnected to another database).
4. Install an Administration Server on the same computer:
-
better install it to the same folder, to which the old Administration Server was installed;
-
as SQL-server define previous SQL-server
-
give the name of the old database to new database
5. Restore the database of the backup copy on the Administration Server
6. Open the Administration Console and connect to the Server. Make sure all client computers have established connection with the new Server (computer icons are bright) – it might take some time (about 60 minutes).
Top of page
How to go to a new Administration Server (the SQL-server remains the same)
1. Backup the Administration Server database using klbackup utility or create backup of Administration Server task
2. Install a new computer on which a new Administration Server better saving the address of the old Administration Server.
3. Reinstall MSDE, if you use it (delete it and then install once again) If you use SQL, delete the database of the old Server.
4. install an Administration Server on a new computer
-
better install it to the same folder, to which the old Administration Server was installed;
-
as SQL-server define new SQL-server
-
give the name of the old database to new database
5. Restore the database of the backup copy on the new Server
6. Open the Administration Console and connect to the Server. Make sure all client computers have established connection with the new Server (computer icons are bright) – it might take some time (about 60 minutes).
Old Administration Server and SQL-server can be deleted only after ALL client computers have connected to a new Server!
7. If the connection cannot be established you probably have not saved the address of the old Server. Then define the address of a new Administration Server for client computers using the klmover utility:
1. run the klmover utility on all client computers with the parameter of the new Server address (for example, writing it to login-script.
2. once the klmover utility was run on all workstations, connect to a new Server in the Administration Console.
3. make sure all client computers have connected to the Server (the computer icons are bright) it may take some time (60 minutes)
Top of page
| 
Knowledge base
Product Info
System requirements
100 
2008 Jul 31 14:23
