Running into an issue when restoring a backup to an alternate server. This server contains multiple restores at any given time.
To get around file conflicts, we move files to appropriate places or names using the MOVE option. While restoring, everything appears okay, but once done, the files disappear and/or are moved one directory level higher, but with original naming (causing naming conflicts on other restores).
We did not see this issue with 6.4 version.
Trying this with 7.4 SQL Backup, Windows Server 2008 R2, SQL Server 2008 R2 SP1.
Here is command example generated by UI. Added some <CR> to make it easier to read:
EXECUTE master..sqlbackup
'-SQL "RESTORE DATABASE [sandbox_s4]
FROM DISK = ''\\BackupServer\DatabaseBackups\s4\FULL_s4_20130729_004816.sqb''
WITH PASSWORD = ''<password>'', RECOVERY,
MOVE ''db_Data'' TO ''C:\DBC1\I7\DATA\sandbox_s4.mdf'',
MOVE ''sysft_KBIndex'' TO ''C:\DBC1\I7\LOG\FullText\KBIndex_sandbox_s4'',
MOVE ''sysft_FieldValueIndex'' TO ''C:\DBC1\I7\LOG\FullText\FieldValueIndex_sandbox_s4'',
MOVE ''sysft_HistoryIndex'' TO ''C:\DBC1\I7\LOG\FullText\HistoryIndex_sandbox_s4'',
MOVE ''db_Log'' TO ''C:\DBC1\I7\LOG\sandbox_s4_log.ldf'', REPLACE, ORPHAN_CHECK"'
In this case, the sysft files are left as more generic names in the FullText directory and not within their respective MOVE directories.
For example, sysft_KBIndex would be expected to be contained in C:\DBC1\I7\LOG\FullText\KBIndex_sandbox_s4 with all it's related files, however, we instead see just this:
C:\DBC1\I7\LOG\FullText\ftrow_KBIndex.ndf
Tried adding a filename even to the MOVE command and that was ignored as well.
To get around file conflicts, we move files to appropriate places or names using the MOVE option. While restoring, everything appears okay, but once done, the files disappear and/or are moved one directory level higher, but with original naming (causing naming conflicts on other restores).
We did not see this issue with 6.4 version.
Trying this with 7.4 SQL Backup, Windows Server 2008 R2, SQL Server 2008 R2 SP1.
Here is command example generated by UI. Added some <CR> to make it easier to read:
EXECUTE master..sqlbackup
'-SQL "RESTORE DATABASE [sandbox_s4]
FROM DISK = ''\\BackupServer\DatabaseBackups\s4\FULL_s4_20130729_004816.sqb''
WITH PASSWORD = ''<password>'', RECOVERY,
MOVE ''db_Data'' TO ''C:\DBC1\I7\DATA\sandbox_s4.mdf'',
MOVE ''sysft_KBIndex'' TO ''C:\DBC1\I7\LOG\FullText\KBIndex_sandbox_s4'',
MOVE ''sysft_FieldValueIndex'' TO ''C:\DBC1\I7\LOG\FullText\FieldValueIndex_sandbox_s4'',
MOVE ''sysft_HistoryIndex'' TO ''C:\DBC1\I7\LOG\FullText\HistoryIndex_sandbox_s4'',
MOVE ''db_Log'' TO ''C:\DBC1\I7\LOG\sandbox_s4_log.ldf'', REPLACE, ORPHAN_CHECK"'
In this case, the sysft files are left as more generic names in the FullText directory and not within their respective MOVE directories.
For example, sysft_KBIndex would be expected to be contained in C:\DBC1\I7\LOG\FullText\KBIndex_sandbox_s4 with all it's related files, however, we instead see just this:
C:\DBC1\I7\LOG\FullText\ftrow_KBIndex.ndf
Tried adding a filename even to the MOVE command and that was ignored as well.