cancel
Showing results for 
Search instead for 
Did you mean: 

Backing up / restoring VM's - 7.6.0.3

lovethatcheese
Level 5

All,

I'm still in the process of figuring out how to correctly backup / restore VM's..

I was able to connect and backup this VM before, but ran into a problem restoring a file to the server. It was put on the back burner for a bit due to other projects, but now that I'm looking at it again, I am running into issues even connecting:

11/17/2014 11:24:26 AM - snapshot backup of client OWLOGGING using method VMware_v2
11/17/2014 11:24:30 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - find_virtual_server_vm: Unable to Login to server: 10.24.32.111: SYM_VMC_FAILED_TO_CREATE_SNAPSHOT
11/17/2014 11:24:33 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - VMware_freeze: Unable to locate VM OWLOGGING using VM hostname
11/17/2014 11:24:34 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
11/17/2014 11:24:34 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
11/17/2014 11:24:34 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - snapshot processing failed, status 4239  
11/17/2014 11:24:34 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - snapshot creation failed, status 4239  
11/17/2014 11:24:34 AM - Warning bpbrm(pid=1788) from client OWLOGGING: WRN - ALL_LOCAL_DRIVES is not frozen   
11/17/2014 11:24:34 AM - Info bpfis(pid=1708) done. status: 4239         
11/17/2014 11:24:34 AM - end Parent Job; elapsed time: 0:00:55
11/17/2014 11:24:34 AM - Info bpfis(pid=1708) done. status: 4239: Unable to find the virtual machine   
11/17/2014 11:24:37 AM - Info bpbrm(pid=4988) Starting delete snapshot processing        
11/17/2014 11:24:38 AM - Info bpfis(pid=3936) Backup started          
11/17/2014 11:24:38 AM - Critical bpbrm(pid=4988) from client OWLOGGING: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.OWLOGGING_1416241419.1.0     
11/17/2014 11:24:38 AM - Info bpfis(pid=3936) done. status: 4207         
11/17/2014 11:24:38 AM - end VMware, Create Snapshot; elapsed time: 0:00:59
11/17/2014 11:24:38 AM - Info bpfis(pid=3936) done. status: 4207: Could not fetch snapshot metadata or state files 
Unable to find the virtual machine(4239)

____________________________________

Is this something as simple as a credential issue? I created a service account for this machine and allowed it access on the OS, but get this as soon as I kick off a backup job.

Thanks for any help / guidance.

-Scott

 

1 ACCEPTED SOLUTION

Accepted Solutions

sksujeet
Level 6
Partner Accredited Certified

11/17/2014 11:24:33 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - VMware_freeze: Unable to locate VM OWLOGGING using VM hostname

11/17/2014 11:24:38 AM - Info bpfis(pid=3936) done. status: 4207: Could not fetch snapshot metadata or state files 
Unable to find the virtual machine(4239)

It seems it is not able to find the vm, please check this TN and make sure you backup it accordingly

Which Vvmware infrastructure you are on?Is this is the only machine having issue? Are the other VMs backing up fine?

Below are the TN if you are the begineer.

http://www.symantec.com/docs/HOWTO70892

http://www.symantec.com/docs/HOWTO70882

 

View solution in original post

2 REPLIES 2

sksujeet
Level 6
Partner Accredited Certified

11/17/2014 11:24:33 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - VMware_freeze: Unable to locate VM OWLOGGING using VM hostname

11/17/2014 11:24:38 AM - Info bpfis(pid=3936) done. status: 4207: Could not fetch snapshot metadata or state files 
Unable to find the virtual machine(4239)

It seems it is not able to find the vm, please check this TN and make sure you backup it accordingly

Which Vvmware infrastructure you are on?Is this is the only machine having issue? Are the other VMs backing up fine?

Below are the TN if you are the begineer.

http://www.symantec.com/docs/HOWTO70892

http://www.symantec.com/docs/HOWTO70882

 

bpdown
Level 4

Looks like permissions issue to me. Checkout this technote and apply all permissions.

http://www.symantec.com/business/support/index?page=content&id=TECH130493