John-Wiesner Contributor.
Contributor.
544 views

"VRDA: Bad catalog access for message #32684 in set 222" while restore

Jump to solution

At a restore from a folder with about 66 GB and 150.000 files on a NSS filesystem I got about 35.000 minor error messages "VRDA: Bad catalog access for message #32684 in set 222". Does anyone know what this means? Is the restored data valid?

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: "VRDA: Bad catalog access for message #32684 in set 222" while restore

Jump to solution

Hello John

I really reviewed this case past friday as part of internal escalation, please let me know if you received information below.

VRDA debugs show the following

 

[ -2] 2018-08-14 17:40:50.714 ("/smsres.c $Rev: 61652 $ $Date:: 2018-01-30 15:09:18 ":994)

[ -2] ERROR: NWSMTSWriteDataSet() (CCODE = fffdffac)

 

 

The VBDA made a call to NWSMTSWriteDataSet() which returned FFFDFFAC,  The meaning for this error message is

 

CCODE=0xFFFDFFAC, I found it under TSAPI and it is explained as:

 

0xFFFDFFAC --- NWSMTS_OUT_OF_QUOTA_SPACE

                        --- A file or directory cannot be restored. The user or directory quota limit is exceeded.

 

http://www.novell.com/developer/documentation/smscomp/sms_docs/?page=/developer/documentation/smscomp/sms_docs/data/hka0ofpt.html

 

From similar issue moving files between OES clients I saw this explanation

 

The error code you received clearly means "out of quota space" and so

indicates that you are exceeding the quota. This could happen for 2

possible reasons:

- the files on the source are compressed and with compressing fall

within the quota limit. The migration uncompresses the files and exceeds

the quota.

 

- the quota on the source has been exceeded because for example the

administrator has lowered the quota below what the user was already

using or because the administrator changed the file ownership. So check

if your users don't already exceed their quotas, especially the user for

the problem file reported.

 

One possible way of avoinding these issues is to disable quotas at

volume level on the destination server, then migrate your data and only

enable quotas after the files have been migrated

 

Therefore please check quota sizes and if are enabled try restore after disable quotas.

Best Regards

 

0 Likes
3 Replies
Micro Focus Expert
Micro Focus Expert

Re: "VRDA: Bad catalog access for message #32684 in set 222" while restore

Jump to solution

Hello @John-Wiesner

It is probably a mismatch of patches between the DA and the GUI or between the CM and the GUI. You can have a DA older than GUI, but not DA newer than GUI. 

Just confirm this. But I can tell you that, if all the DA ends properly means that restore complete correctly. 

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: "VRDA: Bad catalog access for message #32684 in set 222" while restore

Jump to solution

Hello John

I really reviewed this case past friday as part of internal escalation, please let me know if you received information below.

VRDA debugs show the following

 

[ -2] 2018-08-14 17:40:50.714 ("/smsres.c $Rev: 61652 $ $Date:: 2018-01-30 15:09:18 ":994)

[ -2] ERROR: NWSMTSWriteDataSet() (CCODE = fffdffac)

 

 

The VBDA made a call to NWSMTSWriteDataSet() which returned FFFDFFAC,  The meaning for this error message is

 

CCODE=0xFFFDFFAC, I found it under TSAPI and it is explained as:

 

0xFFFDFFAC --- NWSMTS_OUT_OF_QUOTA_SPACE

                        --- A file or directory cannot be restored. The user or directory quota limit is exceeded.

 

http://www.novell.com/developer/documentation/smscomp/sms_docs/?page=/developer/documentation/smscomp/sms_docs/data/hka0ofpt.html

 

From similar issue moving files between OES clients I saw this explanation

 

The error code you received clearly means "out of quota space" and so

indicates that you are exceeding the quota. This could happen for 2

possible reasons:

- the files on the source are compressed and with compressing fall

within the quota limit. The migration uncompresses the files and exceeds

the quota.

 

- the quota on the source has been exceeded because for example the

administrator has lowered the quota below what the user was already

using or because the administrator changed the file ownership. So check

if your users don't already exceed their quotas, especially the user for

the problem file reported.

 

One possible way of avoinding these issues is to disable quotas at

volume level on the destination server, then migrate your data and only

enable quotas after the files have been migrated

 

Therefore please check quota sizes and if are enabled try restore after disable quotas.

Best Regards

 

0 Likes
John-Wiesner Contributor.
Contributor.

Re: "VRDA: Bad catalog access for message #32684 in set 222" while restore

Jump to solution

I can confirm, the problem was the quota. I globally disabled all the user-quotas for the nss volume. After this the restore finished successfully without the error messages.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.