Date: Thu, 28 Mar 2024 10:57:26 +0000 (GMT) Message-ID: <2069532189.395.1711623446097@ip-172-31-38-4.eu-west-1.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_394_215822729.1711623446092" ------=_Part_394_215822729.1711623446092 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Use the CONVERT
command with the SQL Back=
up Pro -SQL
parameter to convert SQL Backup backup f=
iles (.sqb) to Microsoft Tape Format (MTF) files (.bak) using the command l=
ine or extended stored procedure. You can use the native SQL Server
Alternatively, you can use the SQL Backup File Converter (either from th= e command line, or using the GUI application). This application can also co= nvert SQL Backup v7 or v6 files to SQL Backup v5 files; both file types hav= e extension .sqb. See SQL Backup File Converter for more information.<= /p>
If you convert a backup file that was created with multiple threads (THR= EADCOUNT > 1), an individual .bak file is created for each thread. = For example, if backup file BackUpA.sqb was created usin= g three threads, the following files are created when you convert the backu= p:
BackUpA_01.bak
BackUpA_02.bak
BackUpA_03.bak
You can then restore the MTF (.bak) format backups as a group of backup = files.
-SQL
) must be delimited by single quotes. Therefore,=
wherever a single quote is used for the arguments below, for the extended =
stored procedure you must use two single quotes so that SQ=
L Server does not interpret it as a string delimiter. See Using the extended stored procedure for more information.
CONVERT { 'p_hysical_backup_device_name'=
strong> } ] TO { 'physical_file_name
[ WITH
[ [ , ] MAXDATABLOCK =3D { 65536 | 131072 | ... | 2097152 } ]
[ [ , ] PASSWORD =3D { 'password' | 'FILE:=
file_path'} =
a> ]
[ [ , ] SINGLERESULTSET ]
]
Specifies the maximum size of data blocks to be used when SQL Backup Pro= stores backup data. Valid values are integers in multiples of 65536, up to= a maximum value of 2097152. For example:
MAXDATABLOCK =3D 655360
Specifies the password to be used with encrypted SQL Backup backup files= . The resulting MTF (.bak) format file will not be encrypted.
Storing your password in a plain text = file (only available in SQL Backup 7.5 and later)
If you don't want the password to be stored in your SQL Agent jobs, you = can use a password stored in a plain text file instead. This means access t= o the password can be restricted using Windows file permissions.
To do this, specify the file path and name after the PASSWORD keyword in= stead of the password itself.
PASSWOR= D =3D 'FILE:C:\mypasswords\password.txt'
SQL Backup will read only the first line of text in the file (up to the = first line return), and ignore everything after.
Specifies that the results returned by the CONVERT
&nbs=
p;command should be limited to just one result set. This may be useful if y=
ou want to manipulate results using a Transact-SQL script. Such scripts can=
only manipulate results when a single result set is returned. The SINGLERESULTSET
keyword.
This example converts the encrypted backup file pubs.sqb&n= bsp;to an unencrypted MTF format file:
SQLBack= upC.exe -I {instance name} -SQL "CONVERT 'C:\Backups\pubs.sqb' TO 'C:\Backu= ps\pubs.bak' WITH PASSWORD =3D 'MyPassword'"
EXECUTE = master..sqlbackup '-SQL "CONVERT ''C:\Backups\pubs.sqb'' TO ''C:\Backups\pu= bs.bak'' WITH PASSWORD =3D ''MyPassword''"'