2013-04-19 04:14 AM - edited 2015-12-18 02:57 AM
can anybody tell how to backup and restore a Systemstate with the OSSV PlugIn in SnapProtect.
on the CLI without SnapProtect are the comands for backup: snapvault start -S prim_host:SystemState sec_host:/vol/sec_vol/sec_tree and restore: snapvault restore -S sec_host:/vol/sec_vol/sec_tree SystemState
thank you in advance
Solved! SEE THE SOLUTION
2013-04-24 06:23 AM
I've the same issue. Not found any way to backup system state through the plugin. In the specific case it would be useful to offline mine the AD database file, that I don't see in the C: drive OSSV backup.
Anyone with an hint?
Thanks and best regards
2013-05-23 10:07 AM
Hi there, what documentation did you use to get OSSV / SnapProtect working? I am struggling! Documentation is very frustrating, its like there are steps missing. And it was written by someone that could possibly have been half drunk at the time! Anyway heres what I've done so far:
Can you see anything I am missing / or being dumb about. Doesn't seem tike too many people are using snapprotect / ossv together and I'm banging my head against a brick wall here! FYI, snapmirroring / snapvaulting works fine with SP. Everything is upto date too.
2013-05-23 09:23 PM
SystemState backup is performed using Windows iDataAgent. So, ideally you would first backup drives C:\, D:\ etc. using OSSV Plugin and then do SystemState backup using Windows iDataAgent.
Follow this link for detailed steps:
2013-05-24 01:27 AM
yes, dfm server is registered, and works for normal snapmirror / snapvaulting.
This morning I have got slightly further. It seems that making the ossv client a media agent allows me to now populate the pieces I could not do before, obviously every ossv client cannot be a media agent, so it must be something around that as to why I can't select any of the options, perhaps the remote ndmp server piece is required to be working, however that is confusing in itself as the only option is EMC Centera, I'm guessing ndmp is ndmp, but having EMC in a NetApp branded product is blasphemy! But anyway that's where I'm at currently...
2013-05-24 01:32 AM
at least for me as of SP8B OSSV plugin doesn't make use of DFM.
OSSV setup is a bit tricky even following the documentation.
In my case anyhow I've created a single destination volume (size MUST be >= to the sum of the sizes of the OSSV source partitions) on the SnapVault secondary filer and assigned it to a "Destination Volume Pool" as per the documentation.
The "Destination Volume Pools" group will appear under "Storage Resources" after the first OSSV plugin is detected.
You've to assign the destination volume for OSSV to a pool.
Then you can proceed with OSSV plugin configuration.
1.Start the replication as "incremental": you can't use a "Full" backup as base for incrementals.
2. Only after the volume is in a pool it'll be showed as a possible destination for OSSV. You MUST click on "Specify destination volume" and assign each source drive to a destination volume (even the same one for all of them will work, OSSV will create a qtree per source).
For the system state starting SP8 (at least for what I saw) you'll be allowed to create a "classic mode" backup including system state via the filesystem agent. OSSV plugin doesn't handle it. Alternatively you could SnapVault system state through the OSSV interface. We went for the first solution to still have all backups under one roof.
Last but not least: upgrade form SP8B to SP9 broke the OSSV plugin on the DC I was using for testing, I had to roll it back.
2013-05-24 01:50 AM
Very interesting that it does not seem to use DFM at all. The documentation around this needs updating definitely!
Hmm, mines at SP9! I hope that doesn't cause me any issues. So you rolled back just the one ossv client back to SP8?
Did you have to make your test machine a media agent, or can you select a dedicated media agent. My current thought is that I will have to install some of the SnapProtect OSSV bits on one of my proper dedicated media agents so it will at least (I;m guessing here) allow me to select the right options during a ossv policy / subclient setup.
2013-05-24 02:02 AM
Yes, I rolled back that client only to SP8B.
It was relatively easy since I had added SP9 only later on, and I could uninstall patches to point in time using "Remove updates".
2013-05-24 02:05 AM
I opened a Case at the Support and became the same answer, but i forgot update this discussion.
I tested to backup the SystemState with the Filesystem iDataAgent, with a separete Policy and Disklibrary.
Only one thing I've changed from the documentation, I became an error when i want to configure the default Subclient.
I uncheck the SystemState Checkbox and I disabled the default Subclient and created a new one.