Jump to content
ggirao

Problem on Scanning Source

Recommended Posts

Hi,

 

I'm running ok several backups, but this one last times started to give me problemas. When doing Scanning the CPU is about 300% and doesnt go beyond 300GB.

 

This backup source has millions of files and usually is the one that the snapshot (even if it is a small diary backup) lasts about 5 hours.

 

What should I Do?

  • Like 1

Share this post


Link to post
Share on other sites

If it is a Windows client, run CHKDSK on the client.

 

If it is a Mac Client, repair the hard drive on the client. It's probably easiest to do that by a "safe boot" (During boot/startup, hold down shift until you see a progress bar). Then restart the Mac normally.

Share this post


Link to post
Share on other sites

It is a Mac Client, but has it is a RAID with it's "own SO" (LaCie) I cannot repair hard drive. This has only data, not a Mac OS X.

Share this post


Link to post
Share on other sites

You should be able to repair the disk directory using Apple's Disk Utility, even RAID disks. You don't even have to reboot the computer and do a safe boot for that!

Share this post


Link to post
Share on other sites

I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again...

 

I will restart my RAID and server.

 

EDIT - this disk has maximum 4 months old ....

Share this post


Link to post
Share on other sites

I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again...

 

 

That was most likely caused by a buggy RAID system, not by Disk Utility.

Share this post


Link to post
Share on other sites

I Dont think it is a problem with disk errors... This because i added a new favorite folder on same Disk and it was very quick!

Share this post


Link to post
Share on other sites

I will keep the verify disk to my very last option.

 

Today I will:

 - Shutdown server where disk is;

 - Restart or even shutdown RAID Controller (The disk it self);

 - Propagate Permissions and ACLs on Server Admin for that Share (reminding that retro will backup all over again - the BUG)

 

If that doesnt work, I have to think on that option.

Share this post


Link to post
Share on other sites

I will keep the verify disk to my very last option.

...

Why? It's simple and doesn't take particularly long (it checks/repairs the file system's internal data structures, not every block on the device). If you click on the Verify Disk button in DiskUtility>First Aid for the volume it will check the disk's file system without attempting any repairs. Repair Disk will check the disk and attempt to repair its file system.

Share this post


Link to post
Share on other sites

Why? It's simple and doesn't take particularly long (it checks/repairs the file system's internal data structures, not every block on the device). If you click on the Verify Disk button in DiskUtility>First Aid for the volume it will check the disk's file system without attempting any repairs. Repair Disk will check the disk and attempt to repair its file system.

Yes it's simple... but check my comment:

 

"I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again..."

Share this post


Link to post
Share on other sites

I will keep the verify disk to my very last option.

 

Today I will:

 - Shutdown server where disk is;

 - Restart or even shutdown RAID Controller (The disk it self);

 - Propagate Permissions and ACLs on Server Admin for that Share (reminding that retro will backup all over again - the BUG)

 

If that doesnt work, I have to think on that option.

Uncheck:

post-8868-0-24027000-1377679032_thumb.png

post-8868-0-58427500-1377679042_thumb.png

 

Yes it's simple... but check my comment:

 

"I did that once and what i got was damaged disk, with read-only acess. I Don't risk do it again..."

Select "Verify", not "Repair", to avoid trying to make changes.

Also see my comment above.

Share this post


Link to post
Share on other sites

I've done it! One guy added a folder to this share without the right permissions... GRRRRRR

 

I Moved the folder to other side, and voilá!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×