Câu 77: E20-593: Backup Recovery Implementation
A customers EMC NetWorker environment has a Solaris client that had been backing up without failing for several weeks. The client has the following local mount points: ✑ / ✑ /usr ✑ /home ✑ /varAnd two nfs mount points: ✑ /mars/data1 ✑ /jupiter/data1The save set was identified as "ALL" in the client resource. The clien…
Nội dung câu hỏi
A customers EMC NetWorker environment has a Solaris client that had been backing up without failing for several weeks. The client has the following local mount points: ✑ / ✑ /usr ✑ /home ✑ /varAnd two nfs mount points: ✑ /mars/data1 ✑ /jupiter/data1The save set was identified as "ALL" in the client resource. The client had crashed and was successfully rebooted the previous day. The first request for a restore for this client was submitted for the last night's backup of /mars/data1/Monthly.doc and /jupiter/data1/Weekly.xls. The jupiter restore is successful but the mars data is not found and fails to be restored. What is the most likely cause of this restore failure?
Các lựa chọn
Đáp án được giữ gọn theo nhãn A, B, C, D trong phần bình chọn tương tác.
- A. /mars/data1 was not in the /etc/vfstab file and had not been backed up. — đáp án hiện tại
- B. The /nsr/res/servers file on mars is empty, prohibiting the restore.
- C. The nsrexecd was not running on mars, preventing the backup.
- D. The client save set was identified as ALL. ALL does not back up nfs mounts points.
Cộng đồng
0 bình luận công khai. Tên thành viên được ẩn một phần.