10.02.2013 Views

Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Verification <strong>and</strong> Housekeeping Tasks After Upgrading<br />

◆ Checklist for determining the continuing use of a prior installation’s directory:<br />

1. Did the upgrade choose to use the existing data store (the Leave option) in the prior<br />

installation directory structure? [ ] Yes [ ] No<br />

2. Did the upgrade choose to use the existing recovery logs (the Leave option) in the<br />

prior installation directory structure? [ ] Yes [ ] No<br />

3. Are there one or more added broker data stores that are in the prior installation’s<br />

directory structure (instead of being moved to the upgraded installation location)?<br />

[ ] Yes [ ] No<br />

4. Were the certificate stores in the prior installation left in place, pointed to from the<br />

upgraded installation location? [ ] Yes [ ] No<br />

If you checked Yes on any of these items, then refrain from deleting any files.<br />

Consult with <strong>Sonic</strong> technical support for tips <strong>and</strong> techniques that will provide the best<br />

result.<br />

Warning Enabling Roll Back of <strong>Upgrade</strong>s — Your ability to revert to using the installations from<br />

prior versions is dependent on reinstating the configurations in the Directory Service.<br />

Tactics to achieve this include:<br />

■ Because an existing Directory Service installation (as well as its broker <strong>and</strong><br />

container) is unmodified during its upgrade, you can revert the entire domain to<br />

its pre-upgrade image.<br />

■ Consider doing an online backup of the Directory Service store immediately<br />

after the Domain Manager has been upgraded so that all the distributed<br />

containers <strong>and</strong> their components are in their pre-update configurations.<br />

■ Consider blocking inadvertent startup of an inactive domain by, for example,<br />

renaming its boot file from container.xml to container_76_INACTIVE.xml.<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>Installation</strong> <strong>and</strong> <strong>Upgrade</strong> <strong>Guide</strong> <strong>8.5</strong> 219

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!