VMware Cloud Community
lowemic1
Contributor
Contributor

VMware Consolidated Backup - Local Storage

So I'm testing using Consolidated Backup and Avamar for a backup system. Hitting some snags....but my main question is, does Consolidated Backup work on VM's that reside on the hosts local storage?

My test setup is one ESX host....with the proxy server being a VM....and trying to snap another VM on the same host. I've gotten everything setup (I think) but launching the backup job in Avamar the snapshots just don;t happen.

0 Kudos
7 Replies
AntonVZhbankov
Immortal
Immortal

VCB works with local storage in NBD mode.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
lowemic1
Contributor
Contributor

I saw that in the config.js ....I'm wondering if it's an authentication problem? I'm using as the host the VC server's FQDN and for a user the admin on the domain I log into the VC server with.

0 Kudos
AntonVZhbankov
Immortal
Immortal

I'm using vcbmounter directly, so i just specify vCenter host, login and password as parameters and everything works fine.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
lowemic1
Contributor
Contributor

ok I got it making snapshots now...I missed a line in our backup softwares script...the guide contradicts itself....anyway.......it fails right after creating a snapshot and here is the backup softwares log

2009-09-03 16:14:16.421 'App' 1904 error No path to device LVID:4a805458-ccdca918-6b58-0016355b5008/4a805457-1203b0d8-360c-0016355b5008/1 found.

2009-09-03 16:14:16.421 'BlockList' 1904 error

2009-09-03 16:14:16.984 'vcbMounter' 1904 error Error: Failed to open the disk: Cannot access a SAN/iSCSI LUN backing this virtual disk. (Hint: If you are using vcbMounter you can use the option "-m ndb" to switch to network based disk access if this is what you want.) If you were attempting file-level access, stop the vmount Service by typing "net stop vmount2" on a command prompt to force vmount to re-scan for SAN LUNs and re-try the command.

2009-09-03 16:14:16.984 'vcbMounter' 1904 error An error occurred, cleaning up...

...I'm using nbd in the config.js file (although weird the error says to use ndb) any ideas?

0 Kudos
AntonVZhbankov
Immortal
Immortal

Forget about config, when you use vcbmounter directly - add "-m ndb" as a parameter


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
lowemic1
Contributor
Contributor

if I'm not using the scripts...and the config.js..I'd have to run backups by hand.

EDIT: it looks like I got it working by specifying NBD in the utils.js file

0 Kudos
AntonVZhbankov
Immortal
Immortal

Why not use scripts? I scheduled backups by standard Windows Scheduler, all works fine.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos