vFoglight, vRanger connection & vCenter

Hi all.
We have recently updated our virtual environment for vSphere 4U1 with 6 blades connected in vCenter ESX.
We currently have vRanger connection and vCenter installed on the same physical machine attached to the San. He is currently a backup ok.
My question is that we now intend to run vFoglight. I read that vFoglight love using as many resources as it can get, and it is recommended to install it on its own box. If none of the scenarios are considered as 'ok' to do?
1. install the three products (vCenter, vRanger connection, vFoglight) on the same physical machine.
2. install vCenter and vFoglight on the same machine physics and vRanger connection on a virtual machine.
3. install vRanger connection and vCenter on the same physical box (essentially a backup box) and on its own virtual vFoglight.
4. all the separate (and if yes, the best being in the physical box). (it can't really as I'm trying to consolidate servers)
I hope someone can enlighten us on this one and I can make it work.
Bravo for that.
Concerning
Feng

Hi AuscoIT...
(1) No, don't do it. You will be pointing out the machine with all three products running on it too.
(2) is not recommended either, as vCenter performs many vital operations (taking snapshots, the migration of virtual machines, cloning, HA, etc.), and the last thing you want is vFoglight "hungry" this machine of the resources he needs.
(3) is not recommended either, although I've seen it before. This, in my mind, creates an unnecessary risk, as if you lose your VC machine, you also lose connection vRanger machine, etc., and it would inhibit your effort of DR.
(4) If you require on SAN backups, you must have vRanger connection on a physical machine. You could 'make do' with the #3 configuration, but once again, several reasons not to do. The physical machine connection vRanger doesn't have to be ultra powerful, if, then perhaps you could get in with a former dedicated server? If you are ready to go straight to the goal the LAN-based backups, then a virtual machine for vRanger connection is perfectly adequate, as it does not move a lot of data (the ESX hosts carry the burden it). You can compare the costs and benefits, depending on the size of your environment is, and how long is your backup window. We have enough big clients who are perfectly happy with the LAN-based backups.
I hope this helps...

Tags: Dell Tech

