 |
|
|
|
Is this a clustered instance ? If so then you need to specify the new serveraddress pluginoption and specify the cluster address. The above error on google leads to several hits including this one: http://www.symantec.com/connect/forums/none-requested-files-were-backed-ms-sql Which seems to indicate that its a problem at resolving the service inside windows so has little to do with the plugin. This is also more a thing for on the mailinglist then for in a bug database as I wonder if its a bug at all. |
|
|
I am suffering the same issue. Both with MsSQL 2005 Standard (Win2008 x64) and MsSQL Express (Win2003 x86) as well with two different hosts (not clustered). |
|
|
It is standalone instance with several databases. Instance runs in "simple recovery mode", your manual says about "full recovery mode", but IMHO it is recommendation, not requirement. This is devel env, PTR its not so important. version: "Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor) " I tried option serveraddress before. I tried add alias for mssql instance named MSSQLSERVER too. With no success. |
|
|
Try doing some proper debugging first. It can be a ton of reasons that things don't work. See http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-27000025.2 That describes how to capture debug information on windows. The plugin should write out the connect string it uses if you capture that try using that with a external program to see if that connect string can be processed on your system. |
|
|
|
|
|
Please increase the debug level to at least 150 as otherwise the plugin itself doesn't log anything. |
|
|
|
|
|
First trc file was dumped with 200 debug level, second with 2000 debug level. |
|
|
any clue? |
|
|
I can confirm that same symptoms appear with SQLVDI when MSSQL EXPRESS (2012 SP3) is the source for backup. No clues, what or why SQLVDI fails, appear in trace file when FD is running in trace/debug mode. SQL server itself states that SQLEXPRESS is the name of instance and it makes no difference if I use this exact name or if I used "default" I wanted to add few lines of debug code to this plugins source and trace it bit more deeply but I failed to compile vanilla source with mingw64. This obviously is another story, but maybe I could use win SDK's debugger for this. Maybe someone can recommend a tool for testing SQLVDI's config, there is a tool called SQL Backup Simulator but all links I could find are broken and download for this tool is nowhere to be found. |
|
|
I think I have found the cause of this issue. It's the way how the method IClientVirtualDeviceSet2::CreateEx is called. VDI documentation states that the first argument passed to this method must be the instance name or NULL if it's the default instance, I quote: "The instance name must identify the instance to which the Transact-SQL is issued. NULL identifies the default instance. No "machineName\" prefix is accepted" So the code at the line 1432 in file mssqlvdi-fd.c: hr = p_ctx->VDIDeviceSet->CreateEx(NULL, p_ctx->vdsname, &p_ctx->VDIConfig); it should be something like this if (bstrcasecmp(p_ctx->instance, DEFAULT_INSTANCE)) { hr = p_ctx->VDIDeviceSet->CreateEx(NULL, p_ctx->vdsname, &p_ctx->VDIConfig); } else { hr = p_ctx->VDIDeviceSet->CreateEx(p_ctx->instance, p_ctx->vdsname, &p_ctx->VDIConfig); } According to VDI documentation host name can be omitted from the instance name so this fix should work. PS. If I only had access to the Win32 build environment then I could test this theory :) |
|
|
Ok sound plausible, problem is that we cannot ship the Windows headers for VDI and VSS as they are Microsoft proprietary. So you need to get those yourself or do some clever googling as it seems some people do publish them although they probably are not allowed to. I added the patch to a test branch so things should start to compile soon and I will attach the created mssqlvdi-fd.dll here or make it available via other means. |
|
|
A windows installer is made available under http://download.bareos.org/bareos/people/mvw/bug384/ This is the current master code with a somewhat modified version of your patch to make it compile as the argument is wide char and our instance name is normally stored as normal UTF8 string. |
|
|
I confirm that this patch fixed this particular issue. MSSQL VDI plugin correctly handles databases which do not run as the default instance. It looks very promising, I'll do few additional tests to verify correct behaviour of this plugin. Inc, Diff and Full backups of named MSSQL instances are working! |
- Anonymous
