Solved!
Go to Solutionavatar command for image level backups
So I created a script which part of it needs to run this avtar command, scripts works great for filesystem level backups, but for image level, I receive the error.
avtar Error <5126>: Login error 74: Account not found in the Avamar database
avtar FATAL <5308>: Failed to initiate session with server
what I am pulling is just the schedule name for the client...
/usr/bin/avtar --backups --hfsaddr=myavamarserver.com --id=***** --password=***** --path=/mydomain/myclient --quiet | sed -n '3p' |awk '{print $4 }'
is it possible, or is there a work around I can use?
ionthegeek
2 Intern
•
2049 Posts
1546
0
Posted June 13th, 2014 14:00
Glad to hear you got it working! In general, I recommend using mccli rather than lower level commands. There is a REST API coming soon for Avamar 7.0 and 7.1 that you may find useful.
My pleasure!
Hi Ian,
I have a one part question for you.
Usually i do see the error : " avtar Error <5126>: Login error 74: Account not found in the Avamar database " in our environment for DB RMAN failures.
Although the FS backups complete fine under the domain /Cloud/Cloud_unix/Client.x and DB RMAN fails with domain/path as --path=/unix/clientx configured in the RMAN flags.cfg file.
As there was a path mismatch, changing the --path to /Cloud/Cloud_unix/Client.x resolves DB RMAN issue.
But according to this, there should be a RMAN failure for every migration of DB client across different domains on the Grid.
Is there any script which updates the RMAN flags.cfg file upon client migration on the grid or do we need to change those settings manually.
ionthegeek
2 Intern
•
2049 Posts
1546
0
Posted September 2nd, 2014 06:00
If you are not using the Oracle plug-in, the path will need to be updated manually following a client move. I know one of my colleagues from support is working with your team on this. I would recommend following up internally.
ionthegeek
2 Intern
•
2049 Posts
1546
0
Posted June 13th, 2014 11:00
The problem you're seeing is because the GSAN path for VMware Image clients has a GUID appended to the client name so the path you're specifying is incorrect.
Is there a reason you can't use "mccli backup show --verbose"?