Backing up the system

Identify the iBase databases

If you don't know where all the iBase databases to be backed up are located, you can find them by checking the MRU List Manager from the Tools menu in iBase or iBase Designer on users' workstations.

The list of files that you obtain from the MRU List Manager provide the paths and names of the databases. Locating the iBase security (.ids) and database (.idb) files will reveal most of the others. The security file is usually located in the same folder as the databases it secures.

Determine the types of database in use

The iBase security and database files will help you to identify the locations of any SQL Server databases that iBase uses. To determine whether the security and database files are SQL Server or Access:

1. In an iBase client (not iBase Designer), log in as a system administrator, and open each database that you identified earlier.

2. Select File > Security File Properties and File > Database Properties in turn.

In the case of SQL Server security and database files, the properties dialogs will display the database name and the SQL Server name. In general:

• An iBase database name will not contain any spaces, and will always contain at least one underscore character.

• An iBase database will also have an associated audit log database that has the same name as the database, with a suffix of _Log.

• An iBase security file database is suffixed with _Sec.

You must make a note of the names of the SQL Server and the iBase databases, ready for the next part of the process.

Pause scheduled operations

Before backing up, ensure that the Scheduler service on the server that runs scheduled tasks is not performing imports or exports. Then, place the service in the "stopped" state to prevent future imports or exports from running.

If the Scheduler is in the process of running an import or export, wait for it to complete before you stop the service.

Note: For information on how to stop a Windows service, refer to Microsoft's documentation.

Perform the backup

When you have a full list of all the files and databases involved, you can start the backup process. Ensure that you make copies of all the files, and that you store them in a safe location. You will need both network and database admin permissions in order to back up your system successfully.

To back up the files:

1. Log in to the server with network administrator rights.

2. Identify the files to be backed up from the list that you prepared earlier.

3. Back up the files to a safe location.

4. Restore the backup to a test environment to ensure all key files have been recorded.

To back up a SQL Server iBase database:

1. Log in to the system with database administrator rights.

2. Verify that there are no users accessing the database.

3. Set the user access option on the iBase SQL Server database to single-user.

   Provided that you don't log out of SQL Server, only you will have access to the iBase databases, preventing changes from being made during the backup.

4. Perform the backups (including any Analysis Services databases and Audit Log databases for this database).

5. If you're backing up in preparation for another activity (an upgrade, for example), then take the database offline.

Note: Changing the user access option to single-user does not prevent users from accessing the database altogether if you log off. However, it does restrict the amount of change that can occur if a user does access the database. If you're upgrading multiple databases, perform steps 3 and 4 sequentially for each database in turn before you log out.

If you need help with backing up iBase, contact i2 Support.