Direkt zum Inhalt

BR10 Server for Windows - U3 - Shellshock!

Thread needs solution

I have waited very patiently for well over a year on BR10. Waited for Acronis to fix the archive naming convention. U3 did just that. I even gave praise in another thread. My hopes have been dashed.

The first problem I encountered was that the job would run manually but not scheduled. The fix was downloading the latest scheduler. Fresh install of 2008. Fresh install of BR10. Why am I having to download a patch already? U3 is only a couple of weeks old!

The second problem is with vault credentials. I could finally get a scheduled job to run but when I went back in to the management console after the job completed the vault credentials specfied for the job would no longer work. I had to specify a different set of credentials to access the vault

The third problem is very strange. Our network locks us out after three password attempts. About two days ago the account I was using to test BR10 got locked out. I just figured it was me and/or something I did. I am the only one who even knows of this account. I used this account to install BR10. After getting the scheduled job to run yesterday I reboot the machine. The backup didn't run last night. When I went to check in it this morning the account was once again locked out. Nothing ran because the MMS was installed under this account. A fluke? I don't thinnk so. I have a feeling we are back to vault credentials or something. Acronis tries to access something with credentials. After three tries it gets locked out.

0 Users found this helpful