In my Lab i want to remove a DDB that was seal and is not in use and has no more jobs associated with it.
Hey @Fernando Souza ,
Check out the steps followed in this thread and see if that helps:
Let us know how you get on!
Thanks, i removed the DDB sealed.
and i will remove the DDB.
I need to remove this DDB, and i put this DDB as Seal:
What is the next step to remove this DDB?
Hey @Fernando Souza !
Assuming the database shows 0 jobs associated, the DDB will prune off on its own.
However, confirm 100% that the database itself has 0 jobs, not just the GUI. Sometimes index portions remain but don’t show up in the GUI.
ok @Mike Struening how can i see the index portions? by CLI
Check the post linked above for this part:
select * from idxsidbstore
That will show you which jobs the database thinks still exist for that dedupe database.
Hello @Mike Struening
When i try do delete expire jobs (In the DDB) for these backups, received this error:
There’s your answer! You have WORM jobs on this copy.
WORM Copy is an option that prevents the deletion of data that is not qualified for aging. The expiration date for the read-only is set to match the data retention time established in the storage policy copies. These archive files cannot be modified or deleted by any user or application until the specified retention date. Once the retention expires, the system deletes the archives as part of Data Aging.
WORM Copy also prevents deletion of clients, libraries, and mount paths.
After you create a WORM Copy, the following rules are enabled:
WORM Copy cannot be cleared.
The data retention on the WORM Copy can be increased but cannot be lowered.
Hello @Mike Struening
How can i remove these or can´t remove?
WORM jobs can’t be deleted before their retention period ends.
That’s definitely odd….can you confirm you are viewing the jobs on that same copy, and not across the whole Storage Policy?
Also, run a Data Retention Forecast and Compliance Report for this Storage Policy. I want to see why 5929 hasn’t aged yet.
You have me intrigued, my friend!
@Fernando Souza ,
These are the index jobs. They retain the Index Backups for the client indexes protected within them (used for when you browse the client data etc).Can you confirm if those Media Agents associated with SP - ProdVM_DiskLibProd are protecting client data from back then?
have a media agent associated: The CommCell: CommservDEMO
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.