When you have a disk mirrored, both copies must be the same. Sometimes, they are not and then you need to synchronize them (usually by running a command to copy one to the other - realize this is not a cp command but is being explained that way)
With Solaris you would be probably using one of two software products - DiskSuite or Veritas. The commands for each are entirely different. Suggest you figure out which you are using and read the manuals.
$ df -kl
If the output has devices that contain /md/ - Disksuite is being used there.
If the output has devices that contain /vx/ - Veritas Volume Manager is being used.
Opinion - DiskSuite for OS drives - Veritas for Data drives. Veritas is a pain in the neck when dealing with OS drives (which is why most don't use it for OS). DiskSuite isn't as robust for Database/Data drives which is why you spend some $$$ and get Veritas. DiskSuite comes with Solaris 2.6 and above. Not sure about below 2.6.
Check out
docs.sun.com for on-line docs on DiskSuite.
Check out
Veritas Support for on-line docs on Veritas.
For
Linux Mirrors check out this link.
For general info on
Raid levels
The subject you posted "Run process to resynchronize mirrors during database backups" - was this an error while running backups? If so - is it happening on both Linux & Solaris? What type of backup (data dumps, ufsdumps, vxdumps, 3rd party backup solution {version}). Give more info unless you are just looking for information on Raid.