Veeam Agent for Mac Errors

[graymalkin]

Hi All,

I'm running into an odd situation here. I ran Veeam Agent for Mac (2.0.2.854 - Free) backing up to a local external hard drive for weeks without issues. Once I felt confident that Veeam was doing incrementals from my Mac properly, and I could do successful restores, I reconfigured the backup job to send the backups to my home NAS. That was were my smooth experience with Veeam Agent for Mac ended. Since then, I have been unable to perform a successful backup. The two errors I get most often is "Request canceled by user" or "Server error 301: Moved Permanently". I cannot isolate any reason why I get one error or the other. One error of the other will present themselves whether I run the backup manually, or if I let it run via schedule.

In each situation, the job successfully mounts my NAS, creates the backup session folder and copies the metadata successfully. The metadata is a few MB in size. The job then ends in a failed status with one of the two errors listed above.

Things I have tried:
Turning off firewalls on both my Mac and my NAS, to ensure that I am not getting tripped by a firewall issue.
Executing the job with sudo via the CLI on my Mac.
Mounting the NAS share on my Mac before I start the backup.
Using IP rather than host name for the network connection
Disabling Encrypted backup settings.
Re-installing the Veeam Agent for Mac out of sheer desperation.

Here is a log snippet from the "Server error 301: Moved Permanently" error (from /var/log/veeam/Backup/BackupJobName/SessionID/Job.log):

