Skip to main content

It would appear I cannot start my first backup.  I installed VEEAM Backup & Replication 11 community edition on my home setup to learn how to manage our work paid edition.

Using a 3-2-1 rule I wanted to Backup to QNAS NAS/Chris-Garage D drive/external drive air gapped when other two backups are functioning

Step one:       I want to backup my laptop Chris Laptop

Step two:     I installed the software on C:\ of a windows 11 computer called Chris-Garage with cache on D:\

Step three:   Built a backup for Chris Laptop (windows 10) to backup to Chris-Garage in which failed (see picture below) xx.12 is the laptop and xx.71 is the garage computer

Step four:  Build logs but can’t find which log would be the error

 

 

Go to here to check the logs from the Backup Server if that is where jobs are controlled from - C:\ProgramData\Veeam\Backup\<job folder name>

This will show you where the failure is happening to hopefully address the issue.  Feel free to post back here with more details.


Is there a particular log that will show it?  I can’t look until I get home tonight, but the last time I checked there were a tree of folders with logs in every tree if memory serves me correctly.


Is there a particular log that will show it?  I can’t look until I get home tonight, but the last time I checked there were a tree of folders with logs in every tree if memory serves me correctly.

Yes, there is a folder for each job name which contains the logs you need to check.  Just look for the job with the agent backup and check there.


Hi, easy question, did you deploy the agent from the server?

or did you install it manually in the client?

sometimes I’ve got the error when installing the agent / client alone on my lab.

uninstalling and pushing the client from the server did the trick.

cheers-


I only installed the software to the windows 11 computer that I will call the server.  I never pushed/installed anything out to the laptop that I want to back up.  I assume the client is the machine I want to back up.  How do I push to the device?

I only built the backup job as I thought that would deal with the client machine

 

 


It would appear I cannot start my first backup.  I installed VEEAM Backup & Replication 11 community edition on my home setup to learn how to manage our work paid edition.

Using a 3-2-1 rule I wanted to Backup to QNAS NAS/Chris-Garage D drive/external drive air gapped when other two backups are functioning

Step one:       I want to backup my laptop Chris Laptop

Step two:     I installed the software on C:\ of a windows 11 computer called Chris-Garage with cache on D:\

Step three:   Built a backup for Chris Laptop (windows 10) to backup to Chris-Garage in which failed (see picture below) xx.12 is the laptop and xx.71 is the garage computer

Step four:  Build logs but can’t find which log would be the error

 

 

