Sushil_Sakhawal
Level 3
Joined 20 years ago
User Profile
User Widgets
Contributions
Re: Restore Exchange to new installation of Small Business Server
hi Stefan, It is not necessary to use the same account name and password which was used on the old server You can use use any account which has following rights : 1) domain admins 2) local administrator 3) exchange full administrator Also while restoring exchange following names should be same 1) organisation name 2) administrative group name 3) storage group name However it is not necessary if you are restoring exchnage onto a different forest. Please refer following technote on how to restore Exchange to different forest. "How to restore Exchange 2000 or 2003 to a recovery server in a different forest" http://support.veritas.com/docs/247985 Also refer following technote about restoring information store to different domain. "Restoring IS in different domain" http://support.veritas.com/docs/239613 Thanks NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.603Views0likes0CommentsRe: unable to allocate memory
hi Ivana, This error has been observed in certain Dell PowerEdge Servers. Please refer to the following solutions which may help in resolving this issue. 1) Try disabling the antivirus software on the machines and check the results. 2) The problem is observed related to the Dell Open Manager installed on the server. Try backup after uninstalling the Dell OpenManager. This may allow Backup Exec to access the hard disk. Reboot the server and start backup. 3) The error which you have mentioned also occurs due to SCSI misconfiguration in some cases. Please verify that proper SCSI ID's have been configured for the tape device or autoloader. ========== We also would recommend you to download and install the service pack 2 of Backup exec. Install the service pack 2 of Backup exec v9.1 using the following technotes: VERITAS Backup Exec (tm) 9.1 for Windows Servers revision 4691 - Service Pack 2 http://support.veritas.com/docs/275247 NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.348Views0likes0CommentsRe: Tape ejected and Loading Media is the status
hi bert, This issue seems to be related to the alerts from backup exec. ====> Make sure the option "Eject Media after job completes" is deselected. 1) When you click on "Backup", you get the backup job properties window. 2) In that window, on left side click on "Device and Media" option 3) On right side locate the option "Eject Media after job completes". 4) Uncheck this option. Because sometimes after backup job, the media may come out but the job remains in the loading state. ====> Check the alerts. 1) Click the alerts tabs on the navigation bar 2) Then click on active alerts link. 3) Check for pending alerts and respond to them. If these alerts are not responded, they can also create some issues like ejecting media. Or else you can try using "Backup" utility from system tools in windows on the same tape. check the results. Reply if you still have any queries regarding the issue. Thanks NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.468Views0likes0CommentsRe: Email notification
hi tmac01, Backup Exec provides four options to send job notification. 1) SMTP mail 2) MAPI mail 3) VIM mail 4) Pager As you dont have any mail servers in your organisation, you can use SMTP address of your ISP to redirect emails to your POP3 account provided by your ISP. You can use SMTP mail option in this case. Thanks NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.650Views0likes0CommentsRe: error everytime changing backup tape
hi chinh, It is a SCSI and tape device related issue. 1) You can read following Technote about resolving SCSI issues. http://support.veritas.com/docs/191158.htm 2) Check the microsoft link below for scsi device issues How to Troubleshoot Event 9 and Event 11 Error Messages http://support.microsoft.com/default.aspx?scid=kb;en-us;Q154690 Recommend updating firmware and drivers for scsi card and firmware for the drive About the second error "Error 1053: The service did not respond to the start or control request in a timely fashion" please go through following steps. Follow the steps mentioned in the following technote. http://support.veritas.com/docs/239610 You can also try setting the startup type of BE services to MANUAL NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.255Views0likes0CommentsRe: Scheduled job does not complete
hi robert, As i understand from your query that the job failed on friday because of some files in temp folder which are found corrupt. If you want to verify the tape, you can try doing following steps. 1) try running the same job on different Tape. OR 2) try running backup in windows native backup utility (NTBackup) on the suspected Tape. Also if the job is failing because of corrupt files you can try performing steps in the following Technote The Technote gives the exact path to create a registry key which will not fail job for corrupt files. http://support.veritas.com/docs/193940 please reply with the exact Error message in the log file so that we can look for resolution of the issue as soon as possible. NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.109Views0likes0CommentsRe: Error In Log file server 20003
hi Yossi, As i understand from the issue is that you are getting an error message:- "Final Error Code: a000fec9 HEX (0xa000fec9 HEX) or e000fec9 HEX (0xe000fec9 HEX) Final Error Description: "A failure occurred accessing the Writer metadata." Try rebooting the server and run the backup job If that doesnt help then try following technote Shadow copy components by default uses VSS This seems to be a VSS issue This technote is related to the error regarding shadow copy components ==> How to troubleshoot the error "A failure occurred querying the Writer status" (a000fed1 HEX or e000fed1 HEX) using VSSADMIN http://support.veritas.com/docs/261993 ==> if this doesnt work check in the services that whether the Microsoft software shadow copy provider service is started or stopped The Microsoft Software Shadow Copy Provider Service manages software-based volume shadow copies taken by the Volume Shadow Copy service. If this service is stopped, software-based volume shadow copies cannot be managed. If this service is disabled, any services that explicitly depend on it will fail to start. Hence, while configuring a backup job to back up a Windows 2003 machine with selections made from the Shadow Copy Components, it should be ensured that the Microsoft Software Shadow Copy Provider Service and the Volume Shadow Copy Service are running. NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.Message was edited by: Sushil Sakhawalkar198Views0likes0Comments