We had Nexis Pro 40's tied together. Now separated we cannot unbound.
Pieter
Unbind - Applies to Media Packs. Disassociates (unbinds) the Media Pack from the file system. After it is unbound, you can bind it again (for example, with a different bind option; see "Binding Media Packs to the File System" on page 31) and then add it to a Storage Group.
https://resources.avid.com/SupportFiles/attach/AvidNEXIS/AvidNEXIS_AdministrationGuide_v2023.7.0.pdf
Page 18 onward....
Marianna
[email protected]
DQS
www.mpenyc.com
We wanted that nexis to work separately after being paired in 4 nexis cluster. I switched it to run system director. There is no workspaces and no file system on it. Media Pack is not avaliable or invisible for us if you please but in maintnence services page you can see it being bound. I tried to reinstall the system to newer one, create new file system, but it said there are no media packs avaliable. In maintnance web interface under status/servicec i can see mediapack still bound, but there is nothing it could be bound to. I even tried to clean foreign configuration on the drives, didn't help tho.
Are you able to create a case and have the NEXIS tech support group assist you?
Hi Pieter, et al.,
Are you properly removing the Avid NEXIS engine from the storage group? You have to move/delete workspaces from the engine, unbind media pack and give it a new system name before you try to move it to a new storage group or run its own embedded system director.
Thanks,
-------------------
Ferddy Calderon
Avid NEXIS Sr. Principal Product Owner
Avid
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller