Looking for some real-world insight or pointers into a new backup system we are planning and want to test soon. 

We have recently purchased Backup Exec 2014 with V-Ray licensing, Windows agents and several Application & Databases agents.  We are updating our current Backup Exec 2012 system and adding in disk-to-disk and deduplication to the plan.  We purchased a 48TB external RAID unit that will connect directly to our BUE2014 server via a 6GB SAS link.  Also directly attached to the BUE2014 server is an LTO-5 library, also external SAS.  Will be backing up VMware virtual machines, physical Windows servers w/ SQL and Exchange(virtual).  All in all, about 1.5TB nightly, and 3TB for a weekly "full" job.

Been reading about deduplication and disk-to-disk and the Symantec Best Practices guides recommend different disk storage for both, so I'm thinking of splitting my external RAID unit 60/40 (D2D/Deduplication).  I'm thinking of backing up everything to disk using multiple jobs, then other jobs to go from the disk backup to tape for offsite storage.  When does the deduplication come into play? How does deduplication work if I want to do whole virtual machine backups?  Thanks.

Bill

Hi,

I'm using symantec backup exec 2014 with HP 1/8 G2 Autoloader using LTO-6 Ultrium RW tape.

My setup won't detect the tape inside the robotic library. Done setting up the Barcode rules and robotic library.

Any advise will be much appreciate.

Dear Sir :

When I perform the full backup and has the following error :

V-79-57344-65085 - There was a problem running the DBCC. The transaction log for database 'PID' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

How can I solve this problem ? thanks !

Nova

I have just finished installing a new instance of the latest Symantec Backup Exec (v14.1) and would like to use this server in replacement of my current machine (it physically did not have the resources to run properly anymore).

Scenario is as below

MACHINE 1 (Current backup Server)

Windows Server 2008 R2 with Symantec Backup Exec v14.0 rev 1798

MACHINE 2 (New Installation)

Windows Server 2008 R2 with Symantec Backup Exec v14.1 rev rev 1786

QUESTION

How can I take my complete configuration (including backup jobs) from MACHINE 1 and import it to MACHINE 2?

I am close to just creating the jobs again but would prefer a simpler approach which would hopefully upgrade any agenst required in the process.

Any help would be great.

Thanks.

I keep on getting failed NDMP Backups from Netapps, it will backup correctly occasionally but then fails the next few times, I have been going through the logs and have noticed that when I get a failed backup the NDMP Log is very long and it only writes a few KB every 5 minutes and fails when it has exceeded maximum run time 24hrs

