Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
Post Reply
anthonycogswell
Novice
Posts: 4
Liked: never
Joined: Nov 06, 2017 2:55 pm
Full Name: Anthony Cogswell
Contact:

Import configuration not working

Post by anthonycogswell »

Trying to import a config doing an unattended install.

If I use a common file exported from a server that is working the import will not work with the following error.

E:\veeam>"C:\Program Files\Veeam\Endpoint Backup\Veeam.Agent.Configurator.exe" -import /f:"E:\veeam\configuration.xml"
ExitCode: 50

Errors:
Failed to perform the operation.
Invalid job configuration: This type of schedule is not supported.


I can export and import the config on the same server and it works fine. Just not able to use in a deployment model to multiple machines.
Vitaliy S.
VP, Product Management
Posts: 27377
Liked: 2800 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Import configuration not working

Post by Vitaliy S. »

Hi Anthony,

I believe you need to install a license key first, as the error message states that the issues is in scheduling options. These options are more advanced in the server edition, that's why importing this config to a FREE/workstation backup agent does not work.

Thanks!
anthonycogswell
Novice
Posts: 4
Liked: never
Joined: Nov 06, 2017 2:55 pm
Full Name: Anthony Cogswell
Contact:

Re: Import configuration not working

Post by anthonycogswell »

Steps for my unattended.

Install Veeam:
%~dp0VeeamAgentWindows_2.0.0.700.exe /silent /accepteula
Installs without error

Install License
"C:\Program Files\Veeam\Endpoint Backup\veeam.Agent.Configurator.exe" -license /f:"%~dp0veeam_agent_windows_subscription_0.lic" /s
License installs without error

Import Config
"C:\Program Files\Veeam\Endpoint Backup\Veeam.Agent.Configurator.exe" -import /f:"%~dp0130configuration.xml"
Error code 50
Vitaliy S.
VP, Product Management
Posts: 27377
Liked: 2800 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Import configuration not working

Post by Vitaliy S. »

Does it work when you choose a workstation based job configuration?
anthonycogswell
Novice
Posts: 4
Liked: never
Joined: Nov 06, 2017 2:55 pm
Full Name: Anthony Cogswell
Contact:

Re: Import configuration not working

Post by anthonycogswell »

Just did the same steps but with the workstation "/w" with the same error.
Vitaliy S.
VP, Product Management
Posts: 27377
Liked: 2800 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Import configuration not working

Post by Vitaliy S. »

I would suggest to check one more step before contacting our support team > does the backup agent accept the license key you install? Can you check it via its UI?
anthonycogswell
Novice
Posts: 4
Liked: never
Joined: Nov 06, 2017 2:55 pm
Full Name: Anthony Cogswell
Contact:

Re: Import configuration not working

Post by anthonycogswell »

It does accept it. It connects back to a B&R server now and data is going to a data domain. I have 6 machines backing up now and need to do another 40. Was hoping the unattended install along with SCCM was going to make this easy.
vClintWyckoff
Veteran
Posts: 500
Liked: 109 times
Joined: Oct 27, 2012 1:22 am
Full Name: Clint Wyckoff
Location: Technical Evangelist
Contact:

Re: Import configuration not working

Post by vClintWyckoff » 1 person likes this post

Anthony-
When you exported the configuration was the config based on a server schedule / license or workstation? Server and Workstation have different scheduling options, so when you import the key with the /s you specify server and maybe the config you're importing is not a server-based config?
Dima P.
Product Manager
Posts: 14726
Liked: 1707 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Import configuration not working

Post by Dima P. »

Invalid job configuration: This type of schedule is not supported.
Error indicates that you are trying to import the job configuration that has a mismatch with enabled edition. Try to configure one agent running in server edition manually, then export configuration, modify access account if required (or use /u /p commands during import) and try to import config back. If that works, then all the settings specified correctly and match the edition.
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 21 guests