Backing up SharePoint Resources
Hello Ladies and Gents Currently using Symantec Backup Exec 12.5. We also using Sharepoint 2003 on our Network. And having a problem backing up our sharepoint resources. Problem Unable to backup our sharepoint resources, have checked everytthing i am capable of checking, read through many articles still no solution. Have gone to tools and options, and checked the GRT for Ms Sharepoint this is ticked, looked within the poilcy for the job and GRT is checked. Also checked via Backup Tab and new backup job, tried to right click on the sharepoint resoures and slected add new server farm, entered the details of my server farm wla-eportal1 came up with message saying "None of the Web Servers for the specified server farm could be accessed" Tried to google this and went through the article this was not really any help, mentioned about checking Internet Explorer and tool - options, and click the advanced tab, and unchecking the verify publishers certificate, still no joy there. Not sure if i have missed anything out really. Have gone into remote session, and checked the Sharepoint Central Administration page, and all seems fine, are assicoaited as web servers. Have checked our license information all agents are installed, such as SQL and sharepoint. The GRT works for exchnage which embale me to slect individual email but not sharepoint anyt adive would be greatly appreciated. Kind Regards Tashfeen Khan
Se hace el backup pero no finaliza
Estimados tengo un problema con un backup, lo ejecuta pero nucna termina se queda por horas y horas y tengo que darle finalizar para que termine y sale el sgte. error Error category : Job ErrorsError : e0008821 - Job was recovered as a result of Backup Exec RPC service starting. No user action is required. For additional information regarding this error refer to link V-79-57344-34849
How to Protect Backup Exec itself?
We know Backup Exec can protect software and data. But the question is when we backup everything with Backup Exec, How we can trust this software and rely everything on it? I mean what is the solution for protecting Backup Exec from failures, crashing, loss of data, loss of catalogs and Database currupt? Shall we take backup from Backup Exec again manualy or with other Backup Exec or some other Backup software installation? Suppose you backuped everything and your Backup Exec software is corrupted for some reason which cannot be used to reach your backup data and restore them! This whould be a complete disaster!!! Anybody has information about it?
Device Error
Hello, I started my back-up job today. After around 3 hours this error popped up Event id: 34113 Backup Exec Alert: Job Failed (Server: ''Communited03'') (Job: "Dagelijkse Backup") Dagelijkse backup -- The job failed with the following error: The device cannot be found. For more information Click the following link: http://eventlookup.veritas.com/eventlookup/eventlookup.jhtml I've tried a diffrend tape but that didn't seems to work. Same error occured. Is there a problem with my back-up unit, Is it my software? Kind regards, Tim Ververs
Threat from internal - unauthorized changes to back up jobs/applications or configuration.
I consider this to be an extremely high priority. I am having an issue where Ihave found that back up jobs have been changed by: 1)throughremoving the "on hold" jobs and putting them back into scheduled jobs. -----This created an overlap and caused preexisting jobs to fail as the start up times were the same. 2) The device location on a job was changed to a different device that was not to be selected. 3) Some back up jobs have been created without the normal administrators knowledge. I cannot (under the current configurations) protect myself should any other admin go in and make changes. This is a security issue to both the backup jobs themselves and to any Exchange/ exchange back up administrators. I would like to see the ability for Backup Exec to be able to report to an assigned administrator if: 1) A new device has been created - Include what user attempted or authorized the change. 2) A new backup job has been created - Include what user attempted or authorized the change. 3) A backup job has been put on hold or taken off hold - Include what user attempted or authorized the change. 3a) That a password be assigned to protect a backup job from being run when it on hold. As well that a notification be sent out when that job has been changed or an attempt to change it has happened. Include what user attempted or authorized the change. 4) If a backup device within a current job has been changed. such as time, files, saved locations ect. 5) Email notification if a backup log file has been manually deleted - which would include the log file. 6) Once a server has been configured for backups that any attempt to change the entire setup are logged and a notification is sent out. This could be either password protected once the settings are complete and tested. My support tech has a great idea! Subrata Ganguly; Technical Support Analyst suggested that Backup Exec be configured that each individual user be set up with their own account and password (regardless if there is only one admin account being used- this does happen in smaller organizations) The accounts could then be logged or audited for changes made. Does anyone else consider this to be a high priority for job protection(both your own and the backups you look after)? Is there anyone who has suggestions on the best way to protect these situations from occuring?
