EPO 5.9 disaster recovery plan

[Former Member]

Hey all,

We are dealing with a disaster recovery plan in our organization. Notice that redundancy is very important  to our organization 🙂

We have EPO 5.9 Server in MSCluster with Database server (also within MSCluster) in our primary and DR site (the DR site circled with blue)

From our simple knowledge, we have to transfer 2 things to the DR site:

1. EPO directories (under program files)
2. EPO database

Database recovery

we did some searches, and we found that there is an SQL replication solution known as SQL snapshot replication. We are planning to configure  a scheduled backup nightly task in the database (via SQL management studio). We do have some concens: 

• Does anyone have experience with this solution?
• We noticed that the process locks resources within the DB. Won't this hurt the application?
• Is there another thing we have to configure in the DR site in order to the Web application will load the content properly from the replicated Database?

File recovery

For file recovery, we have seen a post talking about inserting those files into the database. So, we are thinking to use an EPO task to insert the files to the Database, transfer them with snapshot replication, and to export them in the DR site.

Another solution we considered is just to put the system directories as shared (on a DFSR replicated folder or something like that).

• Did anyone try to use the backup of the directories within the database backup?
• Are the restore and backup procedures (i.e insert the files into the DB and pulling them back in the DR site) simple to use? can they be scheduled?

Any other advice is more than welcome!

Thanks a lot!

Tankwell

[Hem]

Hi,

Good morning,

If you have ePO on cluster then please look at #: 

https://kc.mcafee.com/corporate/index?page=content&id=KB75497#:~:text=After%20the%20agent%20cans%20s....

Was my reply helpful?

If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

[Former Member]

Hello, 

Thank you for the reply, although it was a bit brief and did not cover our main concerns regarding the DR plan.

We'd like to have some detailed information concerning the subject below, since this is a major issue at the moment in our organization due to our network architecture and bandwidth limitations. 

Database replication

we did some searches, and we found that there is an SQL replication solution known as SQL snapshot replication. We are planning to configure  a scheduled backup nightly task in the database (via SQL management studio). We do have some concens: 

• Does anyone have experience with this solution?
• We noticed that the process locks resources within the DB. Won't this hurt the application?
• Is there another thing we have to configure in the DR site in order to the Web application will load the content properly from the replicated Database?

Thanks,

Tankwell.

[cdinet]

There was a question presented to dev about this and this is their response below.  As with any recovery procedure, the restore from snapshot is the quickest and most efficient, but that also depends on a valid snapshot in the database with known recovery password.  So in the event that would fail, the kb you were given tells what directories to back up as well as the database for a manual recovery.  Always be prepared for manual recovery in case snapshot recovery fails for any reason.

What is the reason for this customer to select Replication? Since they mention the purpose as DR, the entire database should be replicated to other secondary instance\database.

Replication is NOT a best fit for creating a copy of entire database for DR requirement.

Either they should opt for Always On or Database Mirroring, even traditional SQL Server clustering is an option.