Good Morning,

    I have gone thru both articles and numerous others but I have3 still been unable to get the async DR member out of the waiting  status.  In the portal I went to SYSTEM>JOURNALS>MIRROR JOURNAL FILES and no mirror journal files show up.  Are there cache or windows utilities that I can use to trace the activity between these two machines (primary & async member).  What troubleshooting steps should I take now?

I have verified that the ports are open and in process explorer it appears that the async member goes to the primary successfully but I'm still getting an unable to connect in my console log.

There are no errors in my windows event logs.  I turned on all system events in the audit  log for both servers and there are no errors that show up.

I am on CACHE 2014.1.1.702

Thanks for the help.  I am reading both articles to see if I missed anything.  I did compare the encryption key on the databases from the primary and async and they match.  I went thru the SSL procedure and everything seem to work correctly and I have the same certs on both machines.  I did notice that on the async server that the cacheaudit database is Unmounted and will not let me mount it.  Is this because it's the DR Async machine or is this an indicator of a problem?

Hello,  I want to thank everyone for there input it was a great help.  I have the powershell script working on my sandbox server.  two things were really important in getting it to work. that was different than what I had found in the documentation.  The first was using -U%SYS rather than _U%%SYS.  the second was putting the freeze command in double quotes like this "##Class(Backup.General).ExternalFreeze()". 

Today I migrated it over to my production server and I'm having one final issue.  Our production server is in lock down security mode and using the example of passing a file with the userid/password I still get access denied.    Tani do you have an example of using windows authentication and will it work with the powershell script? The < in the command <c:\login.scr causes errors in powershell indicating it's a reserved symbol.

I just looked at the profile for the unknownuser and noticed that it failed due to the namespace %%SYS doesn't exist.  I removed one of the % signs and now the access denied message has quit coming up but the system is just sitting there and I'm not getting any response back to powershell nor to the console log.  When I enter the command ..\bin\cache -s. I get the same response and I have to hit ctrl-c to break in.  Screen below is what I'm getting now with the freeze or the -s. command.

 

Good Morning,  I have turned on Auditing and here is a screen shot of the record produced when I execute the freeze command.  It looks like even though I'm passing the password file that the process is using the unknownuser id.

Command is: 

I put the logfile parameter in but it doesn't create anything.

password file is:

?????<\n>          (userid)

???????<\n>       (password)