Tripp Lite B097048INT Owners Manual for B093- B097- and B098-Series Console Se - Page 241

Backing Up the Configuration Off-Box

Page 241 highlights

15. Advanced Configuration First, check if the USB disk has a label: # /etc/scripts/backup-usb check-magic If this command returns "Magic volume not found", run the following command: # /etc/scripts/backup-usb set-magic To save the configuration: # /etc/scripts/backup-usb save config-20May To check if the backup was saved correctly: # /etc/scripts/backup-usb list If this command does not display "* config-20May", there was an error saving the configuration. The set-default command takes an input file as an argument and renames it to "default.opg". This default configuration remains stored on the USB disk. The next time you want to load the default config, it will be sourced from the new default.opg file. To set a config file as the default: # /etc/scripts/backup-usb set-default config-20May To load this default: # /etc/scripts/backup-usb load-default To load any other config file: # /etc/scripts/backup-usb load {filename} The /etc/scripts/backup-usb script can be executed directly with various COMMANDS or called from other custom scripts you may create. However, it is recommended you do not customize the /etc/scripts/backup-usb script itself. 15.1.9 Backing Up the Configuration Off-Box If you do not have a USB on your console server, you can back up the configuration to an off-box file. Before backing up, you need to arrange a method to transfer the backup off-box. This could be via an NFS share, a Samba (Windows) share to USB storage or copied off-box via the network. If backing up directly to off-box storage, make sure it is mounted. /tmp is not a good location for the backup, except as a temporary location before transferring it off-box. The /tmp directory will not survive a reboot. The /etc/config directory is not a good place either, as it will not survive a restore. Backup and restore should be done by the root user to ensure correct file permissions are set. The config command is used to create a backup tarball: config -e The tarball will be saved to the indicated location. It will contain the contents of the /etc/config / directory in an uncompressed and unencrypted form. Example nfs storage: # mount -t nfs 192.168.0.2:/backups /mnt # config -e /mnt/b098.config # umount/mnt/ Example transfer off-box via scp: # config -e /tmp/b098.config # scp /tmp/b098.config [email protected]:/backups The config command is also used to restore a backup: config -i This will extract the contents of the previously created backup to /tmp, and then synchronize the /etc/config directory with the copy in /tmp. One problem that may arise is a lack of space in /tmp to extract files to. The following command will temporarily increase the size of /tmp: mount -t tmpfs -o remount,size=2048k tmpfs /var 241

  • 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
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288

241
15. Advanced Configuration
First, check if the USB disk has a label:
# /etc/scripts/backup-usb check-magic
If this command returns “Magic volume not found”, run the following command:
# /etc/scripts/backup-usb set-magic
To save the configuration:
# /etc/scripts/backup-usb save config-20May
To check if the backup was saved correctly:
# /etc/scripts/backup-usb list
If this command does not display “
* config-20May
”, there was an error saving the configuration.
The set-default command takes an input file as an argument and renames it to “default.opg”. This default configuration
remains stored on the USB disk. The next time you want to load the default config, it will be sourced from the new default.opg
file. To set a config file as the default:
# /etc/scripts/backup-usb set-default config-20May
To load this default:
# /etc/scripts/backup-usb load-default
To load any other config file:
# /etc/scripts/backup-usb load {filename}
The
/etc/scripts/backup-usb
script can be executed directly with various COMMANDS or called from other custom scripts you
may create. However, it is recommended you do not customize the
/etc/scripts/backup-usb
script itself.
15.1.9 Backing Up the Configuration Off-Box
If you do not have a USB on your console server, you can back up the configuration to an off-box file. Before backing up, you
need to arrange a method to transfer the backup off-box. This could be via an NFS share, a Samba (Windows) share to USB
storage or copied off-box via the network. If backing up directly to off-box storage, make sure it is mounted.
/tmp
is not a good location for the backup, except as a temporary location before transferring it off-box. The
/tmp
directory will
not survive a reboot. The
/etc/config
directory is not a good place either, as it will not survive a restore.
Backup and restore should be done by the root user to ensure correct file permissions are set. The config command is used to
create a backup tarball:
config -e <Output File>
The tarball will be saved to the indicated location. It will contain the contents of the
/etc/config /
directory in an uncompressed
and unencrypted form.
Example nfs storage:
# mount -t nfs 192.168.0.2:/backups /mnt # config -e /mnt/b098.config
# umount/mnt/
Example transfer off-box via scp:
# config -e /tmp/b098.config
# scp /tmp/b098.config [email protected]:/backups
The config command is also used to restore a backup:
config -i <Input File>
This will extract the contents of the previously created backup to
/tmp
, and then synchronize the
/etc/config
directory with the
copy in
/tmp
.
One problem that may arise is a lack of space in
/tmp
to extract files to. The following command will temporarily increase the
size of
/tmp
:
mount -t tmpfs -o remount,size=2048k tmpfs /var