Welcome to your hub for enterprise data protection discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
Access 7.4.2 GAs on October 1 2018
Today (10/1/18) marks the release of the 7.4.2 version of Access. The new release has several new features, but by far the most important of those features is support for NetBackup deduplication on the Access Appliance. Deduplication targets cost-of-ownership reduction (a key focus for the Access Appliance) with features like support for client-direct data deduplication, and multi-domain global deduplication. Most of the Access collateral has been rewritten for this new functionality. Check out the blog here, or visit the Access web page here.
Fujitsu selects Veritas Access as their next-gen storage infrastructure to support K5
Have you read today’s news? FujitsuLimited(Minato-ku, Tokyo) has selectedVeritas TM Access,a software-defined scale-out network-attached storage (NAS) solution, as the premier storage infrastructure for theFujitsu Cloud Service K5. Fujitsu selected Veritas Access due to the following key benefits: Scale-out architecture that enables the cluster’s hardware to be added or replaced without taking systems off-line Flexibility in supporting multiple protocols and the ability to seamlessly interface with different types of storage Control and efficiency Advanced technology with proven record of supporting global mission critical systems Read the press release and share your thoughts by commenting below.can be LDAP/AD users used for console login?
Hello, this forum seems to be very inactive, hopefully somebody will respond:-). When I launch Access console logon screen, "domainname\\username" is displayed in grey as a hint in Username field. However it seems that only local users (with master role) can log in. I cannot define domain-based user in CLISH menu admin, ending with error about unsupported char/format. I have setup both AD domain in the cifs section and LDAP server in the network section, however it seems that AD is for CIFS permissions only, and I am not sure what is LDAP for at all. Regards MichalNo LUNs/disks added when connecting to iSCSI target
Hi everyone! As a part of reconfiguring my network, I started an experiment to move from several different storage system to SDS, and for that I started trial of Veritas Access. For now I managed to install Veritas Access 7.4.2 over RHEL server 7.6 And first task was to attach several iSCSI storage systems to it - and it failed :) Current problem is: access-1.Storage> iscsi target list Target Discovery Address State Disk ------ ----------------- ----- ---- iqn.2005-10.org.freenas.ctl:target1 192.168.88.15:3260 ONLINE iqn.1992-04.com.emc:cx.sl7e2080600017.a0 192.168.10.22:3260 ONLINE iqn.1992-04.com.emc:cx.sl7e2080600017.a1 192.168.10.22:3260 ONLINE iqn.1992-04.com.emc:cx.sl7e2080600017.b0 192.168.10.22:3260 ONLINE iqn.1992-04.com.emc:cx.sl7e2080600017.b1 192.168.10.22:3260 ONLINE As shown here - I've connected to 2 iSCSI storages, but got no disks from them. First is test system with FreeNAS, other is EMC AX4-5i. Both systems can be reached directly, and I can get disks from them on Windows Server for example. Hope someone could help, Veritas tech support refused to talk with me without support agreement :( Thanks in advance !
NFS TCP mounts fail with"portmap query retrying: RPC: Timed out"
NFSv3 and v4 mounts that use TCP fails/hangs when mounting on client from one node in cluster: mount.nfs: timeout set for Thu Jun 23 09:19:20 2022 mount.nfs: trying text-based options 'soft,nordirplus,vers=4.1,addr=10.73.222.117,clientaddr=10.73.222.104' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'soft,nordirplus,vers=4.0,addr=10.73.222.117,clientaddr=10.73.222.104' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'soft,nordirplus,addr=10.73.222.117' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: trying 10.73.222.117 prog 100003 vers 3 prot UDP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 10.73.222.117 prog 100005 vers 3 prot UDP port 4001 mounts using other node in cluster are working fine and ping are okay with no ports blocked or firewall in between. anyone faced similar scenario or have ideas on how to solve?
