10-01-2014 11:25 PM
Hi,
i have hp server with sbs 2011 install and backup exec 2012 sp4. there are 2 jobs 1 to nas and 1 to external tape LTO 4.
everything was working fine until last week. the job start with "snapshot processing" and moved to a "queue" status and stuck in this status for ever.
i dont no what is changed in the server that cause this problem. i uninstall the software and reinstall didn't solve the problem. i tried to instal backup exec 2014 demo just to test it and the same problem.
i tried every solution from symantec knowledge base and from this forum change the problem.
for now i installed arcserve backup so at list i will have some backup
please need help
10-01-2014 11:52 PM
Hi,
open a command prompt and type: vssadmin list writers. Any writers not running and stable are in error, and a server restart will reset them.
Also check to see if there are any pending alerts on the jobs that you need to respond too...if there, do so and then try again.
Thanks!
10-02-2014 12:12 AM
Hi,
thanks for your quick reply
i already check the vss and everything is in "stable no error" status. also there's no alerts.
i add the sgmon file if you can please check it to see what am i missing.
best regards
10-02-2014 12:30 AM
SQL2: failed to attach to SBS2011\SHAREPOINT to query exclude list. <-- does this still exist? If not, deselect or remove it from the backup and try again...
Thanks!
10-02-2014 12:58 AM
in this backup selection i hadn't checked my sql server only backup of one folder in drive D .i dont know why is trying to backup the sharepoint database (by the way i disable the sharepoint services on my sbs 2011)
it happens every job that i run even if my sql is not checked
by the way in the same time the job is started i keep see in the event log the events 17537 17137 source:MSSQL
10-02-2014 01:36 AM
...just make sure that any SharePoint farm that's selected is deselected. otherwise put in an exclusion for this.
Thanks!
10-02-2014 02:14 AM
Please can any help currently I bought the renewal for ma Backup Excel 2012. I lost the CD Installer of 2012, I tried to download the 2012 installer from the site its doesn’t accept it just provide me with 2014 download.
Please let me how I can download installer of Backup Excel 2012 from the site
Thanks,
Ivanso
10-02-2014 03:31 AM
I checked it agin, no sql is selected/ see attech jpg
10-04-2014 11:47 PM
Hi,
Is anyone willing to look into the attached log and tell me:
1.why when I checked only files and folders in the selection list . the backup software accessed always to the sql database?
2. Does all this have something to log explains why the job always stuck in the queue?
10-05-2014 10:03 PM
Try this registry change on media server and see if this helps get around the issue:.. this will be used just as workaround and not permanent solution..
http://www.symantec.com/business/support/index?page=content&id=TECH92375
Have you waited long enough after you get this entry in the sgmon log:
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] - SQL attach called
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] -
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] - >>>> The SQL Agent was passed NT Credentials for user name: 'NDCPA\administrator'
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] - >>>> the agent will ignore these credentials. NT credentials
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] - >>>> need to be applied at the parent server level instead.
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] - >>>> Only SQL credentials should be applied to the SQL resource.
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] -
BEREMOTE: [10/02/14 10:01:23] [14400] 2014-10-02T10:01:23.015 [fsys\sql2] - Attempting attach with inherited credentials
If this is the only entry you see in sgmon log, even after waiting for say 5-10 minutes, it could be a hang on our side and will need to be analyzed using a hang dump.. You may want to get in touch with Tech Support for that..
Thanks
10-05-2014 11:09 PM
10-06-2014 12:44 AM
Are TrendMicro exclusions set for the BE processes ?
Does the backup continue if you add an exclusion for C:\Program Files\Microsoft SQL Server & D:\Program Files\Microsoft SQL Server & C:\Program Files (x86)\Microsoft SQL Server ?
If not, would you post a screenshot of your backup selections (preferably the text view)
10-06-2014 12:54 AM
I only backup just one folder in drive D so no need to do an exclusion. i allready add a print screen of my selection lits i
10-06-2014 01:26 AM
Per the debug, this folder on the D:\ contains .mdf/.ldf files.
Can you try backing up another folder which does not contain these SQL DB files ?
10-06-2014 03:05 AM
I have attached the log is updated at certain selected folder does not include any database.
Also after seeing the previous log-related error messages SharePoint (even though I do not use it so I put his service in Disbel) allows his service and then a log I see progress, but appears to me a strange error message:
Cluster" key is not present in the registry
BEREMOTE: [06/10/14 12:51:29] [16296] Did not detect Microsoft cluster ()
BEREMOTE: [06/10/14 12:51:29] [16296] VCS cluster keys do not appear to be present in the registry
BEREMOTE: [06/10/14 12:51:29] [16296] Did not detect VCS cluster ()
10-06-2014 04:25 AM
These messages are generic and not an error message.
10-06-2014 09:27 PM
The issue here is because of TAMAL_DMS instance on your server to which we are hung when trying to connect.. You may need to check more on this instance.. Whether the sql service corresponding to this is started and if it is using correct service credentials.. Check event viewer if any connection errors for this.. Also, if the version of this instance is different from other SQL instances on the system.
10-06-2014 10:36 PM
Yes, I have this instance of SQL in my server. and it is not in use .but i still don't understand why if i select to backup just folders or other resources that is not SQL. the backup exec starting to check the SQL instance
could you please direct me to the specific lines in the log that showing this problematic instance?