@syko24 said in SAMIT: Why You Can't Share QuickBooks on Google Drive for Mutiuser:

@scottalanmiller said in SAMIT: Why You Can't Share QuickBooks on Google Drive for Mutiuser:

@syko24 said in SAMIT: Why You Can't Share QuickBooks on Google Drive for Mutiuser:

There is a product out there called QBox that allows you to lock and sync the file with multiple locations. The downside is that remote users can only access the file when the local users have closed out of QuickBooks. Kind of a neat product but again not ideal when you need multiuser access all the time. The best solution in my opinion is an RDS server with the QuickBooks data file stored on the RDS for best performance.

As the QuickBooks desktop products seem to be coming closer and closer to an end, I agree that the online version is likely the best way to go. Part of the problem is that users have been using the desktop version for so long that the online version becomes very foreign to them and most want to return back to the desktop version.

https://www.coraltreetech.com/how-qbox-works

Yeah, that's not multiuser but rather "rapidly changing and coordinated single user". Could be a useful solution for some, though. You can do this with most products. NextCloud for example.

From the use case I've seen that is correct on being a single user product. I did watch the video on the link I posted and it does look like you can still do multiuser as long as the users are all on the same network. The remote user can only access once all the local users are out of the file and it has done it's sync. The file locking is automatic as well which is nice. It basically prevents the outside user from accidently overwriting your changes.

Sure, you can always bypass the sync and do local multiuser, but the humans have to manage that.

I don't think that you can do workdrive backups in general as it is not file based and you don't have database access.

@Yonah-S said in Turn server into backup storage for remote servers?:

@Pete-S have you thought of selling it? there is a big market right now for getting rid of old/unused hardware. Especially if you have any SSD's in there.

Thanks, but we're keeping it. Just want to extract the maximum value out of it while it's occupying rack space 🙂

@Matthew-Grieve said in How to Backup Patterson Dental EagleSoft Software:

https://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/dbadmin/da-backup-dbs-5615940.html

SQL Anywhere Volume Shadow Copy Service (VSS)
SQL Anywhere is compatible with the Microsoft Volume Shadow Copy Service (VSS). You can use VSS to create point-in-time snapshots of entire disk volumes or volume sets and to make copies of files that are open for exclusive use by applications such as the SQL Anywhere database server. VSS is supported on 32-bit Windows XP operating systems and on 32-bit and 64-bit editions of Windows 2003 and later operating systems, including Windows Vista.

By default, all SQL Anywhere databases can use the VSS service for backups if the SQL Anywhere VSS writer (dbvss12.exe) is running. You can use VSS without the SQL Anywhere VSS writer to back up databases. However, you might need to use the full SQL Anywhere recovery procedures to restore those databases. To prevent a database server from participating in the VSS service, include -vss- when starting the database server. Alternatively, you can use the Service utility (dbsvc) for Windows to specify when the VSS service is started.

How VSS works with SQL Anywhere:

Your backup application sends a command to VSS to take a snapshot.

VSS issues an identify command to the SQL Anywhere VSS writer (dbvss12.exe).

VSS issues a prepare to snapshot command to suspend all transactions and write all modified pages to disk on all databases on all database servers. If transactions are not suspended on a database within 10 seconds, the snapshot might contain uncommitted transactions and full recovery may be necessary.

VSS issues a freeze command to checkpoint and then suspend all activity on all databases on all database servers. Each SQL Anywhere database server waits a maximum of 60 seconds for all databases to suspend all activity. Typically, this process takes a few seconds.

VSS issues a thaw command to the SQL Anywhere VSS writer to resume all transactions on all databases on all database servers.

In rare circumstances, SQL Anywhere might be unable to suspend transactions or complete a checkpoint within the maximum time allowed by VSS. If this occurs, you must use the transaction log file and the full recovery process to recover the backed up database.

We use StorageCraft ShadowProtect with ImageManager to take hourly incrementals of our clients server volumes. Never had any issues.

That's true when you have SQL Anywhere running as a service. But when embedded, there is nowhere for the VSS to link against. Are you sure that this process will work with EagleSoft and their implementation of SQL Anywhere? I know that a full blown SQL Anywhere can do it. But that's not the issue here.