I haven't seen this error message before but it looks to me like it might just be hitting a limit on the time it is willing to wait for something else to happen and might not refer to what is actually causing the problem itself. Does everything else work besides this restore (backup of this client through this SN, of file system restore of this client for example)? If you find something else that's not working, this could narrow down where the breaking point is. If it's just this operation which is failing, you should try the restore from the command line and see if you can get any more useful error message out of it.
The bottemline of the story is that we have added a large number of groups to the user in AD. Apparantly the kerberos ticket had become too large for restoring the db's.
I created a copy of the problem account and noticed that it had a ticket sze of nearly 16K. A testaccount which I created new had a ticketsize of 4K. I removed groups from the original account until the ticket size had dropped to below 12K. Then the restore went fine.
coganb
736 Posts
1
January 25th, 2011 07:00
Hi,
I haven't seen this error message before but it looks to me like it might just be hitting a limit on the time it is willing to wait for something else to happen and might not refer to what is actually causing the problem itself. Does everything else work besides this restore (backup of this client through this SN, of file system restore of this client for example)? If you find something else that's not working, this could narrow down where the breaking point is. If it's just this operation which is failing, you should try the restore from the command line and see if you can get any more useful error message out of it.
-Bobby
Polska1422
2 Intern
•
128 Posts
1
January 25th, 2011 09:00
Hi Frank,
Is Storage Node under VMWare, too? Please, read first https://solutions.emc.com/emcsolutionview.asp?id=esg115723, it's about VMWare environment and SAN attached tape libraries (you have VTL, but...)
Regards
Claudio
coganb
736 Posts
1
January 26th, 2011 00:00
Hi,
Good point Claudio - link doesn't work for me for some reason. Not sure if it works for others. Here's another link to the same article.
http://solutions.emc.com/EMCSolutionView.asp?id=esg115723&usertype=C
-Bobby
David_Hampson_90e289
2 Intern
•
243 Posts
0
January 26th, 2011 02:00
Link works for me...
beckersf
51 Posts
0
March 8th, 2011 00:00
Ok, finally I found the solution!
The bottemline of the story is that we have added a large number of groups to the user in AD. Apparantly the kerberos ticket had become too large for restoring the db's.
I created a copy of the problem account and noticed that it had a ticket sze of nearly 16K. A testaccount which I created new had a ticketsize of 4K. I removed groups from the original account until the ticket size had dropped to below 12K. Then the restore went fine.
Thanks all for replying.