Unsolved
This post is more than 5 years old
51 Posts
0
1973
Add privileged delete capability to existing pool
I need to add privileged delete capability to a pool that is accessed with an old install of DiskXtender.
I know I need to add it to the pool itself with update pool access, and to the pool's profile with update profile.
When I do the update profile, it asks me if I want to generate a .pea file for the pool. If I accept all the defaults and leave the Profile Secret unchanged, will the old .pea file still work for access to the pool?
I think the answer is yes. I've done it with some orphan pools and the old .pea file works fine. I just don't want to take chances with Diskxtender because it's unsupported.
cincystorage
467 Posts
0
March 14th, 2013 10:00
Unrelated but what source are you using for DiskXtender? Are you arching from Celerra to Centera?
cincystorage
467 Posts
1
March 14th, 2013 10:00
Yes, your old pea file will still work. You can skip the step of generating the pea file if you want - but I always like to as a precaution.
cincystorage
467 Posts
0
March 14th, 2013 11:00
Ah, I was going to suggest Rainfinity if the source was a Celerra. had great success with the product.
mkirsch
51 Posts
0
March 14th, 2013 11:00
Using DiskXtender FSM for Unix.
Basically an NFS server is the source.
mkirsch
51 Posts
0
March 14th, 2013 12:00
We've got that product but right now the Centera's full, there's not enough room to migrate, and they're still deciding on a solution going forward.
cincystorage
467 Posts
0
March 14th, 2013 12:00
Isilon has been awesome for me.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
March 14th, 2013 20:00
good scalability but does not meet regulation requirements for PACS data, plus no dedupe is big for us because many modalities in the hospital scan the same X-RAY/CT scans.
cincystorage
467 Posts
0
March 15th, 2013 01:00
I'm not sure of specific regulatory requirements for PAC data, but Isilon is capable SHS and HIPPA compliance... de-dupe is coming very soon from what I hear.. but for us the price point was so slow using NL nodes de-dupe wasn't a deal breaker. Something else that is comming is federated metadata, which will probally lead to a federated filesystem.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
March 15th, 2013 03:00
Isilon has very limited auditing functionality, i don't see how it meets HIPAA regulations that require enhanced auditing. We would like to offer Isilon to our researchers that have "identified" data but because Isilon can not provide that type of auditing we can't get it past our HIPAA steering committee. We have been beating up Isilon guys for 2 years now ..they are saying auditing is coming, and i am not talking about one big flat file they do today![](https://prod-care-community-cdn.sprinklr.com/community/687062f5-603c-4f5f-ab9d-31aa7cacb376/ReAddprivilegeddeletecapabilit-a464f82a-9c3c-4ca3-9b30-198f3baad95a-1590674886)
cincystorage
467 Posts
0
March 15th, 2013 12:00
I don't see HIPAA requirements but I do see references to it being SEC17a-4 stringent when operating in Compliance mode with SmartLock - at least with 7.0 SmartLock. I ping'ed my regional salges manager to see - since he mtnioned Isilon and HIPAA.