NDMP Log Message: DUMP: creating "/vol/VMWare_VHD_Datastores_3/../snapshot_for_backup.52431" snapshot.
NDMP Log Message: DUMP: Using Full Volume Dump
NDMP Log Message: DUMP: Date of this level 0 dump: Fri Dec 12 09:48:59 2014.
NDMP Log Message: DUMP: Date of last level 0 dump: the epoch.
NDMP Log Message: DUMP: Dumping /vol/VMWare_VHD_Datastores_3 to NDMP connection
NDMP Log Message: DUMP: mapping (Pass I)[regular files]
NDMP Log Message: DUMP: mapping (Pass II)[directories]
NDMP Log Message: DUMP: estimated 633249236 KB.
NDMP Log Message: DUMP: dumping (Pass III) [directories]
NDMP Log Message: DUMP: Fri Dec 12 09:54:47 2014 : We have written 172 KB.
NDMP Log Message: DUMP: dumping (Pass IV) [regular files]
NDMP Log Message: DUMP: Fri Dec 12 09:59:48 2014 : We have written 303 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:04:50 2014 : We have written 440 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:09:55 2014 : We have written 576 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:14:58 2014 : We have written 712 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:20:06 2014 : We have written 849 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:25:11 2014 : We have written 985 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:30:16 2014 : We have written 1121 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:35:21 2014 : We have written 1257 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:40:27 2014 : We have written 1394 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:45:34 2014 : We have written 1530 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:50:39 2014 : We have written 1666 KB.
NDMP Log Message: DUMP: Fri Dec 12 10:55:45 2014 : We have written 1802 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:00:53 2014 : We have written 1939 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:05:58 2014 : We have written 2075 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:11:00 2014 : We have written 2211 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:16:08 2014 : We have written 2347 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:21:16 2014 : We have written 2484 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:26:20 2014 : We have written 2620 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:31:28 2014 : We have written 2756 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:36:36 2014 : We have written 2893 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:41:39 2014 : We have written 3029 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:46:46 2014 : We have written 3165 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:51:51 2014 : We have written 3301 KB.
NDMP Log Message: DUMP: Fri Dec 12 11:56:59 2014 : We have written 3438 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:02:03 2014 : We have written 3574 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:07:11 2014 : We have written 3710 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:12:16 2014 : We have written 3846 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:17:24 2014 : We have written 3983 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:22:31 2014 : We have written 4119 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:27:35 2014 : We have written 4255 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:32:39 2014 : We have written 4391 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:37:40 2014 : We have written 4524 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:42:44 2014 : We have written 4660 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:47:49 2014 : We have written 4796 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:52:50 2014 : We have written 4929 KB.
NDMP Log Message: DUMP: Fri Dec 12 12:57:53 2014 : We have written 5065 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:03:01 2014 : We have written 5201 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:08:05 2014 : We have written 5337 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:13:12 2014 : We have written 5474 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:18:17 2014 : We have written 5610 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:23:24 2014 : We have written 5746 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:28:28 2014 : We have written 5882 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:33:36 2014 : We have written 6019 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:38:44 2014 : We have written 6155 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:43:48 2014 : We have written 6291 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:48:53 2014 : We have written 6427 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:53:53 2014 : We have written 6560 KB.
NDMP Log Message: DUMP: Fri Dec 12 13:58:57 2014 : We have written 6696 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:04:00 2014 : We have written 6832 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:09:07 2014 : We have written 6968 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:14:14 2014 : We have written 7105 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:19:17 2014 : We have written 7241 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:24:24 2014 : We have written 7377 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:29:31 2014 : We have written 7514 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:34:36 2014 : We have written 7650 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:39:42 2014 : We have written 7786 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:44:47 2014 : We have written 7922 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:49:55 2014 : We have written 8059 KB.
NDMP Log Message: DUMP: Fri Dec 12 14:54:58 2014 : We have written 8195 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:00:05 2014 : We have written 8331 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:05:09 2014 : We have written 8467 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:10:16 2014 : We have written 8604 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:15:23 2014 : We have written 8740 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:20:27 2014 : We have written 8876 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:25:30 2014 : We have written 9012 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:30:31 2014 : We have written 9145 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:35:36 2014 : We have written 9281 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:40:39 2014 : We have written 9417 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:45:41 2014 : We have written 9550 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:50:46 2014 : We have written 9686 KB.
NDMP Log Message: DUMP: Fri Dec 12 15:55:52 2014 : We have written 9822 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:00:56 2014 : We have written 9958 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:06:04 2014 : We have written 10095 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:11:08 2014 : We have written 10231 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:16:15 2014 : We have written 10367 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:21:19 2014 : We have written 10503 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:26:26 2014 : We have written 10640 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:31:34 2014 : We have written 10776 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:36:39 2014 : We have written 10912 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:41:42 2014 : We have written 11048 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:46:43 2014 : We have written 11181 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:51:48 2014 : We have written 11317 KB.
NDMP Log Message: DUMP: Fri Dec 12 16:56:52 2014 : We have written 11453 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:02:00 2014 : We have written 11589 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:07:08 2014 : We have written 11726 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:12:12 2014 : We have written 11862 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:17:18 2014 : We have written 11998 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:22:26 2014 : We have written 12135 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:27:29 2014 : We have written 12271 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:32:37 2014 : We have written 12407 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:37:41 2014 : We have written 12543 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:42:48 2014 : We have written 12680 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:47:53 2014 : We have written 12816 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:53:01 2014 : We have written 12952 KB.
NDMP Log Message: DUMP: Fri Dec 12 17:58:04 2014 : We have written 13088 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:03:05 2014 : We have written 13221 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:08:09 2014 : We have written 13357 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:13:12 2014 : We have written 13493 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:18:19 2014 : We have written 13629 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:23:26 2014 : We have written 13766 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:28:30 2014 : We have written 13902 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:33:38 2014 : We have written 14038 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:38:43 2014 : We have written 14175 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:43:47 2014 : We have written 14311 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:48:51 2014 : We have written 14447 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:53:59 2014 : We have written 14583 KB.
NDMP Log Message: DUMP: Fri Dec 12 18:59:06 2014 : We have written 14720 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:04:09 2014 : We have written 14856 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:09:14 2014 : We have written 14992 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:14:17 2014 : We have written 15128 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:19:24 2014 : We have written 15265 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:24:27 2014 : We have written 15401 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:29:33 2014 : We have written 15537 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:34:37 2014 : We have written 15673 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:39:38 2014 : We have written 15806 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:44:41 2014 : We have written 15942 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:49:46 2014 : We have written 16078 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:54:47 2014 : We have written 16211 KB.
NDMP Log Message: DUMP: Fri Dec 12 19:59:50 2014 : We have written 16347 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:04:54 2014 : We have written 16483 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:09:59 2014 : We have written 16619 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:15:06 2014 : We have written 16756 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:20:08 2014 : We have written 16892 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:25:15 2014 : We have written 17028 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:30:18 2014 : We have written 17164 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:35:26 2014 : We have written 17301 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:40:27 2014 : We have written 17437 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:45:35 2014 : We have written 17573 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:50:39 2014 : We have written 17709 KB.
NDMP Log Message: DUMP: Fri Dec 12 20:55:39 2014 : We have written 17842 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:00:44 2014 : We have written 17978 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:05:49 2014 : We have written 18114 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:10:55 2014 : We have written 18250 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:16:03 2014 : We have written 18387 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:21:07 2014 : We have written 18523 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:26:14 2014 : We have written 18659 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:31:22 2014 : We have written 18796 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:36:26 2014 : We have written 18932 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:41:30 2014 : We have written 19068 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:46:38 2014 : We have written 19204 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:51:44 2014 : We have written 19341 KB.
NDMP Log Message: DUMP: Fri Dec 12 21:56:46 2014 : We have written 19477 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:01:54 2014 : We have written 19613 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:06:58 2014 : We have written 19749 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:12:05 2014 : We have written 19886 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:17:13 2014 : We have written 20022 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:22:17 2014 : We have written 20158 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:27:21 2014 : We have written 20294 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:32:22 2014 : We have written 20427 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:37:26 2014 : We have written 20563 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:42:30 2014 : We have written 20699 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:47:30 2014 : We have written 20832 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:52:34 2014 : We have written 20968 KB.
NDMP Log Message: DUMP: Fri Dec 12 22:57:39 2014 : We have written 21104 KB.
NDMP Log Message: DUMP: job aborted by NDMP
NDMP Log Message: DUMP: DUMP IS ABORTED
NDMP Log Message: DUMP: Deleting "/vol/VMWare_VHD_Datastores_3/../snapshot_for_backup.52431" snapshot.
NDMP Log Message: DATA: Backup terminated (for /vol/VMWare_VHD_Datastores_3).
NDMP Data Halted: Aborted
NDMP Log Message: Mover encountered internal socket error.
NDMP Mover Halted: Internal Error

================  NDMP ENVIRONMENT  ================
BASE_DATE=-1
PATHNAME_SEPARATOR=/
NDMP_VERSION=4
DATA_BLOCK_SIZE=64
HIST=Y
NO_ACLS=N
UPDATE=Y
DUMP_DATE=-1
LEVEL=0
FILESYSTEM=/vol/VMWare_VHD_Datastores_3
===============  NDMP ENVIRONMENT END  ===============

And a successful back up it writes a lot of data every 5 Mins and completes in 14hrs

NDMP Log Message: DUMP: creating "/vol/VMWare_VHD_Datastores_3/../snapshot_for_backup.62249" snapshot.
NDMP Log Message: DUMP: Using Full Volume Dump
NDMP Log Message: DUMP: Date of this level 0 dump: Fri Dec 26 10:16:57 2014.
NDMP Log Message: DUMP: Date of last level 0 dump: the epoch.
NDMP Log Message: DUMP: Dumping /vol/VMWare_VHD_Datastores_3 to NDMP connection
NDMP Log Message: DUMP: mapping (Pass I)[regular files]
NDMP Log Message: DUMP: mapping (Pass II)[directories]
NDMP Log Message: DUMP: estimated 633249236 KB.
NDMP Log Message: DUMP: dumping (Pass III) [directories]
NDMP Log Message: DUMP: dumping (Pass IV) [regular files]
NDMP Log Message: DUMP: Fri Dec 26 10:22:46 2014 : We have written 17134002 KB.
NDMP Log Message: DUMP: Fri Dec 26 10:27:46 2014 : We have written 35195485 KB.
NDMP Log Message: DUMP: Fri Dec 26 10:32:46 2014 : We have written 55623975 KB.
NDMP Log Message: DUMP: Fri Dec 26 10:37:46 2014 : We have written 74222742 KB.
NDMP Log Message: DUMP: Fri Dec 26 10:42:46 2014 : We have written 91114178 KB.
NDMP Log Message: DUMP: Fri Dec 26 10:47:46 2014 : We have written 110177674 KB.
NDMP Log Message: DUMP: Fri Dec 26 10:52:46 2014 : We have written 127397239 KB.
NDMP Log Message: DUMP: Fri Dec 26 10:57:46 2014 : We have written 144357555 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:02:46 2014 : We have written 165400097 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:07:46 2014 : We have written 182318554 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:12:46 2014 : We have written 197248170 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:17:46 2014 : We have written 213217548 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:22:46 2014 : We have written 232916506 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:27:46 2014 : We have written 251085611 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:32:47 2014 : We have written 270700375 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:37:47 2014 : We have written 288223986 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:42:47 2014 : We have written 306096148 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:47:47 2014 : We have written 322593407 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:52:47 2014 : We have written 338163558 KB.
NDMP Log Message: DUMP: Fri Dec 26 11:57:47 2014 : We have written 355240342 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:02:47 2014 : We have written 373542427 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:07:47 2014 : We have written 390758318 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:12:47 2014 : We have written 408288311 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:17:47 2014 : We have written 429518840 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:22:47 2014 : We have written 450956986 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:27:47 2014 : We have written 472913799 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:32:47 2014 : We have written 495918302 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:37:47 2014 : We have written 516109040 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:42:47 2014 : We have written 537708298 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:47:47 2014 : We have written 560321037 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:52:47 2014 : We have written 580289213 KB.
NDMP Log Message: DUMP: Fri Dec 26 12:57:47 2014 : We have written 597857628 KB.
NDMP Log Message: DUMP: Fri Dec 26 13:02:47 2014 : We have written 620910497 KB.
NDMP Log Message: ENHANCED_DAR_ENABLED is 'T'
NDMP Log Message: ACL_START is '645910372352'
NDMP Log Message: DUMP: dumping (Pass V) [ACLs]
NDMP Log Message: DUMP: 630771855 KB
NDMP Log Message: DUMP: DUMP IS DONE
NDMP Log Message: DUMP: Deleting "/vol/VMWare_VHD_Datastores_3/../snapshot_for_backup.62249" snapshot.
NDMP Log Message: Mover: Data connection closed by foreign host.
NDMP Data Halted: Succesful
NDMP Mover Halted: Connect Closed

================  NDMP ENVIRONMENT  ================
ACL_START=645910372352
ENHANCED_DAR_ENABLED=T
BASE_DATE=-1
PATHNAME_SEPARATOR=/
NDMP_VERSION=4
DATA_BLOCK_SIZE=64
HIST=Y
NO_ACLS=N
UPDATE=Y
DUMP_DATE=-1
LEVEL=0
FILESYSTEM=/vol/VMWare_VHD_Datastores_3
===============  NDMP ENVIRONMENT END  ===============

Issue happens randomly on our netapp NDMP backups any ideas as to how to solve this issue

Hello everyone,

I have a Windows 2008 R2 server that is virtualized. I am trying to install BE 2012 remote agent on it from another virtualized Windows 2008 R2 server. The push agent pushes the installation down but never completes the installation. If I go to the server I am trying to install the remote agent on, I can find the RAWSX64 folder. I try running the installation manually, the installation goes fine until the actual install occurs. It will just sit at "Symantec Backup Agent for Windows" and the estimated install time is 3 minutes. The progress bar never moves. I've let it sit overnight, and no progress is ever made. I have to kill the installation. I have included a picture of the screen it is sitting at. One more little note, the BE 2012 remote agent was instlaled on this server, but it stopped working, so I uninstalled. Now, this is where I am when trying to reinstall. Anybody ever have this issue? Any help would be greatly appreciated.

Thanks!

Ken

Hi,

I am using BE2012 to make daily SDR backup for file server. This server is running as VM guest.

I want to know how to use SDR recovery disc to recovery this VM guest.

Thanks !

Hi all,

We are implementing BE2014 SP1 at our customer site and it seems running smooth in past month. Now I want to modify job for live run yet it hangs

( any tasks related to job such as create, edit will hang on the first screen it prompted out)

here is detailed message it displayed:

An error with the Backup Exec administration console has occurred.  The administration console will close when you click OK. To restart the console, click the Backup Exec icon or click Start > All Programs > Symantec Backup Exec.

Culture is not supported.
Parameter name: culture
15369 (0x3c09) is an invalid culture identifier.
at System.Globalization.CultureData.GetCultureData(Int32 culture, Boolean bUseUserOverride)
   at System.Globalization.CultureInfo.InitializeFromCultureId(Int32 culture, Boolean useUserOverride)
   at System.Windows.Input.InputLanguageSource.get_CurrentInputLanguage()
   at System.Windows.Input.InputLanguageManager.get_CurrentInputLanguage()
   at System.Windows.Documents.TextSelection.EnsureCaret(Boolean isBlinkEnabled, Boolean isSelectionActive, CaretScrollMethod scrollMethod)
   at System.Windows.Documents.TextSelection.System.Windows.Documents.ITextSelection.UpdateCaretAndHighlight()
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.KeyboardDevice.ChangeFocus(DependencyObject focus, Int32 timestamp)
   at System.Windows.Input.KeyboardDevice.Focus(DependencyObject focus, Boolean askOld, Boolean askNew, Boolean forceToNullIfFailed)
   at System.Windows.Input.KeyboardDevice.Focus(IInputElement element)
   at System.Windows.UIElement.Focus()
   at System.Windows.Input.KeyboardNavigation.Navigate(DependencyObject currentElement, TraversalRequest request, ModifierKeys modifierKeys, DependencyObject firstElement)
   at System.Windows.Input.KeyboardNavigation.Navigate(DependencyObject currentElement, TraversalRequest request)
   at Symantec.HRO.UI.WPFFramework.DialogContentControl.<DialogContentControl_Loaded>b__0()
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

I tried:

- repair DB

- repair program

- uninstall options and add it back

- reboot system

but no luck.

I don't wish update to SP2 now since update of agents is needed  (need take down time for reboot, if necessary) and no warranty the problem can be solved after update. useful suggestion/experience is appreciated. Thanks in advance.

Regards,

Thomas

Hello,

on an SBS2011 with BE 2012 SP4 + Hotfix RDX cartrigdes are not being used/ overwritten. BE shows under device information, that it needs more memory. The RDX cartridge is empty (formatted) and about twice as large as the size of the data to back up. BE is able to write on the catridges because it creates the folder veritas\b2d with the Changer.cfg and the Folder.cfg in it.

