VMware Cloud Community
JCS725
Contributor
Contributor

VCB 1.1 Question regarding vcbmounter

I am able to run the follwing command from my VCB Proxy and it work.

vcbmounter.exe -h myesxhost.mydomain.net -u root -p mypassword -a ipaddr:guestvm.mydomain.org -r e:\backup\guest-file -t file

When I run the following I get the trailing error.

C:\Program Files\VMware\VMware Consolidated Backup Framework>vcbmounter.exe -h vc01.mydomain.org -u vcusername -p vcpassword -a ipaddr:guestvm.mydomain.org -r e:\backup\guestvm-xx-full -t fullvm -m san

Current working directory: C:\Program Files\VMware\VMware Consolidated Backup Framework

HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 2.

HOSTINFO: This machine has 2 physical CPUS, 4 total cores, and 8 logical CPUs.

Using system libcrypto, version 90703F

Error: Other error encountered: Cannot connect to host vc01.mydomain.org: No connection could be made because the target machine actively refused it

Clearly I've missed something somewhere. Any help is greatly appreciated as always.

Thank you

0 Kudos
8 Replies
depping
Leadership
Leadership

did you set the permissions for this specific user within virtual center at the top level ? and did you give it the "vcb" role?

Duncan

My virtualisation blog:

JCS725
Contributor
Contributor

Well, no I didnt. But I created a basic ID on the Virtual Center Server then in the console at Hosts and Clusters added permission, added the ID and assigned that "VCB" role to it.

I'm still getting the same error. Does that ID need to be local admin on the VC Server?

0 Kudos
mittim12
Immortal
Immortal

Do you have port 443 specified in your config.js?

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

Message was edited by: mittim12

0 Kudos
JCS725
Contributor
Contributor

Here's my config.js I really appreciate the help..

/*

  • Generic configuration file for VMware Consolidated Backup (VCB).

*/

/*

  • Directory where all the VM backup jobs are supposed to reside in.

  • For each backup job, a directory with a unique name derived from the

  • backup type and the VM name will be created here.

  • If omitted, BACKUPROOT defaults to c:
    mnt.

  • Make sure this directory exists before attempting any VM backups.

*/

// BACKUPROOT="e:
backup";

/*

  • URL that is used by "mountvm" to obtain the block list for a

  • disk image that is to be mounted on the backup proxy.

*

  • Specifying this option is mandatory. There is no default

  • value.

*/

HOST="vc01.mydomain.org";

/*

  • Port for communicating with all the VC SDK services.

  • Defaults to 902

*/

// PORT="443";

/*

  • Username/password used for authentication against the mountvm server.

  • Specifying these options is mandatory.

*/

USERNAME="VCB_Backup";

PASSWORD="mypassword";

/*

  • SNAPSHOT_POLICY determines how disk snapshots for backup are being created:

  • +) "automatic"

  • A snapshot is being generated automatically by the Interoperability

  • Module right before backup and it is being removed

  • automatically right after backup.

  • +) "manual" -

  • Exactly one snapshot named "_VCB-BACKUP_" must already exist for

  • each protected VM. The snapshot is mounted/unmounted on the proxy,

  • but the snapshot is neither created nor deleted by the Legato Networker

  • Interoperability Module. - This can be used to have external tools

  • manage backup snapshot.

  • +) "createonly"

  • The Interoperability Module will create the snapshot for each VM

  • right before it gets backed up, but will not remove the snapshot

  • after unmounting.

  • +) "deleteonly"

  • The Interoperability Module assumes that the snapshot named

  • "_VCB-BACKUP_" has been created beforehand. The snapshot will be

  • deleted automatically after backup.

*

  • The default option is "automatic"

*

*/

//SNAPSHOT_POLICY="automatic";

/*

  • The criteria to be used to identify a virtual machine

*

  • +) ipaddr

  • VMs are looked up based on their DNS name/IP address.

  • +) name

  • VMs are looked up based on their name as shown in VirtualCenter.

  • Note that backup will fail for VMs with non-unique names.

*

  • The default option is "ipaddr". You should only change this

  • if you have multiple sets of VMs with the same IP address, but with

  • different names.

*/

//VM_LOOKUP_METHOD="ipaddr";

/*

  • Behavior for a backup job when the VM mount point already exists.

  • +) fail

  • A pre-existing mountpoint is causing a backup job to fail

  • +) delete

  • Attempt to remove the pre-existing mount point (and backup

  • snapshots associated with it). If this op. fails, fail

  • the backup job.

*

  • the default option is "fail"

*/

//PREEXISTING_MOUNTPOINT="fail";

/*

  • Behavior for backup job when a previous backup snapshot of a virtual

  • machine already exists.

*

  • +) fail

  • A pre-existing backup snapshot is causing a backup job to fail

  • +) delete

  • Attempt to delete the pre-existing backup snapshot. If the

  • backup snapshot can be deleted without errors, proceed with

  • the backup job. Otherwise fail the backup job.

*

  • the default option is "fail"

*/

//PREEXISTING_VCB_SNAPSHOT="fail";

/*

  • Number of times an operation is re-tried after it fails.

  • You might want to use this option if you see a large number

  • of backup jobs fail with "resource busy" errors.

*

  • Usually, backup software will retry failed jobs, but it

  • might be hours until the backup software retries.

*

  • By default, retry is disabled (set to 0).

*/

//MAX_RETRIES=0;

/*

  • Number of seconds to wait before retrying a failed

  • operation. The default value is 10 seconds.

*

  • If you change this default, you probably also want to change

  • the default for MAX_RETRIES (since this setting only matters

  • if MAX_RETRIES is larger than 0).

*/

//BACKOFF_TIME=10;

0 Kudos
JCS725
Contributor
Contributor

Seems some formatting problem happend when I pasted.

my backuproot is in the config.js as e:\backup (two back slash)

0 Kudos
mittim12
Immortal
Immortal

Any type of firewall software on the VC box that may block a connection? Your backup user doesn't have to be an admin of the box if granted the VCB role but what happens if you try the command with an administrator of the box? Do you get the same message?

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

0 Kudos
JCS725
Contributor
Contributor

There is no firewall enabled on the VC. I'm able to open in a browser.

I added the id to the administrators group on the vcb proxy and the vc and am still getting the same error..

Maddening I tell you.. :smileylaugh:

Thanks for the continued help.

0 Kudos
JCS725
Contributor
Contributor

Anyone have any other ideas?

Thanks

0 Kudos