Similar Questions

  • vRanger connection 7.1.1 migrate again vCenter

    Hello!

    I have to build a replacement vCenter server in a new physical data center and we are * not * re-use of existing vCenter DB, it will be a new database.

    I read a few forum messages:

    http://en.community.Dell.com/TechCenter/data-protection/f/4784/t/19555352

    The conflicts of the article above with Guide from Dell:

    https://support.software.Dell.com/vRanger/KB/82362

    The replacement vCenter server is already online, I just need help to plan my activities of migration in order to ensure the backup jobs/history will not be lost.

    Thank you!

    -Shaun

    While the support KB illustrates the method to directly modify the database connection vRanger table, I would recommend a case of pension to the best advice of opening.

    If you go down the road to edit the database, please note that incorrect updates or deletions to the data in the database can make it unusable. Please make a backup of SQL Server database or save the prior VM (using vRanger connection) vRanger connection for any changes.

    It is best to open a pension case.

    I will add a new element of the road map for vRanger connection consider whether we can allow editing of the address of vCenter.

  • Replace the vCenter without redoing the vRanger connection configuration?

    Hi all

    Experimenting with the new device of VMware vCenter, I ran into a problem with vRanger connection.  I disconnected a host of our existing facility of vCenter and added successfully to the new VCSA.  I also added the new VCSA vRanger connection configuration.  vRanger connection sees the new vCenter, as well as the ESXi host on the new vCenter.

    The problem I see is that jobs do not now for the virtual machines on the host has moved.  I can see the jobs tab in my work, but when I try to run one of them, he fails almost instantly:

    Inventory [vm-11529] node is on a disconnected virtual circuit:

    The work is no longer present in my inventory tab, under the virtual machine in question (I have individual tasks for each virtual computer).  Is there a way to retarget 'with' the new vCenter without having to set up new jobs for each virtual computer after migration?  My concerns are the time to set up 30 + new jobs, the possibility of having to do a backup complete out of sequence, and our peripheral dedupe (ExaGrid) see this new backup as a new source of backup, causing the backup to break chain and forcing the use of the double the hard drive space on our ExaGrids until our retention period is completely recycled (3-4 months).

    Any ideas?

    Thank you

    Judge Quinn

    Quinn,

    Let me be clear. Now your ESX hosts are managed by VCSA, and this one has its own new database. In this case, all the stored in the configuration store object ID is invalid. I'm not familiar with VCSA yet, but if it works with VMware PowerCLI, you should be able to get new IDS and update InventoryNodeVirtualizationObjectId in the BackupTemplateTask table.

    Here is a PowerCLI procedure to get new VM ID. It works with regular, not sure of VCSA VC.

    SE connect-VIServer

    (Get-VM-name ) user.user

    Andrew

  • vRanger connection 7.1.1 and vCenter 5.5 - open filters causing high memory use vpxd?

    Hello

    Displays the first time, hoping you can help me. We are big consumers of vRanger connection in our environment, we use multiple instances to save the production, test, dev, VDI, etc. (6 cases total). Recently, we met our vRanger 7.1.1 connection servers and our vCenter to 5.5 Update 2 b. Since then, every evening when our nightly backups occur to our use of memory for vpxd on our vCenter server (process vpxd.exe) increases, and it remains standing and rising again every night until the that vCenter grave service failed due to memory exhaustion. After 2 weeks of troubleshooting with VMware, their senior engineers think that connection vRanger not close correctly filters, leaving a large number of them that causes the memory out is not in the system.

    Are you aware of any issues like this being reported elsewhere? I tried to find other peoples identify this problem, but it seems that we are the first. Please help, thanks!

    We have not seen this issue in our lab, but we currently 5.5 2d update.  I recommend that you open a support casel

  • VRanger connection-Vsphere so descends from vRanger reports see it and worse still you say no connection

    I noticed sometimes the server Vsphere my guests and my 7.1.1. vRanger of connection depends on the will go down.  The reports that I have vRanger connection send me every day won't NOTICE and either give me 'nothing' in the past days or worse state "successful."

    It is repeatable and I feel goes on all versions of the product.  What he told me, is that error conditions have no "vsphere is down" in the list of errors to report.

    Oh email failure reports fortunately still works.  From my point of view, this is a pretty big omission.

    Technical support referred me here at this precise moment, the product operating as written.

    I added the feature request: FT 1035 improve notifications by e-mail to the employment report failures due to vCenter/ESXi host unreachable

  • VRanger connection... not much .anyone know?

    VRanger connection with ESXi using seems to be a great mystery for both people vizioncore and vmware.  None of them could tell me what I need.

    I have ESXi installed and works with licensed Essentials Foundation.  I use the latest version of vRanger Pro connection and are still unable to the point where he sees my ESX host in the GUI.

    I went KB vRanger connection and typed in ESXi and NOTHING!

    I added the host ESX vRanger connection using the root account and takes it, but nothing appears in the list of hosts.  I tried to create an account on the ESX host admin, but it wrong when I tried to use it in the vRanger connection gui.

    (MB). Here, any help would be great!  Someone at - it this work with ESXi?  What licenses you had to get VMware to get there?

    Thank you!

    That's right, you will need at least VI3 Foundation and vCenter Foundation to back it up with vRanger connection.  I would check what are the requirements to get the latest version (4.0), but I know what are the requirements for 3.x.  If you are looking for a complete recommended alternative, I would look to Veeam Backup.  It is a really nice product and costs about the same as vRanger connection.

  • AppAssure vs. vRanger connection

    How AppAssure differs from vRanger connection specifically for environment VM backups?

    Installed a VM with SQL Server. Need to backup SQL server, that one would be a faster backup solution?

    The two products differ mainly due to the fact that one is an agent of basic solution (AppAssure) and the other is agentless (vRanger connection) for virtual machines. When it comes to physical backups, they both use and the agent that is installed on the local operating system. However if you are referring to virtual VMware or HV machines, then vRanger connection will run the backup via virtual hosts and backup the .vmdks and/or .vhds while AppAssure will use the agent on the local operating system and perform a VSS/backup snapshot.

    About SQL, the question I would have is you are planning on usage of vRanger connection to truncate logs SQL? If so, then vRanger connection will use the VSS writer that is installed on the local during the backup operating system and interacts with the local operating system, if not then the backup will be made independent of the local operating system. The process of vRanger connection is always save virtual blocks (hard and .vhd) but no, it will use the local VSS to truncate the logs.

    What speed is this will always come down to the resources allocated. Virtual backups are likely to provide a high rate due to the fact that you should have less impact on the production of VM, but the performance is on your virtual servers, i/o of the disks on your data warehouses and your storage space and load you plan to do in time, as well as the network. For example, if you are running Vmware 5.5 and you have a vCenter in place that has 8 GB of RAM, so it will be a bottleneck that will impact each backup. Just because there is no agent and the other is Officer Basic does not mean that one will be faster than the other, it just means that there are other variables to consider when it comes to performance.

    In the end I recommend you test this. If it's for a virtual computer, then vRanger connection and AppAssure can coexist in the environment (do not install the AppAssure vRanger connection servers and on the same OS however) since only 1 will use an agent. There is a trial download, try it and see for yourself how it works in your environment:

    Software.Dell.com/.../vRanger

    Software.Dell.com/.../AppAssure

  • Backup DR with vRanger connection devices

    Having Dr. devices dealing with VM backups on-site, but one of the questions that arise is the time of the backup. It takes about 8 hours to backup the SQL files every night. Just to let you know its all upwards in a virtual machine environment.

    Can incorporating vRanger of connection or AppAssure with DR unit affect backup performance?

    Is there a whitepaper on this?

    Thank you!

    Hi Geeka,
    Depending on how you are currently using the device DR with vRanger connection, your current solution could be improved.

    If you are simply using the DR as a CIFS share there is another way.

    vRanger connection also supports the Dell RDA technology, which can provide a level of deduplication side source.

    Consider implementing vRanger connection Virtual appliances (one per host), or one per cluster, your choice, the virtual devices include technology of the GDR.

    Configure the virtual machine backups to cross Virtual Appliances and target (GDR/RDS) container on the Dominican Republic.

    The backup will be a snapshot of the virtual machine, but use hot add technology to fix the disks to the virtual appliance, data are then broadcast through the virtual appliance to the GDR DR container. At the point where the data leaves the appliance virtual it's pattern matched with data stored on the Dominican Republic. All blocks that match are not sent.

    This reduces network traffic and allows backups to do more.

    If you want to add the technology to the protection of SQL as an agent-based application, then take a look at NetVault Backup, it will be directly interfacing with SQL via VDI or VSS, providing full, incremental and differential backups. It's agents also include the GDR technology and can provide source de-duplication to a DR GDR container.

    AppAssure also has an agent and can protect the content of the full virtual machine, including the SQL instance, but it will require its own server and storage and does not directly allow the DR unit to store the initial backup data. It can create Archives of data sets that can be moved from AppAssure on the good DR database server, but it's more for long-term storage.

    I hope this helps.

    See you soon,.
    Adrian.

  • Unable connect Vcenter 5.5 (please help)

    I'm new to vmware technology. I installed vcenter5.5 / with express SQL within a windows 2012R2 VM server. I can not connect my windows client5.5 vsphere vcenter 8 PC. I can connect vcenter in windows server 2012 but I can't even create my data center, no option icon.

    What I am doing wrong? In my lab, should I be loggin in vcenter from my local with vsphere client windows PC?

    I have a HP G6 server with two nested ESXI hosts. I don't have AD Setup and using local DNS...

    vcenter.JPG

    After the screenshot you tried to connect using the Windows administrator account! Please use the SSO account [email protected] to connect. This is the only account with maximum permissions after a basic installation.

    André

  • Server for vmdk hardware backups using vRanger connection

    Hello

    We try to implement vRanger connection for backup of our VMS (ESX 3.5) and would like to have installed on a stand-alone server. There are currently 36 VMs that is likely to grow. Each virtual machine has a disk of 10 GB C residing in SAN. We want to save these files vmdk SAN to the server where vRanger connection is installed.

    Could anyone here suggest some options for a server to have it put in place? Given that the size of the files would be around 400 GB for now and much more later, the speed of the hard drive must be considered too.

    Thank you.

    Cool! So what kind of records should I go then?

    What is your budget?  SAS is the fastest, but we are talking here about 400GB drive will cost twice what a single 1.2 to or even 1.5 TB SATA.  Even if you have the budget for it, it's a complete waste of money, since you can get 4 times the storage for the same price.

    RAID 0 will give you the most performance, however if you keep several revisions on your backup disk, maybe not prudent to use the RAID 0 in the long term, but there again this depends on your backup strategy, you want backups LONG or SHORT term?  If you make full backups every week, as we do, RAID 0 is fine.  We can accept the risk given that do us COMPLETE each week and because backups are unexpected, not to archive, it is not a big problem for us, but every company is different.

    Network is not your main concern, however, if you have a decent network of 1 GB, that's all you need.  Just buy whatever you can afford for storage, if backup speed is your main concern, go SAS, if not go SATA.

  • VM issues after restore vRanger connection

    Our virtual machines are stored on a San. VRanger connection allows us to back up virtual machines. For an Active Directory disaster recovery test, I restored a few domain controllers in a single ESX server (Test Server) local storage.

    I can record the successfully the VM, but when starting the virtual machine I get an error:

    "Virtual Disk hard drive 2 is not accessible on the host: cannot access the file.

    When I tried to remove the discs from the virtual machine, I get the error "invalid configuration for device 0.

    I, ve created a new virtual machine without disks. When I try to add the existing drive, I don't see the drive. But through the ESX console are WINSCP I see the entire disk. Life and the test environment have ESX 3.4/VC2.5

    I tried to rename the files vmdk with vmkfstools - E, perhaps hoping geometry/header file would change. But I get an error ' unable to rename 'VM.vmdk': the system cannot find the specified file (25).

    I think it has something to do with the header for the disk file, but I'm not sure.

    I, ve tried manually by changing the header file, but that did not work. See below what changes, I tried to do:

    1. Disk DescriptorFile

    version = 1

    CID = 00000001

    parentCID = ffffffff

    createType ="monolithicFlat" == > changed to «vmfs

    1. Description of the measure

    RW 21030912 FLAT "scsi0-0-0 -VMNAME1_1 - flat hard" 0== > changed "FLAT" to "VMFS" | " Delete "scsi0-0 - 0 - | Remove the last "" 0 "".

    1. The disk database

    #DDB

    ddb.virtualHWVersion = "4".

    ddb.toolsVersion = "7300.

    DDB. UUID = "60 00 e1 C2 93 03 f3 d9-38 39 4 02 74 39 d 8 d b6"

    DDB. Geometry.Cylinders = '1309 '.

    DDB. Geometry.Heads = "255".

    DDB. Geometry.sectors = "63".

    ddb.adapterType = "free".

    I found a few forums discussions about similar problems, but no solution.

    Hello. According to Vizioncore the resolution to this is as follows.

    "Hi all,"

    Support has a updated with patches for this version.  Please contact support and ask to build the field trials

    ----

  • VRanger connection and VSS support

    Hi, we use the ESX 3.5 U3 (soon to 4) and vRanger connection 3.2.4.2 (with the VCB graft).  IM researching the 'common' best practices when you back up virtual machines containing AD and / or SQL.

    At the present time, I do the following:

    1. install the driver Vizioncore VSS on the virtual machine

    2 Select 'Disable comments paused'

    3 remove the driver to synchronize files VMware since VM tools

    Two questions I have are:

    1. good practice above is?

    2. in the latest version of the tools I see not the sync driver, I Volume Shadow Copy Services Support, can I disable it?

    As in synchronization of file... "

    When not to use the SYNCHRONIZATION driver

    You use the SYNC driver that comes with VMware Tools to stop I/O and flush the Sales data on disk (oil change I/O) to create consistent system backups of file may cause some applications that are sensitive to writing data timely to fail and generate errors. In this case, you can uninstall the driver of file system SYNCHRONIZATION to avoid the delay that is caused by i/o to drain. To uninstall just SYNC driver uninstall VMware Tools, restart and then reinstall it and make sure you select a "Custom" installation type Then, expand VMware device drivers and click "Sync file system driver" and select "this feature will be unavailable." Be aware that if you do that your shots will be crash consistent instead of file-system-compatible. As an alternative, you can suspend custom through backup before and after backup scripts that are executed within the guest operating system. Another alternative is to stop the virtual machine before taking the snapshot, so the virtual machine is consistent application. "

    http://searchdatabackup.TechTarget.com/Tip/0, 289483, sid187_gci1338586, 00.html

  • Backup with vRanger connection using NFS to a Data Domain appliance...

    Did he this?  We are, but have random failures when it appears that the NFS mounting times.   When we go through a connection CIFS on the Data Domain appliance via the server this connection vRanger is installed, we have never failed, but our backup window has passed.

    It's our vSwitch config:

    vSwitch0 - 3 natachasery, vmnic10, vmnic4, vmnic0.  Active service Console Port (vlan id 11) to vmnic0, standby for vmnic4 |  vRangerbackup port vmnic0 standby, active adapter vmnic10, vmotion disabled, group (no ID vlan).  VMotion port group (vlan id 20, active adapter vmnic 4, vmnic0 auxiliary card.)

    Mounting NFS uses only the Group of vRanger connection ports so the primary vmnic10 is used which is an Intel Gigabit VT Quad Port Server Adapter.  The other natachasery is on different maps, being an other Intel 82571EB and the vmnic0 is a Broadcom NetXtreme II BCM5708 onboard.  I read that it is not recommended to use different providers on the same port group.

    One of the experts want to chime on this config?

    Kind regards...

    Jamie

    If you found this information useful, please consider awarding points to 'Correct' or 'useful '.

    Remember, if it isn't one thing, it's your mother...

    I would say that you have a problem NFS.  Try to push a huge file as NFS (no backup) and see what happens.

    It should be pretty easy.  I don't know how you have it setup, but I would set the NFS for vRanger connection VM directly and not try to push the backups for the NFS mount.

    So if your connection VM vRanger is called VCB, and your data store is mounted as NFS01, you must mount NFS01 on VCB via another NIC and do not use the ESX host and the mount rather mount the NFS inside the VM direct.

  • Installation of VMware Consolidated Backup with vRanger connection - first installation

    I want to install VCB (for the first time) that will be integrated with Vizioncore vRanger connection.

    Does anyone have a better practice and document installation on the installation of the VCB process?

    Also someone with experience integrating connection VCB with vRanger?

    Thank you all...

    Follow the instructions of vizioncore.  They pretty much say on complete installation.  This is the best practice.

    vRanger connection works very well with VCB.  Install connection vRanger first then install the VCB proxy for vRanger connection.

  • vRanger connection Vs Netvault

    If we compare vRanger connection and Netvault, that would be a better solution to make backups?

    Thank you!

    Hi GeeKa,

    It depends on what you want to protect. NetVault can safeguard physical and virtual environments and application aware technology who speaks natively for many applications, SQL, Exchange, SharePoint, MySQL, Oracle, PostgreSQL, DB2, Informix, Sybase, NDMP for NAS etc. Sending data on disk or on tape. In addition to supporting Hyper-V & VMware technology.

    vRanger connection specializes in virtualization and has features dedicated to these environments, for example, the setting, the replication of VM, indexing. Scalability through the deployment of virtual appliances based on Linux for VMware offers the possibility to evolve without compromising speed. It is directly targeting technology too, so it's not bottle neck. It also takes care of backup of the physical Windows machines, so if you have a left little more after virtualization, vRanger connection can deal with those too.

    VRanger connection both NetVault can operate devices of series deduplication Dell DR and offer source side deduplication in virtual and physical environments. (vRanger same connection the fact of its virtual appliances!)

    Here are a few links to data sheets.

    http://software.Dell.com/documents/NetVault-backup-datasheet-13228.PDF

    http://software.Dell.com/documents/vRanger-Pro-datasheet-21449.PDF

    and how to compare products...

    http://software.Dell.com/documents/Dell-data-protection-portfolio-brochure-datasheet-72137.PDF

    I hope this helps.

    See you soon,.

    Adrian.

Maybe you are looking for