A customer has multi-site environment and plans to consolidate file and block-level data. A proof of
concept in arranged to familiarize the customer with HPE 3PAR StoreServ File Persona functionality.
Which statement is true when failing over file-level data between the arrays?
A.
The Peer Persisience Arbitirator must register the file shares before a failover is initiated
B.
An automated failback is initiated once the primary storage system comes back online
C.
The clients must reconnect to NAS shares once failover is complete
D.
A second customer IP must be configured as a DNS alias for the file shares running on the HPE
D. A second customer IP must be configured as a DNS alias for the file shares running on the HPE
0
0
A customer has multi-site environment and plans to consolidate file and block-level data. A proof of concept in arranged to familiarize the customer with HPE 3PAR StoreServ File Persona functionality. Which statement is true when failing over file-level data between the arrays?
0
0
C
0
0
Correct Answer: C. The clients must reconnect to NAS shares once failover is complete
0
0
B.
C doesn`t make sense, that the need to reconnect by themself.
0
0
C. When a File Share is restored, it has the default permissions used for newly created File Shares. The permissions that were in place when the source FPG was backed-up with the backupfsconf command are not restored. You must back up the share folder permissions as part of backing up the files with a backup application, or you will need to reconfigure the share folder permissions manually after the restore operation.
0
0
D.
File Persona network recommendations
File Persona on the Source Storage System (System1) can be initially configured with IP addresses on the Virtual File Server (VFS) to support
both the primary site addressing schema and the DR site addressing schema. Pre-configuration of IP addresses on the VFS(s) for both the
primary and DR site expedites the failover process in the event of a failure.
It is recommended to pre-configure the VFS(s) with the IP address(es) of both the primary and DR site IP addresses on the Source Storage
System (System1). If pre-configuration of the IP address(es) cannot be completed prior to failover, then the IP address(es) of the VFS(s) will
have to be modified on the DR site to reflect the correct IP address schema. Otherwise clients will not be able to access the File Persona on the
DR system or Backup Storage System (System2). To modify the VFS(s) after failover follow the instructions in the section “Configuring the
Backup Storage System (System2) VFS(s) IP address(es).”
For IP address-to-VFS’s fully qualified domain name (FQDN) resolution to function correctly after a planned or unplanned failover to the Backup
Storage System (System2), there are three methods to consider:
1. Add the IP address(es) and new FQDN for the Backup Storage System (System2), VFS(s) to the Domain Name System (DNS), and inform
clients to connect to the new FQDN. Configuration of the IP address(es) and FQDN within DNS for the Backup Storage System (System2)
VFS(s), can be completed prior to a planned or unplanned failover. Clients will need to be notified after the planned or unplanned failover to
connect to the new FQDN of the Backup Storage System (System2) VFS(s).
2. After planned or unplanned failover, modify the original DNS entry for the Source Storage System (System1) VFS(s) to point to the IP
address(es) of the Backup Storage System (System2) VFS(s) IP address(es), so clients can connect to the original FQDN.
3. After planned or unplanned failover, only provide the IP address(es) for the Backup Storage System (System2) VFS(s) and inform clients to
connect to those alternate IP address(es) only for connectivity. This procedure does not require modification of the FQDN within DNS.
Each of the recommendations is a valid solution to IP address to FQDN name resolution during a failover to the Backup Storage System
(System2). Fully consider each procedure before implementing a solution to ensure that it achieves the business availability and uptime
requirements.
0
0