Green fields....
What is the best way to "reset" a Spectrum Protect 8.1.1? This one in particular is a replication target which has all kinds of strange behavior on it and after spending far too many hours trying to repair it, I just want to ZAP it, blow all its data and nodes away and start fresh, without having to do any or much configuration at the primary server. What's the best/easiest way to clear the DB, clear all the data and nodes, so I can restart replication to it with a clean slate? Thanks and Best regards, Mike RMD IT Client Services
Re: Decom Node
Please ignore this message. Just found recommissioned node command. Regards Sarav +65 9857 8665 > On 10 May 2021, at 8:28 PM, Saravanan Palanisamy > wrote: > > > Dear team > > We have decommissioned few nodes but would like to replicate those nodes to > different server. Since replication not supported for decom node we would > like to check how to replicate those nodes. > > > Regards > Sarav > +65 9857 8665 >
Multisession backup to Container Pool - Session hang
OS: AIX 7.2 ISP version: 8.1.11.101 Last week I had several incidents with hanging sessions from TDP clients doing a multisession backup in a directory container pool. A problem like this was already fixed a few versions ago. (APAR IT20858: MULTISTREAM BACKUP SESSIONS MAY HANG WHEN SAVING DATA INTO DIRECTORY- OR CLOUD-CONTAINER STORAGE POOLS) The problem has not occurred since the parameter was set via "CheckInFlightChunks" via "setopt CheckInFlightChunks False". Have any of you noticed such behavior? Regards, Uwe
Decom Node
Dear team We have decommissioned few nodes but would like to replicate those nodes to different server. Since replication not supported for decom node we would like to check how to replicate those nodes. Regards Sarav +65 9857 8665
Re: Decom Node
Thanks Frederick. Appreciate your response. Regards Sarav +65 9857 8665 > On 10 May 2021, at 8:47 PM, De Kezel, Frederik > wrote: > > Maybe first recommission those nodes? > Then you will be able to replicate them. > And then decommission again when replication is finished. > > > Use the RECOMMISSION commands to recommission a decommissioned > client node or virtual machine (VM). > > * 3.52.1 RECOMMISSION NODE (Recommission a decommissioned > application or system client node) > > * 3.52.2 RECOMMISSION VM (Recommission a virtual machine) > > > Rgds, > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Saravanan > Palanisamy > Sent: maandag 10 mei 2021 14:29 > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Decom Node > > **This Message originated from a Non-ArcelorMittal source** > > > Dear team > > We have decommissioned few nodes but would like to replicate those nodes to > different server. Since replication not supported for decom node we would > like to check how to replicate those nodes. > > > Regards > Sarav > +65 9857 8665
Re: Decom Node
Maybe first recommission those nodes? Then you will be able to replicate them. And then decommission again when replication is finished. Use the RECOMMISSION commands to recommission a decommissioned client node or virtual machine (VM). * 3.52.1 RECOMMISSION NODE (Recommission a decommissioned application or system client node) * 3.52.2 RECOMMISSION VM (Recommission a virtual machine) Rgds, -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Saravanan Palanisamy Sent: maandag 10 mei 2021 14:29 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Decom Node **This Message originated from a Non-ArcelorMittal source** Dear team We have decommissioned few nodes but would like to replicate those nodes to different server. Since replication not supported for decom node we would like to check how to replicate those nodes. Regards Sarav +65 9857 8665
