Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
mingji
Service Provider
Posts: 22
Liked: 1 time
Joined: Jun 26, 2015 2:05 am
Full Name: MJ
Contact:

AIX Agent failed to import configuration file

Post by mingji »

Installed Veeam Agent on AIX server (generated by Veeam B&R server) but failed to apply configuration file

/root> veeamconfig mode setvbrsettings –cfg masterpack.xml -force
No such file or directory
Failed to connect: /var/tmp/veeam/socket/veeam.sock.
Failed to connect to veeamservice daemon.

Any suggestion?
Mildur
Product Manager
Posts: 9848
Liked: 2607 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: AIX Agent failed to import configuration file

Post by Mildur »

Hi MJ

Please check if the service (veeamservice) is running. From the error message it looks like it is stopped.

May i also know the support case number for this technical issue? Without case number, the topic will eventually be deleted by moderators.

Best regards,
Fabian
Product Management Analyst @ Veeam Software
mingji
Service Provider
Posts: 22
Liked: 1 time
Joined: Jun 26, 2015 2:05 am
Full Name: MJ
Contact:

Re: AIX Agent failed to import configuration file

Post by mingji »

Hi Mildur,

Thanks for your reply. I just logged the case #-------
I'll ask our client to check service status and get back.

#MOD: Removed contract number
mingji
Service Provider
Posts: 22
Liked: 1 time
Joined: Jun 26, 2015 2:05 am
Full Name: MJ
Contact:

Re: AIX Agent failed to import configuration file

Post by mingji »

Ok we tried "startsrc -s veeamsvc" to start Veeam service and it goes well, but ran "lssrc -s veeamsvc" it shows status "inoperative"
Mildur
Product Manager
Posts: 9848
Liked: 2607 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: AIX Agent failed to import configuration file

Post by Mildur »

Hi MJ
Please check again for the case number (#05). You provided a contract number (#02). This shouldn't be shared publicly.

I suggest working together with our support team. I'm sure it can be resolved.

Thanks
Fabian
Product Management Analyst @ Veeam Software
Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests