Unsolved

This post is more than 5 years old

1 Rookie

 • 

2 Posts

16963

October 15th, 2014 16:00

Upgrading Avamar proxy after grid upgrade

Hello, we recently upgraded our Avamar grid to 7.0.2 and are having issues with some of proxies not releasing VM disks after performing their backups. An example:

AvamarProxy01 -> Reconfigures itself with Prod-FS01 disk -> starts backup, backup completes -> disk is not released back to VM (stays attached to AvamarProxy01) -> next daily backup occurs, disk is already loaded so it starts backup. Backup fails as it is unable to create snapshot -> Prod-FS01 now shows "needing disk consolidation" -> In order to perform disk consolidation we have to release the disk from AvamarProxy01 and perform the consolidation, which starts the whole process over.

Sometimes it takes a few days of the drive being "hung" before it will need consolidation.

When I spoke with EMC the tech stated we should upgrade the proxy to 7.0.2 to match the grid but I'm not able to find the 7.0.2 ISO? We have a "AvamarVMWareCombined-Lunx-x86-7.1.100-370.iso" on our download page (from upgrading another client recently). Is this the right ISO to use or where can I get the 7.0.2 ISO?

1 Rookie

 • 

23 Posts

October 15th, 2014 22:00

Hello oisyz - have you checked the Download page of your upgraded Avamar grid?

117 Posts

October 16th, 2014 01:00

Hello,

As you have AvamarVMWareCombined-Lunx-x86-7.1.100-370.iso on your downloads page it looks like the server was upgraded to 7.0.2 however at somepoint you upgraded your client release to 7.1.

As per the Avamar compatibility matrix, 7.1 proxies are compatible with a 7.0 server, HOWEVER please review the release notes (page 36)  that document the limitations around this combination.

If you decide to stay with going up to 7.0.2, which is likely the easier option, then I have uploaded the 7.0.2-47 ISO (for upgrades) and the OVA (for new proxies) here: https://ftp.emc.com/action/login?domain=ftp.emc.com&username=ZW8Qw9y9T&password=lB6BtB7tS7 also accessible via FTP here: ftp://ZW8Qw9y9T:lB6BtB7tS7@ftp.emc.com.

NOTE- the ftp account will only stay active 7 days from today. If you require the ISO at a later date, please open an SR with support so that they can give you access to the ISO.

Regards,

Adam

1 Rookie

 • 

2 Posts

October 16th, 2014 07:00

Adam,

I see the items listed here are "7.0.102-47". Is that the same as the 7.0.2?

This would be exactly what I was looking for.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 16th, 2014 07:00

Thank you Adam,

is there an upgrade procedure for the proxies ? I am currently running 7.0.101

117 Posts

October 16th, 2014 09:00

Hello,

7.0.102-47 is the "client" version associated with Avamar Serverversion 7.0.2, so yes it is the same release.

For upgrade instructions, please see the Avamar 7.0 VMware guide, page 40.

The iso should only be used if the current proxy is an older version and one of the following is true:

  • Avamar server is in 7.0.2 or higher
  • Avamar server is in 7.0 and the plugin catalogue has been updated (mccli plugin show shows version plugins for 7.0.102 or higher)
  • Avamar server is in 7.0 and the the downloads page shows client that are 7.0.102 or higher.

Please always review release notes and the compatibility guide before any upgrades.

Regards,

Adam

2 Intern

 • 

498 Posts

October 17th, 2014 11:00

I go to avamar server via web browser to the server and the down load  -

for me I then go to Vm Ware vSphere

EMC Avamar VMWARE Image Backup/FLR appliance

that has the ova and iso files

We just use the ova file, I pass it on to my Vm guys and they make me new proxies.

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 17th, 2014 11:00

why new proxies versus upgrading existing ones ?  All my proxies are dual-home, it would be PITA to build them from scratch.

2 Intern

 • 

498 Posts

October 17th, 2014 12:00

well when we went from 6.x to 7.x they TOLD us go with new.

I only have

3x8

and 1x8

and I have that command that says make the proxy connect to all datastores and groups.

so does not take a lot for me to make new, and be safe.

If I had more and it was a bother (like back when I had 20 that would have had to be made new) I would upgrade.

this last 2 times I just re-made them (took the vm guy all of 10 minutes) in 30 minutes I was all set.

2 Intern

 • 

498 Posts

October 17th, 2014 13:00

because the ova MAKES proxies.

once I give the ova to the vm guy

he deletes the proxies from vcenter

and then re makes them with the same names

tells me when he is done.

I go into vcenter and open the console and finish booting them

making sure everything is ok (following the manual)

then I usually restart the vcenter connection in avamar

make sure they are added to all datastores and groups ( I don't limit my vm's to specific datastores or groups - if One proxy is down I want the back to be able to use another one)

all done.

that is just the way I saw  the instructions, quick and easy to me!

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 17th, 2014 13:00

do you delete the existing proxies before you deploy and activate new ones ? What the is process that you follow ?

Thank you

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 18th, 2014 05:00

ok, so you don't delete old proxies from Avamar. I have 15 proxies (3 different vCenter environments) so i will try the upgrade route and see how it goes.

Thank you

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 20th, 2014 14:00

Richie,

what does upgradeproxy do ? Where/How does it get the new binaries to upgrade existing proxy VMs ?

21 Posts

October 20th, 2014 14:00

Yes should upgrade just fine. Also to make this alittle easier you can use proxycp.jar

ftp://avamar_ftp:anonymous@ftp.avamar.com/software/scripts/proxycp.jaranonymous@ftp.avamar.com/software/scripts/proxycp.jar

download to utility node, usually /home/admin

In response to your first question you can use this command to release the disks if no backups are running

java -jar proxycp.jar --listproxydisk --cleanup

then to upgrade you can do this.

java -jar proxycp.jar --upgradeproxy

Then once that finishes you can confirm the proxies are updating by this command

java -jar proxycp.jar --cmd "avtar --version | grep version"

and confirm the output is consistent with the new version you installed.

Richie

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

October 20th, 2014 14:00

Very nice, thank you Richie,

when i run java -jar proxycp.jar --cmd "avtar --version | grep version" i get

Error : Auth cancel

i tried the same command with --Password but that did not work either. 

21 Posts

October 20th, 2014 14:00

It grabs the rpm package already located on the utility node if you have your client catalog updated as well to the latest version /usr/local/avamar/src/downloads/.....

then it copies the rpm to the proxies, runs the rpm upgrade, removes the rpm once done and then should be good to go.

Richie

0 events found

No Events found!

Top