Restore failure on TSM for Sharepoint

spiffy

ADSM.ORG Member
Joined
Feb 9, 2007
Messages
374
Reaction score
1
Points
0
hey all

we currently have TSM for sharepoint set up to backup our sharepoint farms. The backups are working fine, we do a full 1 time a week and incrementals daily, and it is full site level/permissions etc backup.
The backups are going to a diskpool first, where they are later migrated to a physical tape pool.
We have tried restoring a subsite, but it is always failing on us with an ANR9999D error

0/22/2009 16:04:15 ANR0405I Session 22678 ended for administrator ADMIN (WinNT). (SESSION: 22678)
10/22/2009 16:05:01 ANR9999D pvrntp.c(2053): ThreadId <26> Illegal block offset for NTP volume DC0816: pos=16981.33519, size=16434. (SESSION: 18723)
10/22/2009 16:05:01 ANR9999D ThreadId <26> issued message 9999 from: (SESSION:18723)
10/22/2009 16:05:01 (26) Context report (SESSION: 18723)
10/22/2009 16:05:01 (26) Thread SsAuxSrcThread (32) is a parent thread related
to: 26 (SESSION: 18723)
10/22/2009 16:05:01 (32) Generating TM Context Report: (struct=tmTxnDesc)
(slots=256)(SESSION: 18723)
10/22/2009 16:05:01 (32) *** no transactions found *** (SESSION: 18723)
10/22/2009 16:05:01 (32) Generating Database Transaction Table Context:
(SESSION: 18723)
10/22/2009 16:05:01 (32) *** no transactions found *** (SESSION: 18723)
10/22/2009 16:05:01 (32) Generating SM Context Report: (SESSION: 18723)
10/22/2009 16:05:01 (32) *** no sessions found *** (SESSION: 18723)
10/22/2009 16:05:01 (32) Generating AS Vol Context Report: (SESSION: 18723)
10/22/2009 16:05:01 (32) Mounted (or mount in progress) volumes: (SESSION:
18723)
10/22/2009 16:05:01 (32) Volume DC0816(32797) --> SessId=5278, Server=DCRTSM
Mode=Input, Use=Bitfile, ClassId=10, ClassName=ACRCLASS,
IsScratch=True, VolSeqNum=0, Pool=DCRTAPEPOOL-1(13),
Allocated=False, NextSeqNum=1666, PosUncertain=True,
Open=True, OpenInProg=False, OpenFailed= False,
MountMode=Read-only, Reuse=Remove, IsFirstMount=False,
IsEmpty=False, IsNewScratch=False, PreemptAccess=False,
Waiters=0, TwoSided=False, SideSeqNum=-1, status=ACTIVE
(SESSION: 18723)


What happens is that the restore does start to restore quite a bit, but then it will just sit there and eventually toss the above error.
I have audited the volume, and the audit comes up clean, and this actually happened on 2 separate volumes on separate restore attempts.

I have not fully familiarized myself with the product, so i am not sure what to look for.

if anyone has any ideas on what may be going on here, let me know

Thanks
 
Back
Top