I don’t have links, and I don’t want to call anyone out even if I did :) but I’ve read/heard/seen 2 answers this this and am wondering if this applied to all subclients, or there are exceptions, or caveats to deleting subclients. Which is “true”, assuming you already had some backups existing for a subclient/backups set/application?
- You can delete subclients all day long, nothing is lost in terms of existing job history/restorability. The backups/backup jobs/data/references/etc are not associated with the subclient(s) but instead are associated with the backup set that the subclients are in (meaning: the subclients are “children” of the backup set). When you delete a subclient, it is still ‘visible and accessible for restores” vis the backupset backup history
OR
- Deleting subclients causes loss of the backup job data. Once subclients are deleted, you cannot go back to view jobs or perform restores. deleting a subclient will remove it from the backupset. A deleted subclient and all its data/jobs are ‘gone”, never to return
Addendum: When I say “delete the subclient” I DO NOT mean deleting the client (which would then, technically, delete the backup set and subclient). I literally only mean manually/purposefully deleting only the subclients and leaving the backup set and all “levels” above it active/licensed.
Notes:
- I’ve read the “default” subclient is not able to be removed unless you use the scripting API, so its “special” somehow. This might only apply to the Filesystem subclients?
- When I say “subclient” I mean literally “every subclient type” meaning: Filesystem, database, Exchange, HANA, etc. literally any and every subclient type of any application/package/backupset that performs backups of data. Just in case there are “exceptions’ and some subclients so not act like others, maybe someone will point them out.
Best answer by Scott Moseman
View original