Unsolved
This post is more than 5 years old
2 Posts
0
2394
January 12th, 2016 01:00
Avamar Backup Error - avtar FATAL<8608>
Hi Experts,
I'm getting an error while running the backup for an AIX client. The backup almost completes and then throws up this error. There is an avtar.cmd file on the client and I have verified that all details in the file are correct. The backups were running fine until a few days ago and then started failing.
Avamar version on grid :- 7.1.2-21
Avamar client version :- 6.0.102-156
2016-01-11 20:00:07 avtar Info <6426>: Done loading cache files
2016-01-11 20:00:07 avtar Info <5113>: Not traversing mount point "/proc"
2016-01-11 20:10:43 avtar Info <5163>: Backup complete, wrapping-up session with Server
2016-01-11 20:10:43 avtar FATAL <8608>: Failed to record backup (MSG_CMD_ACCESS_CHILD=47 serial=274934 seq=0 flags=RU:N:0 kind=2 rsp=MSG_ERR_USER_NOT_FOUND_INT). Is Server read-only? Do user privileges permit backups? (Retries=0)
2016-01-11 20:10:43 avtar Info <5156>: Backup #0 timestamp (none), 97,932 files, 12,276 directories, 14.68 GB (46,546 files, 2.337 GB, 15.92% new)
Regards
Arun
No Events found!
ionthegeek
2 Intern
•
2K Posts
0
January 12th, 2016 06:00
Avamar 6.0 clients are not guaranteed to be compatible with 7.1 servers. The minimum supported client version is 6.1.
I would recommend that you upgrade this client and try again.
arun28_fe268e
2 Posts
0
January 12th, 2016 07:00
Thanks Ian. I understand that and we are planning on upgrading all our clients to the supported versions. However, it is going to take some time, and we would really like for this backup to run till then at least. Is there a solution to this issue?
ionthegeek
2 Intern
•
2K Posts
0
January 12th, 2016 10:00
There is not enough information available to troubleshoot based solely on the client error message. The client tried to seal the backup and the server responded with "MSG_ERR_USER_NOT_FOUND_INT" which implies some kind of issue trying to look up the user account that is trying to seal the backup. The exact cause may only be available in the server logs which are far too large and complex to analyze via the forums.
You mentioned that the backup was working fine until a few days ago. What changes were made in the environment? In particular, were there any password changes on the server side, user account changes, client accounts moved or retired, etc.?
If this is only affecting one client, I would recommend that you upgrade this specific client so the system is in a supported configuration. If the upgrade does not resolve the issue, I would recommend that you open a service request to troubleshoot further.
In future, I would also recommend that you plan your upgrades in advance to ensure that the clients are never more then n+2 releases behind the server. Being in a supported configuration from the start will make it easier to get help if you run into an issue like this in future.