Locked or not locked, it's not a determining factor for expiration. You could also decommission the nodes after you move them to a new server. That will do a few things for you: - prevent the node to perform any new backups/archives, but can still connect to restore older data, if you lock it, they can't backup or restore - disassociate the node from backup schedules, so no misleading missed backups - inactivate all active versions so they are also eligible for expiration based on their retention - once all data is expired, the node will be deleted
HELP DECOM NODE for more information. - Thanks, Marc... ________________________________________________________ Marc Lanteigne Spectrum Protect Specialist AVP / SRT 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 16:00 Eastern Latest Servermon: http://www-01.ibm.com/support/docview.wss?uid=swg21432937 Performance Mustgather: http://www-01.ibm.com/support/docview.wss?uid=swg22013355 Follow me on: Twitter, developerWorks, LinkedIn -----Original Message----- From: J. Eric Wonderley <eric.wonder...@vt.edu> Sent: Wednesday, November 14, 2018 04:34 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] do locked nodes participate in expiration? we trying to lock out clients from a server we're moving off of but we also want data to expire for the locked out clients maybe we need to rename the nodes instead
