Here are some Frequently Asked Questions about SanXfer:
Q: What is SanXfer?
A: SanXfer is a software utility that is used to Migrate Servers and data to new hardware. SanXfer can migrate Windows based servers to new physical hardware (P2P), to or from Virtual Machines (P2V,V2P), as well as migrating local booting servers into a SAN-booting servers. SanXfer can also be used to migrate data-LUNs between homogenous and heterogeneous SANs. SanXfer allows migrating data over high speed Fibre Channel (FC) networks, or over standard IP networks.
SanXfer facilitates hardware independence, server disaster recovery (DR), and streamlines virtualizing strategies.
Q: Can SanXfer be used to convert a SAN booting system back into a local booting system?
A: Yes, the same procedure that is used to convert a local booting system into a SAN booting system can be used to go in the other direction. SanXfer's easy menu options make complex changes, as simple as selecting a new disk to boot from. SanXfer will move the data and make the required changes depending on the location and type of disk selected.
Q: Does the target server hardware that I want to use have to have an OS already installed?
A: No, when replacing a Server's hardware, nothing needs to be preinstalled. If the hardware is for a SAN booting system, the new target hardware does not even need to contain internal disks.
Q: Can't I just replace a physical server with identical hardware?
A: Sure, if you actually have identical hardware. Even identical models often have different chipsets under the covers. These differences in chipsets, CPUs and mass storage controllers, will result in non-booting systems, or the `Blue-Screen-of-Death' (BSOD) in the Windows world. By using SanXfer to replace a Server's physical hardware, you have the freedom of moving to the best available hardware at the time you want to do the replacement. SanXfer also allows for migrating to and from Virtual Machines (VMs), and can perform the server replacement in minutes.
Q: Does SanXfer allow changing the hostname, IP addresses, and other characteristics during a migration?
A: Yes, during the server migration process, SanXfer provides screens to change vital information about a server. These changes are often necessary when doing a server migration as part of a Disaster Recovery (DR), or while provisioning a server.
Q: I have 100s of servers to migrate. Can SanXfer scale to handle large number of servers?
A: Yes, SanXfer was designed with the enterprise market in mind, and can handle a very large number of servers and simultaneous migrations. During an actual server migration, very little data flows through the SanXfer Library Server, rather the data goes from source directly to the destination server. The total number of simultaneous migrations is limited by the capacity of the environment rather than by limitations of SanXfer.
Q: Can local disks be left connected and reused after converting to SAN-booting?
A: Yes, but as a 'Best Practice' SanXfer recommends that after a local-boot to SAN-bot migration, you immediately remove the local drive to eliminate a future compliance threat associated with data on the local drive. When this server is retired or disposed of, there will not be any issues with “resident data” on that server.
Q: What virtualization technologies does SanXfer support?
A: SanXfer supports VMware®, Hyper-V, and XenServer for both Physical-to-Virtual (P2V) and Virtual-to-Physical (V2P) migrations. Depending on the type of VM to be used, SanXfer allows server migrations over either Fibre Channel or IP networks.
Q: I'd like to migrate a physical system to a Virtual system as a part of a DR test, can SanXfer do that?
A: The SanXfer User Guide has specific detailed procedures for the major usage procedures, including using the SanXFer for Disaster Recovery. The SanXfer Automated DR Edition is designed specifically for Server DR work in replicated SAN environments, but the Cloud and VM Optimized Edition can also be used in for DR plans involving servers not connected to the SAN.
Q: What versions of Windows does SanXfer support?
A: SanXfer has two installable components: a Library Server, and Client package. The SanXfer Library Server is normally only installed on one system in an environment, (or two in the case of the Automated DR Edition.) The SanXfer Library Server can be installed on all 32 and 64 bit versions of: Windows 2000, XP, 2003, 2003R2, Vista, 2008, 2008R2, Win7. The SanXfer Client package is installed on all of the systems to be protected by SanXfer; it can be installed on all 32 and 64 bit versions of the following: Windows XP, 2003, 2003R2, 2008, 2008R2, Vista, Win 7.
Q: Does SanXfer support Linux?
A: SanXfer is not supported as a Library Server or Client today. The developers of SanXfer have a deep history of building cross platform systems, and SanXfer was designed with more than just Windows in mind. The decision to support Linux is based on market factors and customer feedback. To provide feedback on Linux, please contact
sales@inquinox.comQ: How big is the SanXfer Client footprint?
A: The SanXfer client is designed as a very small footprint image. It requires only about 3MB of disk space, and it does not leave any processes running after the installation.
Q: What HBAs are supported by SanXfer?
A: SanXfer can support any device (HBA, Nic, Audio, Video, etc) that uses the normal Windows install process. This covers almost all devices on the market. SanXfer does not need a hardware compatibility list of its own. If the Windows Operating System release supports the device, SanXfer can operate with it.
Q: Qlogic just released a new HBA. Do I need a SanXfer update to be able to support it?
A: No update is needed for SanXfer to support new devices. By adding the driver for the new device to the SanXfer Library Server, it will be available for use during a SanXfer migration.
Q: Does SanXfer support iSCSI?
A: Yes, SanXfer allows an iSCSI disk to be used as a source or a target of a migration. A local-booting system can be migrated to an iSCSI-booting system, or an iSCSI-booting system can be migrated to a Fibre Channel (FC) SAN-booting system.
Q: Will SanXfer work on diskless blades?
A: Yes, SanXfer is perfectly suited for use with diskless blades. During a server refresh cycle, nothing is faster at switching a SAN booting blade to new hardware.
Q: How long does it take to migrate a SAN booting system onto new server hardware?
A: Since the data for the OS does not need to move from the SAN, it just needs to be modified to allow the new hardware to boot it, the process is very fast. The time is about 1 minute plus the amount of time the system requires booting a CD (or ISO) and then rebooting on the San again. Typically a SAN-booting server and replace it's server hardware in less than 5 minutes.
Q: How long does it take to migrate a local booting system into a SAN booting system?
A: When migrating from a local booting system to a SAN booting system, the time required depends on the amount of data to be migrated, the number of local Windows drives to be migrated, the Fibre Channel speed, the speed of the target disks, and the time required to boot a CD or ISO. For a typical system with a 30GB C: and 30GB D: drive with a 4GB SAN, the entire process should take less than 15 minutes.
Q: I am converting a number of local booting systems into SAN booting systems. How much traffic
goes over the IP network?
A: Most of the data for the migration will flow directly over the HBA to the SAN. During the migration process, the new server hardware needs an IP connection to the SanXfer Library Server to check licenses, load SanXfer executables and device drivers. Typically, less than 10 MB needs to be transferred over the IP network
Q: I am replacing the server hardware for a number of SAN booting systems. How much traffic goes over the IP network?
A: Very little data goes over the IP network. During the server replacement process, the new server hardware needs an IP connection to the SanXfer Library Server to check licenses, load SanXfer executables and device drivers. Typically, less than 10 MB needs to be transferred over the IP network.
Q: After I convert a local booting system into a SAN booting system, do I need to 'sync' before booting off the SAN?
A: No secondary sync process is required. After a migration, the new hardware is booted and ready for real work.
Q: I Virtualized a server that worked better as a physical server, can I migrate it back?
A: Yes, moving from virtual to physical is the same process as physical to virtual.
Q: Does the system used for the SanXfer Library Server need to be dedicated to that purpose?
A: No, a system does not need to be dedicated completely toward the SanXfer Library Server. The SanXfer Library Server runs a version of Microsoft's SQL Server database and start a couple of network services. Under normal conditions, the Library Server provides a light load on a system.
Q: The home screen of the Library Server GUI shows that I have used all my client licenses. Is it possible to add more client licenses without installing another Library Server?
A: Yes, additional licenses can be added to an existing SanXfer Library Server. Contact your sales representative, or reseller to, to ask about purchasing additional licenses.
Q: I originally purchased the DC Mover Edition, but would like to upgrade to the DataCenter Edition, is that possible?
A: Yes, by contacting your sales representative, you can discuss the license change necessary for upgrading. From a technical standpoint, a new license key can be issued to convert your existing SanXfer Library Server into a different Edition. The SanXfer Client code is the same for all editions, and will not need to change.
Q: Can SanXfer be used with my enterprise backup product to restore a backup to different
hardware?
A: Yes. Although SanXfer is not a backup and recovery tool, SanXfer can be used with backup products to restore to new hardware. Please ask your sales representative or reseller about the InQuinox white paper: "SanXfer and Backups - Easy Hardware Independence."
Q: Our local booting systems have very large boot disks. If we migrate these into the SAN, can we reduce the size of the boot disk?
A: Yes. SanXfer will allow you to reduce the size of any partition. The target disk or partition must be large enough for the existing data.
Q: What advantages are associated with “Boot from SAN”?
A: There are many advantages, including:
- SAN boot disk reliability is a given part of the SAN RAID characteristic
- SAN storage is more fault-tolerant, enabling IT teams to meet user SLAs (Service Level Agreements)
- SANs offer increased data security and storage utilization
- Fewer people are required to manage storage since storage migration is easier
- SANs offer simpler, more reliable Disaster Recovery
- SANs consume less power
- More efficient data management
- SANs help to eliminate non-efficient (local) storage
- SANs help to increase the uptime and reliability of "local boot" servers once migrated to the SAN
Q: Can I re-use SanXfer to migrate a specific server, multiple times?
A: Yes. The DC Mover Edition of SanXfer is licensed on a per-migration basis, so migrating the same server multiple times, would count each migration. The Cloud & VM Optimized Edition and Automated DR Edition are licensed on a per-client basis. Once a server is regisered with the Library Server, it can be migration as many times as needed, and whenever needed.
Q: Can I obtain a trial license of SanXfer for testing in my lab?
A: Yes. Please contact our sales organization at 800-495-2959 or sales@inquinox.com for more details.
Q: Does the Data TranXfer feature enable data to be migrated between different storage hardware and/or networks?
A: Yes, the Data TranXfer feature was created specifically because of customer requests for a tool that would simplify the data migration effort between both heterogeneous and homogeneous storage platforms.
Q: Does Data TranXfer work for all OS types?
A: Yes, this SanXfer feature extends beyond the traditional Windows workload migration functionality, enabling users to migrate data volumes located on an existing SAN to a new one, regardless of vendor, operating system (Windows or non-Windows), or file system.
Q: Can I use Data TranXfer to migrate data from a Fibre Channel SAN to an iSCSI SAN?
A: Yes, Data TranXfer supports Fibre Channel (FC) SANs, iSCSI disks, as well as local disks.
Q: Can I run multiple, parallel data migrations with Data TranXfer?
A: Yes, Data TranXfer will automatically kick off upto five migration streams in parallel if there is available bandwidth. Multiple servers can be running a Data TranXfer migration in parallel as well.
Q: Does SanXfer Support EFI firmware?
A: SanXfer supports migrating systems that use (U)EFI firmware, but the restrictions in the GPT and Dynamic Disks sections should be noted.
Q: Does SanXfer Support GPT and MBR disks?
A: SanXfer can migrate systems that use either the MBR or GPT disk layout scheme. SanXfer allows the user to pick either a blank disk or an existing partition for the destination of a migrated Windows drive {C:, D: E:, etc}. If a blank disk is used, SanXfer will create the needed partitions using an MBR style disk layout, even if the source system was a GPT system. User's have the option of creating a GPT disk layout themselves on the destination disks, and pre-creating the partitions. SanXfer will allow users to select existing partitions as targets, but will always format them before use.
Q: Does SanXfer Support Dynamic Disks and Basic Disks?
A: SanXfer supports migrating all Windows drives from a Windows system that is using Basic Disks. For Windows systems that use Windows Dynamic disks, only the single boot/root partition can be migrated. SanXfer will always use Basic Disks as the target of the migration. User's have the option of converting Basic disks to Dynamic disks after the migration.
Q: Does SanXfer support the XenServer paravirtualizated drivers?
A: No. When migrating to a XenServer based VM, SanXfer can be used out-of-the-box in most cases. During the migration standard device drivers will be used. Due to a XenServer limitation of only allowing access to 3 virtual disks using standard drivers, SanXfer only supports 3 disk dives during a migration to or from a XenServer based VM. After a migration to a XenServer based VM, the XenTools can be installed to use the higher performance paravirtualizated drivers, and to gain access to additional disks.
