Here is the scenario:
1. ePO Server task backs up an ePO directory structure to the SQL database. (dbo.OrionSnapshot). As you can see the pertinent ePO directory structure is being backed up to SQL.
2. The next piece is your ePO database itself. That is why this is a two part backup. The important directories are maintained and everything else that is backed up by SQL or backup software.
3. Between these two parts you should be able to build up the ePO environment that you had, that is now bad.
4. If you utilize virtualization and perform regular clones and\or snapshots then this becomes a redundant task.
Note: Remember that **** happens and if you utilize the backup from ePO and is placed into a corrupt SQL database you might have other problems to deal with as we always check our backups right? <insert your chuckle here>
In the perfect world if you rely on steps one and 2 you are on your way to rebuilding your ePO system. There are other steps of course, but I think you get the idea.
In closing, Depending on your backup software it may not be necessary to shut down the services. It is recommended that you do so that no further events or changes are collected during the backup period.
Thanks for the response!
Let's say that I come in to work monday to find out that my ePO crapped out. Our DB server and ePO server are all virtualized and snapshots (Vmware snapshots) are done daily and so. we want to revert back to Friday's snapshot.
1- Revert the DB to friday's state
2- Re install ePO and tell the installer to use use my disaster recovery's snapshot that I just reverted back to?
Or should I simply revert to my vmware snapshots for both the DB and ePO server?
Since the disaster recovery snapshot contains everything i need, would that be the safest route?
Hopefully this makes sense.
The beauty with virtualization is that it really helps in getting back online quickly. As long
as you have a process for restoring your epo and sql db at roughly the same time, your good.
Using the db snapshot may not be required as long as you have a reliable vm plan. Ask your backup
folks how long to restore both pieces. It is usually under an hour or 2.
Thanks for the quick responses.
Sorry to revive this thread, but does anyone know the best way to remove these snapshots, out sql database is now at a huge 38GB with 99% of that being in the dbo.orionsnapshot table. As our epo server is virtual we use their snapshot facility. Can the table just be emptied?
Hope you can help as I am unable to find any documentation on this.
I would suggest that you create a new post regarding this issue. I'd be curious to see what the answer is,