HP 3PAR StoreServ 7200 2-node HP 3PAR System Reporter 3.1.0 Software User& - Page 220

Extracting Data from the Database with sysbck, sysbck

Page 220 highlights

Figure 67 Microsoft Office Excel Internal Error If you experience a problem with a recovered copy of the workbook (Figure 68 (page 220)), try starting with a fresh copy of System Reporter workbook. Figure 68 Microsoft Excel Recovery Error Extracting Data from the Database with sysbck Sometimes it is necessary to extract some of the data from the System Reporter database. For example, you may want to send that data to HP to help in analyzing a performance problem. This section describes how you can extract all or some of the data from a database using the sysbck command into a set of files that can then be loaded into a different database. NOTE: If necessary, when using sysbck to extract large amounts of data from a database, the contents may be saved in separate 2 Gb files. NOTE: The sysbck command is recommended when extracting a relatively small sampling of the database. The command creates a file with SQL statements to insert each row of extracted data into a database. While this is convenient for subsequently loading the data into a database, especially if the database is of a different type than the source database, the file size can be quite large. If you want to extract the entire database or large sections of the database, it is preferable to dump the entire database as described in "Dumping the Entire Database" (page 224). On Windows the sysbck.exe executable is installed in the System Reporter directory (by default C:\Program Files\3PAR\System Reporter), and on Linux the sysbck.bin executable is installed in the /usr/bin/ directory. The parameters for the sysbck command are shown below: # ./sysbck.binUsage: sysbck [parameters] The [parameters] are -dbtype -dbhost Type of database: sqlite, mysql or oracle. For mysql: name or IP address of host. Default is localhost. 220 Troubleshooting System Reporter

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231

Figure 67 Microsoft Office Excel Internal Error
If you experience a problem with a recovered copy of the workbook (
Figure 68 (page 220)
), try
starting with a fresh copy of System Reporter workbook.
Figure 68 Microsoft Excel Recovery Error
Extracting Data from the Database with
sysbck
Sometimes it is necessary to extract some of the data from the System Reporter database. For
example, you may want to send that data to HP to help in analyzing a performance problem. This
section describes how you can extract all or some of the data from a database using the
sysbck
command into a set of files that can then be loaded into a different database.
NOTE:
If necessary, when using sysbck to extract large amounts of data from a database, the
contents may be saved in separate 2 Gb files.
NOTE:
The
sysbck
command is recommended when extracting a relatively small sampling of
the database. The command creates a file with SQL statements to insert each row of extracted
data into a database. While this is convenient for subsequently loading the data into a database,
especially if the database is of a different type than the source database, the file size can be quite
large. If you want to extract the entire database or large sections of the database, it is preferable
to dump the entire database as described in
“Dumping the Entire Database” (page 224)
.
On Windows the
sysbck.exe
executable is installed in the System Reporter directory (by default
C:\Program Files\3PAR\System Reporter
), and on Linux the
sysbck.bin
executable
is installed in the
/usr/bin/
directory.
The parameters for the
sysbck
command are shown below:
# ./sysbck.bin
Usage:
sysbck [parameters]
The [parameters] are
-dbtype <dbtype>
Type of database: sqlite, mysql or oracle.
-dbhost <dbhost>
For mysql: name or IP address of host.
Default is localhost.
220
Troubleshooting System Reporter