File System Auditor 2.x move database from one server to another (4272044)

Voltar

Feedback enviado

Este artigo resolveu um problema para você?

Selecione a classificação

Título

File System Auditor 2.x move database from one server to another
Descrição

File System Auditor 2.x move database from one server to another

Resolução

The information in this article applies to:

File System Auditor Version 2.x and higher

HOW TO:

Move the database from one server to another

This article describes the process of moving the File System Auditor database from one SQL Server 2005 installation to another SQL Server 2005 installation. The same steps can be followed for SQL 2008.

In some cases (such as limited disk space) it may be necessary to move File System Auditor database from one SQL Server installation to another SQL Server installation located on a different server. The following steps describe how to complete this process.

This task can be accomplished through the use of File System Auditor’s Database Wizard or through the use of Microsoft SQL Management Studio.

The first section applies to the use of the Database Wizard.

The second section applies to the use of SQL Management Studio.

Before using either method it is recommended that you stop the agents on all servers that you are gathering data from in the File system - Agent Configuration Console. Not doing so could lead to a failure of being able to detach the database due to it being in use while attempting to move it.

Make sure the agent is stopped not only on any server you have but on all nodes of any cluster you may be monitoring as well. If an “in use” error still occurs stopping and restarting the “SQL Server” will help end the problem as well.

Right click open image to view full size

Section 1:

To accomplish this task using File System Auditor’s Database Wizard perform the following:

The first step is to detach the database from the current server.

Click Start ---> Programs ---> ScriptLogic Corporation ---> File System Auditor 2 ---> Database Wizard.

Select Detach Database from the main menu under and then click Next.

Verify that the Server Name field specifies the name of the computer that currently houses the SLFileAuditor database.
Verify the name of the File System Auditor Database. (The default database name is SLFileAuditor)
Specify whether to use Windows authentication or SQL authentication. (The default authentication method for FSA is Windows Authentication).
Click Next.

Click Finish then click Close on the Output Results/Messages window.
Click OK to the "Operation completed successfully!" information dialog.

Now click Cancel to exit the Database Maintenance Utility Wizard.

The next step is to copy the database files from the Data folder of the current SQL server to the Data folder of the target SQL server. These files will be the same name as the database. Both the .ldf and .mdf files should be copied. (The default database and file names are SLFileAuditor).

Paste these files into the target Microsoft SQL Server Data directory.

The next step in this process is to attach the database files to the target SQL Server.

Click Start ---> Programs ---> ScriptLogic Corporation ---> File System Auditor 2 ---> Database Wizard.
Select Attach Database from the main menu, and then click Next.

Click the Browse button to locate the SQL server that the SLFileAuditor database files were copied to.
Select the server name and then click OK.
The Database Name field should not need to be reconfigured. This should be displaying the name of the database that was detached previously. (The default database name for FSA is SLFileAuditor)
Choose whether to use Windows authentication or SQL authentication and then click Next. (If SQL authentication is selected, the username and password fields should be configured with the account information provided by the database administrator)

Using the ellipses button, browse to the local folder to locate the database files.
Select the SLFileAuditor file, click Open and then click Next.

Click Finish and then click OK to the "Operation completed successfully!" information dialog.
Click Cancel to exit the Database Maintenance Utility Wizard.

Now open the File System Auditor Agent Configuration Console.

Click Start ---> Programs ---> ScriptLogic Corporation ---> File System Auditor 2 ---> Agent Configuration Console.
Click OK to the error message stating that FSA cannot open the database.
- This error has occurred because the database has been detached from the original SQL server.

Once in the application, we can go ahead and change the actual SQL instance that is attached to each agent running on the monitored servers

Click the Change database Settings

Change the Server Name to reflect the name of the SQL Server that the database was copied to.
Leave the Database Name the same.
Configure the Username and Password fields with a SQL account or Windows Authentication Account, making sure to specify domain\username for the windows authentication method.
Once these parameters have been configured, click OK.
Repeat this step for each computer agent that needs to be configured.
Next Right click each server and choose Start Auditing from the drop down menu.

