Video Screencast Help

Migrate data Virtualization system, need keep data user permission

Created: 14 Nov 2013 • Updated: 27 Dec 2013 | 8 comments
This issue has been solved. See solution.

Hello Symantec Community,

Our company change IT system, need to migrate data from Physical to Virtualization.

The issue which we are facing now is:

1. Keep data user (file/ folder) permission.

2. Time stamp is kept?

3. Log record in detail: what data/ file/ folder (easy to manage backup and restore)

We are not sure our software Symantec Backup Exec could be able to meet that requirements?

In the other hand, we also research at some software (P2V Virtual Machine Converter, ...), do anyone here know which software could do this?

Your advice is highly appreciated.

Thank you very much,


Operating Systems:

Comments 8 CommentsJump to latest comment

CraigV's picture


BE 2012 can do a would be the same as VMware Converter etc, and move all settings and files across from a physical server to a VM.

Read below:


Alternative ways to access Backup Exec Technical Support:

SOLUTION's picture

Hi CraigV,

Very thanks for your information.

May i ask more where (or how) we can check and manage log record in detail of data?

Since last time we have faced 01 case with Symantec Backup Exec 2012:

We copied data from server01 to server02, then checking quantity of the number of file/folder is ok, but content inside file is not yet full updated, it have some lastest files, some not lastest files.

So how can we fully manage data? such as time stamp, log record detail...

Highly appreciated for your advice.

Best regards,


CraigV's picture

...did you do this via a normal Windows copy? If so, this isn't a Backup Exec issue if the data wasn't restored...


Alternative ways to access Backup Exec Technical Support:'s picture

Hi CraigV and Symantec Community,

Thanks for your response.

Last time we did it by Symantec Backup Exec (backup and restore then), not via a normal Windows copy. So it made we be at a loss about the operation of Symantec.

Maybe we do not have understanding thoroughtly at some steps and Symantec's operation, hope to get your advice which help us understand above questions (how to check log record detail, time stamp...).

Thanks very much.

Best regards,


CraigV's picture

...some of those questions are pretty technical...but:

1. The permissions should all be restored. Read the section on restoring data in the Admin Guide for further reference.

2. When you restore a file, the original time stamp is not maintained. Don't forget the file is effectively changed on the restore destination!

3. If you increase the level of your logging, you should see what files are backed up and restored. Just bear in mind though that this is going to seriously increase the size of your log files, and possibly ensure you run out of disk space quickly if you don't move the logs to another drive with enough space.

You should be able to confirm all of this with technical support if need-be.


Alternative ways to access Backup Exec Technical Support:'s picture

Hi CraigV,

Thanks very much for your response.

I think that it is helpful with these confirmation information:

-The permissions should all be restored.

-The original time stamp is not maintained when restore a file.

-About log collection, could you explain more "increase the level of logging"?

I have tried at some document and testing like below links:

However we still not yet thoroughly got it. Could you please instruct us how to collect log to see what data/ folder/ file be backup and restored? (we knew about the giant increase the size of log files already)

Thanks you.

Best regards,


pkh's picture

When you restore a file, unless you specify in your job NOT to restore the permission, by default the permissions are restored along with the file.

To show the files/folders backed up in a job, click on the BE button ---> Configuration and Settings ---> Backup Exec Settings --- Job Log and change what to display in the job log.

BE 2012 - job log.png

Note that this is a global setting and all jobs will be affected.  Make sure you have a lot of space on your C: drive when you turn on detailed logging.