Couple of things here. First the LDF file is (probably) growing because the SQL nightly and weekly backup jobs are failing.
For immediate relief, first shrink the LDF file:
Open a command prompt on the Unity server
c:\osql -E
1> use unitydb
2> go
1> backup log unitydb with no_log
2> go
1> dbcc shrinkdatabase(unitydb)
2> go
1>exit
--- Fix the Jobs --
Then fix the SQL backup jobs. These are failing because the MSSQLSERVER service and the SQL backup jobs are not being run by the same type of account. One runs as a local account and the other as a domain account.
Go into SQL Enterprise Manager to look at the jobs
Start -> Programs -> Microsoft SQL Server -> Enterprise Manager
Expand the branches to Jobs.
Microsoft SQL Servers -> Local -> Management -> SQL Server Agent -> Jobs.
You should see 3 jobs. Right click on a job and select "View Job History". The result will say "Failed" with an error message of:
"The job failed. Unable to determine if the owner (DOMAIN\UnityInstall) of job SqlNightlyBackupJob has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\UnityInstall'. [SQLSTATE 42000] (Error 8198)).
This means the backup job tried to run under a domain account but the MSSQLSERVER Service is set to "Log on as: Local System Account". Thus the problem. A proper Unity Installation will set the MSSQLSERVER service to "Log on as: DOMAIN\UnityInstall (or UnityAdmin") and the SQL backup jobs to an owner of DOMAIN\UnityInstall.
--- 2 Fixes ---
So there is 2 fixes, do one of them. Fix 1 is the configuration Cisco intended to get from the Unity Installation. Fix 2 doesn't require services to be restarted.
1. Change the MSSQLSERVER service to log on as DOMAIN\UnityInstall.
or
2. Set the SQL Backup jobs to run from a Local Administrator account.
1. From Services right click MSSQLSERVER -> Properties -> Log On. Check This account and select UnityInstall and enter the password. OK out and restart the service.
or
2. Start -> Programs -> Microsoft SQL Server -> Enterprise Manager
Expand the branches to Jobs.
Microsoft SQL Servers -> Local -> Management -> SQL Server Agent -> Jobs.
Right Click SqlNightlyBackupJob -> Properties. Under "Owner" select Administrator. (repeat for SqlWeeklyBackupJob)
If Administrator is not an option you must add the account to SQL. Microsoft SQL Servers -> Local -> Security -> Logins. Right Click on the left pane and select New Login.
From Name Find the local Administrator account. On the "Server Roles" tab check "System Administrator". On the "Database Access" check both ReportDb and UnityDb databases. For both databases the "Permit in Database Role" check "public" and "db_owner". Click OK. Then go back to configuring the owner for the SQL Backup Jobs.
--- Confirm the SQL Backup Jobs will run ---
To test the job right click and "Start Job" after a few seconds, right click the job and "view job History.
