Good Day,

I just want to know/ask if the issue of slow running backup on a DFS server was already resolved on Backup Exec 2012. As I back read some threads, there are issues of slow running backup on version 12.5 and 2010. Or if you can give me some guide or article as a supporting document. Thanks

I'd like to understand GRT.  According to the Backup)Exec_2012_Agent_for_VMware_TechnicalFeatrue_Brief.pdf, it states:

it is not necessary to have the Agent for Windows Servers (AWS) installed to the vm in order for granular files and folder recovery to be possible.  However, having the agent installed to the virtual machine is required in order to recover files and folders directly back to the source virtual machine.

Optionally, or if the AWS agent is not installed to the original machine from which backups were captured, files and folders can be reovered to a local directory on the Backup Exec server, and moved back to the original virtual machine using other methods.

I don't see how this works.  I have the Agent for VMware installed and I've enabled GRT on a VM (but not selected any of the 4 GRT features that you require the agent for applications).  This VM does not have the AWS installed.  When I try to restore, I see no option to resote individual files/folders.  From everything else I've read, it seems that the AWS has to be installed on the VM in order to use GRT.  So what's the story?  Is the techincal feature brief incorrect??  Under waht circumstances can you utilise GRT without the AWS installed on the VM?

I also saw in another post that you can install as many AWS agents on VM's if you have the Agent for VMware licensed installe on the host.  is this true?

Thanks in advance!

I'm have backing up Exchange 2010 for the last (2) years using the same Symantec configuration with no errors, but tonight's backups are failing with the following errors:

"Final error: 0xe0008516 - Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.
Final error category: System Errors" 

Backup- C380MB1

V-79-57344-34070 - AOFO: Initialization failure on: "Microsoft Information Store". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE0008516): Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.

Check the Windows Event Viewer for details.

Backup- C380MB2

V-79-57344-34070 - AOFO: Initialization failure on: "Microsoft Information Store". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE0008516): Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.

Check the Windows Event Viewer for details.

V-79-57344-34070 - AOFO: Initialization failure on: "Microsoft Information Store". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE0008516): Resources specified for snapshot do not have any valid data on them. Check if files were deleted or renamed.

Check the Windows Event Viewer for details

I check both of the writers on the Exchange server and the backup server and there are no errors being reported.  I also un-installed the remote Agent and the backup job is still failing.  Does anyone have any other suggestions besides re-booting the Exchange server?

Thanks,

Hello,

my problem is, that the Linux Agent for BE2012 is not supported on SLES11 SP3.

Workarounds like patching the agent manually is not allowed in our systems.

Hints to buy other Symantec products are not very useful, because we have paid for BE2012 and many agents, also for the support of this products.

When Symantec is not able to support our landscape anymore, then our management will decide that we have to change our complete backup-infrastructure (and so the infrastructure of our customers too).

So please understand me. To just close a thread with the "solution" to use another product is not the way to get satisfied customers.

So when Symantec don't want to support Linux Kernel 3.0 anymore for the BE2012 Linux Agent, then just declare this and I have to search for another product.

Best regards,

Andreas

I want to create a media set that has no append, currently the lowest append period is 1 hour which means that it is almost impossible to introduce new tapes to an autoloader whilst jobs may want to append to a tape that is already in there.

Previous version at our site was BE 2010 and we could then put in 0 hours.

Help please 

Hello,

My environment is quickly moving forward wiith Linux kernel updates and BE2012 is not following soon enough!

The current SCL shows compatibility up to Oracle Linux 6.1. Oracle is already relesing OL6.5. I have tested with the higher kernel and BE2012 will not work.

I am running BE2012 SP3 on a Windows 2008 R2 server.

Does anyone at Symantec have a clue as to when the compatibility will be updated.

My planned production environment will be Oracle Linux 6.3 with the kernel level - 2.6.39-200.24.1.el6uek.x86_64

Thanks

Michele

Hi guys,

We currently run back-up Exec 2012 to run a full tape back-up of a couple of our servers each night. The problem we have at present however is that the job takes around 12 hours am some times is still running when users arrive the next day.

Iv'e considered changing the back-ups to incremental/ differential, however I believe a full back-up each night is still the best approach for our business.

