If it is, simply create a new backup job and drill down to the server and the SQL databases you want to protect and back them up that way. They are on your radar because the backup job has a hidden folder selected for backup that should not be selected.What I would recommend is that you check to see if the SQL agent is licensed and installed. So like I said, you are worried about files that I believe to be a red herring and not related to anything. So I am not real familar with Backup Exec.Great thanks for that information. Matthewbrink wrote:I personally use Veeam with my environments but this is coming from a user I am assiting. The name of these files are:ﷀŪ墰ᦒȓ鶀䄺ƚ(They did not show up exactly like they are on the server due to the Font's but hopefully it gives you an idea.Edited at 14:57 UTC. Epo Scan Files Opened For Backup Windows 7Įach are a 1GB a piece and where created about the same time that this Server was stood up.When it runs there is an error that says:'08-May 22:42:21 Unable to scan file for hardlinks:?GLOBALROOTDeviceHarddiskVolumeShadowCopy2WindowsSystem32LogFilesSumﷀŪ (OS error (0x2): Thesystem cannot find the file specified)'.One thing I noticed was that in this directory:C:WindowsSystem32LogFilesSumThere are 3 files that are not in English and/or Plaintext and I have no idea what they are? Has someone seen these before? Hello,I am running Backup Exec on my SQL Server which is running on Windows Server 2016.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |