View some of the Frequently Asked Questions to our support staff. Included are some tips and tricks making this forum ideal for users getting started with GoAnywhere MFT. Note: Users can reply to existing topics but only our support staff can add new topics to this forum.
- Posts: 592
- Joined: Tue Jul 17, 2012 2:12 pm
- Location: Phoenix, AZ
Saving GoAnywhere Product
iSeries – Saving
Using the supplied iSeries command named SAVPRD, you can save the GoAnywhere product from an iSeries machine. This will save all GoAnywhere objects and user data (including configurations and transfer definitions) into a single iSeries Save file. This will allow you to easily restore GoAnywhere onto another iSeries machine, which is especially useful for disaster recovery purposes.
Perform the following steps to save the GoAnywhere product using the iSeries SAVPRD command:
1. First end the GoAnywhere subsystem using the GOANYWHERE/ENDGA command. Then, key in the iSeries command LIBRARY/SAVPRD, where “LIBRARY” is the installation library of the GoAnywhere server engine. The default installation library is “GOANYWHERE”.
2. Press F4 to prompt the command.
3. Specify the name of the library that contains the GoAnywhere product.
4. Specify the name and library of the Save file to store the GoAnywhere product. The specified Save file will be automatically created.
5. Press enter to perform the save operation.
6. Make sure that you save the license file. ( /Linoma/goanywhere/goanywhere.lic ) The license key is unique to each system.
Save GoAnywhere Objects (SAVPRD)
Type choices, press Enter.
Product library . . . . . . . . GOANYWHERE Character value
Save File . . . . . . . . . . . GOANYWHERE Name
Library . . . . . . . . . . . QGPL Name, *LIBL
The following steps are performed by the SAVPRD command:
1. The GoAnywhere library is saved into a temporary Save file named QTEMP/SLIBGA.
2. The GoAnywhere IFS folder is saved into a temporary Save file named QTEMP/SIFSGA.
3. Both temporary Save files are saved into the Save file specified on the SAVPRD command.
iSeries – Restoring
Follow these steps to restore the GoAnywhere product from the Save file:
1. If you are using a specific user profile to start GoAnywhere, then you will need to create that user profile on the target system. Using the CRTUSRPRF command, create a user profile with the same name and authorities that were used in the original installation of GoAnywhere. Example: CRTUSRPRF USRPRF(GOANYWHERE)
2. Restore the temporary Save files into the QTEMP library. Example: RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(QGPL/GOANYWHERE)
3. Restore the GoAnywhere library from the Save file named SLIBGA.
Example: RSTLIB SAVLIB(GOANYWHERE) DEV(*SAVF) SAVF(QTEMP/SLIBGA)
4. Restore the GoAnywhere IFS folder from the Save file named SIFSGA.
Example: RST DEV('/QSYS.LIB/QTEMP.LIB/ SIFSGA.FILE') OBJ(('/linoma/*'))
5. If the iSeries IP address is different than the IP address of the original installation, then you should run the CFGGA command (contained in the GoAnywhere library) and specify the new IP address.
Lead Solutions Consultant
- Posts: 13
- Joined: Wed Jan 25, 2012 10:38 am
What about real-time replication with a product like Vision solutions Mimix? We don't want to rely on a save/restore process in a crisis. If a data center or even just the production iseries is lost suddenly in a disaster it might be too late for SAVPRD. In that case everything since the last save was done is lost.
With Mimix we have real time replication. Everything that happens in the native database and the IFS is replicated to our backup iseries. What we need is a white paper from Linoma detailing what needs to be replicated and what should not be replicated (i.e. GAMFT.LIC) so that we can successfully recover from a disaster with little or no effort. We should end up with everything we need so we can just bring up the backup iseries, and plug it into the network. And then be good to go.
Of course we are heading towards a hardware based remote disk copy solution using SAN. So we will need to collaborate on the challenges this presents in keeping the backup iseries in sync without overwriting something like the GAMFT.LIC file from production to the backup iseries.
We have just upgraded from GoAnywhere Director to GoAnywhere MFT. Other than the license file, is there anything else which has changed which we need to know about in what we replicate (and don't want to replicate) in the GoAnywhere MFT product?
- Posts: 1
- Joined: Mon Nov 07, 2016 3:29 am
What a lifesaver, thanks for posting this Rick.
Return to “Knowledge Center”