11-30-2014 10:15 AM
Hi
I have recently upgraded the Media Server and installed Windows 2012 R2 server. Now this server is running BE 2014 with SP1. I restored the data and started up the BE 2014. Most of the jobs are working fine but i am experiencing issues with 3 servers. I would appreciate if someone could help me out with this. Please see the screenshots below for the errors i am receiving.
Solved! Go to Solution.
11-30-2014 10:26 AM
Hi,
Check below and see if this relates to your issue:
http://www.symantec.com/business/support/index?page=content&id=TECH139703
THanks!
11-30-2014 05:22 PM
Turn off AOF in your job and try again.
12-03-2014 01:20 AM
As you can see, the physical size of the DB container is 11404 MB (approx 12 GB), though the actual used space of the DB is 735072+155984 KB ~ approx 1GB.. Pretty much the same size when backed up by BE.
11-30-2014 10:26 AM
Hi,
Check below and see if this relates to your issue:
http://www.symantec.com/business/support/index?page=content&id=TECH139703
THanks!
11-30-2014 10:36 AM
...also, restart the media server if you haven't done so after upgrading it.
Thanks!
11-30-2014 05:22 PM
Turn off AOF in your job and try again.
12-01-2014 12:45 AM
Oki here is the update, for 2 of the servers, it was just as minor as not restarting the servers after agent upgrade. But the third one is still failing. It is still getting the same error as given above, the one at bottom saying
12-01-2014 12:58 AM
The server which is failing now basically only have 2 SQL database selected which is of very importance. And then there is System Status selected, and i think it is failing on the system status. Pkh are you sure i unselecting the snapshot will help?
12-01-2014 01:17 AM
...disabling AOFO is recommended with DBs. You can split your backups off from each other (AOFO with files/System State; no AOFO with SQL). Try this and report back with an update.
Thanks!
12-01-2014 03:19 AM
Oki, here is the update, sins i am only interested in the SQL databases on this particular server, i deselcted the System State, and only selected the 2 databases i am interested in. Then i did as suggested by removing the AOF sins its SQL databases i am taking backup of. The job completed successfully. however what worries me is the amount of GB of the backup data. It was only 0,9 GB datam while the SQL database is atleast more then 12 GB total for both of the databases. I enabled the AOF and ran the job again, this time it gave me around 12GB of backup data, but it failed on the very end with the exact same error as mentioned earlier. So my questions is, as a result of disabling the AOF, are you guys sure it is taking backup of the entire SQL database? Would appreciate a feedback on this, thanks.
12-01-2014 03:33 AM
When AOFO is used with SQL backups, tthe backup will contain the complete physical size of the SQL DB as opposed to a non AOFO backup of SQL which will contain only the used data. Hence, with AOFO enabled, the SQL agent backups are larger than the non AOFO ones.
12-01-2014 04:27 AM
Well my backup setup is that it takes 1 full backup and then 4 incremential, so disabling the AOFO will never be able to take the full Backup weekly then, what am i suppose to do then?
And why am I having this issue now, i never had this problem before upgrading?
12-01-2014 10:44 AM
12-01-2014 07:37 PM
Here is a KB validating what I mentioned earlier - http://www.symantec.com/business/support/index?page=content&id=TECH166067
In case of a SQL restore, a non-AOFO backup of the DBs will of course help.
12-02-2014 03:16 AM
Cool. That explained a little bit. Please tell me one thing, data backed up with and without AOFO were following:
With AOFO: around 12GB
Without AOFO: around 1 GB
According to the KB you provided, does it mean there is 11GB with empty space in that database file?
12-02-2014 03:20 AM
Possibly yes. You can run the following query from SQL itself to double-check using this post - http://stackoverflow.com/questions/18014392/select-sql-server-database-size
12-03-2014 01:13 AM
Thats what i get when i run the query, seems like the database is suppose to be larger then 1GB
12-03-2014 01:20 AM
As you can see, the physical size of the DB container is 11404 MB (approx 12 GB), though the actual used space of the DB is 735072+155984 KB ~ approx 1GB.. Pretty much the same size when backed up by BE.
12-04-2014 01:08 AM
Hmm, then i guess we are good to go, thanks alot VJware, i appreciate all your feedbacks, Very kind. I will proceed and take backup by disabling AOFO. Thanks alot to all of you :)