I would like to hear your thoughts on whether this approach is appropriate.
[Objective] I am planning to replicate VTL data backed up on a NetVault server at Site A to Site B. My goal is to use the save sets from Site A for restoration at Site B by performing a media scan. To avoid inconsistencies caused by residual device information or media information (labels, indexes) at Site B, I am considering a procedure to clean up the Site B environment before re-adding the VTL.
[Environment]
- NetVault Version: 13.2
- OS: Windows Server 2019
- Replication Method: Storage-based replication from Site A to Site B. The replicated VTL data is copied to a specified location at the file level.
[Proposed Procedures] The following steps are based on the premise that existing VTL and save set information at Site B can be completely discarded.
1. Replicate the VTL data from Site A to the designated path at Site B.
2. Cleanup of existing information at Site B: Perform a "Blank" operation on all media within the existing VTL at Site B to completely erase existing media information (labels, indexes) from the NetVault Database (NVDB).
3. Device Removal: Remove the existing VTL via the NetVault WebUI (Device Management).
4. Physical Directory Deletion: Delete the physical directory (data storage folder) of the existing VTL on the OS side.
5. Service Stop: Stop the NetVault Service.
6. Data Placement (Copy Site A Data): Copy the VTL data replicated from Site A to the same location as the directory deleted in Step 4.
Note: The goal is to reuse the path information recorded in diskdevices.cfg etc., without manual editing.
7. Service Start: Start the NetVault Service.
8. Device Re-registration: In Device Management, enable the "Re-add previously generated virtual device" option and specify the corresponding path.
9. Save Set Import: After confirming the VTL is recognized, perform a media scan to import the Site A save set information into the NVDB.
[Consultation/Confirmation Items]
Q1. From the perspective of consistency between the NVDB and physical data, are there any operations in the above steps that are not recommended by official support, or is there a more appropriate procedure?
Q2. Regarding Step 6, is the method of omitting edits to diskdevices.cfg by using the identical physical path considered a valid approach during the "Re-add" process?
I would appreciate any insights or suggestions you may have. Thank you!
Best Regards,
Kouji Kimura