Storage and Disk Space

The more MyQ is used, the more space it needs to store data. Recommended storage space is estimated based on the number of connected devices. These recommendations are based on our testing, however, your needs may differ.

System Requirements for Storage and Disk Space

Recommended Disk Space Settings

Low Disk Space Warnings

See Settings – System Management both on the Print Server and Central Server Web Interfaces and set the appropriate storage warning levels.

MyQ will send notifications to the admin’s email address when it reaches this level of free disk space so that they can react in time.

When the critical level is reached, the MyQ X system is stopped.

Old History Deletion and Self-maintenance

You should configure how much back history you want to keep and how often MyQ X should perform maintenance of temporary files.

In Settings – System Management, you should go through the settings in the History section, especially:

Delete jobs older than – this is how long a document sent by a user for print is kept in MyQ X; during this period, it can be printed, or reprinted, unless it is deleted manually.
Delete history older than – MyQ will regularly delete old data to cleanse the database, effectively limiting for how long MyQ X stores prints, scans, and other data.
Delete archived reports older than – how long a generated report is retained in MyQ and can be downloaded for; if you send reports via email or store them/archive them elsewhere, you can set a fairly short period here to save space

What you set in Delete history older than determines how much historical data you will see in all reports. For example, if you specify 365 days here, you will get data in reports from only the last year, as anything older than 365 days is deleted daily.

Once data is deleted, it can be only recovered if you restore a full backup containing this data.

In Settings – Task Scheduler, plan the System Maintenance task to run occasionally as it cleans temporary data and orphaned job files, and anything else that the system failed to delete previously.

Recommended Data Storage Settings

Database Backup Location

When setting up your automatic database backups in Task Scheduler, select the location where backups are saved and choose after how much time they get automatically deleted.

Print and Scan Recommendations

If you expect your server to grow in size quickly, design an external storage for the print data files or databases and set these locations ahead of time in the Easy Config – see Change locations of database and print jobs below.
When setting up Easy Scan destinations on the Print Server, choose a storage destination not at the same server but elsewhere, such as cloud services, FTP servers, network folders, or network drives.
Set maximum file sizes for incoming print jobs and jobs uploaded via the Web Interface.

Job Archiving and Job Preview

If you are using Job archiving, set the destination for archived jobs ahead of time and consider choosing a lower resolution. Remember that archived jobs can cause the disk space taken by MyQ X to increase rapidly.
Set restrictive Job preview options, e.g. limit the number of pages to be generated.

Change Locations of Database and Print Jobs

To save disk space on your print server, or if your server is running out of space, you can change the location MyQ uses to save data.

Data folder dictates where the MyQ database is saved.
Jobs folder dictates where MyQ saves print files of jobs that are waiting to be printed (Print Server only).

Related links:

Size of Logging Data

Thanks to all these subsystems logging, you can always check what is happening anywhere in the system, and debug when something goes wrong. Logs are also important if you need to file a support ticket with your MyQ X provider.

However, logs can also take up a lot of your disk space. To prevent this, make sure that:

You do not have the debug log mode enabled for longer periods as it significantly increases the log database size.
In Settings – Task Scheduler, you can also adjust settings for the Log backup task – how often a new log backup should be created and how often old backups are deleted automatically.
Consider storing the log backups on a different drive in your system.

Size of Replication Data

In Central-Site environments, it is good practice to regularly check the status of Replications. If errors appear during replications to the Central Server, the Site server’s database may start growing in size rapidly due to the bloating replication log table in the database.