Backing up and collecting diagnostic configuration information on Director
BlueCoat Support has asked for an Archive (Archive all) of my Director configuration. How do I do this?
Blue Coat Support has asked for a Memory dump of DIrector. How do I do this?
How do I back up my Director configuration?
How can I back up Director?
How can I extract an overlay file for support?
This article discusses how to archive (that is, back up) Director and store the archive on a remote server that Director can access. Other than for safety and security reasons, you can optionally restore the archive on another Director appliance.
This article is written for SGME 184.108.40.206 and later; some features discussed in this article (for example, archiving Director using a job) are available only on SGME 220.127.116.11 and later.
For instructions on archiving Director on earlier SGME versions, see the Configuration and Management Guide. You can also refer to this article.
Archiving Director involves the following high-level tasks:
What an archive contains:
The following are not included in an archive configuration:
NOTE: After each command in the Command Line Interface (CLI), you can enter a question mark "?" to display more information about it, such as sub-commands.
Task 1 - Back up your configuration
Log in to the CLI using SSH and enter the following:
Task 2 - Check the configuration file
Enter the following:
To rename a configuration file, enter:
Task 3 - Make the configuration file the current file
Enter the following:
Alternatively, the following command makes a older archive the current file:
NOTE: The argument -write - (used in Task 1) saves the active configuration to a file and makes the file the active configuration, but not the 'current' one.
Task 4 - Create an archive of your configuration and logs for Blue Coat Support
Generate a private key:
Use the private key to create a dump file:
Important: You will be prompted for a pass phrase, which is the same as your key name. You will need to provide this public key to Blue Coat Support so that they can extract your archive. When Support extracts the archive onto the LAB Director appliance, their admin password will change to your own password. In other words, Support needs your password. Blue Coat recommends that you change your password after sending in the archive. Creating a key is necessary for Blue Coat Support to open the file on their own Director appliances. Archives created without a key can only be extracted on the same Director appliance that they were created on.
To create an archive without a key:
To send the archive to an off-box location:
To send the archive to Blue Coat Support, upload the debug dump to https://upload.bluecoat.com. Specify all of the information requested in the form, including the Service Request Number (Support ticket number).
Fetching and restoring Archive commands:
Task 5 - Create and send the debug dump file to Blue Coat Support
Generate the dump file:
Blue Coat will request for extra logging in the debug dump file. Please make sure the logging level is set to
To send a memory dump file to an off-box location:
If you are using Linux:
You can obtain some manual information by using the Linux prompt to collect the output of these commands. Refer to KB4178 for more information.
NOTE: Execute these commands only if specifically requested:
Send the file to Blue Coat Support:
To delete a dump file:
Task 6 - Retrieve an overlay file that Director might pull from a ProxySG appliance
Method 1: Using the CLI
Method 2: Using the Management Console
For more information on topics related to this article, see the following articles.
270K • < 1 minute @ 56k, < 1 minute @ broadband
Rate this Page
Please take a moment to complete this form to help us better serve you.