How do we decommission our local Voyager server
- Product: Voyager
- Product Version: 7
- Relevant for Installation Type: Local
We need to decommission our local Voyager server. What do we need to do?
You would decommission the server in accordance with your I.T. Department's best practices and local policies. If you are migrating to Alma, invoicing from Ex Libris should reflect that you’ve moved from Voyager to Alma. You may want to confirm this is reflected on your next invoice.
You can keep your Voyager server up for reference in Read-Only mode after go-live; customers hosted by Ex Libris have access to their hosted Voyager environments for 90 days after go-live on Alma, but do not refer to them very much after the first 30 days.
it is important that you check with your Account Manager about licensing. Both the Voyager software and the Oracle software may have licensing requirements. Prorated contracts are handled on a case by case basis.
If you wish to place your Voyager into Oracle Tablespace Read-Only mode, please open a Case with Support.
See also the following article which provides information on disabling patron activities, placing clients in read-only mode, etc.: Overview of Voyager Articles related to Alma migration
- Article last edited: 20-Mar-2019