Hi @christo in your image we can see rescan of you laptop fails. so is natural backup not work. Have you installed agent v6? Have you checked system and port requirement (https://helpcenter.veeam.com/docs/agentforwindows/userguide/system_requirements.html?ver=60)? 

How have you created backup jobs? I think, quoting @Chris.Childerhose and @HunterLAFR, you can check log file trying to figure where is the issue. 

Let us know about your troubleshooting


Hi, due to troubleshooting, that is something more related to “support”, I don`t want to get into that, 

following the community perspective, I suggest you to check this information, and run a test:

https://helpcenter.veeam.com/docs/backup/agents/protected_computers_install.html?ver=120

From the Veeam B&R server, you add the computer you want to backup, and then you trigger the agent installation.

Please make sure they are in the same network, or they can see each other in the net they are.

Run some tests and let us know the results, to keep assisting you in this topic.

Cheers.

Luis.


Thank you for all the information you have provided.  I will attend to this tonight.  I did check the log file and there wasn’t anything obvious in it.  I mean, the log started off by fixing about 12 files, then it did 5 lines of network checking, then it came to a conclusion that it failed and then repeated a couple more times.  As a next step I will install the agent from the link given above and try backing up again.

I will report my findings and thank you again.


It would appear I cannot install the agent either as a rescan has to succeed before the installation can be performed from the server.  I have looked at the log file and there isn’t anything obvious there either except to say that it fails.  I will try to paste a portion into this window:

 

/12.02.2023 16:19:35] <16> Info         - - - - Response: EpDiscovery: id 'a591a521-69fc-4b24-ba82-b2d480d9021c', container id '00000000-0000-0000-0000-000000000000'
012.02.2023 16:19:36] <16> Info         oWaitingForRescan] Waiting for rescan finished: Session 25fd9852-1c16-4bb5-8727-71cdf15466bd, oij 280c44b1-2aff-49a8-9651-21dca1f26a9f, result Failed
t12.02.2023 16:19:36] <16> Info         CEpAgentPolicyTaskScheduler] Object 53708ccd-979f-43d4-9648-fdafea395efb contains 1 agents.
n12.02.2023 16:19:36] <16> Info         &CEpAgentPolicyTaskScheduler] Policy task type is ProcessAll
p12.02.2023 16:19:36] <16> Info         File exclude settings is ignored due to the license limitations
12.02.2023 16:19:36] <16> Info         ]EpAgentPolicyJobPerformer] Processing task 1
o12.02.2023 16:19:36] <15> Info             ]DB] Sync agent odc485e22-2fb1-4969-ac94-4eca61c6bb8a], managementMode -ByAgent]
b12.02.2023 16:19:36] <15> Info         3CPolicyTaskAgentPreparer] There is no started discovery job(s)
e12.02.2023 16:19:36] <01> Info         .EpAgentPolicyJobPerformer] Processing '192.168.0.71'.
b12.02.2023 16:19:36] <01> Info         Agent dc485e22-2fb1-4969-ac94-4eca61c6bb8a used in job
212.02.2023 16:19:36] <01> Info         /EpAgentPolicyJobPerformer] Preparing '192.168.0.71'.
t12.02.2023 16:19:36] <01> Info         Credentials was found on 6192.168.0.71]
12.02.2023 16:19:36] <01> Info         .EpAgentPolicyJobPerformer] 192.168.0.71 skipped.
12.02.2023 16:19:36] <01> Info         Job has been stopped successfully. Name: 1Laptop1], JobId: 15254761-0f71-498b-88bf-3687f9ac0e39]
:12.02.2023 16:19:36] <01> Info         6BackupJobPostActivity] JobSession 'f2d5eaac-9cb9-4f44-8212-11999eb73db1' PostActivity: 'AskService'
d12.02.2023 16:19:36] <01> Info         tBackupJobPostActivity] Session result is Failed. Checking if it is last retry
s12.02.2023 16:19:36] <01> Info         BackupJobPostActivity] wouldBeRetried: 'False'. Need post activity: 'True'
u12.02.2023 16:19:36] <01> Info         eJobSession] Completing session 'f2d5eaac-9cb9-4f44-8212-11999eb73db1'.
12.02.2023 16:19:36] <01> Info         Backuped size: 0 B, total backuped size: 0 B
912.02.2023 16:19:36] <01> Info         Job session 'f2d5eaac-9cb9-4f44-8212-11999eb73db1' has been completed, status: 'Failed', '0 B' of '0 B' bytes, '0' of '0' tasks, '0' successful, '0' failed, details: '', PointId: 00000000-0000-0000-0000-000000000000]
c12.02.2023 16:19:36] <01> Info         0BackupJobPostActivity] JobSession 'f2d5eaac-9cb9-4f44-8212-11999eb73db1' PostActivity: 'AskService'
A12.02.2023 16:19:36] <01> Info         1BackupJobPostActivity] Session result is Failed. Checking if it is last retry
12.02.2023 16:19:36] <01> Info         sBackupJobPostActivity] wouldBeRetried: 'False'. Need post activity: 'True'
;12.02.2023 16:19:36] <01> Info             Job event 'ready2finish' was created for session 'f2d5eaac-9cb9-4f44-8212-11999eb73db1'. Event full name: 'Global\ready2finishvmjobeventf2d5eaac-9cb9-4f44-8212-11999eb73db1'
-12.02.2023 16:19:36] <01> Info         Job iLaptop1] is ready to finish. SessionId: 9f2d5eaac-9cb9-4f44-8212-11999eb73db1]
g12.02.2023 16:19:36] <01> Info             Job event 'ready2finish' was disposed. Session: 'f2d5eaac-9cb9-4f44-8212-11999eb73db1'.
I12.02.2023 16:19:36] <01> Info             Job event 'finished' was disposed. Session: 'f2d5eaac-9cb9-4f44-8212-11999eb73db1'.
l12.02.2023 16:19:36] <01> Info         Disposing SVeeamBackupService...
a12.02.2023 16:19:36] <01> Info             Unregistering TCP client channel bstcp]
g12.02.2023 16:19:36] <01> Info             Channel successfully unregistered
e12.02.2023 16:19:36] <01> Info             Unregistering TCP client channel bs_tcp]
12.02.2023 16:19:36] <01> Info             Channel successfully unregistered
12.02.2023 16:19:36] <01> Info             Unregistering TCP client channel &cat_tcp]
12.02.2023 16:19:36] <01> Info             Channel successfully unregistered


At this point if you can get Support then I would suggest going that route.  They should be able to help get you going with this.  Nothing jumps out from the logs to me either.


I turned off windows firewall and I finally see an error, and yes my account has admin privileges':

[16.02.2023 16:50:50] <19> Info         RPC] Making sure that the deployment service installed on host o192.168.0.12].
r16.02.2023 16:50:50] <19> Info         RPC] Creating persistent connection to ADMIN$ shared folder on host o192.168.0.12].
]16.02.2023 16:51:11] <19> Info         RPC] Creating persistent connection to ADMIN$ shared folder on host d192.168.0.12]. Failed.
a16.02.2023 16:51:11] <19> Info         nRPC] Making sure that the deployment service installed on host s192.168.0.12]. Failed.
]16.02.2023 16:51:11] <01> Warning      t192.168.0.12] Failed to install Installer service on 192.168.0.12:6160. Reason: The network name cannot be found.
n16.02.2023 16:51:11] <01> Warning      The network name cannot be found. (ERROR_BAD_NET_NAME)
O16.02.2023 16:51:11] <01> Warning      --tr:Error code: 0x00000043
o16.02.2023 16:51:11] <01> Warning      --tr:Failed to create persistent connection to ADMIN$ shared folder on host D192.168.0.12].
n16.02.2023 16:51:11] <01> Warning      --tr:Failed to install service -VeeamDeploySvc] was not installed on the host 192.168.0.12].   at VeeamProxyClient.GenerateComException(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* excMsg, Int32 errHrCode)


[16.02.2023 17:26:55] <01> Error        The network name cannot be found.
r16.02.2023 17:26:55] <01> Error        The network name cannot be found. (ERROR_BAD_NET_NAME)

 

I didn’t set up a name as I used an ip.  I wonder what name I got wrong? and what was going on with not creating the ADMIN$


DNS possibly?  I would check that too if applicable.


I want to thank everybody for your ideas and suggestions.  Since I am not entitled for tech support with the community edition I will just go ahead and delete the application.

As I learn the product in my work environment I may learn what went wrong at my home setup.

Until then, everybody take care and once and thank you 


It seems like I'm encountering difficulties starting my initial backup process with VEEAM Backup & Replication 11 Community Edition. Despite setting up the software on my Windows 11 machine, including cache allocation on the D:\ drive, the backup for my Windows 10 laptop to Chris-Garage isn't progressing as intended. Now, I'm troubleshooting to locate the specific error within the build logs.


It seems like I'm encountering difficulties starting my initial backup process with VEEAM Backup & Replication 11 Community Edition. Despite setting up the software on my Windows 11 machine, including cache allocation on the D:\ drive, the backup for my Windows 10 laptop to Chris-Garage isn't progressing as intended. Now, I'm troubleshooting to locate the specific error within the build logs.

Why are you using v11?  You should upgrade to v12 as that is the most current and supports newer OS versions.  It could be a compatibility issue so check the supporting OSes for v11.


It seems like I'm encountering difficulties starting my initial backup process with VEEAM Backup & Replication 11 Community Edition. Despite setting up the software on my Windows 11 machine, including cache allocation on the D:\ drive, the backup for my Windows 10 laptop to Chris-Garage isn't progressing as intended. Now, I'm troubleshooting to locate the specific error within the build logs. 

Again why are you using v11 when v12 is out?  Upgrade to v12 and the agent to the latest release to see if that helps.


Comment