[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 307
  • Last Modified:

Jumbled charecters on Veritas DLO documents

I've recently upgraded my backup server to a newer machine.  We are using Veritas 9.1, and Windows 2003 server R2.  All of the workstations are XP, and the backups are scheduled, and set to backup when a user logs off.  
The problem is that the file sizes of backed up documents has decreased, and the documents themselves are nothing but a jumble of letters.  I've tried opening the documents with Word, Wordpad, and Open Office.

Any help would be much appreciated,
Thanks
0
pepadmin
Asked:
pepadmin
  • 3
  • 2
1 Solution
 
David_FongCommented:
Do you mean you've restored the backed up documents to a different location and they are a different size or are you trying to read the compressed backup files themselves?
0
 
pepadminAuthor Commented:
When the DLO runs it copies files to a seperate network drive.  These files are not compressed when they are backed up.  The files should be readable from the backup location.  Instead of having a readable .xls or .doc, I get gobbledygook (technical term).  
0
 
David_FongCommented:
The files should be readable with the DLO agent from the client, not from the backup server by looking at the raw files. See the sizing calculation in http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/278174.pdf for example:

(Size of all users' data to backup) / (Compression ratio)] * (Number of copies) / (data change
expectation) * (Expected user data growth percentage (Addition of users and current users data
growth))

Number of copies/data change expectation - it does not store multiple copies of the files but one base copy plus deltas for each subsequent copy. If it stored each file then you would not divide by data change expectation. 2 versions of the same word doc with one word changed would result in one large compressed file and one small one with just info about the changed word in it. that's why compression and expected change is taken into account.

How easy the sizing calculation would be if it didn't compress but simply coppied the files to a new location each time - size of all users data * number of copies.
0
 
pepadminAuthor Commented:
Before we migrated to the new server the files were plainly visable, and could be opened and read. As a matter of fact, I'm looking at the old machine right now, and am able to open the files from previous backups.  Basically, I used to be able to map to the storage location and drag and drop from folder A to folder B.
0
 
pepadminAuthor Commented:
It turns out the encryption was on.  I am able to restore the files fine, so I'll leave it on.  
Thanks David.
0

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now