BE2012 WAN optimized deduplication with a communication or Central Adminstration Server (CAS) failure
Version 14.0 1798 Problem: I’m having trouble getting past some issues with this structure. It comes down to either optimized deduplication works, but I can’t use the MBES/MMS when the CAS is down or both sites are fault tolerant but I can’t setup optimized deduplication between them. Goal: My goal is to use optimized/shared deduplication to replicate server backups between my two sites and be able to restore those backups and local backups during a vpn failure or site failure. If site A is down, I want to recover site A servers to site B. If site B is down, I want to recover site B servers to site A. Details: I thought that I could place a Backup Exec 2012 server at each site and use optimized deduplication for this, but I ran into a few problems. Optimized deduplication, or shared deduplication as it is now called, seems to require the Central Administration Server Option and this has the following options for its Managed Backup Exec Servers: 1. Centrally managed Backup Exec server 1a. Centrally managed Backup Exec server with Unrestricted access to catalogs and backup sets for restore 2. Locally managed Backup Exec server Options 1 & 1a: With the “Centrally managed Backup Exec server” option chosen for the Managed Backup Exec Server. Having a CAS with a deduplication folder at site A and a MBES with a deduplication folder at site B works and staged jobs will run from one deduplication folder to the other. The problem here is that if the CAS is down or the VPN is down, I can’t even bring up the BE2012 console on the MBES let alone run jobs or restores. The MBES is totally dependant on a persistent communication link with the CAS under the “Centrally managed Backup Exec server” “Managed Backup Exec Server Configuration” option. Option 2: MBES that is a “Locally managed Backup Exec server”. While the CAS and MBES can still function without each other under this scenario, I can not share the MBES deduplication folder with the CAS. So I can’t do optimized deduplication between the two. Am I wrong about optimized deduplication requiring CAS + Centrally managed Backup Exec server? If so, please explain how to set it up. Is there a way to use the Centrally managed Backup Exec server when the CAS is down? I don’t understand how I’m supposed to recover if the CAS is gone.
Very slow job rate
Hi Actually using new backup exec 2012 Server 24 Gb RAM, 4 processor with 6 core each. Deduplication storage located on a HP StorageWorks with 12 disks10K Sometimes, everything is ok. But the week end during full backups, it may happen that 7 to 10 jobs run during the same time. and this may become fuckinngggg slow. Most of times, job rate is from 1000 MB to 2000 MB/mn but sometimes, during week end, all jobs run from 8 to 20Mb /mn and take forever, I need to stop them to launch them again What the heck is going on? Cpu usage is under 5%, Memory seems to be under 25% usage. Disk queue is under 0,05 , network is 10% of 1GB card I really dont know what I need to do...
NIC Teaming Slow Throughput, any ideas?
Hey guys, We currently have 2Gig set up through NIC teaming for our backup exec setup.When we have backups running, it barely reaches 35-40% of the bandwith. I am using Backup Exec 2010. Has anyone else here set up NIC teaming before? What are some things that might cause slow performance? Are there any specific settings in Backup Exec that may help? Thanks!Disk-to-tape backup taking progressively longer for single job
Have a about a dozen various backup jobs and they all follow the same pattern, backup to a deduplication disk, then later the job is duplicated out to tape. This has been working fairly well but I've noticed an issue over the past 2+ weeks for a single job. This job backs up our Exchange databases to the dedupe disk, then later out to tape. The disk-to-disk portion has stayed consistent, 250GB transferred at 2500MB/min on average. The disk-to-tape part is where it has gotten out of whack. It started out taking an hour and a half to two hours to copy, but has gradually gotten longer and longer until now it is reporting over 6 hours to do the same amount of data. We haven't changed anything since this job was created, same dedupe disk, same tape library, same type of tapes, same encryption, etc. This is the only job that is doing this, all the others are running just fine in a fairly consistent time frame. Any ideas?
NB7.5 Remote Backup Procedure after upgrading & changing Master
Environment: NetBackup 7.5 Media Server with Puredisk and Tape Library attached. I need to backup remote site "ZXY" over a WAN Link. History: Previously we were backing up XYZ using Synthetic Backups to Media Server "B" with Master Server "A" in another location. We then moved to a new Master Server "A1"and media server "B1." Before moving we replicated data using SLP from B to B1. We used the following link to seed: http://www.symantec.com/business/support/index?page=content&id=TECH144437 In particular this section: For example, assume two new remote clients, remote_client1 and remote_client2, are being backed up for the first time.Data for both clients has been copied via a transfer drive and backed up locally to the media server media1, using a policy called “transfer_drive”. Run the following commands on the media server to setup a special seeding directory using the transfer_drive backup images for each client: $ seedutil -seed -sclient media1 -spolicy transfer_drive -dclient remote_client1 $ seedutil -seed -sclient media1 -spolicy transfer_drive -dclient remote_client2 Verify the seeding directory has been populated for each client: $ seedutil –list_images remote_client1 $ seedutil –list_images remote_client2 Run backups for remote_client1 and remote_client2. Clean-up the special seeding directory.: $ seedutil –clear remote_client1 $ seedutil –clear remote_client2 Clearing the special seeding directory is important.The source backup images referenced in the special seeding directory will not be expired until they are no longer referenced.To help with this, the special seeding directory for a client will automatically be cleared whenever an image is expired by NetBackup for that client.That being said, it is good practice to explicitly cleanup the special seeding directory when it is no longer needed Now: We attempted to run backups but continually failed with Error 14. We had the Accelerator unticked. Due to the way our VPN's and WAN links are setup we decided to point the Client to another Media Server C1 which connects to A1 Master Server. How should I progress with backing up the client. Shall I use the Accelerator, have Client Side Dedupe and just run a Full Backup over the link? Or shall I some how replicate from Media Server B to C1 or from B1 to C1, then follow the above link on seeding and then run a full backup? Im a little confused on how remote backups are actually suppose to work and whether the Accelerator works on the first backup. Also whether it will use the dedupe data. Any help is appreciated.