Requirements on the remote server

The SQL Server version must either be the same on both systems used or must be higher on the remote server than on the local server.

On the remote server, proceed as described in"Requirements" on page 48.

4.7.2

Configuration steps

To move the ServerView database from the local management station to the remotely installed SQL Server, proceed as follows:

1. Upgrade the local ServerView Operations Manager installation:

Log onto the management station as the local administrator. Upgrade the local ServerView Operations Manager installation to the current version. It is absolutely essential to use the same version intended for the remote installation. Otherwise the database schema will not fit.

2. Stop all applications and services with access to the ServerView database, especially the following services:

l ServerView Services

l ServerView Download Service

l ServerView JBoss Application Server 7

3. Save the following folders of the current local installation; a copy of this data is needed because uninstallation/reinstallation will have to be performed later on:

l ServerView Suite\svom\data\ServerView\SnmpExport\Logs

l ServerView Suite\svom\data\ServerView\SnmpExport\Tasks l ServerView Suite\svom\data\ServerView\SnmpInventory\InventoryTasks l ServerView Suite\svom\data\ServerView\InventoryArchives l ServerView Suite\svom\data\ServerView\Download\svtmpdir l ServerView Suite\svom\data\ServerView\Download\Tasks l ServerView Suite\svom\data\ServerView\OnlineUpdate\Logs l ServerView Suite\svom\data\ServerView\OnlineUpdate\Tasks l ServerView Suite\svom\data\ServerView\SnmpArchive\ArchiveTasks l ServerView Suite\svom\data\ServerView\SnmpArchive\Logs l ServerView Suite\svom\data\ServerView\Archive

l ServerView Suite /svom/data/ServerView/CSVFiles l ServerView

Suite/ServerView/ServerViewServices/scripts/ServerView/common/ mibs

4. Detach and copy the ServerView database from the local SQL Server instance:

The current SQL database must now be copied from the local server. Proceed as follows:

1. Determine the current path for the ServerView database files. The path is displayed in SQL Server Management Studio within the context menu ofdatabase–ServerViewDB–Properties–Files.

2. Detach the database using the corresponding SQL Server administration tools with the following functions:

Tasks–Detach(SQL Server Management Studio)

3. The database filesServerViewDB.mdfandServerViewDB_log.LDF are now removed from the instance and ready to be copied.

4. Copy the database files to another folder. You will need these files later to replace the ServerView database on the remote SQL Server instance.

5. Uninstall the local ServerView Operations Manager installation: The locally installed ServerView Operations Manager must now be

uninstalled on the management station. In order to work correctly without error messages, the ServerView database must be temporarily re-attached to the instance from its original path. Attach the database with the

corresponding SQL Server administration tools from the context menu of databases. The current path to the database file (ServerViewDB.mdf) must be specified in the dialogAttach(SQL Server Management Studio).

Perform the uninstallation, see"Uninstalling the Operations Manager software" on page 165.

6. New installation with remote SQL Server

Now start a new installation of ServerView Operations Manager on the management station and choose the optionUse existing remote SQL Server. Proceed as described in"Further procedure on the management station" on page 96.

7. Replace the ServerView database on the remote SQL Server:

Following installation, the ServerView database on the remote server must now be replaced with the database previously copied from the local installation. Proceed as follows:

1. Stop all applications on the management station and services with access to the ServerView database, especially servicesServerView Services,ServerView Download ServiceandServerView JBoss Application Server 7.

2. Open SQL Server Management Studio on the remote SQL Server and connect to the remote instance.

3. Get the current path for the ServerView database.

4. Detach the existing database on the remote SQL Server as described above for the local database.

5. Replace the database files with the corresponding files copied from the local server.

6. Re-attach the database.

8. If the database was upgraded from an earlier SQL Server version during migration, it is recommended that you run the following command on the

upgraded database (via Management Studio):

DBCC UPDATEUSAGE ('ServerViewDB')

9. In case your remote installation was performed with "sysadmin" access, you have to adapt theJBoss Service Logon Informationwindow. If a different domain user account was used than for the ’remote’ installation, the JBoss user account in the migrated database must be entered again:

1. Find out the value of<JBoss Accountname>and use it in the next steps:

OpenAdministrative Tools-Servicesand scroll to the service ServerView JBoss Application Server 7. ColumnLog On Ascontains the required value.

2. Find out the value of theServer_Instanceparameter in the configuration fileServerViewDB.ini.

3. Open SQL Server Management Studio: Connect with<Server_Instance>. SelectSecurity-Logins.

Look for<JBoss Accountname>and note spelling and upper and lower case.

4. Log in at the central management station and switch to the directory <Installation_path>\ServerView Services\scripts\ServerView\Tools. 5. Execute the following batch file located in this directory and apply the

<JBoss Accountname>:

GrantLoginJBoss.bat

10. If your remote installation was performed without "sysadmin" access, you must check and possibly add any domain accounts used for ServerView services in the migrated database:

1. Find out the accounts needed and use them in the next step: Open Administrative Tools-Servicesand note the accounts used for ServerView Services,ServerView Download ServiceandServerView JBoss Application Server 7.

2. Open SQL Server Management Studio and connect to the SQL Server instance. Check that these accounts are present underSecurity- Loginsand note the spelling in correct upper and lower case.

3. Log in on the central management station and switch to the following directory:

<Installation_path>\ServerView Services\scripts\ServerView\Tools 4. Execute the following batch file located in this directory and apply the

account names noted in the step above: GrantLoginSecure.bat.

NOTE: You will have to call the batch file separately for each account. 11. Back up the database on the remote SQL Server instance.

12. Copy the folders saved from the previous installation (as specified in step 3) to the corresponding folders on the local management station.

13. Finally, restart the servicesServerView Services,ServerView JBoss Application Server 7andServerView Download Serviceon the local management station.

Please wait about five minutes until all JBoss processes are completely restarted.

4.8

Changing the load distribution

ServerView allows you to influence the system load it incurs or the number of concurrent jobs.

The following services start jobs whose concurrent number may be defined in an inifile.

ArchiveService <scripts>/ServerView/SnmpArchive/SVArchiveServer.ini ExportService <scripts>/ServerView/SnmpExport/ExportServer.ini

InventoryService <scripts>/ServerView/SnmpInventory/ SVInventoryServer.ini <scripts>: directory<Installation_path>/ServerView Services/scripts

Each of these configuration files holds a variableConcurrentJobsAllowedin the sectionGLOBALS. The number given there states how many concurrent jobs are started.

Example

Archiving is activated for all servers and 100 manageable servers are present in the server list. IfConcurrentJobsAllowedis set to 30 in

SVArchiveServer.ini, there will always be at most 30 servers being archived at the same time. Once archiving is finished for one server of the 30 started jobs, then archiving for another server is started. This is repeated until all 100 servers are archived.

The current default values forConcurrentJobsAllowedare: SVArchiveServer.ini 30

DownloadServer.ini 30 ExportServer.ini 100 SVInventoryServer.ini 10

If you upgrade the Operations Manager software, the value for ConcurrentJobsAllowedparameter will be reset to the default value.

1. Before changing the number ofConcurrentJobsAllowed: Before changing the number ofConcurrentJobsAllowed, please ensure that no jobs of the respective service are running. For ArchiveService,DownloadServiceandExportServicethis can easily be verified via the respective GUI in the tab settings. If there are blue arrows displayed for the status of a task then a job is running for the server.

ForInventoryServiceplease check in the process list whether a process calledSVSnmpInventoryis running. In Linux you can view the process list via the commandps.

2. Effect of reducing the number of concurrent jobs:

Reducing the number of concurrent jobs has two effects: On the one hand it reduces the system load; on the other it increases the time required by a job to process a group of servers.