05-18-2016 07:30 AM
Hi all.
We want to delete the whole VSG.
The VSG contain 2 VS with 2 Partititions.
All archives are deleted as we see in VAC, SQL-Query and DTrace. We get this Information for both VS:
(StorageDelete) <13344> EV:L CDeleteVault::DeleteVaultStore Information: No archives found for vaultStoreEntryId = [EDIT: correct ID]
But we found SIS-Parts in all 4 Partititions. Just a few:
(StorageDelete) <13344> EV:L CDeleteVault::PartitionContainsSisParts Information: Total [4] SISParts found in FPCDB for VaultStoreGroupIdentity = [1]
(StorageDelete) <13344> EV:L CDeleteVault::PartitionContainsSisParts Information: Total [1] SISParts found in FPCDB for VaultStoreGroupIdentity = [1]
979 07:52:35.972 [20744] (StorageDelete) <13344> EV:L CDeleteVault::DeleteVaultStore Information: Found a non-empty Partition with EntryId = [EDIT: correct ID] for vaultStoreEntryId = [EDIT: correct ID]
How it's possible to delete the SIS-Parts. Idea was to us EVSVR and DeleteSurPlusReference, but the VS are marked for deletion and it's neccessary to set the VS in BackupMode for DeleteSurPlusReference:
Operation: Repair
Option: Delete Surplus References
Vault Store 'EDIT: correct Name' is not in a Read Only state.
The Vault Store is not in Backup Mode. Please set the Vault Store in Backup Mode.
Any ideas?
Thanks.
Kai
05-18-2016 07:42 AM
are you trying to decom ev completely or you just have this VSG and all its components to delete and leaving other parts of the system intact?
05-18-2016 08:28 AM
Hi!
Customer has a new VSG and move the archives from the old VSG to the new VSG. So we want to keep the new VSG and drop the old VSG.
05-18-2016 10:05 AM
sounds like your customer is in a sticky situation because of trying to delete the vault store or vsg before validating that no items were still associated with it. working around the checks and balances in EV will likely require editing directly in SQL which is risky since you're working on a fully live system and therefore i recommend opening a support case.
05-27-2016 03:44 PM
05-30-2016 03:04 AM
Hey Kai,
im not sure, but can it that the customers have "Sharing with Group" in the past active and then changed this to "not sharing"?
One of my customers does the same and delete the journal store. In the second we could take a re-design and run into the same errors like you.
Result was, that we have taken a manual remove from the SQL Database with the permission, that old archived items cant be rebuild.
Regards,
WW
06-13-2016 06:25 AM
@Manideep: Right, but no idea how to solve.
@Wilbur: Sharing is active and as far as I know never disabled.
I will open a new case at Veritas and let you know how we solved it.
Thanks for suggestions.
Kind Regards
kai