[

Code: Select all

12.05.2023 07:52:44.023] <0x027141> lpbcore  |   AWS aux data are set.
[12.05.2023 07:52:44.023] <0x027141> vmb      |   Aux data are deleted.
[12.05.2023 07:52:44.023] <0x027141> lpbcore  |   Product specific aux data are serialized.
[12.05.2023 07:52:44.023] <0x027141> lpbcore  |   Aux data are set as [REDACTED]
[12.05.2023 07:52:44.023] <0x027141> vmb      |   Getting Google OIB metadata from: http://metadata.google.internal.
[12.05.2023 07:52:44.271] <0x027141> vmb      |   Getting Google OIB metadata from: http://metadata.google.internal. Failed.
[12.05.2023 07:52:44.271] <0x027141> vmb      |     [c683] >> : disconnect
[12.05.2023 07:52:44.273] <0x027141> vmb      |     [c683] out: 
[12.05.2023 07:52:44.273] <0x0272be> vmb      | WARN|Connection was closed.
[12.05.2023 07:52:44.274] <0x0272be>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:52:44.274] <0x0272bb> vmb      | WARN|Connection was closed.
[12.05.2023 07:52:44.274] <0x0272bb>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:52:45.617] <0x02727f> vmb      | WARN|Connection was closed.
[12.05.2023 07:52:45.617] <0x02727f>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:52:45.617] <0x02726a> vmb      | WARN|Connection was closed.
[12.05.2023 07:52:45.617] <0x02726a>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:52:45.618] <0x027141> vmb      |   [SessionLog][processing] Releasing snapshot.
[12.05.2023 07:52:45.626] <0x027141> lpbcore  | BackupJobPerformer: Creating backup. Failed.
[12.05.2023 07:52:45.626] <0x027141> vmb      | [SessionLog][error] Failed to perform backup.
[12.05.2023 07:52:45.629] <0x027141> vmb      | [SessionLog][error] Server error 301: Moved Permanently.
[12.05.2023 07:52:45.632] <0x027141> vmb      | [SessionLog][error] Processing finished with errors at 2023-05-12 12:52:45 UTC.
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | ERR |Server error 301: Moved Permanently
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |--tr:Failed to make http request: [http://metadata.google.internal/computeMetadata/v1/instance/licenses//0/id].
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |--tr:in astr (anonymous namespace)::GetHttpResponseBodySafe(const astr &) at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/VmbPlatformLib/vmbplatform/publiccloud/GoogleMetadata.cpp:45
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |--tr:Failed to collect google metadata.
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |--tr:in static SGoogleMetadata::Ptr vmbplatform::SGoogleMetadata::Collect() at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/VmbPlatformLib/vmbplatform/publiccloud/GoogleMetadata.cpp:79
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |--tr:Failed to create Oib summary XML.
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |--tr:in static lpbcorelib::backup::IBackupObjectPtr lpbcorelib::backup::CBackupJobHelper::CreateOibSummaryXml(vmbplatform::model::COibPtr, const std::list<IBackupObjectPtr> &, vmbplatform::model::CBackupJobPtr &, indexing::CIndexingPtr, managed::CLocationInfoSpec::Ptr, const lpbcorelib::backup::CCbtDataContainer &) at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/LPBCoreLib/lpbcorelib/backup/BackupJobHelper.cpp:168
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |Backup job has failed.
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |--tr:in virtual void lpbcorelib::backup::CBackupJobPerformer::execute() at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/LPBCoreLib/lpbcorelib/backup/BackupJobPerformer.cpp:210
[12.05.2023 07:52:45.634] <0x027141> lpbcore  | >>  |An exception was thrown from thread [160065].
[12.05.2023 07:52:45.642] <0x0270ff>          |   Closing socket device.
[12.05.2023 07:52:45.642] <0x0270ff> lpbcore  | LpbManSession: Processing commands. ok.
[12.05.2023 07:52:45.642] <0x0270ff>          | Closing socket device.
[12.05.2023 07:52:45.642] <0x027215>          | Thread finished. Role: 'free space watcher'.
[12.05.2023 07:52:46.861] <0x027141> lpbcore  | JOB STATUS: FAILED.
[12.05.2023 07:52:46.861] <0x027141>          | Thread finished. Role: 'Backup job execution'.
[12.05.2023 07:52:46.862] <0x0270ff>          | Closing socket device.
[12.05.2023 07:52:46.863] <0x0270ff> jobman   | Application session has been finished.

And here is one from the "Request canceled by user" error:

Code: Select all

[12.05.2023 07:56:12.457] <0x0279a5> lpbcore  |   AWS aux data are set.
[12.05.2023 07:56:12.457] <0x0279a5> vmb      |   Aux data are deleted.
[12.05.2023 07:56:12.457] <0x0279a5> lpbcore  |   Product specific aux data are serialized.
[12.05.2023 07:56:12.458] <0x0279a5> lpbcore  |   Aux data are set as [REDACTED]
[12.05.2023 07:56:12.458] <0x0279a5> vmb      |   Getting Google OIB metadata from: http://metadata.google.internal.
[12.05.2023 07:56:28.529] <0x0279a5> vmb      |   Getting Google OIB metadata from: http://metadata.google.internal. Failed.
[12.05.2023 07:56:28.529] <0x0279a5> vmb      |     [3348] >> : disconnect
[12.05.2023 07:56:28.531] <0x0279a5> vmb      |     [3348] out: 
[12.05.2023 07:56:28.532] <0x027abc> vmb      | WARN|Connection was closed.
[12.05.2023 07:56:28.532] <0x027abc>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:56:28.532] <0x027ab9> vmb      | WARN|Connection was closed.
[12.05.2023 07:56:28.532] <0x027ab9>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:56:29.834] <0x027a74> vmb      | WARN|Connection was closed.
[12.05.2023 07:56:29.834] <0x027a74>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:56:29.835] <0x027a59> vmb      | WARN|Connection was closed.
[12.05.2023 07:56:29.835] <0x027a59>          | Thread finished. Role: 'Client receiver'.
[12.05.2023 07:56:29.835] <0x0279a5> vmb      |   [SessionLog][processing] Releasing snapshot.
[12.05.2023 07:56:29.842] <0x0279a5> lpbcore  | BackupJobPerformer: Creating backup. Failed.
[12.05.2023 07:56:29.843] <0x0279a5> vmb      | [SessionLog][error] Failed to perform backup.
[12.05.2023 07:56:29.846] <0x0279a5> vmb      | [SessionLog][error] Request canceled by user.
[12.05.2023 07:56:29.848] <0x0279a5> vmb      | [SessionLog][error] Processing finished with errors at 2023-05-12 12:56:29 UTC.
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | ERR |Request canceled by user.
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |--tr:Failed to make http request: [http://metadata.google.internal/computeMetadata/v1/instance/image].
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |--tr:in astr (anonymous namespace)::GetHttpResponseBodySafe(const astr &) at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/VmbPlatformLib/vmbplatform/publiccloud/GoogleMetadata.cpp:45
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |--tr:Failed to collect google metadata.
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |--tr:in static SGoogleMetadata::Ptr vmbplatform::SGoogleMetadata::Collect() at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/VmbPlatformLib/vmbplatform/publiccloud/GoogleMetadata.cpp:79
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |--tr:Failed to create Oib summary XML.
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |--tr:in static lpbcorelib::backup::IBackupObjectPtr lpbcorelib::backup::CBackupJobHelper::CreateOibSummaryXml(vmbplatform::model::COibPtr, const std::list<IBackupObjectPtr> &, vmbplatform::model::CBackupJobPtr &, indexing::CIndexingPtr, managed::CLocationInfoSpec::Ptr, const lpbcorelib::backup::CCbtDataContainer &) at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/LPBCoreLib/lpbcorelib/backup/BackupJobHelper.cpp:168
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |Backup job has failed.
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |--tr:in virtual void lpbcorelib::backup::CBackupJobPerformer::execute() at /Users/builder/VAM/vam_2.0.2/VeeamAgentEx/Sources/LPBCoreLib/lpbcorelib/backup/BackupJobPerformer.cpp:210
[12.05.2023 07:56:29.851] <0x0279a5> lpbcore  | >>  |An exception was thrown from thread [162213].
[12.05.2023 07:56:29.861] <0x027954>          |   Closing socket device.
[12.05.2023 07:56:29.862] <0x027954> lpbcore  | LpbManSession: Processing commands. ok.
[12.05.2023 07:56:29.862] <0x027954>          | Closing socket device.
[12.05.2023 07:56:29.862] <0x027a13>          | Thread finished. Role: 'free space watcher'.
[12.05.2023 07:56:31.047] <0x0279a5> lpbcore  | JOB STATUS: FAILED.
[12.05.2023 07:56:31.047] <0x0279a5>          | Thread finished. Role: 'Backup job execution'.
[12.05.2023 07:56:31.048] <0x027954>          | Closing socket device.
[12.05.2023 07:56:31.049] <0x027954> jobman   | Application session has been finished.

Anyone have any idea what is going on here? If I revert back to using a local drive, backup runs fine. Thanks for any advice.

[Mildur]

Hi Joseph

This is not a support forum and it is not allowed to post log files.
Please respect our forum rules which were provided with you in red letters when you created this topic:

POSTING AN ERROR OR TECHNICAL ISSUE?
You must include Veeam support case ID, or your post will be removed (learn more)

Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be deleted by moderators.

Best,
Fabian

[PTide]

Hello,

Would you provide more details about your setup please? This part of the log is the most interesting to me:

Code: Select all

http://metadata.google.internal/computeMetadata/v1/instance/licenses//0/id

What kind of NAS do you use?

Is google somehow involved here on your part?

If not, then I suspect that it's a known bug (to be fixed in the next patch) and the following workaround may help:

add this to /etc/hosts: 127.0.0.1 metadata.google.internal

And restart veeamservice

Thanks!

[graymalkin]

Hi PTide, thanks for your reply. I was told not to post technical issues here, so I unfortunately abandoned my Veeam for Mac agent for the time being and just wrote my own file backup solution using rsync and rsnapshot. I am a fan of Veeam products and use them professionally, so eventually I may return to this and try to get it working again.

However, to answer your questions, my NAS is a Fedora Linux machine with a ton of storage. The share is accessible via samba. Linux and Windows Veeam clients can backup to this share with no issues.

The Google line is not from any products I use, I assumed that the Veeam client needs to reach out to that URL.

Thanks again for taking the time to reply, I really appreciate it. If and when I get back to this, I will try your suggestions and put an update in a separate post that hopefully better aligns with Veeam's Forum guidelines.