Hi Randy -

I would be very careful with using Shadow Copy restores with any relational database.  You could for example, restore a new.prt file from a shadow copy if you haven't printed or generate direct deposits.  Because the data is all contained in that single file with no supporting entries being created in CM or GL yet (assuming you don't have SM time being sent to PR).  So using Shadow Copy restores or any active backup solution that doesn't take the pervasive engines offline prior to backup, has the potential of corrupting the database as a whole.

I usually write a powershell script that runs nightly.  It takes the Pervasive and Sage Framework services offline, in essence kicking everyone out of the database and copies the Data Folders to a "Workfile" location.  Then turn back on the services, this minimizes down time.  Then I usually perform a compression routine on the Data Folders in the "Workfile" location and move it to an archive.  Monthly, I would do the same routine, but include folders in the 9.5 share that have the potential of data being changed on a much less frequent schedule. I.E.-Formulas, Reports.

Good Luck,

John McLagan
Sage Consultant
Johnny on the Spot

Randy,

As of version 17.1, Sage has included an automated backup option.  It is new and still leaves a lot to be desired.  However, it does:

• Automatically backup the 9.5 folder and contents each time.
• Can either backup the entire contents of your company folder or just the Data files (for a smaller backup).
• Backup any other folder you specify (external to your company folder - for attachments, install files, or other).
• Can initially be schedule on the hour 24 hours a day.
• Has a Restore feature - can restore only the 9.5 contents (or partial as needed) or a single company folder, etc.
• Create a Job in Task Scheduler

Once the Job is created, you can access it in Task Scheduler and can then select any time to launch it and if you only work M-F, you can have it back up only M-F.  This does not kick anyone out of the data, so it will fail if files are in use.  It also does not have a retainage policy so you will need to monitor/maintain the folder you elect to back up to.

If you are a 24/7 operation, this still may not be the answer for you and using John's solution or one like it may be your best bet.

As John mentioned, it is very risky to restore any portion of a company folder when using a relational database.  If you believe that is what you want/need to do, I would strongly suggest you obtain confirmation from a Sage Certified Consultant or a Sage Support Analyst before proceeding.  I recommend if you are able to use the System Administrator to create an automated back up, then coordinate it with just about any other back up process to copy it off-site (meaning it is okay to partner with a back up process that uses incremental or differential backups as they will back up the entire back up file that is generated by Sage).

You can see more detail in the Users Guide under Chapter 5: System Guidance.

Todd Baker

Sage Consultant

The Sage backup feature is way better than it used to be but it is still mostly worthless. We've always run our Sage servers as a VM, since 9.8 in 2013, so the image based snapshot for VM backups works VERY well (we use Veeam).

I did try Hyper-V replication as well initially, which uses the same technology as Shadow Copies but pushes it to an image on another host across the network. I can confirm it is not appropriate for a records management system like BTRIEVE/Pervasive, any more than it is for a real RDBMS like SQL Server. I spun up the replica for testing and it was un-useable.

I keep an attached VHDX available for backing up with the Sage tool, which is then backed up as well on the normal Veeam schedule.

I've restored whole VM's for testing, fortunately never in anger, and individual files are restored for quarterly maintenance & testing. Fortunately we've never had to dump a whole VM back over the wire, but it only takes a couple of minutes. The Veeam Sandbox is a handy tool to test your VM's for functionality and integrity. 

We also spin up a new VM for every iteration of Sage, the major version upgrades, and use the data migration toolkit. It adds a bit of time to version changes, but we will never have the failed in-place upgrades that have happened to other folks. 

Hi John,

Would you be willing to share your PowerShell script?