Quite abit of our data has not been accessed for some time, so one idea I have had is to decrease the time a full back-up takes, by only backing-up data accessed within a certain time period, but my question is - is there a better way of decreasing the time a full back-up takes? If not, what's the best way to archive off old data from a file server?

Kind regards

Hello guys,

I'm new in this forum and hope you can help me with my problem.

I've problems with a library in BE 2010 R3 running at Win 2008 r2 x64.
The state of the library is flapping very fast to "In use" and back. Funny thing is that there are no jobs (e.g. Backup, Inventory,...) that might use the library.

I've already restartet the BE services but this doesn't resolved my problem.

BR, Florian

Hi People,

i am just have a Exchange Informationstore Backup which is not longer running since 23.02.2014.

We havent changed on that weekend anything. The job was running one day bevor without any problems.

Environment:
Backup Exec 2012 V14 1798.1300 on Windows 2008 R2 SP1
Exchange 2013 Version 15.0 ?(Build 712.22) on Windows 2012

there is also running a Backup via Acronis without any Problems. (Before and after the 23.02.2014)

On the 23.02.2014 the Log of the Backup Exec shows the following errors:
 - Snapshot: Initialisierungsfehler auf: "Microsoft Information Store". Snapshot: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11235 - VSS Snapshot-Fehler. Microsoft Volume Shadow Copy Service (VSS) kann keine Verbindung mit den Writers herstellen. Überprüfen Sie, ob Volume Shadow Copy Service gestartet wurde und ob in der Windows Ereignisanzeige diesen Dienst betreffende Fehler vorliegen.

 - Snapshot: Initialisierungsfehler auf: "Microsoft Information Store". Snapshot: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11235 - VSS Snapshot-Fehler. Microsoft Volume Shadow Copy Service (VSS) kann keine Verbindung mit den Writers herstellen. Überprüfen Sie, ob Volume Shadow Copy Service gestartet wurde und ob in der Windows Ereignisanzeige diesen Dienst betreffende Fehler vorliegen.

Sichern - Snapshot: Initialisierungsfehler auf: "System?State". Snapshot: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11235 - VSS Snapshot-Fehler. Microsoft Volume Shadow Copy Service (VSS) kann keine Verbindung mit den Writers herstellen. Überprüfen Sie, ob Volume Shadow Copy Service gestartet wurde und ob in der Windows Ereignisanzeige diesen Dienst betreffende Fehler vorliegen.

Ive restarted the whole VSS Services, but it doesnt helped. Also a reboto of the whole server brings a solution.

Ive excluded now the Backup from the Information Store from the normal Backup and made for the Informationstore Backup another job.

The GRT Options are not enabled on that job. Ive tried also the InfoStore Backup without the AOFO Options without any result.

At the moment i get the following errors:
V-79-57344-34070 - Snapshot: Initialisierungsfehler auf: "Microsoft Information Store". Snapshot: Microsoft Volume Shadow Copy Service (VSS).

I hope anyone can help me to find a solution.

Hi People,

we added to our Backup Exec 2012 a Tandberg Storageloader 1U Autoloader with a HP Ultrium 5 SCSI Drive. The loader appears under Windows as Tandberg Data StorageLoader\StorageLibrary without any sign of a problem.
In BackupExec 2012 apears only the Drive and not the loader with his 8 slots. But without the detect of the slots and the loader we cant configure the Backup to tape.
I am just testet to move a tape into the drive and running a inventory job. If i do this Backup Exec find the tape in the drive. If i move the tape back to the slot the tape disappear in the drive under Backup exec.
Under the tape details, in backup Exec, is shown the right drive.
Backup Exec is installed on a Windows 2012 R1 SP1 Server.

So why doenst appear the loader and the slots in Backup Exec?

I recently faced having to try to restore the contents of a failed server to another machine and came up against a problem.

The replacement hardware was completely different from the original server so I set the new one up with a plain installation of Windows Server 2003 and intended to do a redirected restore of the files from our failed machine onto the new one.

I couldn't get the Media Server to "see" the machine I was trying to redirect to, even though it was available on our network, and after putting the full path of where I wanted the files to go and setting the restore running I got an error saying that the job had failed because there was no Remote Agent on the destination machine.

Are we expected to buy an extra Remote Agent licence in case of a disaster recovery situation, which all being well will never be used? Was there something else going on that caused the problem? I didn't want to back up the new machine or use BackupExec on it, just copy the files across to it as an emergency measure, so I didn't expect to need an extra Agent.

Hello all, I am having difficulty restoring the Single Instance Storage componants.

We have CASO, where the jobs were created. BE2012R2 / W2K3R2.

We are restoring to a W2K8R2 Cluster server.

The strange thing is, all our standard file backups and restores are running at 3GB/s, but as soon as we select the hidden componants of SIS to restore we get 1MB/s (16MB in 15hrs) - we have 600Gb to restore(!)

The other odd thing I noticed, was that if we select the files only, then its slow, but if I select the files and the SIS store, then the NIC reports 100%. But the server that it is restoring to is at 20% utilisation on the NIC. Both 1GB NICS in to a 10GB switch. (TCPIP Offloading disabled)

So, I have been reading articles from MS and Sym and cant really find any good docs about it. A lot of people (independant forums) say that it is problematic, and I have even found one that suggests it will run at a 3rd of the speed of any other jobs.

Anyone out there with any experince of this, PLEASE let me know as I am struggling.

Good morning.

 I'm looking for istructions/documents about response files to automate VRTSralus installation on RedHat 6. Ralus installer seems to provide sorts of automated installation options but I'm not able to find any reference about it on BE2012 Admin guide.

 Mainly, I'm looking for info about "-pkgpath " and "-responsefile" switches.

[root@repo ralus]# ./installralus --help

Usage: installralus [ <system1> <system2>... ]
        [ -installonly ]
        [ -configure ]
        [ -responsefile <response_file> ]        [ -forcelocal ]
        [ -logdir <log-and-response-file-directory> ]
        [ -pkgpath <pkg_path> ]        [ -logfile <log-file-location-and-name> ]
        [ -tmppath <tmp_path> ]
        [ -usessh ]
        [ -hostspace <hostname>:/<larger_volume> ]

The -installonly option is used to install product packages on systems without configuration.
The -configure option is used to configure a product following use of the -installonly option.
The -responsefile option is used to perform an automated installations which install and configure using information stored in a file rather than prompting for information. <response_file> is the full path of the file which contains configuration information.
The -logdir option permits specification of a particular directory where VxIF is to place the log and response files.  For example: -logdir /tmp/log
The -pkgpath option is used to eliminate the step of copying packages to each system.  <pkg_path> is the complete path of a directory, usually NFS mounted, which contains all packages to be installed by installralus on all systems.
The -logfile option permits the designation of the name and location of the file to contain the log file.  For example: -logfile /tmp/stuff/install.log
The -tmppath option is used to select a directory other than /var/tmp/vxif as the working directory for installralus.  This destination is where initial logging is performed and where  are copied on remote systems before installation.
The -usessh option is used when ssh and scp are to be used for communication between systems instead of rsh and rcp. The -usessh option requires that systems be pre-configured such that ssh commands between systems execute without prompting for passwords or confirmations.
The -forcelocal option is used to install the software on the local machine only.
The -hostspace option provides specification of specific target volumes for extracting archives.  For example: -hostspace hostname:/larger_volume.

 Can someone help me?

Hi,

I have a back-up tape I have carried out numerous restores from on backup exec 11d. One day I ran inventory on the tape to another restore but when I tried to expand the folders to select the files I wanted to restore, the folders where empty. All the folders have a white circle with a ? in it. All the data is still on the disc and the tape is showing as not having been modified since the back-up was origninally done.Can you help me please?

Thanks,

Seamus

Can annybody advise me on what this error (from the BE job log) means?

Job ended: Thursday, March 06, 2014 at 8:41:45 PM
Completed status: Failed
Final error: 0xe0009425 - The Shadow Copy Components file system has been modified to contain only user-defined data, such as Backup Exec Deduplication Disk Storage (PDDE) and Distributed File System Replcation (DFSR).  All other operating system-related data is now incorporated into System State.  As a result, existing Shadow Copy Components file system backups and backup sets are incompatible with Backup Exec 2012.  You should edit the job, delete the Shadow Copy Components selection, and then run the job again.
Final error category: System Errors