After Auditing has been started on all servers and cluster nodes your move is complete.

All new audit events will now write to the SQL Server database.

Start the Reporting Configuration Console
Click Start ---> Programs ---> ScriptLogic Corporation ---> File System Auditor 2 ---> Report Configuration Console.

Create a new report and add in the new database information.

Your new reports will now be gathering data from the new database location.

Section 2:

To accomplish this task through Microsoft SQL Management Studio perform the following:

Click Start ---> Programs ---> Microsoft SQL Server 2005 ---> SQL Server Management Studio.

Select the server that the File System Auditor database is currently located on and then click Add.
Click Next.

Select whether to use Windows authentication or SQL authentication and then click Next. (FSA default authentication method is Windows authentication.)
- If SQL authentication was selected, enter SQL username and password. Configure these fields with the account information provided by the database administrator and then click Next.
If Windows authentication was selected just click connect.

The SQL server that was just connected to should now be visible in the left window pane of Management Studio Object Explorer.

Expand the server that houses the FSA database and then expand databases.
Right click the SLFileAuditor database and select Tasks.
Select Detach Database from the context menu.

On the next screen, verify that there are no current connections to the database (if there are click the clear button to close those connections and verify the STATUS displays the message "Ready".

If connections are active refer to start of this guide on how to stop agents from running in the console before proceeding.

Click OK.

Click OK to the process will occur and your database will disappear from the listed databases on the left.

The next step is to copy the database files from the Data folder of the current SQL server to the Data folder of the target SQL server. These files will be the same name as the database. The default database and file names are SLFileAuditor. Both the .ldf and .mdf files should be copied.

Paste these files into the target MS SQL Server’s Data directory.

The next step in this process is to attach the database files to the target SQL Server.

Again open the SQL Management Studio on the new SQL server.
In the left hand panel of the new server’s Database list right click on the word Databases and choose the Attach option.

The Attach Database dialog box should now appear.

Click the add button to browse for the database files.

Navigate to the folder where the .mdf and .ldf files were copied to. (The default location is the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data folder). Select the .mdf file and then click OK.

The Attach Database dialog box should now look like the following. Note that the .ldf file was automatically located.

Click OK on this screen.

You should now see the Database you have attached in the left pane

You can now exit your SQL Management Studio

The configuration of the target SQL Server is now complete.

Now open the File System Auditor Agent Configuration Console.

Click Start ---> Programs ---> ScriptLogic Corporation ---> File System Auditor 2 ---> Agent Configuration Console.
Click OK to the error message stating that FSA cannot open the database.
- This error has occurred because the database has been detached from the original SQL server.

Once in the application, we can go ahead and change the actual SQL instance that is attached to each agent running on the monitored servers

Click the Change database Settings

Change the Server Name to reflect the name of the SQL Server that the database was copied to.
Leave the Database Name the same.
Configure the Username and Password fields with a SQL account or Windows Authentication Account, making sure to specify domain\username for the windows authentication method.
Once these parameters have been configured, click OK.
Repeat this step for each computer agent that needs to be configured.
Next Right click each server and choose Start Auditing from the drop down menu.

After Auditing has been started on all servers and cluster nodes your move is complete.

All new audit events will now write to the SQL Server database.

Start the Report Configuration Console
Click Start ---> Programs ---> ScriptLogic Corporation ---> File System Auditor 2 ---> Report Configuration Console.

Create a new report and add in the new database information.

Your new reports will now be gathering data from the new database location.

Feedback enviado

Este artigo resolveu um problema para você?

Selecione a classificação

Solicitar um artigo da base de conhecimento

Conteúdo recomendado

Produto(s):

Tópico(s):: How To

Histórico do artigo:: Criado em: 6/26/2009
Última atualização em: 5/7/2023

Search All Knowledge Base

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

File System Auditor 2.x move database from one server to another (4272044)

Título

Descrição

Resolução

Leave a Comment