03-05-2013 03:47 AM
Hi all,
I made a change to the backup procedure as i noticed the Partitions werent thinking they were getting backed up and it was due to the Arcserve account was trying to put the SG into Read only mode using the standrad script. Thats all sorted now as the backups run fine and no erros are being seen for that now.
However after the services started backup we have seen 62 7110 fired saying:
An invalid SIS part was encountered while doing watch file scan. Following further information is available.
Partition Name = Exchange Ptn1
VaultStoreEntryId = 16015A7981113D14DB2558EB2F56A1C8D1210000evserver1
ParentTransactionID = B13B152FD8A7D87A1ABD7AC147B84C71
Invalid Reason = Verification failed for sis part when post processing Saveset with TID = [D09FF3461A987B5936EFCF5B4466A6A1].
Following sis part details are available:
FPDistinctionByte = [123]
FPHashPart1 = [359658472]
UniqueId = [0].
The Parent Transaction ID isnt always the same and so is the invalid reason.
The FPDistinctionByte and FPHashPart1 are always different.
Ive also changed the Partition to check from Use trigger file to use archive attribute
Can anyone help with what these are and if we need to worry?
Thanks
03-05-2013 04:04 AM
03-05-2013 04:16 AM
In addition, we have had lots more fire off in the last 20 mins. Probably getting about 10-15 a minute.
Clearly one of the changes made has kicked it into life to be checking something it hasnt checked in months.
It does seem to have finished now.
03-05-2013 04:20 AM
check this out
03-05-2013 04:20 AM
Yes we do, ill take a look at the link now and let you know.
03-05-2013 04:23 AM
Ahh yes i did see this earlier but couldnt see how i could check if the ARCHDVSSP or even where its particular location was to confirm if this was why i was seeing it.
Can i regard it as a non issue? I wont expect to see them again?
Regards
03-05-2013 05:33 AM
As of now you can subscribe to the technote and you will be noticed when it is fixed. You can ignore this error for now, just make sure those items are retrieved without any error at client end
03-05-2013 05:47 AM
Thanks Arjun,
How do i find what items these are refering too? They are just alpha/numeric sequences...
I will tack them down if i know how.
Regards
03-05-2013 06:05 AM
Basically the Parent Trasaction ID is your main Saveset. So using this ID in SQL query, you can find which Archive it is associated with.
Use VaultStoreDBName
--Declare parameters in our case IDTras = B13B152FD8A7D87A1ABD7AC147B84C71
Set @IDTransaction = 'B13B152F-D8A7-D87A-1ABD7AC147B84C71'
Select
Arch1.archivename
,IDTransaction
,ArchivepointID
from enterprisevaultdirectory.dbo.archive Arch1
join enterprisevaultdirectory.dbo.root r1 on Arch1.rootidentity = r1.rootidentity
join archivepoint on r1.vaultentryid = archivepoint.archivepointid
join saveset on archivepoint.archivepointidentity = saveset.archivepointidentity
where idtransaction = @IDtransaction
Once you know the name of the archive, you can use EVSVR interactive mode and use DumpSaveset with Archive ID and Saveset ID to recombine the archived item in MSG file. Try to open the msg file, if it opens up fine then you are good.
Refer DumpSaveset command using EVSVR
Article URL http://www.symantec.com/docs/HOWTO37697
03-05-2013 06:38 AM
Im in a bit deep here so bare with me!
Ive run your query against the Vault store DB and got then when i parse it:
Msg 137, Level 15, State 1, Line 5
Must declare the scalar variable "@IDTransaction".
Msg 137, Level 15, State 2, Line 23
Must declare the scalar variable "@IDtransaction".
What have i done wrong here, i wouldnt call myself a SQL guru....
03-05-2013 11:31 PM
Oh my bad...you will need to declare the variable in this query...so add following on top
Use VaultStoreDBName
declare @IDTransaction varchar(36)
Set @IDTransaction = 'B13B152F-D8A7-D87A-1ABD7AC147B84C71'
Select
Arch1.archivename
,IDTransaction
,ArchivepointID
from enterprisevaultdirectory.dbo.archive Arch1
join enterprisevaultdirectory.dbo.root r1 on Arch1.rootidentity = r1.rootidentity
join archivepoint on r1.vaultentryid = archivepoint.archivepointid
join saveset on archivepoint.archivepointidentity = saveset.archivepointidentity
where idtransaction = @IDtransaction
03-07-2013 06:34 AM
Did you try this query on affected saveset?