Support Bundle Commands

Commands are case sensitive. Do not type "<" or ">" in the command; they are used as placeholders. Include a space between parameters. Parameters are provided in long and short form for convenience.

Examples:

If servers have Internet access, this command will collect and upload files: DcsSupportbundle.exe /c:dcsw /u:username /p:password /i:dddddd-dddddd /t:ticketnumber /co:Company Name

If servers do not have Internet access, this command will collect the files and skip the upload: DcsSupportbundle.exe /c:dcsw /u:username /p:password /i:dddddd-dddddd /t:ticketnumber /co:Company Name/

To collect a support bundle with minimal parameters (without an incident number or company identification) and skip the upload:DcsSupportbundle.exe /c:dcsw /u:username /p:password /su

Support Bundle Command Line Parameters
/anonUserData:- Disables anonymization.
/anonUserData:+ Creates anonymized bundle.

/connectionType:string

or

/c:<string> 

Specifies the type of connection the service will establish to upload the bundle. The only valid connection type is dcsw.

/skipCollect[+|-]

or

/sc

Instructs the service not to collect new log data before uploading.

/skipUpload[+|-]

or

/su

Instructs the service not to upload the support bundle.

/SupportBundleRelayAddress:<string>:<int>

[+|-]

or

/BundleRelay:<string>:<int>

Include this parameter if using DataCore Support Bundle Relay.

The value is the IP address or hostname for a server running the DataCore Support Bundle Relay Service. Also include the port to use if using a non-default port. Do not include the port number if using the default port of 3795.

For example: /BundleRelay:RelayServer1 would use the Support Bundle Relay Server named "RelayServer1" and the default port of "3795". (Do not include the port in the parameter  if using the default 3795.)

/BundleRelay:RelayServer1:3700 would use the Support Bundle Relay Server named "RelayServer1" and non-default port "3700".

/bundleType:

or

/b:<CrashDump|Mini|Full|Standard

Instructs the service whether it should collect the standard support bundle, full support bundle, mini support bundle, or crash dump.

If a crash dump is required, create a support bundle once to collect the crash dump, and again to collect the full support bundle. Both files should be sent (either manually or automatically) to DataCore Technical Support.

/disableLogging[+|-]

or

/d

Instructs the service to avoid logging messages when operations are performed.

/username:string

or

/u:<string> 

User name used to log in to the DataCore Management Console. This is used for authentication.

/password:<string>

or

/p:<string>

Password used to log in to the DataCore Management Console. This is used for authentication.

/incidentNumber:string

or

/i:<string>

The incident number that was opened for the problem. DataCore Technical Support will be able to identify the support bundle and match it to the corresponding incident for analysis.

Incident number is a 12-digit decimal number in this format: dddddd-dddddd. The first group of six digits represents the date (

/ticketNumber:string

or

/t:<string>

The ticket number is a reference number used to associate support bundle folders from more than one server. Use a ticket number if the connection to the other server in the group is lost.

If you have access to the DataCore Management Console, a ticket number is automatically created and is listed as a message entry in the Task Details page in the Events Log tab.

If you cannot access the DataCore Management Console, you can enter a ticket number based on the date and time; such as the year-month-day (dddd_dd_dd) and 24-hour time (dd_dd_dd). Connect the two formats with an underscore.

For example: /t:2021_07_01_13_30_00 would refer to a timestamp of July 1, 2021 at 1:30 PM.

/companyName:string

or

/co:string

Name of the company of the end-user where the software is installed. Use quotes around the string if a space exists in the name.

For example: /co:Acme