Block-Level Replication FAQ
This document (7920943) is provided subject to the disclaimer at the end of this document.
Block-level replication is designed to migrate and protect Windows workloads without requiring the source workload to be taken offline. Block-level replication is most suitable for servers with high transaction activity (for example, database transactions) as during the transfer, the block level mechanism will copy only the changed blocks instead of the entire file.
Supported Source Operating Systems for Block-Level Replication:
Windows 2003 Server (SP1+)
Windows 2008 Server
Windows 2008 Server R2
Supported Job Types:
Note: Forge and Protect do not offer P2P functionality.
When configuring a job to use Block-level replication, the following will occur:
Frequently Asked Questions:
Which Target Servers can I use when configuring a job with Block-level replication?
Any supported target can be used for Block-level migrations/replications, with one exception: Block-level is not supported when capturing or deploying an Image.
What are the best scenarios to use Block-level replication?
Block-Level replication is recommended for the following scenarios:
Windows Workloads with high disk, application and database activity – Block-level replication is recommended for these servers as it copies only the actual blocks which were changed during the transfer step instead of the entire file. For example, if a 1 GB database file was changed during copy, the block level filter driver will mark these blocks and will copy only these blocks (File level transfer would have copied the entire 1 GB file again). This process will significantly reduce the network traffic and the total migration time.
Windows workloads located in a network with high latency and low bandwidth – Block-level replication is recommended for networks with high latency and low bandwidth as it copies less data between synchronization attempts. Furthermore, the transfer protocol is able to produce high transfer rates when compared to other transfer protocols (e.g. Take Control transfer and Live file based transfer protocol).
Workload Migration or Workload Protection jobs where service downtime is not possible – Since Block-level replication is able to copy locked and in-use files, source workload services will not be stopped during relocation or incremental backup jobs.
What job features are not available when using Block-level replication?
Disk Resizing – if Block-level replication is selected, Disk resizing will be disabled, although selecting which volume to copy is available
Can I use Block-level replication to create PlateSpin Flexible Image?
Block-Level Migration is available only for Windows workload Peer-to-Peer jobs. PlateSpin Flexible Images can be created with Take Control or Live file based transfer options.
Can I transfer SQL, Exchange, Oracle, Sybase or other proprietary applications with Block-level replication?
There are no restrictions to the types of applications for Block-level replication. Block level transfer will copy the entire volume to the target and will provide a ‘crash consistent’ state volume on the target.
2. Ensure the RPC Service is running on the source and that the RPC Protocol between the source and the target servers is not blocked by Firewall.
3. Check with your application vendor if information is cached in the memory before performing a workload relocation job. If needed, shutdown the application and the related services to ensure the highest level of synchronization
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7920943
- Creation Date:24-MAY-07
- Modified Date:09-APR-13
- NetIQPlateSpin ForgePlateSpin MigratePlateSpin Protect
Did this document solve your problem? Provide Feedback