Hp XP Continuous Access Software Manual de usuario Pagina 339
- Pagina / 412
- Tabla de contenidos
- SOLUCIÓN DE PROBLEMAS
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
HA Failover and failback 339
SVOL_PSUS) between P-VOL and S-VOL may need to handled by HA
control scripts.
Async-CA specific behavior
Before the S-VOL is changed to SSUS, an SVOL-takeover will try to copy
non-transmitted data, which remains in the FIFO queue (sidefile) of the
P-VOL, to the S-VOL side.
In the case of an ESCON/FC link failure, this data synchronize operation
may fail. Even so, the SVOL-takeover function performs the force split to
SSUS, and enables usage of the secondary volume.
Non-transmitted data, which remains in the FIFO queue (sidefile) of the
P-VOL, will be moved to a BITMAP to empty the FIFO queue, and the pair
state will be set to PSUE.
Caution Ordering information regarding the non-transmitted data that is moved to
a BITMAP will be lost. The data represented in the bitmap can be
resynchronized (lost) as the new S-VOL by issuing pairresync –swaps for
recovery from a SVOL-SSUS-takeover at the takeover site (Host B).
Recovery from a SVOL-SSUS-takeover
After the recovery of the ESCON/FC link, this special state (PVOL_PSUE
and SVOL_PSUS) will be changed to COPY state. Thus, the original
S-VOL becomes the NEW_PVOL and overwrites the NEW_SVOL, by
issuing the
pairresync –swaps command at the takeover site (Host B).
- HP StorageWorks 1
- RAID Manager XP 1
- User’s Guide 1
- Contents 3
- Contents 5 5
- Contents 7 7
- About this guide 9
- HP technical support 10
- HP storage website 10
- Document conventions 11
- Revision history 12
- Warranty statement 13
- About this guide 15 15
- Description 17
- Continuous Access (CA) 19
- Business Copy (BC) 20
- Pairs and pair management 21
- Creating SnapShot pairs 22
- RAID Manager instances 23
- RAID Manager command device 25
- Shell/iX> cd /tmp/raidmgr 34
- Shell/iX> ./RMinstsh 34
- Installation prerequisites 37
- Installation 38
- Directory locations 39
- Services file 40
- Hosts file 40
- Windows NT/2000/2003 41
- Open VMS 42
- Parameter 43
- Default 43
- Type Limit 43
- HORCM_MON section 44
- XP Array 45
- HORCM_CMD section 46
- HORCM_DEV section 49
- Feature SMPL P-VOL S-VOL 50
- Example HORCM_DEV 51
- HORCM_LDEV section 52
- HORCM_INST section 53
- Starting the instances 54
- Environment variables for CA 56
- Paired volume configuration 57
- Using RAID Manager 59
- RAID Manager pair commands 60
- Using RAID Manager 61 61
- Vo lu me 63
- Secondary 63
- Vo lu m e 63
- Vo l um e 65
- Using RAID Manager 67 67
- File types and structure 68
- Using RAID Manager 69 69
- Title File name, Location 69
- Executable for 69
- Using RAID Manager 71 71
- Log files 72
- Windows NT/2000/2003 Systems 73
- MPE/iX Systems 73
- OpenVMS Systems 73
- Log directories 74
- Output to host log file 74
- User-created files 75
- RM environment variables 76
- Using RAID Manager 77 77
- RM protection 79
- Permission command 81
- Protection facility support 81
- Command device configuration 82
- Visibility to Grp2 only 83
- Visibility to Grp1,Grp3,Grp4 83
- Naming the $HORCMPERM file 87
- UNIX systems 87
- Verifying a group for vg01: 87
- Windows NT/2000/2003 systems 88
- Verifying a group for DB1: 88
- # lsdev –C –c disk 89
- $HORCMPROMOD 90
- $HORCMPERM 90
- # horcctl –D 91
- Using RAID Manager 93 93
- Using RAID Manager 95 95
- Restrictions 96
- Example 1 97
- Example: 99
- LUN Security Extension 101
- Using RAID Manager 103 103
- General commands 106
- Windows NT/2000/2003 commands 107
- Data integrity check commands 108
- Syntax horcctl –h 109
- # horcctl -D 111
- Syntax HP-UX: 113
- Examples 124
- and system 128
- # lsdev -C -c disk 129
- DYNIX/ptx 130
- Configuration file: 133
- Example 144
- Async-CA Sync-CA BC 151
- Syntax pairevtwait –h 157
- Report pair transition status 162
- # pairmon –allsnd –nowait 164
- –restore option is used, the 169
- S-VOL 170
- In the P-VOL case, this 172
- Split a pair 173
- CA Operation 174
- –FCA option. In the example 174
- BC Operation 174
- –FBC option. In the example 174
- # pairvolchk -g oradb 193
- –c argument is specified 194
- –s 1 x x x x x x COPY* 194
- –ss 1 x x x x x x COPY* 194
- BC with CT Group: 196
- Syntax raidar –h 197
- Related 199
- Information 199
- Syntax raidqry –h 200
- Display Example # raidqry -l 201
- Syntax raidscan 202
- –. For BC, the MU# is 209
- 0, 1, or 2 209
- –find option 210
- SCSI Port Specification 212
- Manager command 217
- Any general RM command 217
- Syntax RM_command –x mount 220
- [SYNC] C: HarddiskVolume3 230
- Data Integrity Check Commands 235
- [rtime] 240
- 0 0 1 1 242
- 0 0 0 1 242
- JNLS Other info 259
- P-JNL S-JNL QCNT AP 259
- # raidvchkscan -v jnlt 260
- Troubleshooting RAID Manager 263
- Error reporting 264
- Operational notes 265
- (continued) 266
- Error Solution 267
- Error codes 268
- $HORCM_CONF 269
- Command return values 270
- Command Error Error Message 272
- Command errors 273
- Command Error Problem Action 275
- Configuration file examples 279
- 0 (or 1 or 2) means BC only 280
- Cascading BC 281
- Connecting CA and BC 283
- A B C D 285
- CL1-A, T1, L1 and 288
- CL1-D, T2, L1 288
- A B 290
- (/etc/horcm0.conf) 295
- (/etc/horcm1.conf) 295
- # setenv HORCMINST 0 296
- (/etc/horcm.conf) 299
- # setenv HORCC_MRCF 1 301
- # paircreate -g Oradb -vl 301
- # paircreate -g Oradb -vr 302
- # paircreate -g Oradb1 -vl 303
- # setenv HORCC_MRCF 1 304
- # paircreate -g Oradb1 -vr 304
- # paircreate -g Oradb2 -vr 306
- Instance 0: 316
- Two-host BC configuration 317
- Two BC mirror configuration 319
- Three-host BC configuration 321
- Device group configuration 323
- HA Failover and failback 325
- HA Failover and failback 327 327
- Table terms: 328
- HA Failover and failback 329 329
- HA Failover and failback 331 331
- State No.1 332
- HA Failover and failback 333 333
- 9). Therefore, the 334
- HA Failover and failback 335 335
- ESCON/FC failure 335
- P-VOL group status 336
- Another PVOL-Takeover Case 337
- → SSUS) state 338
- → PSUE for async-CA 338
- Async-CA specific behavior 339
- HA Failover and failback 341 341
- –t timeout option) 342
- HA Failover and failback 343 343
- SMPL — — Needs to be 344
- P-VOL — — Needs to be 344
- S-VOL COPY data Inconsistent 344
- HA Failover and failback 345 345
- Object volume 345
- Currency 345
- SVOL_Takeover 345
- **no action needed to allow 346
- HA Failover and failback 349 349
- –t timeout option 351
- Scenario 355
- Abnormal termination 357
- Fibre Channel addressing 359
- Fibre Channel TID 360
- (QLogic or Emulex driver) 363
- STDIN file formats 365
- Porting notice for MPE/iX 367
- MPEKXU3 369
- Installing 370
- Uninstalling 370
- MPE socket hang 370
- Porting notice for MPE/iX 371 371
- /users/HORCM 372
- Make a JOB control file 373
- HORCM_DEV 375
- HORCM_INST 375
- Porting notice for OpenVMS 377
- HORCM daemon startup 379
- Command device 380
- Syslog function 381
- Startup log files 382
- Using the spawn command 382
- To install RAID Manager: 384
- To uninstall RAID Manager: 384
- DKA150 - - - - - - - 385
- $1$DGA145…) as either 386
- SHOW DEVICE command and the 386
- LNM$TEMPORARY_MAILBOX in the 387
- Executing a “horcmstart 0” 388
- $ HORCMINST := 0 389
- $ horcmshutdown 0 389
- HORCM Shutdown inst 0 !!! 389
- DCL command examples 391
- in the 397
- DEVICE_FILE UID S/F PORT 398
- LUN SERIAL LDEV PRODUCT_ID 398
- Starting “horcmstart 0 1” 399
- Glossary 401
- Glossary 403 403
- Glossary 405 405
- Glossary 407 407
- Index 409 409
- Index 411 411
Relacionado con productos y manuales para Almacenamiento Hp XP Continuous Access Software
Almacenamiento Hp NetStorage 6000 Manual de usuario
(192 paginas)
(192 paginas)
Almacenamiento Hp XP P9500 Storage Manual de usuario
(192 paginas)
(192 paginas)
Almacenamiento Hp XP P9500 Storage Manual de usuario
(132 paginas)
(132 paginas)
Almacenamiento Hp XP P9500 Storage Manual de usuario
(113 paginas)
(113 paginas)
© 2020, manymanuals.es. Todos los derechos reservados | 0.039 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales