Thanks Skylar. I noticed it was possible to inactive by running "tdpsqlc inactivate <db>" but the problem from our TSM side is that we don't notice these things and doing regular investigations into this matter is a chore. Wondered if there could be some settings or other tricks to automate this.
Regards, Hans Chr. On Tue, Mar 12, 2019 at 4:17 PM Skylar Thompson <skyl...@uw.edu> wrote: > A few ways to do it: > > 1. Run a full incremental backup on the node after the database is removed > 2. Use the client-side EXPIRE command with a list of paths to mark inactive > 3. If the entire node is going away, use the server-side DECOMMISSION NODE > command (take note of the caveats in the documentation though) > > On Tue, Mar 12, 2019 at 04:08:58PM +0100, Hans Christian Riksheim wrote: > > Newbie question(only 18 years of experience with TSM) : > > > > How do I ensure that deleted databases get inactivated and expired > > according to the copygroup settings? As far as I know inactivation of > > copies >retonly occurs when the database is backed up. If the database is > > removed all active copies will stay active forever and it is now a manual > > task to inactivate them from the client. > > > > Regards, > > > > Hans Chr. > > -- > -- Skylar Thompson (skyl...@u.washington.edu) > -- Genome Sciences Department, System Administrator > -- Foege Building S046, (206)-685-7354 > -- University of Washington School of Medicine >
