FloydATC
ADSM.ORG Member
After successfully deploying FastBack, creating a FastBack BMR boot image and completing a BMR test, my FastBack server heartbeat reports the following:
I'm assuming this is because during BMR restore the client connected to the FastBack server to perform some sort of "syncronization" whereby the client was somehow registered with the FastBack server.
The only reference I can find to this warning message is a an IBM article noting that a similar issue was fixed in level 6.1.7:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC85902
I'm running 6.1.9 so... how do I get rid of this (non-existing) client? Am I supposed to manually clean out this "state.txt" file? I can't find any references to a client "fastback-bmr" in the FastBack Server Manager.
Code:
=========================
Unprotected Servers
Connected servers that have no policy,
or servers that all their policies/schedulers are paused:
'fastback-bmr' (No Policy)
I'm assuming this is because during BMR restore the client connected to the FastBack server to perform some sort of "syncronization" whereby the client was somehow registered with the FastBack server.
The only reference I can find to this warning message is a an IBM article noting that a similar issue was fixed in level 6.1.7:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC85902
I'm running 6.1.9 so... how do I get rid of this (non-existing) client? Am I supposed to manually clean out this "state.txt" file? I can't find any references to a client "fastback-bmr" in the FastBack Server Manager.