This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrading vRanger

I am new to vRanger, just had it dumped in my lap actually.

Anyway, we have vRanger 7.1 and I see vRanger 7.6 is available.

Can I just download the upgrade and install it on-top of 7.1?

We currently have vSphere 5.5

  • Hello johnfli,

    Welcome to the vRanger family!

    First of all, I would recommend not to attempt the upgrade in place. Going from 7.1.x to 7.6.4 crosses at least 6 released versions so a direct upgrade would not have been tested.

    Also, there are a number of environmental factors to consider before upgrading:
    1. Is vRanger on a VM or a physical machine?
    2. What kind of repositories are being used? Are they Windows CIFS shares, or something like Data Domain or Quest DR Series?
    3. Is the vRanger database local or remote?
    4. Is vRanger being used for backups, replications, or both?
    5. Are vRanger Virtual Appliances being used?
    6. How many hosts and VMs are in the environment?
    7. How many vRanger jobs are being run?
    8. Are there plans in place to be upgrading the vSphere environment?

    Last, but certainly not least, are things working or was there a specific issue you would be attempting to resolve by upgrading?

    We would be happy to review things with you and look at the best path getting vRanger current. I will reach out to you via a direct message to look into opening a Service Request to do just that.
  • Hmmmm, wish I would have noticed your question earlier. ;)
    I went ahead and upgraded straight to 7.6.4.0
    Upgrade went just fine, only issue I had was not being able to connect to 'services', but a quick search on here showed that I just needed to download a file from MS. Appeared to go great. When I open vRanger, all my jobs are there, the history is there everything.
    BUT (notice the big but?)
    all the jobs fail now. the logs are not helpfull at all.
    Here are the answers to your previous questions:
    1. vRanger is on a physical machine
    2. repositories are all windows cifs shares
    3. vRanger database is on another machine
    4. vRanger is only doing backups, no replication
    5. no virtual appliances
    6. 12 hosts, over 200 vm's
    7. 14 jobs, each job covering several vm's
    8. we are planing on upgrading vSphere.

    Below is the end part of the log file:
    [2018-03-16 04:15:55.620]: Beginning backup task for BackupGroup-TestDev-DIFF-G1VTFMS01
    [2018-03-16 04:15:55.620]: Starting task validation.
    [2018-03-16 04:15:55.620]: Connection to g1ppvcs01.firemountain.local was properly validated.
    [2018-03-16 04:15:55.620]: g1ppesx11.firemountain.local is properly licensed.
    [2018-03-16 04:15:55.620]: Test connection to repository TESTDEV-Diff-g1ppbtgt01 starting...
    [2018-03-16 04:15:56.025]: Test connection to repository TESTDEV-Diff-g1ppbtgt01 successful!
    [2018-03-16 04:15:56.025]: Ending task validation... success!
    [2018-03-16 04:15:56.025]: Beginning initialization of backup information.
    [2018-03-16 04:15:56.914]: Retrieving the tasks parent information.
    [2018-03-16 04:15:56.946]: Retrieving save points for any full backups associated with this job.
    [2018-03-16 04:15:57.320]: Verifying content of repository.
    [2018-03-16 04:16:01.126]: Finished initialization of backup information successfully.
    [2018-03-16 04:16:01.126]: Initialization was sucessful. Backup type to run: Differential
    [2018-03-16 04:16:02.187]: A block size change was detected in the vRanger configuration file. The previous blocksize will be used until the retention policy triggers the next Full backup.
    [2018-03-16 04:16:03.857]: Retrieving the VM BIOS configuration completed.
    [2018-03-16 04:16:05.151]: Setting VM event completed.
    [2018-03-16 04:16:07.398]: Error:
  • Ok, found the issue. I had to change the vCenter account info:
    right-click the vCenter in vRanger inventory, click properties. CHange it to administrator@vsphere.local. Then restart the Quest.vRanger.Service. Ran the backup job again and it worked great.