For additional information regarding this error refer to link V-79-57344-37925

The message seems clear that I need to simply edit the job and deselect the Shadow Copy Components item in the list of checkboxes, which I did just now and am running the job again to see what happens.  It's backup to tape, and will take the whole day so I'll check tonight's job log. But what's confusing is what this actuall means? 

Just that I do not think I was getting this error a month  or more ago, and it was only within the past few weeks that I tried deduplication.  Is it possible that by creating and then deleting deduplication storage devices and jobs that I've put something into the selections list that's now stuck and gives this error?  Before now, the server was Fully Selected - everytihng checked - but I don't recall whether or not this Shadow Copy Components item existed or not. 

Thanks. 

We have a windows server 2008R2 box running SQL server hosted on a VMware box.  The server has 2 nics, one going to our main network the other is for iSCSI to the SAN which holds ONE of our databases.  We backup 5 other VMware servers ranging between 2003 and 2008, one being another SQL box.  Normal throughput on the servers is about gigabit speed.  For this particualr server we see 100MB.  As a test I tried to backup a database located on the local VMware guest, same speed, then tried to backup just some OS files, all tests show the same speed.  Both NICs are operating at GB speed.  Suggestions?  We are up to date on patches on the server and backup exec.  Backup exec is running on a physical server with an attached tape device. 

Ran into this error,

job failed with the following error: Database Query Failure

Wanted to know if you have seen this and any possible repairs?

Greetings, all!

I've had a BE11D/Windows 2003 32 bit server with an IBM LTO5 tape drive for 3 years now. Last Fall, I stopped getting backup reports. I discovered that the server was down but brought it back online quickly. Since then, nothing has been written to tape or even backed up by the system. I see the backup scans running but that's it. I have to kill these jobs as they seem to never end. I updated the Symantec drivers for my tape drive & can inventory the tapes, but BE11D does not write to it & does not backup. I checked the credentials & tested them, all passing.

Please let me know if you see anything I have missed or haven't tried!

Thanks!

David

Backup Exec 2010 R3 Service Pack 4 - Small Business Server Suite  (Media Server Version 13.0 Rev 5204 (32-bit).  Administration Consol Version 13.0 Rev 5204.1270 (32-bit) Desktop and Laptop Option Version 3.1 Rev 3.46.06a.  FIPS version - not enabled.

Server 2003 with a Quantum Ultrium 3 deck.

I'm trying to figure out why a client's backup job has stopped completing succesfully.  The size of the back up has grown steadily in the last few months mostly due to Exchange growth and the number of Quickbook backups they are keeping.  The jobs are failing indicating the backup window has expired.  The jobs typically complete in 2hrs, the windows is 6hrs.  After troubleshooting I find that the tapes are full.  I have done the following since making this determination.

- Checked overwrite and apend settings.  For purposes of trying to get successful backup I have set overwrite protection to none and apend to infinite.  The job is set to use hardware compression if available otherwise software.

- Did a quick erase, verified the tape was 'blank' and put the tape back into the correct media set.

- Ran a successful test job that shows the total byte count of 201,976,547,800 bytes or about 188GB. It further shows an Online overwrite capacity of 400,308.00MB or about 390GB which is what the physical tape shows under Devices. 

- I went through and deleted about 40GB of data to reduce the size of the backup job.

Ok.  So I ran a job last night.  The result - it failed.  I assume it was waiting for a second tape.  The tape is now full showing used capacity is 389.7 GB of 390.9 GB available.  Ok. The tape is full.  However, byte count in the job monitor is showing a byte count of 183,392,700,450 bytes or about 170GB.   In my job history I have successful jobs on a single tape that were 246,688,635,872 bytes or about 229GB.  

So I expect with compression to have the ability to backup ~300GB of data.  Yet my blank tape is full at 390GB but I have a byte count of 170GB.   I know I'm missing something here but I can't figure it out - never had a BE problem in 15 years that I couldn't figure out myself.  I'm open to any suggestions.  Thanks.

Mike