Hallo,
ich kann von meinem Exchange 2010 Backup kein granular restore machen.
ich bekomme immer die Fehlermeldung:
V-79-57344-759 - Der Vorgang kann nicht abgeschlossen werden. Der folgende Fehler wurde beim Öffnen der Exchange-Datenbankdatei ausgegeben: '-515 The timestamp in the next log does not match the expected timestamp. '
Das Backup selbst läuft ohne Fehlermeldung.
ich verwende Backupexec 15 mit allen Updates
Kann mir wer helfen?
Hi,
I need to create the Simplified Disaster Recovery Disk on my SBS 2008 (SP2)
The Wizard tells me my System does not support ADK (Windows Assessment & Deployment Kit) although it is listet as compatible
So I downloaded the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 Update (https://www.microsoft.com/de-DE/download/details.aspx?id=39982) and installed it myself.
I selected the Deployment Tools and Windows PE but Symantec Backup Exec 2014 (14.1 Rec. 1786) still says it can't find the ADK
Is there something wrong with my Version of the ADK? I do not have another Server 2008R2 ready to create the Medium as the Wizard suggests
I have Windows Server 2008, Windows SharePoint Services (WSS) 3.0, and Backup Exec 15 with all updates installed. I used to have Backup Exec 2010. Since I upgraded to 15, I see that two of SharePoint databases SharedServices_DB and SharedServices_Search_DB are no longer grayed out under MSSQLSERVER while SharePoint resources SharedServices and Global Settings no longer show up under my Server Farm.
Dear good morning, I wish to consultation regarding the credentials that backup is made to Linux servers as Red Hat Enterprise V6.0, you can support another account other than ROOT, please help me with this issue I have a customer that due audit your windows administrator credentials and Linux ROOT change every three months, and the client asks me to work with other non-root account on Linux. for authentication and backup and restore on Linux server.
thank them their suggestion, thanks.
Job ended: lunes, 28 de septiembre de 2015 at 11:00:47 a.m. Completed status: Failed Final error: 0xe0009b63 - The logon account is either expired or deleted or uses an expired password. Change the account's expiration date, check if user exists or not, reset the password, or choose another logon account that has the appropriate privileges for the selected resource. Final error category: Security Errors For additional information regarding this error refer to link V-79-57344-39779
Hello,
I'm new to using Backup Exec, specificly we have ver. 2010. My question is after swapping tapes do I need to do an import?
The steps I've done so far are.
1. Unlock tape dirve
2. Removed full tapes
3. Put in new tapes.
4. Lock tape drive
5. Do an inventory
6. Put new tapes into scratch.
Is there a step I have missed? Do I need to import the tapes?
Thank you
Does this error always indicate a hardware error of some type?
Hi,
I am new to backup exec 15 and currently on a trial.
I did a test job with backup to disk then duplicate to tape.
Everything seems to work fine, verify part succeeded, duplicate job succeeded, and I can restore data from tape and disk.
I am wondering why I see a different byte count for the backup to disk job and the duplicate to tape job.
For example, the backup to disk job has a byte count of 19.5 GB
And the duplicate to tape job has a byte count of 13.5 GB
Is that normal behavior and if so, what is causing this 6gb difference is quite major.
Regards
I found this article:
https://www-secure.symantec.com/connect/forums/wha...
but was wondering if there was anything else to it.
I notice that there is no longer a "copy" function (or i missed it). You used to be able to do a full backup "copy" mode where it ignored the archive bit - the "copy" backup backed everything up regardless of bit, it ignored it on backing up, and it didnt flip it once the file was copied. I don't see that option anymore.
Is there any difference between the two methods, other than described in that linked article?
I'm inclined to continue using the archive bit as the one sentence from the link has me a little squeamish about using "Modified Date":
"In case of files which are renamed, copied or whose attributes are changed, currently, you need to add these files manually in the backup job."
maybe the archive bit ALSO isn't flipped for these procedures, but i think i'll still just use the archive bit.
any thoughts or opinions?
Hi everyone,
I have Backup Exec 15 (v14.2) with Feature Pack 1 and Hotfix 232086 installed. I'm getting constant ODBC access errors - Event ID 34326 and 34338:
Backup Exec Alert: Catalog Error
(Server: "BE2012") ODBC access error. Possible lost connection to database or unsuccessful access to catalog index in the database.
Access to catalog index (Catalog index database) failed.
Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK_CatDlmProcessedImage'. Cannot insert duplicate key in object 'dbo.CatDlmProcessedImage'. The duplicate key value is (BE2012). CCatRecordSet::Open
r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(1889)
{CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)}
Access to catalog index (Catalog index database) failed.
Reason: [Microsoft][ODBC Driver Manager] Function sequence error CCatRecordSet::GetRecordCount
r:\maldives\1180r\becat\segodbc\seg_odbc.cpp(3629)
{CALL CATDLM_New_GetExpirableMedia(?,?,?,?,?,?,?)}
I tried to rebuild the catalog index with catrebuildindex -r , but it does not seems to help at all.
Do you have any solution / hotfix for these errors?
Regards!
Hello everyone,
I'm currently running Backup Exec 2015 and I'm backing up 43 VM's, devided over 1 vCenter and 3 ESXi hosts. I'm connecting to the vCenter server in order to get full VM backups - which is the preferred method for this company.
The problem is, if I add or remove VM's, Backup Exec will throw out warnings. The list is not up-to-date, and the only way to retrieve a new up-to-date VM list is to manually log into Backup Exec and press the Refresh button (screenshot attached).
I'd like to automatically refresh the VM list before the backup job starts, is this possible somehow?
We have a Server 2012 standard running Backup Exec 2015. Last night I have been getting this error a lot. I've encountered this before but It just seems to vanish and clear itself on it own and backups return to normal.
What is the cause and what can be done to remedy the issue? I can still see all these files on the server but for some reasone BE can't find them or access them.
V-79-57344-41488 - Due to one or more errors in \\Server.local\D:, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore. Directory User Shares\userA\ was not found, or could not be accessed. None of the files or subdirectories contained within will be backed up. V-79-57344-33967 - The directory or file was not found, or could not be accessed.
hi
we are in the process of migrating BE license from an old server to a new server
do i have to remove the license from the old server and completely uninstall that BE from it in order to activate BE on the new server?
or can we still shave it installed and licensed for a failback operation if the migration didnt work pretty well ?
thanks
Can you point me to the location where I can download the SDR ISO for Backup Exec 2012?
Regards,
John
I have setup a large backup job, in BE15, to backup all VM's in my enivornment to disk storage, doing a weekly full and daily differential. The weekly full runs over the weeked and then starts a duplicate to tape(which takes around 3 days to complete).
During the backup to tape the backup task is unable to run the daily deduplication because it is waiting for the 'related' tape job to complete.
Is there any way of seperating the tape duplication job so that the daily differential can run whilst the tape job is completing?
Ideally I don't want to split the job into multiple jobs that can complete within a day.
I have a remote site which is not manned but requires regular backups. I am planning to implement a Backup Exec 2014 server with a deduplicate storage disk where I will run daily backups and then run a duplicate job to backup to a remote Backup Exec server over the WAN in our main office. This server (office server) will also have a deduplicate disk to where the backups will be replicated to and I will then run another duplicate job against that to tape.
I want to know if I can do this without the CASO option or is this a requirement for duplicating deduplicated backup sets? If anyone has any advice regarding this, Backup Exec versions, options, agents, etc that would be great and also any other advice generally related to this implementation.
Thanks
Chris
Hello,
I've 2 VMs running W2012r2 (DCSRV01 and DCSRV02) with Active Directories in a same forest.
Should I backup AD SystemState for both VM or just one is enough ?
Regards.
I have a Tandberg LTO6 autoloader & BE2012 that I support at one site, and an Overland LTO6 autoloader & BE15 at another. All tapes at both sites are bar-coded.
At the Tandberg/BE2012 site, when I rotate previously used, but now overwritable, tapes into the slots and do a Scan from BE, the tapes are shown with their correct labels and are recognized.
At the Overland/BE15 site, when I do the same thing, the tapes that I've just loaded show the correct Barcode and Media Label, and all other columns for that matter. But in the Description column, it shows "(Unknown media)". If I inventory those slots, (or just let BE choose those tapes for a backup) the "(Unknown media)" designation goes away.
There's no practical difference, so this is really just curiosity, but why are tapes at the Tandberg/BE2012 site recognized correctly, and those at the Overland/BE15 site "unknown" until I inventory or reuse them? Is it an Option setting? Difference between BE2012 and BE15 media management? Autoloader hardware difference?
Hello,
I am performing a test restore of a Windows 2012 R2 file server. It was backed up using Backup Exec 2014 with SP2 + hotfix 227745. The Backup Exec media server is also running Windows Server 2012 R2.
The file server was backed up using the BE agent running on the file server. It has a C: drive (OS), a D: drive (most of the file data) and an E: drive (more file data).
I am restoring to a test VM and booting the VM using a restore CD created on the Backup Exec media server above.
The CD boots fine, it sees my attached backup media hard drive and reads the simplified restore information file fine.
However, I get an error message at the partitioning disk step. The Backup Exec restore environment lists just the D: drive under the "Mismatched Volumes" list even though there is a drive large enough to hold the D: data.
In the Advanced Disk Configuration screen, I can partition and format the new volume that will hold the restored D: drive data. This works fine as long as I give this new empty drive some letter other than D:. But as soon as I change the drive letter to D:, I get a popup error message, "The minimum size required for this volume [D:] is : 8.59 TB." and I cannot continue.
The C: and E: drives are prepared for restore by Backup Exec fine. Just the D: drive has this problem.
D: is different in that it has Windows Server 2012 R2 file deduplication turned on on the original file server. This is supposed to be supported and I have plenty of room on the new disk that is the restore target even accounting for unduplication of restored data (as is described in the Backup Exec admin guide).
Has anyone seen this as well?
Thanks,
Tim Miller Dyck
Hello,
I receive an error every time I try to configure an Amazon S3 bucket as a storage device I get the error: BEMSDK Failure Code: A0009B23.
I am running on server 2012 R2, using Backup Exec 15 FP1.
I have gone through and installed the latest update that hot fixed this connection issue with S3. I have followed the how to doc for connecting S3 as a storage device. I have disabled the firewall to see if that was the issue. I created a user specified account in AWS to try accessing the S3 buckets. I tried my admin credentials as well and am still unable to connect, receiving the same error.
I have looked online as well as this forum to see if there is a solution but have found none. I am wondering if anyone has had the same problem and if so has come up with or found a solution.
Thank you!
Is there a logic what BE2010R3 uses when restoring data from a library.
We have a backup job that currently uses 12 tapes (slots 1 to 12), I've started a restore (90mb) and I can see the job status switching between queued/loading media which has now been running 2h:45m
I do have blank tapes in slots 13 to 23 but I'm wondering what's going on?