What did I do to this point:

-manually removed remaining IMG folders and even formatted the cartridges

-restartet the BE services

-created a seperate backup job to backup a small text file

-checked the credentials

-removed all media from the Backup Exec- and Windows NT-Backup media sets

What is to do next? Any help is appreciated.

hello dear,

Cannot push or otherwise communicate with Backup Exec 2014 Remote Agent for Windows. Receive error: 0xe00086ce - Backup exec cannot connect to the remote computer.

i have disabled firewall
network connection is now ok
i can re-add the server
but when i try to push the agent. i get those errors

I need your support, thank you.

We had this working fine under BE 2010, but now that we're on BE 2014, I think things have changed for the worse.

I have a backup job that I want to be available to run within a 24hr window. We *need* daily backups.  For this particular server, we need to lock some files to get a consistent state backup - but we can't keep the files locked for too long.  We have a pre-job to lock, and a post-job to unlock. No problem.

Here's the catch - I want the backup job to cancel if it runs longer than 4 hours from whenever it actually started. (not from when it was scheduled)

Under the job's schedule section, there's an option to cancel the job - but the minimum time is the reschedule time plus 1 hour.  I don't want that.  I want the job to run for sure today, but only for up to 4 hours from the actual start time.

Is there a way to do this with BE 2014?

In a week I plan to convert a physical Windows Small Business Server 2008 (SBS2008) to a virtual machine. Hyper-V with one guest is installed on this SBS2008 machine and its also the primary Backup Excec 2014 server.

The plan is to install Hyper-V Core 2012 R2 to the physical machine and run the SBS2008 server and the other guest on Hyper-V Core to take advantage of the ram thats installed on this server. The server has 60GB ram installed. Windows Small Business Server limits Ram to 32GB. Hyper-V Core has a 1TB Ram limit.

The problem im running into is this is the only Hyper-V machine on the network and the Convert to Virtual option in Backup Excec 2014 is greyed out so I cannot use Backup Exec 2014 to convert this SBS2008 machine to a virtual.

I have a daily backup that the Simplified Disaster Recovery is not enabled on so when I called Symantec they said I needed to complete a one time backup with it enabled to activate the convert to virtual. This didnt make alot of sense as the option to backup and convert to virtual was disabled but I did it anyways and after the one time bakcup completed with SDR green I still cannot convert to virtual.

Does anyone have any suggestions? 

Hello,

We recently added an additional BE 2014 media server along with the Enterprise Server Option for CASO to backup servers that have been moved to our off-site location.  Most of our backups are done to disk, but once a month we have some month-end backups that go to tape.  The problem is that the tape library is connected to the media server in our main location, but one of the databases that we backup at ME is in the off-site location.  So, how can I backup the database on one media server, then move it to a tape drive connected to another media server?  The original suggestion I had was to set up the tape library as a private cloud backup device, but it wouldn't let me do this with a tape library.  This is what I'm working with:

Location A
Database to be backed up
BE 2014 Media Server A
Storage device used:  Network share A on local EMC DataDomain 620 (deduplicated and synched to a share at location B)

Location B
BE 2014 Media Server B
Storage devices used:  Synched share on local EMC DataDomain 620 (from network share A at location A), direct attached LTO5 tape library

The locations are connected by a 50 Mbps eline connection - this can be temporarily bumped up as high as 150 Mbps on-demand if needed.  Ultimately what we want to do is back up the database at location A to tape at location B.  However, we stop the database to do an offline backup for month-end, so I wanted to do the initial backup to local storage first so that the database isn't down while moving the backup between locations.  Anyone have any ideas on how we could do this?

Thanks...  Mike

Olá pessoal meu backupexec 2010 R3 ficou doido, ele não executa nenhuma ação, todas as tarefas que eu crio ele não executa e coloca em agendada.

Desinstalei tudo e reinstalei e nada, sempre esta ficando em agendada, mando executa e nada.

O que pode ser?

New install of Backup Exec 2014 on a Windows 2012R2 server.  I've installed the main license and all the agent licenses we've purchased and wanting to push the agents out to servers.  In the License Information screen of Backup Exec, I see "Agent for Applications and Databases" with 3 licenses, I also see "Agent for Windows".  These are correct.  When I goto install agents on the other servers, I add the server I want then when it asks what product to install, I only see "Agent for Windows" and "Symantec Backup Exec".  I'm wanting to install a SQ:L agent and an Exchange agent to their respective servers, but I don't see the "Agent for Applications and Databases" listed.  What gives?  I've rebooted the server and restarted services and this is consistent.  Am I reading this wrong?  Thanks.

Hello,

I am using the Trial of Backup Exec 2012 and i'm finding that its organizational properties are not what I am looking for. I am looking to confirm if Backup Exec 2012 can be configured to create a sub-directory or "folder" with the name of the date it was created as the folder name. Once the folder is created can the backup files for a job be generated in this created sub-directory or "folder". So each Backup generated is placed in its own folder with the date it was generated as the folder name.

Currently Backup Exec 2012 creates all backup files for all jobs in one directory called BEData.

Thanks for anyone willing to share.

Hello,

I have a colo site that will contain DR equipment. We have an audit process that requires us to POC the site before deployment. I am currently attempting to restore MY Primary Domain Controller by following the instructions listed here.

http://www.symantec.com/business/support/index?page=content&id=TECH83015&actp=search&viewlocale=en_US&searchid=1288726274344

I'm having some issues. After I create the new recovery server with the same hardware specs as my old Primary DC. I run the restore job with the settings detailed in the above post within BUE 2012 the restore job completes succesffuly, then in the instructions it says just reboot the server. I do that and all I get is my same old recovery server with a few new folders added to it. I know I'm missing something in the instructions so my questions are,

On the recovered server do I need to add the Active Directory sites and Services role before I do the BUE restore job?

Why can't the server just restore to the exact state it was in from the backup I have, in my mind it would just reboot and then be my PDC with the new name, and login information and whatever basically a clone of my recovered server?

Should I just do SDR?

Do I have to do SDR to get the results I'm after ie.. just an exact replica of my old Primary Doman Controller?

Any help would be greatly appreciated. I'm just looking to udnerstand what I'm missing.

Currently, we are using Symantec Backup Exec 2014 to backup 12TB of server data to an on-site host with SAN storage, doing weekly full backups and daily incremental backups. We have our own remote site with a high-speed broadband connection that we want to use to host our off-site storage.

What is the recommended configuration for BE2014 to backup off-site?  Do I need to mess with CASO, or can I just set up storage at a remote site and have the the backup duplicate to the off-site storage?  

Can some one please help? I had a machine crash and I'm trying to restore data from a backup that was created in BE 2012. I put the tape in another server running BE 2012 and inventoried and cataloged the tape. Since the original server is dead, I select restore to a different location and select a local drive on the current machine running BE 2012. Upon running the job I get a credential error. Can some one please assist?

Thanks

Hi All,

I need to configure NDMP backup on my backup exec to backup my Netapp, and i have tape library, and i have been reading the NDMP document and i have come across the statemement from Backup exec Admin Doc Page No:- 1787

" To configure Backup Exec to use theNDMPoption, you must add theNDMPserver
to Backup Exec. If any storage devices are attached to the NDMP server, Backup
Exec discovers them automatically after the services are restarted, and then adds
them to the list of devices." 

This means i need to connect my tape autoloader only to my Netapp Storage , No need to zone it to my media server ? So as soon as i add my NDMP Device and restart my Backup exec Services my Tape drive attached to my Netapp will be added to device list , Later which i can choose this device to perform backup ? Am i right to say this ? May i know how this communication happens ? 

Also Can help me to understand backup exec actually performs an Incremental Backup using NDMP ? My understanding from Netbackup is that we cannot have an incremental backup because NDMP backup always dumps the whole volume/qtree of netbackup on to tapes but i doesn's perform an incremental. 

Any Document or white Paper would be a great help.

Thanks,

Nayab