Odd behavior during CIFS file restore

Folks: Now that Paul Zarnowski and his extensive knowledge and experience have retired to greener pastures, we need to reach out to the community for some insight. We have a NetApp appliance that supports our Shared File Service for campus, offering both CIFS and NFS shares. In line with

Re: [EXTERNAL] Re: [ADSM-L] sp 8.1.2

Thanks for the suggestions but none of them will ever work in our chosen configuration/environment. Since it was clarified that the web interface/support is being removed from the server only (not the client), I no longer have a concern. On Thu, Aug 10, 2017 at 11:02 AM, J. Pohlmann

Re: deleting a directory container

Hi Remco! Yes, there is a small delay of a few minutes before containers are actually removed, I noticed that behavior too. You stated "it should not, there is no use in retaining damaged containers". True, but if you roll back your database for some reason, you want all containers to be there

Re: [EXTERNAL] Re: [ADSM-L] sp 8.1.2

Hi Zoltan. I suppose the approach now for a helpdesk is to have the helpdesk folks have root access, have X11/Xwindows installed on the client, and then if the helpdesk uses Windows, have MobaXterm or similar to provide access to dsmj. On Windows, RDP or TeamViewer or similar might be the

AW: deleting a directory container

Hallo, If your command sequence happend today, you only have to wait another day and the extents should be gone. If this ist the case BUT you would like to delete the unused container(s) earlier: Try: q extentupdates if you see „Extent Reuse Delay (Days) NOT equal

Re: deleting a directory container

and apparently, waiting for some time does help…. > On 10 Aug 2017, at 16:48, Remco Post wrote: > >> On 10 Aug 2017, at 16:42, Loon, Eric van (ITOPT3) - KLM >> wrote: >> >> Hi Remco! >> Could it be that the reusedelay on the storagepool is preventing

Re: deleting a directory container

> On 10 Aug 2017, at 16:42, Loon, Eric van (ITOPT3) - KLM > wrote: > > Hi Remco! > Could it be that the reusedelay on the storagepool is preventing TSM from > removing the containers? it should not, there is no us in retaining damaged containers. But to make sure,

Re: deleting a directory container

Hi Remco! Could it be that the reusedelay on the storagepool is preventing TSM from removing the containers? Kind regards, Eric van Loon Air France/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco Post Sent:

Re: deleting a directory container

and, as long as we’re on the topic of directory container pools: it is suggested to define a next stg on e.g. tape, but then, how do I get the data from tape back into the directory container pool once I’ve added extra space? > On 10 Aug 2017, at 16:26, Remco Post wrote: > >

deleting a directory container

Hi all, On our new tsm 8.1.1 server I have a directory container pool CC_COM that I no longer want to use. It has been used as a target pool for protect stg once, but when I saw that a subsequent repl node again copies all data because the stgpool in the copygroup is CP_COM (which also