Hi,
I'd like to hear from users who use Veeam as part of their SharePoint Disaster Recovery Plan.
We would like to use Veeam to backup our SharePoint WFE and APP servers nightly and to build a new farm from in the event of a disaster. Has anyone gone down this road? How do you test your backups? What steps are required to bring up a functioning farm when using Veeam? I'm imaging it would go something like:
1. Restore Virtual server C drives from Veeam backups
2. Manually create secondary drives and restore critical contents from Symantec backups
3. Restore SQL from SQL backups
4. Restore SharePoint Farm from Symantec backups
5. Set IP’s for servers to match OKC.
6. Create DNS records to match IP’s
Thanks!
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 14, 2015 6:30 pm
- Contact:
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Feb 09, 2016 9:44 am
- Full Name: Disconnect
- Contact:
Re: Veeam as DR for SharePoint 2013
We'd like to use Veeam for SharePoint DR as well.
This is an existing Veeam implementation with a SQL Express backend (which will need to be moved to full SQL to accommodate the 10GB+ content db)
SharePoint 2013
SQL Server is 2008 R2 and is separate to the SharePoint Application Server
The following databases are active
Name
----
AppManagement
Config
Content_Admin
Content_MySites
Content_Portal
MetaData
Profile
Search
Search_AnalyticsReportingStore
Search_CrawlStore
Search_LinksStore
SecureStore
Social
StateService
SubscriptionSettings
Sync
TranslationService
UsageAndHealth
WSS_Content
Whatever recovery solution we go for will require that these databases are in sync with the application and, in some cases, with each other
The SQL server is backend for multiple unrelated databases so we cannot realistically roll the VM back without losing work for other applications
We need to devise and test a full DR Recovery solution
Any help appreciated
This is an existing Veeam implementation with a SQL Express backend (which will need to be moved to full SQL to accommodate the 10GB+ content db)
SharePoint 2013
SQL Server is 2008 R2 and is separate to the SharePoint Application Server
The following databases are active
Name
----
AppManagement
Config
Content_Admin
Content_MySites
Content_Portal
MetaData
Profile
Search
Search_AnalyticsReportingStore
Search_CrawlStore
Search_LinksStore
SecureStore
Social
StateService
SubscriptionSettings
Sync
TranslationService
UsageAndHealth
WSS_Content
Whatever recovery solution we go for will require that these databases are in sync with the application and, in some cases, with each other
The SQL server is backend for multiple unrelated databases so we cannot realistically roll the VM back without losing work for other applications
We need to devise and test a full DR Recovery solution
Any help appreciated
Who is online
Users browsing this forum: No registered users and 67 guests