System data is copied from the Master unit to the designated Backup Master unit as soon as Backup Master
operation is enabled through system programming.
System data is copied from the Master unit to Slave units whenever system data is saved. Data is saved
when the programmer clicks the save button in Web Maintenance Console and when the programmer logs
out of Web Maintenance Console. Data is also saved automatically every 30 minutes.
•
During Backup Master operation and Isolated operation, system data can be changed. However, the
changed data is not copied back to the Master unit (or Backup Master unit) when normal operation resumes.
•
Unified Messaging data is not copied to the Backup Master unit or other Slave units. For details about
Unified Messaging survivability features, see "4.2.3.3 UM Group Failover".
•
SRAM data such as SMDR data, the error log, timed reminders, etc., is not copied to the Backup Master
unit or other Slave units. While the Master unit (or Backup Master unit) is offline, the SRAM data is
maintained so that when normal operation resumes, the SRAM is in the same state it was in when the
Master unit (or Backup Master unit) went offline.
•
During Backup Master operation or Isolated operation, data stored in the SRAM, such as SMDR data, is
collected at the Backup Master unit (in Backup Master mode) or Isolated unit (in Isolated mode). However,
this data is not copied back to the Master unit (or Backup Master unit) when normal operation resumes. If
it is necessary to output this data, connect a printer to the appropriate unit and print out the necessary data.
Outputting the SRAM data must be done in Backup Master mode for the Backup Master unit or in Isolated
mode for an Isolated unit.
•
OGM data is not copied to the Backup Master unit or other Slave units. OGM messages are stored
separately at each site. If OGM must be the same between sites, copy the messages manually beforehand.
•
System Time
–
Backup Master unit: If the unit is configured to retrieve the current time from an ISDN line, Caller ID,
or NTP, or if the time is set manually, it continues to use that method. If the unit was retrieving the
current time from the Master unit, it continues using the time it had when operation switched to Backup
Master mode.
–
Slave units (in Backup Master mode): If the unit is configured to retrieve the current time from the
Master unit, it will retrieve the time from the Backup Master unit. Otherwise, it continues using the
specified method (ISDN, Caller ID, etc.).
–
Isolated units: If the unit is configured to retrieve the current time from the Master unit, it will continue
using the time it had when operation switched to Isolated mode. Otherwise, it continues using the
specified method (ISDN, Caller ID, etc.).
[CA (Communication Assistant)]
•
If you are using CA Server, a separate, backup CA Server must be connected to the Backup Master unit
to continue operation of CA in Backup Master mode. CA Client users will need to restart the CA Client
programme and manually input the IP address of the CA Server connected to the Backup Master unit.
To continue operation of CA in Isolated mode, a backup CA Server will need to be connected to each PBX
from which CA services will be provided. CA Client users will also need to change the IP address for CA
Server as necessary.
•
If you are using CA in PBX-only mode (i.e., without CA Server), CA services will be provided automatically
by the Backup Master unit or isolated unit. However, CA Client users will need to restart the CA Client
programme and manually input the IP address of the Backup Master unit or isolated unit as necessary.
[IMAP4]
•
If you are using IMAP integration (
®
3.3.2 IMAP Integration), you can use one of the following methods
to continue operation in Backup Master mode and Isolated mode:
–
In the mail client, configure multiple accounts: one to contact the Master unit and the others to contact
the Backup Master unit, Isolated units, etc.
–
If you use a DNS server to resolve a host name (FQDN) for connecting to the IMAP server, configure
the IMAP server’s DNS record to contain the IP addresses of the Backup Master unit and Isolated units
as alternate addresses.
366
Feature Guide
4.2.3 One-look Networking Survivability
Summary of Contents for KX-NS1000
Page 14: ...14 Feature Guide Table of Contents...
Page 15: ...Section 1 For Your Safety Feature Guide 15...
Page 18: ...18 Feature Guide 1 1 1 For Your Safety...
Page 19: ...Section 2 Call Handling Features Feature Guide 19...
Page 278: ...278 Feature Guide 2 28 2 Outgoing Message OGM...
Page 279: ...Section 3 Unified Messaging System Feature Guide 279...
Page 335: ...Section 4 Network Features Feature Guide 335...
Page 434: ...434 Feature Guide 4 3 6 Network ICD Group...
Page 435: ...Section 5 System Configuration and Administration Features Feature Guide 435...
Page 521: ...Section 6 Appendix Feature Guide 521...
Page 540: ...540 Feature Guide 6 5 4 PCMPR Software File Version 003 2xxxx...
Page 541: ...Feature Guide 541 Notes...