@Arunkumar P Hello,
thanks for the information and digging a little bit deeper, was the same I found yesterday evening with a colleague of mine which told me the same. But he also told me about a problem that DDBs got not sealed which will be fixed in the new Release from today 11.28.83 →
Auto Sealing DDB's not acting as expected | 5302, 5303, 5304 |
| |
So we are on 11.28.72 and I will update the next days to 11.28.83 and check how sealing and index cleanup will work and post it here.
@Arunkumar P maybe meanwhile you can discuss internal my thoughts on the last post how
Marcel Geisen wrote:
Anyone else with ideas / experiences regarding how to handle Index Jobs with Immutable copy?
Different Options possible:
- Change Index Retention for StoragePolicies somehow when using Immutable?
- Makes it sense and how it is possible?
- Do not copy Index Jobs to Immutable Copy
- How is this possible?
- Makes it sense ? and what is with Restore from WORM Copy without Index?
- Leave it in Standard
- Scenario Storage Policies with
- Primary Copy 30Days 4 Cycles
- WORM Copy - All Jobs - 7 Days 0 Cycles
- When will be the jobs cleaned and the sealed DDBs deleted
Thx & BR
Marcel
to handle Index Jobs in general with Immutable and what is best with index jobs, if you have different Retention on Primary Copy and Immutable copy . I think somehow a BestPractises or some Guidelines would be helpful for all.
I keep you here posted when I updated and tested.
Thx a lot for your support and Greets
Marcel