magicmarker
1 Nickel

Re: Proxy VMDK extraction to alternate location?

Jump to solution

I can now see the UUIDs with Adam's suggestion. I think it's safer to view in mccli.

I've performed restores directly to the Iomega via the built in client for File agent based backups very successfully.

I've reached the point where I have turned on ssh on the Iomega and attempting to use avtar for the remaining restores for vmdk backups. When I execute the avtar command, I get command not found. So I performed a Linux search and found the avamar directory under: /mnt/system/opt/apps/emc/Avamar/avamar.

Under there is a bin and var folder. The avtar command is actually there but I cant execute it. Not sure what the extra -r in front of the standard permissions are. I'm not proficient in Linux permissions. Maybe Iomega has locked it down?

I guess I could map this device on a regular client but sure is ashamed I've come this far and cant execute avtar on Iomega.

root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/bin# ls -l

total 13284

-r-xr-xr-x 1 root root 3399304 Feb 12  2013 avagent.bin

-r-xr-xr-x 1 root root 2800168 Feb 12  2013 avscc

-r-xr-xr-x 1 root root    1700 Feb 12  2013 avtar

-r-xr-xr-x 1 root root 7389848 Feb 12  2013 avtar.bin

-r-xr-xr-x 1 root root     121 Feb 12  2013 unix.pin

root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/bin#

root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/bin# avtar --help
-sh: avtar: command not found
root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/bin# ./avtar --help
./avtar: line 23: BASEDIR: command not found
./avtar: line 23: BASEDIR: command not found
./avtar: line 47: unexpected EOF while looking for matching `"'
./avtar: line 49: syntax error: unexpected end of file
root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/bin#


root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/bin# cd ..
root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar# cd var
root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/var# ls -l
total 804
-rw-r----- 1 root root   7779 Nov 19 18:22 MOD-1384906786014-1001-Unix.alg
-rw-r----- 1 root root   7386 Nov 19 18:22 MOD-1384906786014-1001-Unix.log
-rw-r----- 1 root root   8433 Nov 19 23:20 MOD-1384907589160-1001-Unix.alg
-rw-r----- 1 root root 616845 Nov 19 23:20 MOD-1384907589160-1001-Unix.log
-rw-r----- 1 root root   8083 Nov 19 23:43 MOD-1384923637042-1001-Unix.alg
-rw-r----- 1 root root   8027 Nov 19 23:43 MOD-1384923637042-1001-Unix.log
-rw-r----- 1 root root   8291 Nov 20 11:49 MOD-1384926688209-1001-Unix.alg
-rw-r----- 1 root root  20152 Nov 20 11:49 MOD-1384926688209-1001-Unix.log
-rw-r----- 1 root root   8153 Nov 20 15:30 MOD-1384976095505-1001-Unix.alg
-rw-r----- 1 root root   9942 Nov 20 15:30 MOD-1384976095505-1001-Unix.log
-rw-r----- 1 root root   7690 Nov 20 18:01 MOD-1384987398842-1001-Unix.alg
-rw-r----- 1 root root   8457 Nov 20 18:01 MOD-1384987398842-1001-Unix.log
-rw-r----- 1 root root   8170 Nov 20 19:39 MOD-1384995535904-1001-Unix.alg
-rw-r----- 1 root root  15258 Nov 20 19:39 MOD-1384995535904-1001-Unix.log
-rw-r--r-- 1 root root    151 Nov 19 18:02 avagent.cfg
-rw-rw-rw- 1 root root     28 Nov 19 18:02 avagent.lck
-rw-r--r-- 1 root root  33472 Nov 21 12:03 avagent.log
-r-xr-xr-x 1 root root     69 Feb 12  2013 avtar.cmd
-rw-r--r-- 1 root root     85 Nov 19 18:02 cid.bin
root@px6-300d-TIJY3T:/mnt/system/opt/apps/emc/Avamar/avamar/var#

0 Kudos
Highlighted
ionthegeek
4 Ruthenium

Re: Proxy VMDK extraction to alternate location?

Jump to solution

On Linux and some other UNIX / UNIX-like platforms, the "avtar" command is a wrapper script for avtar.bin. It looks like there's some problem with this wrapper script. Try using avtar.bin instead of avtar in your command calls.

magicmarker
1 Nickel

Re: Proxy VMDK extraction to alternate location?

Jump to solution

Thanks Ian. Excellent. avtar.bin does seem to work. I can now experiment with the commands.

magicmarker
1 Nickel

Re: Proxy VMDK extraction to alternate location?

Jump to solution

To Restore a backup: CD to the bin directory. Avtar.bin is not in the Iomega path. You must use avtar.bin because the wrapper does not work.

   

cd /mnt/system/opt/apps/emc/Avamar/avamar/bin

 

./avtar.bin --extract --id=MCUser--password=MCUser1--path=/VcenterName/VirtualMachines/"VMName and UUID" --labelnum=XX --target=/nfs/Backups/VMName

This command will restore the entire backup of label#XX to the Iomega device in the local directory of the target option. One thing I've realized is you cannot monitor the backup activity in activity monitor. But I can live with that. Thanks to EMC, Ian Anderson and Adam Kirkpatrick for all the good advise.