Backup to disk - then schedule to tape?
I am looking at switching our backup to go to disk every evening, and then once a month (last day of the month), roll those off to tape. I'm confused on how I can schedule this to be done. I have created my incremental backup job that is being used on our backup tape library. Can I just apply a new policy to that existing job? Or do I have to create a new job based on the policy? If I have to create the job based on the policy, it appears that BE2010 then creates about 4 new jobs in my job setup list? Is that the correct way to do this? Or are there instructions somewhere that will walk me through how to do this???
Anyone have an idea how to fix Final error: 0x320050 - 0x 320050 (3276880)
Running 12.5, Doing incremental job and now recieve this error and job fails. All searches provide little info. The link below goes to: Symantec Suggest NO Answers Found. Any help would be appreciated. Job ended: Friday, January 20, 2012 at 1:03:26 AM Completed status: Failed Final error: 0x320050 - 0x 320050 (3276880) Final error category: Other Errors For additional information regarding this error refer to link V-79-50-80Restoring Full DB + Archive logs (SAP agent / oracle backend)
Backing up using: Brbackup & BRArchive (backint) Restored files: From backup exec catalog I have DB and archive logs files in DR site already, how to i recover DB with archive logs? "Recover database using controlfile" ? will this make the log sequence inconsistent.
BackupExec 2010 File Server Archiving Option
Hi, Everyone. I have a customer trying to reduce the size of file server front line storage, they want to have link or placeholder of these files in the file server once they were archive, because the have a netapp filer FAS2020 with SATA disks they want to send the archived files directly to tape. This is posible? They don't want to use Evault because the cost. Thanks for your help, Gonzalo GomezBackups failing with Final error: 0xe000846b - and Final error: 0xe0000f04
I hav etwo jobs that have been working fine for a few weeks, when suddenly last night, both failed. the first job is a full daily backup of my media host machine running W2k3 SP2 and Backupexec 2010. the BEWS agent is installed and has been working fine. The other job is an incremental VMWare backup of two VM's on a single host. I have the BEWS agent installed on both VM's and it has been working fine in the past. When I run a test of the jobs, the following output is observed. Job 1: Credentials CheckDevice : \\CHD10S01, C:Check status : Error: e000846b, The job failed.Device : \\CHD10S01, D:Check status : Error: e000846b, The job failed.Device : \\CHD10S01, \\CHD10S01\<Utility Partition>Check status : Error: e000846b, The job failed.Device : \\CHD10S01, Shadow?Copy?ComponentsCheck status : Error: e000846b, The job failed.Device : \\CHD10S01, System?StateCheck status : Error: e000846b, The job failed. Job2: Credentials CheckDevice : \\167.78.128.141, VMVCB::\\167.78.128.141\VCGuestVm\(DC)ha-datacenter(DC)\vm\CHD10VRI01Check status : Error: e0000f04, The job failed with the following error: The media server could not connect to the remote computer. The remote computer may not be running the Backup Exec Remote Agent for Windows/Linux. Make sure that the correct version of the Remote Agent is installed and running on the target computer. Device : \\167.78.128.141, VMVCB::\\167.78.128.141\VCGuestVm\ha-datacenter\vm\CHD10VRI01Check status : Error: e0000f04, The job failed with the following error: The media server could not connect to the remote computer. The remote computer may not be running the Backup Exec Remote Agent for Windows/Linux. Make sure that the correct version of the Remote Agent is installed and running on the target computer. Device : \\167.78.128.141, VMVCB::\\167.78.128.141\VCGuestVm\ha-datacenter\vm\CHD10VFP01Check status : Error: e0000f04, The job failed with the following error: The media server could not connect to the remote computer. The remote computer may not be running the Backup Exec Remote Agent for Windows/Linux. Make sure that the correct version of the Remote Agent is installed and running on the target computer. Media and Capacity checks are seccessful. I repeat, the BEWS agent is installed on all W2k3 hosts and has been working before yesterday. I have been migrating my DHCP scopes over the past couple of days, but there are no network issues or inaccessible hosts. DHCP is working fine. These jobs use the system account. It has not been changed, as far as I can tell. Thanks Denise000ff18 - A communications failure has occurred with a Virtual Machine resource
I get this error randomly on nightly incremental jobs, or weekly full jobs on one particular ESX 4.0 VM running Win2k3 SP2.. I also get a SNMP alert on that VM stating that the device was not reachable for ~300 seconds, which coincides with the end of the BEWS processing window for that particular VM. the log also indicates data IS being backed up and there are no skipped or corrupted files reported, but the job fails anyway. This is annoying because it does not happen every night and returns no relevant Windows event log entries on the VM in question. My other VM's on this VSphere host backup fine every night. I have WSUS and Numara Patch manager running on this VM, which both use SQL server express. I do NOT have the VSS option enebled in the job because it causes my other VM's to fail when enebled.
