Backup syntax
Use the backup command syntax diagrams as a reference to view available options and truncation requirements.
Backup optional parameters
Notes:
- 1 For the optional parameters, the /BACKUPMETHod= is only valid when using the full or copyfull positional parameters. The full and copyfull backups can be performed using VSS or legacy operations. The /BACKUPMETHod= parameter is used to choose between the options. The log, diff, file, and group backups can be performed only when using legacy operations. You cannot specify the /BACKUPMETHod= parameter with these types of backups because only legacy backups are viable.
- 2 The /BACKUPDESTination parameter is valid only when using the full or copyfull positional parameters. The full and copyfull backups can be saved to local storage, TSM server storage, or both. The /BACKUPDESTination parameter is used to choose among the options.

/AAGName=AlwaysOn Availability Group
name/ALWAYSONPriority/BACKUPDESTination=LOCALTSMBOTH/BACKUPMETHod=LEGACYVSS/CONFIGfile=tdpsql.cfg?=configfilename/ENABLEREPlacementchars=No?=Yes/EXCLUDEdb,=db-name,.../EXCLUDEALwaysondbs/EXCLUDESTandarddbs/FCMOPTFile=dsm.opt?=dsmoptfilename/LOGFile=tdpsql.log
[or cfg value]?=logfilename/LOGPrune=60 [or cfg
value]?=numdays=No/OFFLOAD/Quiet/SQLAUTHentication=INTegrated [or cfg
value]?=SQLuserid/SQLCHECKSum=No?Yes/SQLPassword=" "?=sqlpasswordname/SQLSERVer=[local computer name
or cfg value]?=sqlserver-connection/SQLUSer=sa?=sqlusername