7 dumping the entire database, 1 dumping the entire sqlite database, Dumping the entire database – HP 3PAR System Reporter Software User Manual
Page 362: Dumping the entire sqlite database
11.12
Dumping the Entire Database
3PAR System Reporter User’s Guide
System Reporter 2.8
11.7 Dumping the Entire Database
When you want to extract a large part of the database, it may be more efficient, both in time
and disk space, to dump the entire database instead of using
sysbck
. The method for
dumping the entire database depends on the database type. The process for SQLite is
11.7.1 Dumping the Entire SQLite Database
on page 11.12 while the process for
11.7.2 Dumping the Entire MySQL Database
please refer to the Oracle documentation.
11.7.1 Dumping the Entire SQLite Database
The SQLite database is just a file (by default
C:\Program Files\3par\System
Reporter\inservstats\inservstats.db
on Windows and
/var/inservstats/
inservstats
on Linux). However, if there are other files in the same directory created by
SQLite, such as a journal file (
inservstats.db-journal
) you cannot just copy the database
file to another location and open it as an SQLite database. The presence of the other files, such
as the journal file, indicates that the database is not in a consistent state. The recommended
way to get a copy is to follow these steps:
1
Stop the 3PAR System Reporter sampler service (Windows) or daemon (Linux) so that the
database is not active while you are making the copy.
2
If there is no other file (such as the journal file), the database is now consistent and you can
just copy the
inservstats.db
file.
3
If there is another file (such as the journal file), the database is still inconsistent. In this case,
you must first open the database with SQLite which will automatically apply the journal
changes. The easiest way to do this is to generate a report from the database using a web
browser. The web server will open the database, the journal changes will be automatically
applied, and the journal file will be automatically deleted. Then you can copy the database
file.
4
After the database file has been copied, you can re-start the 3PAR System Reporter sampler
service (Windows) or daemon (Linux).
NOTE: When executing
sysbck.exe
from any other directory on Windows,
ensure that the
PATH
environment variable is set to the System Reporter root
directory path (by default, this path is
C:\Program Files\3par)
.