35 GB Full backup and 200 GB Incrementals
Hi Everyone I have a group of Vmware VMs in our VCSA 6.5, which are applications servers, running Wonderware software on windows server 2016. I backed them up in 2 groups (5 VMs in each). Weekly Full backup and Daily Incremental. Both the daily and the incrementals are configured in the same backup job. All the application servers have 200 GB thin provisioned Harddrives. 6 of the servers, split between the 2 groups are backing up just fine. 35-ish GB Full backups and 1-4 GB incrementals. However, the remaining 4, also split across the 2 groups have huge incremental backups. Full 35GB and Incremental 200 GB. (Which is 100% of their harddrives) All 10 application servers have the same backup settings as they are grouped together. (2 groups of 5) Here are the different backup settings. * Backed up to a storage device pool with 2 Disk storages (Not dedup) * No compression or encryption * Verify at end of job * Instant GRT enbaled * Use snapshot technology is enabled * Automatic - Allow VSS to select snapshot provider * Process logical volumes for backup one at a time * Use Backup exec GRT is enabled * Backup using VSS is enabled *Transport mode: SAN > Hotadd > NBD > NBDSSL I hope someone is able to help me find a sollution to this. Best Regards BrianSolved1.8KViews0likes5Comments
SQL - query multiple archive-databases
Hi all I'm a bloody beginner with sql-code. What I want to know is to the amount of archived data for last night (22:00-06:00) and the night before. Both for two different archives. My code is the following: (SELECT "date" = '2018-02-17', "MB mailarch1" = sum (originalsize)/1024/1024,"MB mailarch2"='' from EVVSVSArchiveMail1.dbo.Saveset with (nolock) inner join EVVSVSArchiveMail1.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-17 20:00' and archiveddate < '2018-02-18 06:00' union SELECT "date" = '2018-02-18',"MB (orig) mailarch1" = sum (originalsize)/1024/1024,"MB (orig) mailarch2"='' from EVVSVSArchiveMail1.dbo.Saveset with (nolock) inner join EVVSVSArchiveMail1.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-18 20:00' and archiveddate < '2018-02-19 06:00') UNION ALL (SELECT "date" = '2018-02-17',"MB (orig) mailarch1"='',"MB mailarch2" = sum (originalsize)/1024/1024 from EVVSVSArchiveMail2.dbo.saveset with (nolock) inner join EVVSVSArchiveMail2.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-17 20:00' and archiveddate < '2018-02-18 06:00' union SELECT "date" = '2018-02-18',"MB (orig) mailarch1"='',"MB mailarch2" = sum (originalsize)/1024/1024 from EVVSVSArchiveMail2.dbo.saveset with (nolock) inner join EVVSVSArchiveMail2.dbo.savesetproperty with (nolock) ON saveset.savesetidentity = savesetproperty.savesetidentity WHERE archiveddate > '2018-02-18 20:00' and archiveddate < '2018-02-19 06:00') The output I want is a table like: date MB mailarchive1 MB mailarchive2 2018-02-17 8556 9234 2018-02-18 9432 9834 I am sure there is a much more elegant and straightforward query, but I am not able to improve it. Has anyone of you scripted a similar thing and could let me know? Thanks a lot, MikeSolved1.6KViews0likes4Comments
EV 11.0.1 EV Search - Strange behavior with large files
Hi, we have a strange behavior with the EV 11.0.1 Search. There're archived files with a size 4GB and more. If the file is 4,05 GB big in the EV Search the size displays about 50 MB. Is there a limitation of the used filetyp? Is there a workaround from veritas to fix it or an offical statement why files over 4 GB not displayed correctly? Thanks for your reply and kind regards.:smileyhappy:1KViews0likes1Comment
EV 11.0.1 EV Search - Strange behavior with large files
Hi, we have a strange behavior with the EV 11.0.1 Search. There're archived files with a size 4GB and more. If the file is 4,05 GB big in the EV Search the size displays about 50 MB. Is there a limitation of the used filetyp? Is there a workaround from veritas to fix it or an offical statement why files over 4 GB not displayed correctly? Thanks for your reply and kind regards.:smileyhappy: