Applicable till 8.1 version (Till 8121 builds)
Nowadays the database size is huge in various users instance. It is because the indexing related files, archived files, file attachments are folder are huge in size. Due to which either our application is facing performance issues, Backup is not working or time taken to restore is huge.
To overcome this, we have a workaround. Please follow this and check whether it works. Try this in the user non-operational hours.
1. Edit the backUpData.bat (present under SupportCenter\bin folder) and add the below entries in the last line(in bold alone) and also tune the backUpData.bat as the conversation files are huge in size around 10 Gb
Refer content in Bold and make changes.
%JAVA% %JAVA_OPTS% -Xms128m -Xmx4096m -Dsdp.backup.home=%BACKUP_DIR% -Dsdp.backup.type=%1 -Dignore.folder=index,archive -Dsdp.backup.ignoretables=AaaAccSessionAudit,AaaAccHttpSession,AaaAccSessionProp,AaaAccSession,AuditRecord,OperationAuditRecord,ErrorLog,ErrorLogOwner,AuditResultProperty,AuditResourceProp,AuditOperProperty,RecentItems -cp %CLASS_PATH% com.adventnet.servicedesk.tools.SDBackUp
PS : Tune according to the server capacity (above is applicable for 8 GB RAM machine)
2. Disable the automatic backup scheduling from the user interface. Admin -> Global Settings -> Backup Scheduling -> Edit scheduling.
3. Open a command prompt and navigate into SupportCenter\bin folder and execute backUpData.bat --trimmed
This will take backup without attachments.
PS : You can copy the inlineimages , fileAttachments , images present under SupportCenter folder separately. These folders combined is equal to full back up of the database.
- Once the backup is complete, a backup file with .data extension is placed in the Backup folder under the Supportcenter Plus\trimmedbackup directory. You can use it for further usage.
Some users may get Stream Closed Error at the final stage (post taking the backup), we can ignore the message.
In case you still find any errors, please send the SDPbackup.log file present under SupportCenter\bin folder and also the error thrown in the command prompt.
PS : In case , we ask this trimmed backup for our analysis , just send the final trimmedback up taken.
If you are using SQL database, just take the .bak file (SQL Backup) and restore it in a test SQL environment.
Dont uninstall the existing installation till all your expected goal is completed.
Attached are the sample files, you can replace this files under SupportCenter\bin folder and continue to take the backup file.
In case of Linux environment - use the .sh file.
in case of windows environment - rename the txt file as bat file (batch file) and then use it.