go to post Anzelem Sanyatwe · Dec 5, 2016 Hi Shawn;Your method you mentioned works perfectly well. I have used it a lot, am predominantly Linux and my most preferred share is over 'nfs'. Ensure you have write permissions to that drive and that there is no network performance impact when it is running between the two servers, but with the speed you mentioned the impact is insignificant. The other advantage is that the write I/O will be on the other server. Regards;Anzelem.
go to post Anzelem Sanyatwe · Oct 26, 2016 Hi Heikki;I just recently been faced with the same situation you are in. I doubt it shadow is supported between those two versions, you can check it here 4) Supported Version Interoperability http://docs.intersystems.com/documentation/ISP/ISP-20162.pdfThe method we used was a Full Backup on old system and a restore on the new system just before the Migration day, and then during the downtime after users are stopped in the migration window we did a cumulative backup and restore (1, the cumulative backup and restore minimizes downtime 2, it's quick to copy over - as it is smaller). This plan worked well for us.
go to post Anzelem Sanyatwe · Oct 25, 2016 I previously wrote this to WRC, and still waiting for it to be ratified, if this is a viable alternative. """"The one I’ve been thinking of all along which could be an easy way forward if it is possible you can re-package ISCAgent installer to install in a different directory instead of the default one. The default directory is the one giving us headaches as it is linked back to the cluster disk.This I mean if I’m on the secondary node without the cluster disks, this is what you will encounter: []# pwd/usr/local/etc[]# ls -al cachesyslrwxrwxrwx. 1 root root 43 May 28 2015 cachesys -> /tcl_prod_db/labsys/usr/local/etc/cachesys/ (This path resides on a cluster disk).[]# cd /usr/local/etc/cachesys-bash: cd: /usr/local/etc/cachesys: No such file or directory So in this scenario I cannot install the ISCAgent independently in its default format as it will fail as above.That link we cannot touch as that will break the Cluster FailOver. So the modifications I’m talking about will be:to change the default directory by creating a new one to ‘/usr/local/etc/iscagent’Then modify the etc/init.d/ISCAgent script on this line from AGENTDIR=${CACHESYS:-"/usr/local/etc/cachesys"} to AGENTDIR=${CACHESYS:-"/usr/local/etc/iscagent"} After the installation this seems achievable by doing this :-rsync -av /usr/local/etc/cachesys/* /usr/local/etc/iscagent/Then edit etc/init.d/ISCAgent as suggested on 2. AboveThe issue I’ve with this is that there could be other references in the installer that I might not be aware of. If so, hence suggesting you guys re-package it with the modifications as suggested above. This way we make ISCAgent independent and resides locally on the TWO nodes (primary and secondary failover node), as it’s binaries don’t really need to follow the Cluster Resources all the time. This way we also make etc/init.d/ISCAgent start automatically with the OS."""'''
