Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

FIX YOUR DATABASE!!!

Created: 20 Nov 2012 • Updated: 12 Dec 2012 | 4 comments
Data Integral's picture
1 Agree
1 Disagree
0 2 Votes
Login to vote
Status: Reviewed

Please fix your databases..

Half of your technicans posted links dont work... there is always

HTTP Status 500 - Database connection is not valid

 

for example on: http://www.symantec.com/business/support/index?pag...

and many others.... This is just annoying if u are partner and need fast help and half of the forumposted links of your technicans doesnt work..

 

Kind Regards

Felix M.

Comments 4 CommentsJump to latest comment

isleifurg's picture

I agree this - fix it!

-1
Login to vote
CraigV's picture

...please go to the link below and log an official query. You've added an idea which will give you no traction whatsoever:

https://www-secure.symantec.com/connect/inside-sym...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

0
Login to vote
LeslieMiller's picture

These links are not under the control of Connect; however, I will be happy to pass your request on to the techs and ask them to update their links.

0
Login to vote
lex13's picture

Our apologies for this link issue. During periods of database updates, some documents are expiring. This document has expired due to a liability issue using regedit.

Locale English
Document ID TECH36571
   
Issue

How to force a .DR file to be created or updated even though some files and/or folders are excluded during a backup when the IDR (Intelligent Disaster Recovery) option is enabled

 

Solution

By default, if any files or folders are excluded in a backup job, Backup Exec will not create or update the machine specific .DR file that maintains the list of backup sets used to restore the system to its most recent backup. It is possible to make a change to the registry to alter the default behavior.

Warning: Incorrect use of the Windows Registry Editor can have disastrous results on a server operating system. Great care should be taken when making changes to a Windows Registry. Registry modifications should only be carried out by persons experienced in the use of the Registry Editor application

 

If you still need the document and accept the disclaimer, open a support case and the engineer will review this with you, regarding the technote issue, it is now listed as internal.

The author stated: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Thank you for your patience and using our forums to communicate the issue.

 

0
Login to vote