Hp Storage Mirroring Software Bedienungsanleitung Seite 617

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 678
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 616
Recommended optimizations Page 616 of 677
General optimizations
The following are general optimizations that can be used for any Storage Mirroring
Recover workload type.
l Performance optimizations
l General manageability
l Anti-virus protection
l Hardware configurations
Performance optimizations
l Initial mirror across slow network—A large amount of data that is being mirrored
across a slow network may take days to complete the initial mirror, depending on
the amount of data and the available bandwidth. You may want to consider the
following options to reduce the amount of time for the initial mirror.
l Move the target server to the source's site for the initial mirror. When the
mirror is complete, move the target server to its permanent location and
create a new connection using a difference mirror.
l Archive the data to media that can be transported to the target site and
restored to the target server. When the data is restored to the target, create
the connection using a difference mirror.
l Create a compressed archive of the source data, copy the archive to the
target, uncompress the data, and then create the connection using a
difference mirror.
l Disable replication during the initial mirror. This will allow the mirror to
complete as quickly as possible without having to contend with replication
traffic for bandwidth. After the mirror is complete, start replication and start a
difference mirror.
l Compression—Storage Mirroring Recover compression should be used when
network bandwidth between the source and target is limited. In some cases,
performance may also be improved by enabling compression in high-bandwidth
environments. The best level of compression for a given solution will depend on a
number of factors, including the type of data being replicated, CPU load, and
available bandwidth. Since compression settings can be changed dynamically, the
easiest way to find the best level of compression is to enable it at level 1 and
monitor the results. If data is still being queued on the source, increase the
compression level to 2 or 3. If CPU load becomes an issue on the server, decrease
the compression level.
Seitenansicht 616
1 2 ... 612 613 614 615 616 617 618 619 620 621 622 ... 677 678

Kommentare zu diesen Handbüchern

Keine Kommentare