HP Cisco MDS 9020 Cisco MDS 9000 Family Storage Media Encryption Configuration - Page 266

Restoring Fabric Manager Server Database, Database Backup and Restore Operations

Page 266 highlights

Restoring Fabric Manager Server Database Appendix E Database Backup and Restore Send documentation comments to [email protected] Restoring Fabric Manager Server Database To restore the Fabric Manager Server database, use the pg_restore command. cd $ INSTALLDIR/bin ./pgrestore.sh 02252008.data (on Linux and Solaris operating systems) pgrestore.bat 02252008.data (on Windows operating system) The backup restore process requires the server to be stopped. Note In all operating systems, the scripts run pg_restore command to restore the database. Database Backup and Restore Operations When implementing the Fabric Manager Server backup and restore operations, note the following guidelines: • The new media keys created after the backup of the database are lost after the restore operation since the backup copy does not have the latest media keys. • If there are new tape backup groups and tape volume groups created after the database backup, the property should be set to true in smeserver.properties before starting the Fabric Manager Server. This will synchronize the new volume group keys to the KMC. sme.kmc.sync.model.at.startup=true This property is also applicable for any tape volume group rekey operation. • If a master key is rekeyed after the database backup, then restoring the data of the previous database makes the cluster unusable. After the master key rekey operation, make a backup of the database and discard the copies of the previous database backup. Cisco MDS 9000 Family Storage Media Encryption Configuration Guide E-2 OL-18091-01, Cisco MDS NX-OS Release 4.x

  • 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
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280

Send documentation comments to [email protected]
E-2
Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
OL-18091-01, Cisco MDS NX-OS Release 4.x
Appendix E
Database Backup and Restore
Restoring Fabric Manager Server Database
Restoring Fabric Manager Server Database
To restore the Fabric Manager Server database, use the
pg_restore
command.
cd $
INSTALLDIR/bin
./pgrestore.sh 02252008.data
(on Linux and Solaris operating systems)
pgrestore.bat 02252008.data
(on Windows operating system)
The backup restore process requires the server to be stopped.
Note
In all operating systems, the scripts run
pg_restore
command to restore the database.
Database Backup and Restore Operations
When implementing the Fabric Manager Server backup and restore operations, note the following
guidelines:
The new media keys created after the backup of the database are lost after the restore operation since
the backup copy does not have the latest media keys.
If there are new tape backup groups and tape volume groups created after the database backup, the
property should be set to true in smeserver.properties before starting the Fabric Manager Server.
This will synchronize the new volume group keys to the KMC.
sme.kmc.sync.model.at.startup=true
This property is also applicable for any tape volume group rekey operation.
If a master key is rekeyed after the database backup, then restoring the data of the previous database
makes the cluster unusable. After the master key rekey operation, make a backup of the database and
discard the copies of the previous database backup.