Blackberry NEWS FEEDS - RELEASE NOTES 1.0 Información técnica Pagina 29

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 32
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 28
Localized Versions
Chapter 5: Known Issues 29
For Periodic Replication: You may experience delays when applying replication data
depending on the data size and number of files to apply, because the process
assures data consistency. You can set the parameter, KeepUndoForPeriodic, to false
to halt generation of the undo file and speed up the application of aggregated
changes, but should not do so for database scenarios. This parameter is in the
ws_rep.cfg file.
For Network Traffic Redirection: After a switchover takes place, the A-records of
Master and Replica servers are changed on the DNS server, depending on which
Network Redirection Methods you select. The following table shows what network
redirection methods impact the DNS A-record.
If the Network Redirection method is Move IP, the DNS A-record is not
impacted.
If the Network Redirection is DNS redirection, the A-record Master redirects to
the Replica IP after switchover, while the Replica A-record doesn't change.
If the Network Redirection is Switch Computer Name, the Master A-record
changes to Master-xo after switchover, and the Replica A-record changes to
Master.
If the network redirections are DNS redirection and switch computer name, the
result is same as only DNS redirection.
If you want to keep the Replica A-Record, use the DNS Redirection method or
DNS and Switch Computer Name methods.
For CA ARCserve Backup and CA ARCserve RHA integration: When restoring a SQL
database on the Master with CA ARCserve Backup, you may receive a "Windows
could not start the SQL Server" error if running SQL Server 2008. (This error does
not affect SQL Server 2005 restore jobs.) This error is caused by the Network
Service or Local Service accounts, which do not have access rights to the SQL log file
on the Master. There are three ways to avoid this issue:
In CA ARCserve RHA, set the scenario Replicate ACL option to On. Doing so
guarantees that all ACL information for the Master SQL data directories are
retained after recovery, allowing the SQL service to operate.
In CA ARCserve Backup, manually add the following user account after recovery
to the ACL of the SQL data directories on the Master:
SQLServerMSSQLUser$Computer Name$Instance Name
In CA ARCserve Backup disable the following restore option to NOT overwrite
the ACL of the SQL data folders on the Master after restore: CA ARCserve
Backup Manager, Global Options, Operation. Click to enable or disable the
option, Restore and Preserve File Attributes and Security Information. Checking
this option overwrites the ACL. Clearing the option does NOT overwrite the
ACL.
Vista de pagina 28
1 2 ... 24 25 26 27 28 29 30 31 32

Comentarios a estos manuales

Sin comentarios