File Library and File Jukebox relocation in DP

14
If identical mount-points can’t be maintained, the situation becomes pretty difficult.
In another chapter we’ll indicate what can be done in such cases.
Copy to Tape
In our lab setup we had no physical tape drive at our disposal, hence we copied towards a
null-device called BlackHole
Copy-to-BlackHole
Interactively we copied sessions 2008/07/19-1 and 2008/07/19-2.
Both copy sessions 2008/07/25-8 and 2008/07/25-9 completed successfully though with a mount
request which was simply confirmed.
An exhaustive session report of these session is to be found in Appendix B.
The mount request is due to a change to the original device; the backup was piloted by host kiekeboe
while now host lminnaert was controlling the same device. We could have avoided this mount request
by changing TransFL_Writer0 to TransFL_Writer1 and TransJB_D1 to TransJB_D2.
So now we got our data on another media without having used the LAN. This is what we had to
proof.
Relocate Again
Before the next run of the datalist in a LAN-free way, one has to relocate the logical device once
again to the host kiekeboe.
Hence we need to replace
HOST lminnaert.company.com
in all our logical device definition ascii files again into
HOST kiekeboe.company.com
And re-execute
C:\Program Files\OmniBack\bin>omniupload -modify_library TransFL -file C:\temp\TransFL
C:\Program Files\OmniBack\bin>omniupload -modify_library TransJB -file C:\temp\TransJB
C:\Program Files\OmniBack\bin>omniupload -modify_device TransFL_Writer0 -file
C:\temp\FL0
C:\Program Files\OmniBack\bin>omniupload -modify_device TransFL_Writer1 -file
C:\temp\FL1
C:\Program Files\OmniBack\bin>omniupload -modify_device TransJB_D1 -file C:\temp\JB1
C:\Program Files\OmniBack\bin>omniupload -modify_device TransJB_D2 -file C:\temp\JB2
By now the cycle can be repeated.