ContributionsMost RecentMost LikesSolutionsRe: running out of tape spaceHi Al: You are already getting a pretty good compression ratio on these tapes. You either need to buy an additional tape drive or one that uses higher capacity tapes. JayRe: Can I move the BE 11d 2005 DB to a SQL 2000 DB?Hi John: No, you cannot. This is how Microsoft designed SQL Express (only can be moved to SQL 2005 Full Installation). Why would you want to move it to a regular SQL Installation anyway? I do not see any benefit to this, especially if this SQL Server is a different machine, because of possible network connection issues. JayRe: Error for System State BackupHi Alvinesh: Re-apply Service Pack One for Windows 2003 to the machine. If the error still occurs after, put the Remote Agent in debug mode (-debug), run the backup again, and have to log readily available when you open a support case. JayRe: CPU for beserver.exe goes to 30% constant, and memory goes upHi Peter: Run a repair on the .Net 2.0 Framework Installation by browsing to Winnt\Install\DotNetFX\DotNetFX.Exe File from the Backup Exec 11D Installation Software. Double click on this and select the "Repair" Option when the wizard comes up. JayRe: Problems with 11d speed/performaneHi Benjamin: The one thing I don't see anyone addressing in their posts is the amount of available physical memory (Ram) in the media server. Backup Exec 11D now uses SQL Express (SQL 2005 Desktop Edition) and it uses more memory than the previous SQL MSDE Version did. SQL Express and Backup Exec 11D should have a minimum of 500mb allocated. If the machine is a domain controller, there should be 1GB for that. If there is another database application running on the machine, 1GB for that application. Anti-virus Software or other third party application, a minimum of 500mb. ***So in other words, unless the media server is just being used as a dedicated backup server, the amount of physical memory may not be enough to keep up with the load on the machine. A lot of people wonder why their backups run slow and they never take the amount of physical memory or the driver/firmware level on all the hardware (SCSI/Raid, NIC, etc...) into consideration. If Backup Exec 11D were installed on an SBS 2003 Server with all the SBS Options enabled and with anti-virus software installed, there should be a minimum of 3GB of Physical Memory (Ram) in the machine. All the memory also needs to be the same make/model and be approved by the server manufacturer. JayRe: 11d SQL Agent on an NT 4 boxHi Dave: Backup Exec is only designed to be able to use a Remote Agent that is one version prior to the version installed on the media server. So a 9.1 Remote Agent cannot be used with a version 11D Media Server. There is also limited support for a file system backup of NT4 and you will not be able to utilize the SQL Agent unless the NT4 Machine is upgraded to Windows 2000 or 2003. What you will have to do is use the SQL Backup Utility to dump the data to disk, then use Backup Exec to backup the dump file (.bak). JayRe: HELP!!! BE 11D, 3 different problemsP.S.: If you are backing up remote servers with a Remote Agent installed on them, the Remote Agent needs to be re-installed after all the latest patches for Backup Exec have been applied to the media server. Confirm also that the network card drivers are at the latest level on each machine (media server and remote) and review each machine's Windows Event Viewer Logs for warnings/errors. JayRe: HELP!!! BE 11D, 3 different problemsHi Al: Recreating your jobs will not resolve the three issues that you are experiencing. And the version of the backup software is not the cause of the backup taking up more than one tape. The Super DLT1 Tapes can be used in either a 110/220 or 160/320 Tape Drive. Your tape drive only supports a native capacity of 110GB and a maximum rated capacity of 220GB. The only way to get more capacity out of those tapes than 220GB (which you most likely would never even get this much compression, even if software compression is used) is to replace the existing drive with a 160/320GB Model. http://h20000.www2.hp.com/bc/docs/support/UCR/SupportManual/TPM_201412e2(1)/TPM_201412e2(1).pdf?jumpid=reg_R1002_USEN ***The type of data you are backing up is also a major contributor to the amount of compression that can be achieved. http://support.veritas.com/docs/199542 ***The Technote listed immediately above can also explain one reason why the backups are taking longer. Trying to use hardware compression to backup data that is already in a highly compressed state will cause the data to expand, take up more room on the tape, and slow the backup down. ***AOFO and VSP Errors usually occur for the following reasons: 1. Your anti-virus software is scanning the AOFO Cache Folder or the Hidden System Volume Information Folder where the VSP Shadow Copy Snapshot gets created. The virus scanning should never scan these folders or any folders where database transaction logging occurs (Exchange, SQL, Active Directory Domain Controller NTDS Files/Folders, etc...). http://support.microsoft.com/kb/822158 2. The hard disks are heavily fragmented or need to have a Check Disk run on them (chkdsk /f). http://seer.support.veritas.com/docs/237444.htm ***Make sure also that the hard disks are not running out of free disk space. Each partition should have a minimum of 15% free disk space available. 3. There is not enough memory or the memory is mis-matched (different brands). If a machine is only a workgroup or member server (not a domain controller, Exchange or SQL Server) and only being used as a file server without AOFO being installed, then 1.5GB of Ram would be an adequate amount of memory if the machine got backed up at a time when there was minimal disk activity (after hours when no users are accessing it). But since Backup Exec 11D now uses SQL Express (SQL 2005 Desktop Edition that requires more memory), because of the amount of memory anti-virus software uses, and add in AOFO & any other third party applications - 1.5GB of Ram is not enough. Each application/installation/upgrade should be allocated at least 500mb of Ram. So if you install Windows fresh on a machine, it should have at least 500mb of Ram. If you upgrade it to a domain controller, add another 500mb. Install Backup Exec 11D, add another 500mb, install anti-virus software, add another 500mb, etc... ***Exchange, Oracle, Lotus Domino, and SQL Servers should have a minimum of 1GB of memory allocated just for their applications. The UserVA and 3GB Parameters should be enabled in the Boot.ini File also. http://support.microsoft.com/kb/810371 ***When you upgraded to 11D, at least 500mb minimum of Ram should have been added to the server. Memory is cheap now days, so I would adding at least 1 to 1.5 GB more and confirm it is all the same HP/Compaq Approved Ram. 4. Another third party application that uses a filter driver is installed or running at the same time the backup is. Products like Diskeeper should not run when the backup does. And any other third party replication or open file applications should not be installed on a machine if you want to backup that machine with Backup Exec. 5. The SofPaqs or RomPaqs are not at the latest level. The firmware also needs to be at the latest level on the tape drive and it should be cleaned per the manufacturer's recommendation. 6. Service Pack One for Windows 2003 needs to be re-applied. Microsoft claims that this is not necessary in the newer versions of Windows, but they also have claimed in the past that servers never have to be rebooted or that plug & play hardware can just be connected to a server without requiring a reboot or shutdown. Unless Backup Exec was installed prior to Service Pack One being applied, re-apply the service pack. ***Please realize that the backup software is only part of the total equation here. The tape hardware can only backup/compress what it is rated for. VSP/AOFO Errors occur because of other third party application conflicts, a lack of available memory (Ram), heavy disk I/O (excessive paging due to lack of memory), a lack of available hard disk space, heavy disk fragmentation, etc... ***If you perform the steps above, confirm that there are no application or hardware warnings/errors in the Windows Event Viewer, and the backups still take a long time or error out, then I would agree with you regarding there being an issue with the backup software. One other thing to realize is that some of the new Backup Exec Features, such as data encryption, are going to make the backups run slower, because of the additional processing it takes to encrypt the data. You also cannot use hardware compression when encryption is selected and software compression with encryption will make the backup run even slower. JayRe: Robotic Library Error when doing an inventory on an empty slotAny time an error occurs when running an inventory, you should open a support case with the hardware manufacturer. The backup software only sends commands to the device to pull a tape from the slot, put it in the tape drive, read the header information on it, and return it to the slot. If the device goes offline, then it is usually the hardware that terminates the connection to the backup software and/or OS if something is not configured properly on the library or if the device is defective.