Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Upgrading Critical Storage: Page 4 of 8

We were aware that this product performs 24/7 synchronization of files, and that applications nearly always use a Windows Service or Linux Daemon to ensure reliability of 24/7 applications through system reboots and downtime. But we didn't bother looking into whether there were services running to support WANSynchHA. Turns out there were, and they were logged in as "localSystem."

XOsoft's technical support gently reminded us that services (by default) run as the "localSystem" user. Our Snap 18000 was configured to get authentication information from Active Directory, so once we stopped the replication and synchronization service, gave it a valid Active Directory Services user ID and restarted it, our error messages subsided and replication was under way.

The lesson here is to consider the overall system, not just one piece. We were so focused on the storage upgrade that we missed a basic Windows management issue. Don't fall into that trap.

Still to go: The tape backup system needed some tweaks so it would work with the new storage server. And as long as we were on an upgrade rampage, we decided we would fix that, too.

While WANSynch was replicating the NSS to the Snap, we made our backup changes and double-checked everything. With backups configured to handle the new Snap and tapes set up for the increased disk capacity, we were set. You'll definitely need more or larger tapes, and your backup schedule might change because of the increased storage size, so don't forget to check backups.