Ignoring Stub Files
Can we filter our Backup Policy based on file size. Regardless of whether or not it is a stub file. Can we backup files ONLY greater than 8k? or by file creation date. Currently we have a process that we purchased (Rainfinity from EMC) that takes images once a month and stores the image on lower cost file system and leaves a stub file that is 8k in size. When I run a full backup the policy sees the 8k and backs up the file. Which is great but the stub file is 8k the actual file is larger and has to be retrieve from the lower cost disk which is very slow so my 1TB area takes days to backup to tape because of the slow retrieval speed. Yes EMC can replicate the data to another area but because of the cost this is not an option at this time
Accelerator for a VMWare Backup Policy with AIR
Hello Experts, I am using NBU 7.7.3. I have a VMWare policy querying a cluster for an annotation to backup some clients. This policy has 4 schedules. Each Schedule has override policy storage selection checked with a corresponding AIR (Automated Image Replication) SLP's as the selection. The Storage selected in the SLP is an EMC DataDomain Storage unit (Using OST Plugin) setup as a Source for AIR. Attached some screenshots. With this setup, Should the 'Use Accelarator' Option be available for selection on the policy? Currently I see it grayed out.
NetBackup 7.5.0.4 with DataDomain and Status 2106
(1) Master/Media Server Windows 2008 R2 Standard (3) Media Servers Windows 2008 R2 Standard (2) DataDomain DD670's Monday, I disabled all backup policies. Then I shutdown NetBackup on all 4 severs. Then I did a shutdown on 1 DataDomain so that I could physically move the unit to make room for a new DataDomain 890 unit. After moving the 670, (I had to replace 4 CAT6 cables with new ones for length)I powered up the DAE's first and let then settle to a ready state. Then I powered up the Head Unit. Initially, the head Unit locked up half way into the boot. Called DataDomain andthey had me force power off the unit and had me pull it out and reseat all the RAM, PCI Riser cards and all the Hard Drives. Then replaced and repowered and all came up fine. I then started NetBackup services on the Master and then all the media servers. After everything was up, I reactivated all the policies. This ran fine until 1:00am on Thursday. Then, the DataDomain unit I moved started failing every job that ran on it with a status of 2106 (Status 2106: Disk storage server is down). I had Symantec look at it (logs sent in that were requested), and they siad it had to be a DD-Boost problem, as they could not see an issue. I then called DataDomain and they put there people on it and said it was a network problem because they couldn't ping the server from the unit. So then I went (tonight) and ran a network tester on the cables between the unit and the core switch. Cables tested fine and i have normal flashing link lights... So I did a shutdown restart on the DD head unit. After it came back up, i could ping the server from the unit. Kicked off a failed backup and it failed again with 2106 or a media write error(84)... When looking up the 2106 error this morning, I found a Symantec article that said I needed to reautherize the the servers to the DD unit. How do I do that? Does anyone else have an idea what would be causing all this? I now have Duplications (LCP) kicking off by the hundreds every 15 or minutes and I have to clean those all up too because they are failing with a status 84 and Image Cleanups failing with a status 83... I want to pull my hair out, but I don't have any left to pull out! Hope some one can help. John
NDMP Restore getting hung
Hi, the backup which was duplicated from one media server is not able restore from other media server Master OS -- > Solaris 10, NBU 7.5.0.4 Media ( where the backups duplicated ) server -- > 6.5.6, SUSE Linux 10 Media ( from Where we are trying to restore) server -- > 6.5.6, SUSE Linux 10 Restore is not progressing anything ... its not going to media server media ZXXXXX required,02/07/13 10:52:38 - restoring image YYYYY_1357302655,02/07/13 10:52:39 - Info bprd(pid=3499) Restoring from copy 2 of image created Fri Jan 04 18:00:55 2013,02/07/13 19:25:38 - connecting,02/07/13 19:25:38 - connected; connect time: 000:00:00,02/07/13 19:25:39 - started process bptm.... its strucking here.. Can someone please help me..